![]() |
![]() |
Subject: | Upgrade to Zenoss 5.0.3 - Step 5 on upgrade guide...am I missing something?! |
Author: | [Not Specified] |
Posted: | 2015-07-21 08:18 |
Hi Zenoss community,
I was looking into upgrading our Zenoss 5.0.2 to Zenoss 5.0.4 but I have to go to 5.0.3 first (which is fine), however when I get to upgrading Zenoss core I am following this guide - http://www.zenoss.com/sites/default/files/documentation/Zenoss_Core_Upgr...
However I cannot see an upgrade script for 5.0.3 so when I run:
serviced script run /root/5.0.x/5.0.3-upgrade-core.txt \--service Zenoss.core
It understandably fails. Now that section of the guide says "This procedure describes how to upgrade Zenoss Core to 5.0.0, 5.0.1, or 5.0.2." but its under the how to to upgrade to 5.0.3 and yet I can't see anyway of actually updating. What am I missing
Subject: | please submit a P1 bug |
Author: | Andrew Kirch |
Posted: | 2015-07-21 14:04 |
please submit a P1 bug against Documentation on http://jira.zenoss.com
Andrew Kirch
akirch@gvit.com
Need Zenoss support, consulting or custom development Look no further. Email or PM me!
Ready for Distributed Topology (collectors) for Zenoss 5 Coming May 1st from GoVanguard
Subject: | Logged, cheers Andrew! |
Author: | [Not Specified] |
Posted: | 2015-07-22 04:57 |
Logged, cheers Andrew!
Glad its not just me missing something obvious
https://jira.zenoss.com/browse/ZEN-18869
Subject: | I am unsure about that step, |
Author: | [Not Specified] |
Posted: | 2015-07-27 07:34 |
I am unsure about that step, but i was already in 5.0.3 and i had issues upgrading to 5.0.4:
1) the path to the scripts had a "5.0" folder in between that did not exist, i had to move them there after creating it or they would fail
2) After migrating the docker partition to the new driver, it was EMPTY, so it had to download everything again (expected). What was NOT expected, was that my zenoss 5.0.4 was not fully there and could not start. I had to delete it, restore the 5.0.3 backup and re-upgrade
3) as with ALL THE OTHER UPGRADES, the sripts FAIL to find the CUSTOM zenpacks, so they are left in "missing" state. (Except the vmware esxi monitor one, that one is BROKEN)
EDIT: just noticed that the microsoft windows zenpack is not ok after the upgrade
Subject: | please submit a P1 Defect |
Author: | Andrew Kirch |
Posted: | 2015-07-27 08:50 |
please submit a P1 Defect (not a doc bug this time) on http://jira.zenoss.com
Andrew Kirch
akirch@gvit.com
Need Zenoss support, consulting or custom development Look no further. Email or PM me!
Ready for Distributed Topology (collectors) for Zenoss 5 Coming May 1st from GoVanguard
Subject: | I created this: |
Author: | [Not Specified] |
Posted: | 2015-07-27 10:00 |
I created this:
https://jira.zenoss.com/browse/ZEN-18937
hope it is ok
Subject: | Thanks! |
Author: | Andrew Kirch |
Posted: | 2015-07-29 08:56 |
Thanks!
Andrew Kirch
akirch@gvit.com
Need Zenoss support, consulting or custom development Look no further. Email or PM me!
Ready for Distributed Topology (collectors) for Zenoss 5 Coming May 1st from GoVanguard
< |
Previous Cannot model newly added decvices |
Next threshold of high utilization exceeded on lo interface |
> |