Hi All,

vdsm version i am using is vdsm-4.18.13-1.el7ev.x86_64. I am trying to upgrade a RHV-H node from UI when i saw the following trace back in the vdsm log.

Thanks
kasturi

On 09/30/2016 06:28 PM, knarra 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
b38e7a14-f880-4259-a7dd-3994bae2dbc2::DEBUG::2016-09-30 18:20:25,065::__init__::398::IOProcessClient::(_startCommunication) Communication thread for client ioprocess-7 started ioprocess communication (22325)::INFO::2016-09-30 18:20:25,067::__init__::447::IOProcess::(_processLogs) Starting ioprocess ioprocess communication (22325)::INFO::2016-09-30 18:20:25,067::__init__::447::IOProcess::(_processLogs) Starting ioprocess

Thanks

kasturi

_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Reply via email to