I had a catastrophic failure of the IB switch that was used by all my
storage domains. I had one data domain that was NFS and one that was
iSCSI. I managed to get the iSCSI LUN detached using the docs [1] but now I
noticed that somehow my master domain went from the NFS domain to the iSCSI
domain
I was able to get iSCSI over TCP working...but now the task of adding the
LUN to the GUI has been stuck at the spinning icon for about 20 minutes.
I see these entries in vdsm.log over and over with the Task value changing:
Thread-14::DEBUG::2014-10-21
John,
Thanks for reply. The Discover function in GUI works...it's once I try and
login (Click the array next to target) that things just hang indefinitely.
# iscsiadm -m session
tcp: [2] 10.0.0.10:3260,1
iqn.2014-04.edu.tamu.brazos.vmstore1:ovirt-data_iscsi
# iscsiadm -m node
10.0.0.10:3260,1
Trey,
The thread that keeps repeating is the call to repoStats. I believe
it's part of the storage monitoring and in my environment it repeats
every 15 seconds
Mine looks like
Thread-168::INFO::2014-10-21
15:02:42,616::logUtils::44::dispatcher::(wrapper) Run and protect:
repoStats(options=None)
John,
Thanks again for the reply. Yes the API at the path you mentioned shows
the domain. This has to have been a bug as things began working after I
changed values in the database. Somehow setting the new IP for the storage
connection in the database for both NFS and iSCSI resulted in the NFS
5 matches
Mail list logo