I've just tried to upgrade one of my Zenoss 4 test boxes from 4.1.70-1554 to 4.1.70-1562, but unfortunately got the following error:
jzen04 ~ $ rpm -Uvh zenoss-4.1.70-1562.el6.x86_64.rpm warning: zenoss-4.1.70-1562.el6.x86_64.rpm: Header V3 DSA/SHA1 Signature, key ID aa5a1ad7: NOKEY Preparing... ########################################### [100%] /var/tmp/rpm-tmp.FH6s8E: line 230: [: too many arguments ==================================================================== Unable to parse /opt/zenoss/etc/zope.conf for ZODB connection parameters. EC=101 See: /tmp/zodbchk.5564 Unable to check if this is a transaction history-keeping schema. Please contact support for details on how to test this manually and bypass this check. Do not attempt to upgrade until this has been properly investigated. ==================================================================== error: %pre(zenoss-4.1.70-1562.el6.x86_64) scriptlet failed, exit status 101 error: install: %pre scriptlet failed (2), skipping zenoss-4.1.70-1562.el6 jzen04 ~ $ more /tmp/zodbchk.5564 <relstorage> cache-servers 127.0.0.1:11211 cache-module-name memcache keep-history false %include zodb_db_main.conf </relstorage>
There is a /opt/zenoss/etc/zope.conf and Zenoss was down at the time. I'm assuming it is possible to upgrade from one beta version of Zenoss 4 to another. Is that correct?
If this is properly broken, then I'll log something in Jira.
I've heard from one of the Zenoss team on Jira that is it not possible to upgrade between different builds (1554, 1562) of the same version (4.1.70).
Fair enough, so will have to see if a zenbackup/restore works between builds, of failing that some temp Zenpacks.
The preferred option would actually be to use zenbatchdump/zenbatchload. Zenbatchdump exports a control file with the information of your devices, and zenbatchload reloads that into the product. With that solution, if there is any mysql change or something that would have required a migrate script, you'll work around the issue.
Any issues with that process, please open a ticket.
The problem with upgrading between the same Zenoss version (just different builds) is that it isn't an "upgrade" - in essence they are the same bits, but if say there was a migrate script, it would not run, as the Zenoss version didn't change.
Thanks, very useful to know. I'll give that a go in the next day or so.
I've just done a zenbackup/re-install/zenrestore which seemed to get most things. Though that did delete some of my customised modeler plugins.
If you have a moment, please open a ticket for the customised modeler plugins that were missed with as much detail as possible. Not sure that we can address it in time for the 4.2 release (pretty certain we cannot, actually) but we can review it at our defect review meeting and get it into the system.
actually it is possible
here is the jira:
it is about zope.conf parsing . (look in the above link to see how to comment and include statement and to insert the mysql db ones)
had done it 3 times (even the last time was without a single error) and everything seems working (however backup before)
Follow Us On Twitter »
||Latest from the Zenoss Blog »||Community||Products||Services||Customers||About Us|
Copyright © 2005-2011 Zenoss, Inc.