Created attachment 1226821 [details] vdsm log Description of problem: When selecting a new host as SPM, in it's vdsm.log an Unhandled exception is raised from vdsm.log: Thread-1470::ERROR::2016-12-01 14:52:27,358::utils::375::Storage.StoragePool::(wrapper) Unhandled exception Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 372, in wrapper return f(*a, **kw) File "/usr/lib/python2.7/site-packages/vdsm/concurrent.py", line 177, in run return func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/storage/securable.py", line 78, in wrapper return method(self, *args, **kwargs) File "/usr/share/vdsm/storage/sp.py", line 207, in _upgradePoolDomain self._finalizePoolUpgradeIfNeeded() File "/usr/lib/python2.7/site-packages/vdsm/storage/securable.py", line 76, in wrapper raise SecureError("Secured object is not in safe state") SecureError: Secured object is not in safe state Version-Release number of selected component (if applicable): vdsm-4.18.17-1.el7ev.x86_64 ovirt-engine-4.0.6-0.1.el7ev.noarch How reproducible: 100% Steps to Reproduce: 1. Select new host as SPM 2. 3. Actual results: An Unhandled exception is raised in the elected host's logs Expected results: Additional info:
*** Bug 1400622 has been marked as a duplicate of this bug. ***
*** Bug 1381418 has been marked as a duplicate of this bug. ***
Tal, I found the root cause while looking a similar issue, so I sent a fix. I hope you don't mind taking your bug :-)
Fix merged upstream. Tal, do we want a backport to 4.1?
This is vdsm bug, not engine.
Nir, please backport to 4.1 as well
Patch backported, should be merged soon.
No response from Olimp after more then 2 weeks, removing the customer ticket since it is not related to this bug.
Verified with the following code: ----------------------------------- vdsm-4.19.11-1.el7ev.x86_64 ovirt-engine-4.1.2-0.1.el7.noarch rhevm-4.1.2-0.1.el7.noarch Verified with the following scenario: ---------------------------------------- 1. Select a new host as SPM >>>>> works fine and no error is reported in the vdsm log Moving to VERIFIED!