On Fri, Sep 30, 2016 at 3:58 PM, knarra <knarra@redhat.com> wrote:
Hi,
I see below trace back in my vdsm.log. Can some one help me understand why these are logged?
is free, finding out if anyone is waiting for it. Thread-557::DEBUG::2016-09-30 18:20:25,064::resourceManager::661::Storage.ResourceManager::(releaseResource) No one is waiting for resource 'Storage.upgrade_57ee3a08-004b-02 7b-0395-0000000001d6', Clearing records. Thread-557::ERROR::2016-09-30 18:20:25,064::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
This means that the when an domain upgrade thread has finished, the spm was stopped. I'm seeing these errors from time to time on my development host using master. I don't think you should worry about them. Can you file a bug about this? we should clean this sometimes. Nir