Created attachment 609638 [details] log Description of problem: when a host becomes non-operational because it cannot access a domain, even log reports the event without the domain name. Host gold-vdsd cannot access one of the Storage Domains attached to it, or the Data Center object. Setting Host state to Non-Operational. Version-Release number of selected component (if applicable): si16 How reproducible: 100% Steps to Reproduce: 1. in a two hosts cluster block one of the domains in one of the hosts only 2. 3. Actual results: the following event is shown in the event log: Host gold-vdsd cannot access one of the Storage Domains attached to it, or the Data Center object. Setting Host state to Non-Operational. Expected results: we should specify the domain's name to allow better debugging by the user. Additional info: backend log is not much help as well and a separate bug is opened for backend log 2012-09-04 12:48:12,219 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStorageServerVDSCommand] (QuartzScheduler_Worker-45) [4e183cd4] START, ConnectStorageServerVDSCommand(vdsId = 8c289d3a-f4d7-11e1-8cda-001a4a169741, storageP oolId = f570527f-004a-4cab-8bee-129fa589bec5, storageType = ISCSI, connectionList = [{ id: bc1efcff-3f14-4502-9728-89fbc29e0100, connection: 10.35.64.10 };{ id: c5a034c9-db6e-4741-ac6e-b84495e7cc37, connection: 10.35.64.11 };{ id: ff668 0e9-2550-4a30-b947-1648617c62cc, connection: 10.35.160.7 };{ id: 6a41fd87-0726-43a3-9306-32fb3e241ed5, connection: 10.35.64.10 };{ id: bed3f09f-d7d4-4f8f-bcd6-e7f55df5be31, connection: 10.35.64.10 };]), log id: 3380e3f8 2012-09-04 12:48:13,390 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStorageServerVDSCommand] (QuartzScheduler_Worker-45) [4e183cd4] FINISH, ConnectStorageServerVDSCommand, return: {bc1efcff-3f14-4502-9728-89fbc29e0100=0, c5a 034c9-db6e-4741-ac6e-b84495e7cc37=0, ff6680e9-2550-4a30-b947-1648617c62cc=0, 6a41fd87-0726-43a3-9306-32fb3e241ed5=0, bed3f09f-d7d4-4f8f-bcd6-e7f55df5be31=465}, log id: 3380e3f8 2012-09-04 12:48:13,402 INFO [org.ovirt.engine.core.bll.storage.ISCSIStorageHelper] (QuartzScheduler_Worker-45) [4e183cd4] The lun with id HXT9pz-3stk-TPSL-Irup-5P31-887A-3AZMHm was reported as problematic ! 2012-09-04 12:48:13,436 ERROR [org.ovirt.engine.core.bll.storage.ISCSIStorageHelper] (QuartzScheduler_Worker-45) [4e183cd4] The connection with details 10.35.64.10 failed because of error code 465 and error message is: failed to setup i scsi subsystem 2012-09-04 12:48:13,436 INFO [org.ovirt.engine.core.bll.storage.ConnectHostToStoragePoolServersCommand] (QuartzScheduler_Worker-45) [4e183cd4] Host gold-vdsd storage connection was failed
http://gerrit.ovirt.org/#/c/8306/
Merged change-id I18abfa25c762a19bb65f65d62b310fe22bea1aaf
same error: Host gold-vdsd cannot access one of the Storage Domains attached to the Data Center TESTI. Setting Host state to Non-Operational.
http://gerrit.ovirt.org/#/c/8605/
Added a log entry before the one above which contains all the storage domains that had an error when connecting to
Merged Ib412608941f1223eb52bbde85ef7ece52c64ec0f
tested in si21.1 when the storage domain is created from one lun than we see the following error: Storage Domain testi-01 (Data Center iSCSI) was deactivated by system because it's not visible by any of the hosts. but when the storage was created from two different luns which are on different storages we do not see the storage name or the problematic lun (no other entry)i: Host gold-vdsc cannot access one of the Storage Domains attached to the Data Center iSCSI. Setting Host state to Non-Operational. moving back to devel
Created attachment 630886 [details] logs
Dafna, what's the difference between this and bug 854214?
these are two different flows. this one is for a problematic domain when all luns are invisible (I am testing with a domain with one lun on one server). in this case we would like to see the domain name (not just uuid) in event log. for bug 854214 its a problematic lun out of the domain. so i am testing with a domain with 2 luns on 2 storage servers when only one lun is invisible. in this case we would like to see both the domain name and the problematic lun in event log.
Please attach VDSM log too
(In reply to comment #13) > Please attach VDSM log too why do you need vdsm log ? this is a backend issue.
To determine the whole process and the error code sent from VDSM, the command which is called can be invoked from a lot of places, need to find the correct one
http://gerrit.ovirt.org/#/c/9399/
All events were correctly displayed regarding the specific storage domain
RHEV-M 3.5.0 has been released, closing this bug.