Re: [Users] Unable to activate iSCSI domain after crash of host
If you do not have an iptables or any connectivity issue still existing
from the host to the storage than your host is not seeing any of the
devices on the storage
it might be a problem with access list (password or iqn) but the storage
is not exposing the luns to the host.
On 02/07/2014 09:29 AM, Gianluca Cecchi wrote:
On Fri, Feb 7, 2014 at 10:19 AM, Dafna Ron wrote:
> can you try to restart ovirt-engine as well?
> Also, can you run vdsClient -s 0 getDeviceList on the host?
restarted engine
[root@ovirt ovirt-engine]# systemctl status ovirt-engine
ovirt-engine.service - oVirt Engine
Loaded: loaded (/usr/lib/systemd/system/ovirt-engine.service; enabled)
Active: active (running) since Fri 2014-02-07 10:23:16 CET; 45s ago
Main PID: 18479 (ovirt-engine.py)
CGroup: name=systemd:/system/ovirt-engine.service
ââ18479 /usr/bin/python
/usr/share/ovirt-engine/services/ovirt-engine/ovirt-engine.py
--redirect-output start
ââ18499 ovirt-engine -server -XX:+TieredCompilation -Xms1g
-Xmx1g -XX:PermSize=256m -XX:MaxPermSize=256m
-Djava.net.preferIPv4Sta...
Feb 07 10:23:16 ovirt.localdomain.local systemd[1]: Started oVirt Engine.
On node
[root@ovnode03 192.168.230.101,3260]# vdsClient -s 0 getDeviceList
[]
[root@ovnode03 192.168.230.101,3260]#
engine.log here:
https://drive.google.com/file/d/0BwoPbcrMv8mvYjliV19JclZha3c/edit?usp=sha...
Thanks for viewing
Gianluca
--
Dafna Ron