Difference between revisions of "ZenUp"

From Zenoss Wiki
Jump to: navigation, search
m (formatting)
m (Tagged "current" ZUP file and added release date.)
(32 intermediate revisions by 9 users not shown)
Line 1: Line 1:
 
==About Zenup==
 
==About Zenup==
 
Zenup is the new Zenoss patch manager.  New patches are provided for both the Core, and Commercial products at intervals that fix bugs which don't require large internal fixes in Zenoss.  Larger internal fixes will wait for a subsequent release.
 
Zenup is the new Zenoss patch manager.  New patches are provided for both the Core, and Commercial products at intervals that fix bugs which don't require large internal fixes in Zenoss.  Larger internal fixes will wait for a subsequent release.
 
You can see the patch level of your install with the following command:
 
  $ zenup status
 
  Home: /opt/zenoss
 
  Revision: 0
 
  Upgrading: 457
 
  Last Attempted Step: post/install_mibs
 
  Updated On: Wed Sep  9 14:23:06 2015
 
 
  
 
==Getting ZenUp and patches==
 
==Getting ZenUp and patches==
As the users listed below download the appropriate files for your version of RedHat/CentOS. You will need to download the ZenUp package and version-dependent Pristine Copy (used as a basis for patch calculations) and ZUP update file.
+
As the users listed below download the appropriate files for your version of RedHat/CentOS. You will need to download the ZenUp package and version-dependant Pristine Copy (used as a basis for patch calculations) and ZUP update file.
 
+
To see changes introduced by a ZenUp package, use the zenup command. For example:
+
 
+
<console>
+
$ ##i##zenup info --showall zenoss_core-4.2.5-SP457-zenup11.zup
+
$ ##i##zenup info --showall zenoss_core-4.2.5-SP457-zenup11.zup | grep +++
+
$ ##i##zenup info --showall zenoss_core-4.2.5-SP457-zenup11.zup  | egrep -A3 "^.ZEN-"
+
</console>
+
 
+
  
 
===Step 1===
 
===Step 1===
 
 
First download the ZenUp package as the root user:
 
