
Dear All, After we updated our hypervisors to : vdsm-4.16.7-1.gitdb83943.el6.x86_64 vdsm-python-4.16.7-1.gitdb83943.el6.noarch vdsm-python-zombiereaper-4.16.7-1.gitdb83943.el6.noarch vdsm-xmlrpc-4.16.7-1.gitdb83943.el6.noarch vdsm-yajsonrpc-4.16.7-1.gitdb83943.el6.noarch vdsm-jsonrpc-4.16.7-1.gitdb83943.el6.noarch vdsm-cli-4.16.7-1.gitdb83943.el6.noarch We don't have access to our storage domain anymore. He jsut doesn't see the disks anymore... I added the vdsm log and engine log. I'm clueless... BEfore he did see the storage domains, now after the system update he doesn't anymore... Thanks in advance, Kind regards, Koen

Never mind. Installed a new updated brocade driver on the hypervisor, restarted the engine after after 10 minutes, the engine restored everything itself :-) 2014-12-04 9:04 GMT+01:00 Koen Vanoppen <vanoppen.koen@gmail.com>:
Dear All,
After we updated our hypervisors to : vdsm-4.16.7-1.gitdb83943.el6.x86_64 vdsm-python-4.16.7-1.gitdb83943.el6.noarch vdsm-python-zombiereaper-4.16.7-1.gitdb83943.el6.noarch vdsm-xmlrpc-4.16.7-1.gitdb83943.el6.noarch vdsm-yajsonrpc-4.16.7-1.gitdb83943.el6.noarch vdsm-jsonrpc-4.16.7-1.gitdb83943.el6.noarch vdsm-cli-4.16.7-1.gitdb83943.el6.noarch
We don't have access to our storage domain anymore. He jsut doesn't see the disks anymore...
I added the vdsm log and engine log. I'm clueless... BEfore he did see the storage domains, now after the system update he doesn't anymore...
Thanks in advance,
Kind regards, Koen
participants (1)
-
Koen Vanoppen