Bug 1369413
| Summary: | Add 3.6 host fails in rhv-m 3.6.8 from time to time and after few minutes it auto recovering and comes up | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [oVirt] vdsm-jsonrpc-java | Reporter: | Michael Burman <mburman> | ||||||
| Component: | General | Assignee: | Piotr Kliczewski <pkliczew> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Michael Burman <mburman> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | --- | CC: | bazulay, bugs, gklein, lsurette, mburman, mperina, oourfali, pkliczew, Rhev-m-bugs, ykaul | ||||||
| Target Milestone: | ovirt-4.1.0-alpha | Flags: | rule-engine:
ovirt-4.1+
rule-engine: planning_ack+ mperina: devel_ack+ pstehlik: testing_ack+ |
||||||
| Target Release: | --- | ||||||||
| 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-15 15:06:34 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: |
|
||||||||
After discussion with Piotr we agreed that it's real corner case and it doesn't cause any "real" harm, so I'm retargeting to 4.1. But of course if really needed we can backport. Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone. Hi On what version this should be tested? This bug was reported against 3.6.x versions..so i'm not sure on what versions we want to test this bug. I see it targeted for 4.1.. Please verify this BZ in 4.1 (In reply to Piotr Kliczewski from comment #9) > Please verify this BZ in 4.1 Ok, so just to clarify, test it with engine 4.1, but what host and cluster? Should it be host 3.6 in cluster 3.6 or host 4.1 in cluster 4.1? this is quite confusing. The bug was in the engine so it should be transparent which host should be used. Piotr, i can't test or verify this bug. Add host failing all the time on 4.1 upstream - 4.1.0-0.4.master.20170110134514.git1586fd4.el7.centos I don't know if it's related to this bug, but it blocking from testing it. Attaching logs. Created attachment 1239842 [details]
add_host_failed_logs
Michal, Which jsonrpc are you using? Please make sure you are using 1.3.6 when using 4.1. I am about to fix the regression on master. You are right, i was using the broken jsonrpc version. Verified on - 4.1.0-0.4.master.20170112090858.git916b67a.el7.centos with vdsm-jsonrpc-java-1.3.6-1.20170111073901.gita5e600c.el7.centos.noarch vdsm-4.19.1-29.git40ed539.el7.centos.x86_64 |
Created attachment 1193301 [details] Logs Description of problem: Add 3.6 host fails in rhv-m 3.6.8 from time to time and after few minutes it auto recovering and comes up 2016-08-23 13:50:47,017 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand] (org.ovirt.thread.pool-6-thread-2) [7fec9d5b] Error: VDSGenericException: VDSNetworkException: Waiting for conn ect interrupted 2016-08-23 13:50:47,017 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand] (org.ovirt.thread.pool-6-thread-2) [7fec9d5b] Exception: org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkEx ception: VDSGenericException: VDSNetworkException: Waiting for connect interrupted Version-Release number of selected component (if applicable): rhevm-3.6.8.1-0.1.el6.noarch vdsm-4.17.33-1.el7ev.noarch How reproducible: from time to time Steps to Reproduce: 1. Add 3.6 host(vdsm-4.17.33-1.el7ev.noarch) to rhv-m 3.6.8 Actual results: Sometimes add host fails and auto recovering after few minutes Expected results: Should work as expected.