First download the ZenUp package as the root user:
*Current ZenUp 1.1 [http://sourceforge.net/projects/zenoss/files/zenup-1.1/zenup-1.1.0.267.869d67a-1.el5.x86_64.rpm/download EL5] or [http://sourceforge.net/projects/zenoss/files/zenup-1.1/zenup-1.1.0.267.869d67a-1.el6.x86_64.rpm/download EL6]
+
 
*Old (use for 4.2.3 and 4.2.4) [http://wiki.zenoss.org/download/core/zenup/zenup-1.0.0.131-1.el5.x86_64.rpm EL5] or [http://wiki.zenoss.org/download/core/zenup/zenup-1.0.0.131-1.el6.x86_64.rpm EL6]
+
ZenUp: [http://wiki.zenoss.org/download/core/zenup/zenup-1.0.0.131-1.el5.x86_64.rpm EL5] or [http://wiki.zenoss.org/download/core/zenup/zenup-1.0.0.131-1.el6.x86_64.rpm EL6]
Note, you can check the version of zenoss you are using by going to '''Settings --> Versions'''
+
  
 
===Step 2===
 
===Step 2===
Now as the zenoss user download the Pristine Copy and ZUP update file relevant to your version of Zenoss:
+
Now as the zenoss user download the Pristine Copy and ZUP update file relevent to your version of Zenoss:
====Zenoss 4.2.5====
+
  
Note that the Zenoss updates page at SourceForge is at [http://sourceforge.net/projects/zenoss/files/zenoss-4.2/zenoss-4.2.5/updates Zenoss Updates]
+
====Zenoss 4.2.4====
 +
Pristine Copy: [http://wiki.zenoss.org/download/core/zenup/zenoss_core-4.2.4.el5-pristine.tgz EL5] or [http://wiki.zenoss.org/download/core/zenup/zenoss_core-4.2.4.el6-pristine.tgz EL6]
  
Pristine Copy: [http://sourceforge.net/projects/zenoss/files/zenoss-4.2/zenoss-4.2.5/updates/2014-08-06/zenoss_core-4.2.5-2108.el5-pristine-SP203.tgz/download EL5] or [http://sourceforge.net/projects/zenoss/files/zenoss-4.2/zenoss-4.2.5/updates/2014-08-06/zenoss_core-4.2.5-2108.el6-pristine-SP203.tgz/download EL6]
+
ZUP:
 +
*[http://sourceforge.net/projects/zenoss/files/zenoss-4.2/zenoss-4.2.4/updates/2013-11-21/zenoss_core-4.2.4-SP179.zup/download SP179 ZUP File] November 19, 2013 (Current)
 +
*[http://downloads.sourceforge.net/project/zenoss/zenoss-4.2/zenoss-4.2.4/updates/2013-11-13/zenoss_core-4.2.4-SP174.zup?r=http%3A%2F%2Fsourceforge.net%2Fprojects%2Fzenoss%2Ffiles%2Fzenoss-4.2%2Fzenoss-4.2.4%2Fupdates%2F2013-11-13%2F&ts=1384377260&use_mirror=softlayer-dal SP174 ZUP File] November 13, 2013
 +
'''this fixes the bug referenced below, if you installed SP154 or SP163, PLEASE UPGRADE IMMEDIATELY!'''
  
{{note}} use Zenup 1.1 above
+
'''Be Careful! SP174 has a new bug, when a network object is about to be removed a new function is called getMacAddressCache() that gives a NoneType attribute error, because of this objects can not be reclassified, deleted, and sometimes modeling. Confirmed as it was tested on clean Zenoss install also.'''
  
*[http://sourceforge.net/projects/zenoss/files/zenoss-4.2/zenoss-4.2.5/updates/2016-02-26/zenoss_core-4.2.5-SP671-zenup11.zup/download SP671 ZUP File] Feb 26, 2016  (USE ZENUP 1.1 ABOVE! - latest SUP as of April 25th, 2016)
+
'''Broken:'''
  
*[http://sourceforge.net/projects/zenoss/files/zenoss-4.2/zenoss-4.2.5/updates/2015-04-10/zenoss_core-4.2.5-SP457-zenup11.zup/download SP457 ZUP File] Apr 4, 2015  (USE ZENUP 1.1 ABOVE!)
+
SP163 October 29, 2013
  
*[http://sourceforge.net/projects/zenoss/files/zenoss-4.2/zenoss-4.2.5/updates/2014-08-06/zenoss_core-4.2.5-SP203-zenup11.zup/download SP203 ZUP File] Aug 6, 2014 (USE ZENUP 1.1 ABOVE!)
+
SP154 October 15, 2013
  
*[http://sourceforge.net/projects/zenoss/files/zenoss-4.2/zenoss-4.2.5/updates/2014-06-19/zenoss_core-4.2.5-SP167-zenup11.zup/download SP167 ZUP File] June 19, 2014 (USE ZENUP 1.1 ABOVE!)
+
{{note}} SP154 and SP163 are not cumulative and assume that you have SP71.
  
*[http://sourceforge.net/projects/zenoss/files/zenoss-4.2/zenoss-4.2.5/updates/2014-06-05/zenoss_core-4.2.5-SP150-zenup11.zup/download SP150 ZUP File] March 21, 2014 (USE ZENUP 1.1 ABOVE!)
 
 
*[http://sourceforge.net/projects/zenoss/files/zenoss-4.2/zenoss-4.2.5/updates/2014-05-22/zenoss_core-4.2.5-SP136.zup/download SP136 ZUP File] May 22, 2014
 
 
*[http://sourceforge.net/projects/zenoss/files/zenoss-4.2/zenoss-4.2.5/updates/2014-04-29/zenoss_core-4.2.5-SP105.zup/download SP105 ZUP File] April 29, 2014
 
 
====Zenoss 4.2.4====
 
Pristine Copy: [http://wiki.zenoss.org/download/core/zenup/zenoss_core-4.2.4.el5-pristine.tgz EL5] or [http://wiki.zenoss.org/download/core/zenup/zenoss_core-4.2.4.el6-pristine.tgz EL6]
 
 
ZUP: (Note, ZUPs are cumulative, you do not need to install each one in order)
 
*[http://sourceforge.net/projects/zenoss/files/zenoss-4.2/zenoss-4.2.4/updates/2014-04-03/zenoss_core-4.2.4-SP464.zup/download SP464 ZUP File] April 3, 2014 (Current)
 
*[http://sourceforge.net/projects/zenoss/files/zenoss-4.2/zenoss-4.2.4/updates/2014-03-21/zenoss_core-4.2.4-SP445.zup/download SP445 ZUP File] March 21, 2014
 
*[http://sourceforge.net/projects/zenoss/files/zenoss-4.2/zenoss-4.2.4/updates/2014-03-04/zenoss_core-4.2.4-SP409.zup/download SP409 ZUP File] March 4, 2014
 
*[http://sourceforge.net/projects/zenoss/files/zenoss-4.2/zenoss-4.2.4/updates/2014-02-26/zenoss_core-4.2.4-SP405.zup/download SP405 ZUP File] February 26, 2014
 
*[http://sourceforge.net/projects/zenoss/files/zenoss-4.2/zenoss-4.2.4/updates/2014-02-07/zenoss_core-4.2.4-SP383.zup/download SP383 ZUP File] February 7, 2014
 
*[http://sourceforge.net/projects/zenoss/files/zenoss-4.2/zenoss-4.2.4/updates/2014-01-23/zenoss_core-4.2.4-SP367.zup/download SP367 ZUP File] January 23, 2014
 
*[http://sourceforge.net/projects/zenoss/files/zenoss-4.2/zenoss-4.2.4/updates/2014-01-08/zenoss_core-4.2.4-SP336.zup/download SP336 ZUP File] January 8, 2014
 
 
'''Broken:'''
 
 
*SP174 November 13, 2013
 
*SP163 October 29, 2013
 
*SP154 October 15, 2013
 
 
{{note}} For more information see [https://jira.zenoss.com/browse/ZEN-8901 ZUP SP163 breaks zeneventd processing.], also confirmed for 154, and [http://community.zenoss.org/thread/20420 ZenUp patching and flapping_interval_seconds.][http://sourceforge.net/projects/zenoss/files/Documentation/zenoss-4.2.x-docs/zendocs-4.2.4/Zenoss_Core_Administration_02-102013-4.2-v07.pdf/download Zenoss Admin Guide.]
 
{{note}} For more information see [https://jira.zenoss.com/browse/ZEN-8901 ZUP SP163 breaks zeneventd processing.], also confirmed for 154, and [http://community.zenoss.org/thread/20420 ZenUp patching and flapping_interval_seconds.][http://sourceforge.net/projects/zenoss/files/Documentation/zenoss-4.2.x-docs/zendocs-4.2.4/Zenoss_Core_Administration_02-102013-4.2-v07.pdf/download Zenoss Admin Guide.]
  
 
Older:
 
Older:
 +
 
[http://wiki.zenoss.org/download/core/zenup/zenoss_core-4.2.4-SP71.zup SP71 ZUP File] August 28, 2013 (Historical)
 
[http://wiki.zenoss.org/download/core/zenup/zenoss_core-4.2.4-SP71.zup SP71 ZUP File] August 28, 2013 (Historical)
 +
 
[http://wiki.zenoss.org/download/core/zenup/zenoss_core-4.2.4-SP12.zup SP12 ZUP File] July 29, 2013 (Historical)
 
[http://wiki.zenoss.org/download/core/zenup/zenoss_core-4.2.4-SP12.zup SP12 ZUP File] July 29, 2013 (Historical)
 +
 
====Zenoss 4.2.3====
 
====Zenoss 4.2.3====
 
Pristine Copy: [http://wiki.zenoss.org/download/core/zenup/zenoss_core-4.2.3-pristine-el5-May17.tgz EL5] or [http://wiki.zenoss.org/download/core/zenup/zenoss_core-4.2.3-pristine-el6-May17.tgz EL6]
 
Pristine Copy: [http://wiki.zenoss.org/download/core/zenup/zenoss_core-4.2.3-pristine-el5-May17.tgz EL5] or [http://wiki.zenoss.org/download/core/zenup/zenoss_core-4.2.3-pristine-el6-May17.tgz EL6]
Line 101: Line 64:
 
* Install the ZenUp RPM (as root user)
 
* Install the ZenUp RPM (as root user)
 
<console># ##i##yum install zenup-XXX.rpm -y --nogpgcheck</console>
 
<console># ##i##yum install zenup-XXX.rpm -y --nogpgcheck</console>
* Create backup of Zenoss Directory (date here uses unix timestamp, to use another date format see 'man date')
+
* Create backup of Zenoss Directory
<console># ##i##tar --exclude backups --exclude perf --exclude log -czvf zenoss_core-4.2.X-SPXXX_backup.$(date +%s).tgz /opt/zenoss</console>
+
<console># ##i##tar --exclude backups --exclude perf --exclude log -czf zenoss_core-4.2.X-SPXXX_backup.[TIMESTAMP].tgz /opt/zenoss</console>
 
* Switch to the Zenoss User
 
* Switch to the Zenoss User
 
<console># ##i##su - zenoss</console>
 
<console># ##i##su - zenoss</console>
Line 111: Line 74:
 
* Examine differences between Zenoss Folder and a pristine installation (should always be 0 files)
 
* Examine differences between Zenoss Folder and a pristine installation (should always be 0 files)
 
<console>$ ##i##zenup diff</console>
 
<console>$ ##i##zenup diff</console>
* Test run of the patch install
+
* Test run of the patch install</console>
 
<console>$ ##i##zenup install zenoss_core-XXX.zup --dry-run</console>
 
<console>$ ##i##zenup install zenoss_core-XXX.zup --dry-run</console>
 
* Install the patch
 
* Install the patch

Revision as of 21:46, 2 January 2014

About Zenup

Zenup is the new Zenoss patch manager. New patches are provided for both the Core, and Commercial products at intervals that fix bugs which don't require large internal fixes in Zenoss. Larger internal fixes will wait for a subsequent release.

Getting ZenUp and patches

As the users listed below download the appropriate files for your version of RedHat/CentOS. You will need to download the ZenUp package and version-dependant Pristine Copy (used as a basis for patch calculations) and ZUP update file.

Step 1

First download the ZenUp package as the root user:

ZenUp: EL5 or EL6

Step 2

Now as the zenoss user download the Pristine Copy and ZUP update file relevent to your version of Zenoss:

Zenoss 4.2.4

Pristine Copy: EL5 or EL6

ZUP:

this fixes the bug referenced below, if you installed SP154 or SP163, PLEASE UPGRADE IMMEDIATELY!

Be Careful! SP174 has a new bug, when a network object is about to be removed a new function is called getMacAddressCache() that gives a NoneType attribute error, because of this objects can not be reclassified, deleted, and sometimes modeling. Confirmed as it was tested on clean Zenoss install also.

Broken:

SP163 October 29, 2013

SP154 October 15, 2013

Bulbgraph.png Note: SP154 and SP163 are not cumulative and assume that you have SP71.

Bulbgraph.png Note: For more information see ZUP SP163 breaks zeneventd processing., also confirmed for 154, and ZenUp patching and flapping_interval_seconds.Zenoss Admin Guide.

Older:

SP71 ZUP File August 28, 2013 (Historical)

SP12 ZUP File July 29, 2013 (Historical)

Zenoss 4.2.3

Pristine Copy: EL5 or EL6

ZUP:

SP254 ZUP File Aug 9, 2013 (Current)

Older:

SP248 ZUP File Aug 9, 2013 (Historical)

SP153 ZUP File (Historical)

Bulbgraph.png Note: SP153 is considered beta and probably should not be installed in production at all.

Reporting Bugs

To report ZenUp or RPS bugs, please use the process outlined in the Bug_FAQ. Note specifically the version of Zenoss, the version of ZenUp, and the specific RPS that you're applying in any bug reports you file against a system running ZenUp.

Using ZenUp to read a patch

To see the list of fixes in an RPS, run the following

$ zenup info zenoss_core-4.2.3-SP153.zup

Using ZenUp to apply a patch

  • Install the ZenUp RPM (as root user)
# yum install zenup-XXX.rpm -y --nogpgcheck
  • Create backup of Zenoss Directory
# tar --exclude backups --exclude perf --exclude log -czf zenoss_core-4.2.X-SPXXX_backup.[TIMESTAMP].tgz /opt/zenoss
  • Switch to the Zenoss User
# su - zenoss
  • Tell Zenup to manage Zenoss Patching
$ zenup init zenoss_core-XXX-pristine-XXX.tgz $ZENHOME
  • Confirm that Zenoss is managed by ZenUp
$ zenup status
  • Examine differences between Zenoss Folder and a pristine installation (should always be 0 files)
$ zenup diff
  • Test run of the patch install</console>
$ zenup install zenoss_core-XXX.zup --dry-run
  • Install the patch
$ zenup install zenoss_core-XXX.zup
  • This will show you're on the new RPS and will list all the fixes
$ zenup status --verbose
  • This should show 0 files modified since the patch. However if you have added any customised files yourself, they may show up here.
$ zenup diff

Troubleshooting

If you run:

$ zenup install --dry-run zenoss_core-4.2.4-SPXXX.zup

And get an error like:

Looking for new migrate scripts to load...
Traceback (most recent call last):
  File "/tmp/zenoss-core-4.2.4_he022p/new_zup/generate_script_list", line 116, in <module>
    generator.generate()
  File "/tmp/zenoss-core-4.2.4_he022p/new_zup/generate_script_list", line 50, in generate
    self._openStatusYaml()
  File "/tmp/zenoss-core-4.2.4_he022p/new_zup/generate_script_list", line 99, in _openStatusYaml
    self.statusYaml = yaml.load(fp)
  File "/opt/zenup/python/yaml/__init__.py", line 71, in load
    return loader.get_single_data()
  File "/opt/zenup/python/yaml/constructor.py", line 37, in get_single_data
    node = self.get_single_node()
  File "/opt/zenup/python/yaml/composer.py", line 43, in get_single_node
    event.start_mark)
yaml.composer.ComposerError: expected a single document in the stream
  in "/opt/zenup/var/status.yaml", line 2, column 1
but found another document
  in "/opt/zenup/var/status.yaml", line 22, column 1
ERROR: /tmp/zenoss-core-4.2.4_he022p/new_zup/check returned a non-zero exit code: 1.
No changes have been applied to your system

Edit your /opt/zenup/var/status.yaml file and remove the top section that references the older version:

---
!!map {
  ? !!str "created"
  : !!str "Tue Nov 12 08:07:07 2013",
  ? !!str "home"
  : !!str "/opt/zenoss",
  ? !!str "id_"
  : !!str "zenoss-core-4.2.3",
  ? !!str "lastupdate"
  : !!str "Tue Nov 12 08:07:07 2013",
  ? !!str "name"
  : !!str "zenoss-core-4.2.3",
  ? !!str "path"
  : !!str "/opt/zenup/var/zenoss-core-4.2.3",
  ? !!str "revision"
  : !!str "",
  ? !!str "verbose"
  : !!bool "false",
  ? !!str "zupfile"
  : !!str "",
}
---
!!map {
  ? !!str "created"
  : !!str "Thu Nov 14 08:51:55 2013",
  ? !!str "home"
  : !!str "/opt/zenoss",
  ? !!str "id_"
  : !!str "zenoss-core-4.2.4",
  ? !!str "lastupdate"
  : !!str "Thu Nov 14 08:51:55 2013",
  ? !!str "name"
  : !!str "zenoss-core-4.2.4",
  ? !!str "path"
  : !!str "/opt/zenup/var/zenoss-core-4.2.4",
  ? !!str "revision"
  : !!str "",
  ? !!str "verbose"
  : !!bool "false",
  ? !!str "zupfile"
  : !!str "",
}

Run the command again and it should succeed. This seems to happen when an in-place upgrade is performed and it does not clean up status.yaml properly.