Many Thanks Pablo for the comments!
I have tested upgrade now couple of times in my Dev env; and like you said, it goes pretty nicely & straightforward.
The repos give me headache, since in our RHEL satellite; they have sync only on major level (RHEL 7/8 etc) ..
meaning that now when RHEL 8.5 >> Those binaries are the ones that come from there by default..and since 8.5 is not officially supported by PVC ...
Everything else seems to be working fine though, but Registering a Backup Node is not functioning for me. :(
Registration goes thru, but the added backup node health remains in "Pending" state. Same issue whether U try to add either Local or Remote backup node.
And when U try to export an image to that node ...python throws up quite decent amount of errors :( Examples below.
I believe it is some RHEL 8.4 / RHEL8 python3 incompatibility issue; but would need to have exact RHEL8.4 repo available on our Satellite to verify that...working on that now.. also having a Support case open regarding this.
2021-12-01 12:14:57.708 29636 ERROR cinder.api.middleware.fault [req-ef287956-f92b-471f-934f-2fb4d8d39437 0688b01e6439ca32d698d20789d52169126fb41fb1a4ddafcebb97d854e836c9 6c5014ffed2c45c182e643668fe17c04 - default default] Caught error: <class 'oslo_messaging.rpc.client.RemoteError'> Remote error: NoSuchMethod Endpoint does not support RPC method is_enough_space_available
['Traceback (most recent call last):\n', ' File "/usr/lib/python3.6/site-packages/oslo_messaging/rpc/server.py", line 165, in _process_incoming\n res = self.dispatcher.dispatch(message)\n', ' File "/usr/lib/python3.6/site-packages/oslo_messaging/rpc/dispatcher.py", line 318, in dispatch\n raise NoSuchMethod(method)\n', 'oslo_messaging.rpc.dispatcher.NoSuchMethod: Endpoint does not support RPC method is_enough_space_available\n'].: oslo_messaging.rpc.client.RemoteError: Remote error: NoSuchMethod Endpoint does not support RPC method is_enough_space_available
['Traceback (most recent call last):\n', ' File "/usr/lib/python3.6/site-packages/oslo_messaging/rpc/server.py", line 165, in _process_incoming\n res = self.dispatcher.dispatch(message)\n', ' File "/usr/lib/python3.6/site-packages/oslo_messaging/rpc/dispatcher.py", line 318, in dispatch\n raise NoSuchMethod(method)\n', 'oslo_messaging.rpc.dispatcher.NoSuchMethod: Endpoint does not support RPC method is_enough_space_available\n'].
2021-12-01 12:14:57.708 29636 ERROR cinder.api.middleware.fault Traceback (most recent call last):
2021-12-01 12:14:57.708 29636 ERROR cinder.api.middleware.fault File "/usr/lib/python3.6/site-packages/cinder/api/middleware/fault.py", line 84, in __call__
2021-12-01 12:14:57.708 29636 ERROR cinder.api.middleware.fault return req.get_response(self.application)
2021-12-01 12:14:57.708 29636 ERROR cinder.api.middleware.fault File "/usr/lib/python3.6/site-packages/webob/request.py", line 1314, in send
2021-12-01 12:14:57.708 29636 ERROR cinder.api.middleware.fault application, catch_exc_info=False)
2021-12-01 12:14:57.708 29636 ERROR cinder.api.middleware.fault File "/usr/lib/python3.6/site-packages/webob/request.py", line 1278, in call_application
2021-12-01 12:14:57.708 29636 ERROR cinder.api.middleware.fault app_iter = application(self.environ, start_response)
2021-12-01 12:14:57.708 29636 ERROR cinder.api.middleware.fault File "/usr/lib/python3.6/site-packages/webob/dec.py", line 143, in __call__
2021-12-01 12:14:57.708 29636 ERROR cinder.api.middleware.fault return resp(environ, start_response)
2021-12-01 12:14:57.708 29636 ERROR cinder.api.middleware.fault File "/usr/lib/python3.6/site-packages/webob/dec.py", line 129, in __call__
2021-12-01 12:14:57.708 29636 ERROR cinder.api.middleware.fault resp = self.call_func(req, *args, **kw)
2021-12-01 12:14:57.708 29636 ERROR cinder.api.middleware.fault File "/usr/lib/python3.6/site-packages/webob/dec.py", line 193, in call_func
------------------------------
Tommi Sihvo, Lead Service Architect
TietoEVRY, Compute Services
email
tommi.sihvo@tieto.com mobile +358 (0)40 5180 Finland
------------------------------
Original Message:
Sent: Wed December 01, 2021 10:51 AM
From: Pablo Pereira
Subject: Migration path from PowerVC 1.4.4 > 2.0.2
Hi Tommi;
Recently we've upgraded our powervc 1.4.4 installation. The procedure that we followed was
- Take backup from 1.4.4 system with special backup_n_uninstall_144.sh script
- Shut down of the 1.4.4 server.
- Create new RHEL8.4 node with the same ip and hostname of the original server;
- install PowerVC 2.0.0 there and latest available fixes.
- Restore backup taken from 1.4.4
- Check that everithing works fine.
- Take backup in PowerVC 2.0.0 system
- Uninstall Powervc 2.0.0 and install Powervc 2.0.2 and latest available fixes.
- Restore 2.0.0 backup to the 2.0.2
So far it is runing quite fine. You should be careful about the repositories that you need to enable on each PowerVC installation (it is well docummented on the migration procedure for each version. You also should be aware that at installation time you must configure a 1 node cluster for the 2.0.2 version (later you can add additional nodes). Nothing complicated but you need to think a little bit about cluster names and service ip.
Regards.
Pablo.
------------------------------
Pablo Pereira
Original Message:
Sent: Mon November 01, 2021 02:22 AM
From: Tommi Sihvo
Subject: Migration path from PowerVC 1.4.4 > 2.0.2
Thanks Jan! :)
Br,
tommi
------------------------------
Tommi Sihvo, Lead Service Architect
TietoEVRY, Compute Services
email tommi.sihvo@tieto.com mobile +358 (0)40 5180 Finland
Original Message:
Sent: Fri October 29, 2021 03:31 AM
From: Jan Hölscher
Subject: Migration path from PowerVC 1.4.4 > 2.0.2
Hi,
regarding to a recent case of PowerVC migration so short tips. I have started from unpatched 2.0.1 Version)
- iFixes of PowerVC 2.0.1 must be installed (see https://www.ibm.com/support/pages/node/6495087), i had an error restoring storage provider config without these fixes
- You must take an active backup of PowerVC 2.0.1 (
powervc-backup --active) - You need to activate Red Hat HA Repository on the new node
I hope this helps a liitle bit.
Reg.
Jan
------------------------------
Jan Hölscher
Original Message:
Sent: Thu October 28, 2021 08:59 AM
From: Tommi Sihvo
Subject: Migration path from PowerVC 1.4.4 > 2.0.2
Hi,
What are the best bractises / recommandations for migration path from pvc 144 > pvc 202?
Direct migration is not doable, if I have understood correctly?
So one needs go via 2.0.0 / 2.0.1, steps something like this.
- Take backup from 1.4.4 system with special backup_n_uninstall_144.sh script
- Create temporary RHEL8.4 node; install PowerVC 2.0.x there
< would plain 2.0.0 do ? or would the recommendation be to install 2.0.1? (and how about the iFixes..there is a bunch (>20) of those, are all these needed to be installed)?
- Take backup in PowerVC 2.0.0 / 2.0.1 system
- Install new fresh RHEL 8.4 node with PowerVC 2.0.2
- Restore 2.0.x backup to the 2.0.2 VM
> All Good
------------------------------
Tommi Sihvo, Lead Service Architect
TietoEVRY, Compute Services
email tommi.sihvo@tieto.com mobile +358 (0)40 5180 Finland
------------------------------
#PowerVC