Thanks for the response. I looked at my install notes, and it should be in /root. I will try the install again to confirm though. I'm attaching the log from the previous attempt.
Subject: |
RE: Problem Upgrading from Zenoss 6.2.1 to 6.3.2 |
Author: |
Arthur |
Posted: |
2020-07-09 16:14 |
Hi Larry
I'm only aware of two possibilites to
alter an docker image.
1. Edit the docker file
I haven't seen any docker file for any Zenoss core_X.X
2. Build a new image form a running instance with the modification and then make it work for an update - I don't have this knowledge.
Possible choices are:
A)
As far as I have seen, an install error from a ZP during an update normally should not break the update. So reinstall it afer you have
installed the needed depencencies on the updated instance.
B)
Remove the ZP before update and then install the dependencies and ZP.
Can you tell me how you installed it on 6.2.1?
I would also confirm if you have the python jira library installed.
#serviced service attache zope
[root@bd49e0bfd48d /]# python
#import jira
SyntaxError: invalid syntax
>>> import jira
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
ImportError: No module named jira
>>>
## output means jira not installed
--------------
[root@centos74-test ~]# python
Python 2.7.5 (default, Aug 4 2017, 00:39:18)
[GCC 4.8.5 20150623 (Red Hat 4.8.5-16)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import jira
>>>
## output means jira installed
Have a good backup and do it on a test unit first!
Cheers
------------------------------
Arthur
------------------------------
Subject: |
RE: Problem Upgrading from Zenoss 6.2.1 to 6.3.2 |
Author: |
Larry |
Posted: |
2020-07-09 17:48 |
Hi Arthur,
Thanks for the response. I
mynew=python
serviced service shell -s $mynew -i zope
su - zenoss
pip install jira==2.0
exit
exit
serviced snapshot commit $mynew
serviced service restart Zenoss.core/zenoss
I see jira in the zope container if I'm the zenoss user (not as root though):
[root@vnoc-dev1-uet1b lschauer]# serviced service attach zope
[root@cff47e9b49d8 /]# su - zenoss
Last login: Thu Jul 9 21:37:07 UTC 2020
(zenoss) [zenoss@cff47e9b49d8 ~]$ pip list|grep jira
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
jira (2.0.0)
You are using pip version 9.0.1, however version 20.1.1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
(zenoss) [zenoss@cff47e9b49d8 ~]$
[root@cff47e9b49d8 /]# su - zenoss
Last login: Thu Jul 9 21:47:35 UTC 2020
(zenoss) [zenoss@cff47e9b49d8 ~]$ python
Python 2.7.10 (default, Apr 30 2020, 02:44:43)
[GCC 4.8.5 20150623 (Red Hat 4.8.5-39)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import jira
>>>
------------------------------
Larry
------------------------------
Subject: |
RE: Problem Upgrading from Zenoss 6.2.1 to 6.3.2 |
Author: |
Arthur |
Posted: |
2020-07-12 06:54 |
Hi Larry
After you installed the python jira library where you able to install your jira ZP now?
And where you able to do the upgrade now?
------------------------------
Arthur
------------------------------
Subject: |
RE: Problem Upgrading from Zenoss 6.2.1 to 6.3.2 |
Author: |
Larry |
Posted: |
2020-07-16 23:53 |
Hi Arthur,
Thanks for your message. Sorry for the delay in responding.
I'm not exactly sure what you mean about installing the python jira library. The library already existed for the zenoss user.
I took the path of uninstalling the Jira ZP. The install failed again, but this time it was because of the Linux and Windows ZPs (botocore mentioned). Logs are attached.
Thoughts?
Thanks,
------------------------------
Larry
------------------------------
Subject: |
RE: Problem Upgrading from Zenoss 6.2.1 to 6.3.2 |
Author: |
Larry |
Posted: |
2020-07-30 19:53 |
Hi Arthur,
Any ideas on how to proceed?
Thanks,
------------------------------
Larry
------------------------------
Subject: |
RE: Problem Upgrading from Zenoss 6.2.1 to 6.3.2 |
Author: |
Arthur |
Posted: |
2020-08-03 16:12 |
Larry: I'm not exactly sure what you mean about installing the python jira library. The library already existed for the zenoss user.
Arthur: As I see in your 5th response you installed the jira 2.0 library into the zope container. And that why it is there.
So I'm not sure when you did this. At least you should be able now to install your Jira ZP from my point of view.
Larry: I took the path of uninstalling the Jira ZP.
Arthur: OK
Larry: ImportError: No module named botocore
Arthur: Where are you running this Zenoss instance? VMWare, Amazone Web Service(AWS) etc?
Just found the following link:
https://github.com/cascadeo/ZenPacks.Cascadeo.ZenRDS
It looks like you have this ZP installed and it has the dependencie of the python boto library.
E
rror importing Boto module. This is a pre-requisite. ** Make sure that zenoss' python environment has access to the Boto library.Cheers
------------------------------
Arthur
------------------------------
Subject: |
RE: Problem Upgrading from Zenoss 6.2.1 to 6.3.2 |
Author: |
Larry |
Posted: |
2020-08-03 20:14 |
Hi Arthur,
Thanks for the response. To answer your questions:
Arthur: Where are you running this Zenoss instance? VMWare, Amazone Web Service(AWS) etc?Larry: AWS.
ZenRDS: I will try uninstalling it and running the upgrade again.
Error importing Boto module. This is a pre-requisite. ** Make sure that zenoss' python environment has access to the Boto library.Larry: It is installed before the upgrade is started. I don't know why the upgrade script can't see it. Is it using what's installed or a "clean" image?
Thanks,
------------------------------
Larry
------------------------------
Subject: |
RE: Problem Upgrading from Zenoss 6.2.1 to 6.3.2 |
Author: |
Arthur |
Posted: |
2020-08-07 10:45 |
Hi Larry
As far as I understand it, it uses a new image. So all changes which are not in special
DFS directory will be lost.
Cheers
------------------------------
Arthur
------------------------------
Subject: |
RE: Problem Upgrading from Zenoss 6.2.1 to 6.3.2 |
Author: |
Larry |
Posted: |
2020-08-07 23:50 |
Thanks Arthur. I found a third ZenPack which uses boto and uninstalled all three before the upgrade. And the upgrade worked!
However, I can't start Zenoss though. I get this error:
[root@hostname username]# serviced service start Zenoss.core/zenoss
facade: service is missing an address assignment
This also happened before the upgrade (after uninstalling a ZP). Rebooting the server would fix it though. Now it doesn't.
This command works and shows Zenoss as stopped:
[root@hostname username]# serviced service status Zenoss.core/zenoss
Any ideas?
Thanks,
------------------------------
Larry
------------------------------
Subject: |
RE: Problem Upgrading from Zenoss 6.2.1 to 6.3.2 |
Author: |
Arthur |
Posted: |
2020-08-08 11:28 |
Hi Larry
Often there is a IP assigned missing for a required service. Check out this
link.
Cheers
------------------------------
Arthur
------------------------------
Subject: |
RE: Problem Upgrading from Zenoss 6.2.1 to 6.3.2 |
Author: |
Larry |
Posted: |
2020-10-01 17:31 |
Hi Arthur,
Thanks for the latest tip! It worked!
The upgrade works for our DEV installation but fails on PROD. Some of the ZenPacks display a status of "missing" or "broken" after the upgrade. I'm trying to fix any data integrity issues first, as I think that might be the issue. I've used the Zenoss Toolkit a lot with Zenoss 4.2.5, but Zenoss 6 is a different story. I tried following this, but I don't think it worked:
https://help.zenoss.com/zsd/RM/updating-resource-manager-to-release-6-4-1/using-zenoss-toolbox/zenoss-toolbox-tools
Any help with running Zenoss Toolkit on 6.x would be greatly appreciated. I didn't find any other documentation about the toolkit for 6.x.
Thanks,
Larry
------------------------------
Larry
------------------------------
Subject: |
RE: Problem Upgrading from Zenoss 6.2.1 to 6.3.2 |
Author: |
Arthur |
Posted: |
2020-10-07 04:39 |
Hi Larry
I paste my tool box tool answer
here.
Cheers
------------------------------
Arthur
------------------------------