Re: [Users] Host cannot access storage domains

Dafna, you were right, it seems to be a caching issue. Rebooting the host did the job: Before Reboot: [root@host01 log]# vdsClient -s 0 getStorageDomainsList 52cf84ce-6eda-4337-8c94-491d94f5a18d f404398a-97f9-474c-af2c-e8887f53f688 7841a1c0-181a-4d43-9a25-b707accb5c4b [root@host02 log]# vdsClient -s 0 getStorageDomainsList 52cf84ce-6eda-4337-8c94-491d94f5a18d f404398a-97f9-474c-af2c-e8887f53f688 7841a1c0-181a-4d43-9a25-b707accb5c4b 925ee53a-69b5-440f-b145-138ada5b452e After Reboot: [root@host02 admin]# vdsClient -s 0 getStorageDomainsList 52cf84ce-6eda-4337-8c94-491d94f5a18d f404398a-97f9-474c-af2c-e8887f53f688 7841a1c0-181a-4d43-9a25-b707accb5c4b So now I have both hosts up and running but when I try to start a VM on the second host, I receive the following messages in the events pane: VM TEST2 was started by oliver.albl (Host: host02) VM TEST2 is down. Exit message: Child quit during startup handshake: Input/output error. Thanks again for your help! Oliver -----Ursprüngliche Nachricht----- Von: Dafna Ron [mailto:dron@redhat.com] Gesendet: Freitag, 03. Jänner 2014 14:22 An: Albl, Oliver Cc: users(a)ovirt.org Betreff: Re: [Users] Host cannot access storage domains yes, please attach the vdsm log also, can you run vdsClient 0 getStorageDomainsList and vdsClient 0 getDeviceList on both hosts? It might be a cache issue, so can you please restart the host and if it helps attach output before and after the reboot? Thanks, Dafna On 01/03/2014 01:12 PM, Albl, Oliver wrote: > Hi, > > I am starting with oVirt 3.3.2 and I have an issue adding a host to a > cluster. > > I am using oVirt Engine Version 3.3.2-1.el6 > > There is a cluster with one host (installed with oVirt Node - 3.0.3 - > 1.1.fc19 ISO image) up and running. > > I installed a second host using the same ISO image. > > I approved the host in the cluster. > > When I try to activate the second host, I receive the following > messages in the events pane: > > State was set to Up for host host02. > > Host host02 reports about one of the Active Storage Domains as > Problematic. > > Host host02 cannot access one of the Storage Domains attached to the > Data Center Test303. Stetting Host state to Non-Operational. > > Failed to connect Host host02 to Storage Pool Test303 > > There are 3 FC Storage Domains configured and visible to both hosts. > > multipath -ll shows all LUNs on both hosts. > > The engine.log reports the following about every five minutes: > > 2014-01-03 13:50:15,408 ERROR > [org.ovirt.engine.core.vdsbroker.irsbroker.IrsBrokerCommand] > (pool-6-thread-44) Domain 7841a1c0-181a-4d43-9a25-b707accb5c4b: > LUN_105 check timeot 69.7 is too big > > 2014-01-03 13:50:15,409 ERROR > [org.ovirt.engine.core.vdsbroker.irsbroker.IrsBrokerCommand] > (pool-6-thread-44) Domain 52cf84ce-6eda-4337-8c94-491d94f5a18d: > LUN_103 check timeot 59.6 is too big > > 2014-01-03 13:50:15,410 ERROR > [org.ovirt.engine.core.bll.InitVdsOnUpCommand] (pool-6-thread-44) > Storage Domain LUN_105 of pool Test303 is in problem in host host02 > > 2014-01-03 13:50:15,411 ERROR > [org.ovirt.engine.core.bll.InitVdsOnUpCommand] (pool-6-thread-44) > Storage Domain LUN_103 of pool Test030 is in problem in host host02 > > Please let me know if there are any log files I should attach. > > Thank you for your help! > > All the best, > > Oliver Albl > > > > _______________________________________________ > Users mailing list > Users(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/users -- Dafna Ron