Bug 1116820
| Summary: | When setting a host to non-operational the problematic Storage domain is not indicated | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] oVirt | Reporter: | Kevin Alon Goldblatt <kgoldbla> | ||||
| Component: | ovirt-engine-core | Assignee: | Tal Nisan <tnisan> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Kevin Alon Goldblatt <kgoldbla> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 3.5 | CC: | acanan, amureini, bugs, gklein, iheim, rbalakri, tnisan, yeylon | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 3.5.0 | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | storage | ||||||
| Fixed In Version: | ovirt-3.5.0_rc2 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2014-10-17 12:27:27 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | Storage | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 1079583 | ||||||
| Attachments: |
|
||||||
Should be solved by the fix provide for bug 1079583 - moving to ON_QA to verify. Verified on: ovirt-engine-3.5.0-0.0.master.20140821064931.gitb794d66.el6.noarch vdsm-4.16.2-1.gite8cba75.el6.x86_64 I ran the same scenario again and the following message was reported in the engine log>>>>>>>>> 1. Create DC with cluster, host and storage domain (block) 2. Add 2nd host 3. Block connectivity to the second host with "iptables" >>>>> after several minutes the host is made 'non-operational' BUT instead of indicating the WHICH storage domain it cannot connect to the following error is reported: 2014-09-03 16:56:01,543 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (org.ovirt.thread.pool-8-thread-10) [5bd829d3] Correlation ID: 5bd829d3, Job ID: 01273d11-3fae-4d4b-bf24-b2ad759cd45a, Call Stack: null, Custom Event ID: -1, Message: Host nott-vds2 cannot access the Storage Domain(s) <UNKNOWN> attached to the Data Center dc_1. Setting Host state to Non-Operational. Setting to Assigned Tested with V3.5 vt4. The message is now correctly displayed indicating the problematic Storage Domain. Moving to Verified! Output from engine log: ---------------------------------- Custom Event ID: -1, Message: Host nott-vds2 cannot access the Storage Domain(s) blk1 attached to the Data Center data1. Setting Host state to Non-Operational. oVirt 3.5 has been released and should include the fix for this issue. |
Created attachment 916049 [details] vdsm and engine and server logs Description of problem: Version-Release number of selected component (if applicable): ovirt-engine-3.5.0-0.0.master.20140629172257.git0b16ed7.el6.noarch vdsm-4.16.0-3.git601f786.el6.x86_64 How reproducible: Every time Steps to Reproduce: 1. Create DC with cluster, host and storage domain (block) 2. Add 2nd host 3. Block connectivity to the second host with "iptables" >>>>> after several minutes the host is made 'non-operational' BUT instead of indicating the WHICH storage domain it cannot connect to the following error is reported: "Host nott-vds2.qa.lab.tlv.redhat.com cannot access the Storage Domain(s) Non interactive user attached to the Data Center dc_one. Setting Host state to Non-Operational." Actual results: The problematic Storage Domain in not indicated Expected results: Additional info: Fron engine.log >>>>>>>>>>>>>>>>>>>>>>>>>>>> 2014-07-07 12:29:57,121 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.IrsProxyData] (org.ovirt.thread.pool-8-thread-46) Removing vds [225e8db3-4361-45d7-a713-035e007ccfe1] from the domain in maintenance cache 2014-07-07 12:29:57,134 INFO [org.ovirt.engine.core.bll.SetNonOperationalVdsCommand] (org.ovirt.thread.pool-8-thread-14) [4b795e59] Running command: SetNonOperationalVdsCommand internal: true. Entities affected : ID: 225e8db3-4361-4 5d7-a713-035e007ccfe1 Type: VDS 2014-07-07 12:29:57,137 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (org.ovirt.thread.pool-8-thread-14) [4b795e59] START, SetVdsStatusVDSCommand(HostName = nott-vds2.qa.lab.tlv.redhat.com, HostId = 225e8db3-4361-45d 7-a713-035e007ccfe1, status=NonOperational, nonOperationalReason=STORAGE_DOMAIN_UNREACHABLE, stopSpmFailureLogged=false), log id: 47a22b90 2014-07-07 12:29:57,142 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (org.ovirt.thread.pool-8-thread-14) [4b795e59] FINISH, SetVdsStatusVDSCommand, log id: 47a22b90 2014-07-07 12:29:57,154 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (org.ovirt.thread.pool-8-thread-14) [4b795e59] Correlation ID: 4b795e59, Job ID: 33b41875-5037-4a4f-a8f1-39a289b69099, Call Stack: null, Custom Event ID: -1, Message: Host nott-vds2.qa.lab.tlv.redhat.com cannot access the Storage Domain(s) Non interactive user attached to the Data Center dc_one. Setting Host state to Non-Operational. 2014-07-07 12:30:00,009 INFO [org.ovirt.engine.core.bll.AutoRecoveryManager] (DefaultQuartzScheduler_Worker-59) Autorecovering 1 hosts