Bug 1412092
| Summary: | Hosts moving to connecting state if one of the servers in the DC is in non-responsive state | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Michael Burman <mburman> | ||||||
| Component: | BLL.Infra | Assignee: | Piotr Kliczewski <pkliczew> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Petr Matyáš <pmatyas> | ||||||
| Severity: | urgent | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | future | CC: | bugs, gklein, mperina, oourfali, pkliczew | ||||||
| Target Milestone: | ovirt-4.1.0-rc | Keywords: | Regression | ||||||
| Target Release: | 4.1.0 | Flags: | rule-engine:
ovirt-4.1+
rule-engine: blocker+ |
||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2017-02-01 14:59:03 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | Infra | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
Created attachment 1239365 [details]
new engine log
There is wrong version of the library used so changing the version. When I stop vdsm on one of the hosts (with PM) it stays in connecting for 60s and doesn't do anything to the other hosts. But after that, it goes to non responsive and isn't fenced, should I report this as a new bug or move this one to assigned? Petr fencing is not part of this patch. I suggest to open new BZ for it. In that case, verified on 4.1.0-8 |
Created attachment 1239364 [details] engine logs Description of problem: Hosts moving to connecting state if one of the servers in the DC is in non-responsive state Version-Release number of selected component (if applicable): 4.1.0-0.4.master.20170110134514.git1586fd4.el7.centos vdsm-4.19.1-26.gitc25fa08.el7.centos.x86_64 How reproducible: 100% Steps to Reproduce: 1. Have few hosts in a DC 2. Make one host non-responsive(stop vdsmd) or try to add host and fail 3. All servers and storage domain are going down, DC is down and all serves stuck in connecting state forever. Only engine restart make them come UP again.