Bug 1168723
| Summary: | After adding host rhev-hypervisor 7.0 to RHEVM 3.5, host change state to non-responsive | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Petr Kubica <pkubica> | ||||||
| Component: | rhev-hypervisor | Assignee: | Fabian Deutsch <fdeutsch> | ||||||
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Petr Kubica <pkubica> | ||||||
| Severity: | urgent | Docs Contact: | |||||||
| Priority: | urgent | ||||||||
| Version: | 3.5.0 | CC: | cshao, danken, dfediuck, ecohen, gklein, hadong, huiwa, iheim, leiwang, lsurette, pkubica, pstehlik, shihliu, yaniwang, ycui, yeylon | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | 3.5.0 | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | node | ||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2014-11-30 12:45:05 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | Node | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Bug Depends On: | |||||||||
| Bug Blocks: | 1094719 | ||||||||
| Attachments: |
|
||||||||
Created attachment 962162 [details]
vdsm-log
I saw this in the vdsm logs: MainThread::DEBUG::2014-11-27 15:48:04,660::libvirtconnection::143::root::(wrapper) Unknown libvirterror: ecode: 43 edom: 19 level: 2 message: Network not found: no network with matching name 'vdsm-rhevm' Dan, could this lead to connection issues? This bug can't reproduce every time. I try it as the following steps. it can't reproduce now. 1. when rhevh in non-responsive status,the bug can't reproduce after reboot it, rhevh can register to rhevm server successfully. 2. Reinstall the rhev-hypervisor7-7.0-20141119.0.el7ev on the same machine which occurred this problem, then registered it to rhevm-3.5.0-0.21.el6ev.noarch, it's success to register it to rhevm. 3.Install the same rhevh on another two machines, then register it to rhevm3.5. it also can't reproduce. (In reply to Fabian Deutsch from comment #7) > I saw this in the vdsm logs: > > MainThread::DEBUG::2014-11-27 > 15:48:04,660::libvirtconnection::143::root::(wrapper) Unknown libvirterror: > ecode: 43 edom: 19 level: 2 message: Network not found: no network with > matching name 'vdsm-rhevm' > > Dan, could this lead to connection issues? I don't think so. this log noise looks much more like bug 1121571 annoying false error when starting vdsmd Could you share connectivity.log from the host? I cannot reproduce with my step now, thought yesterday it happen to me with two rhev-h 7.0 machine. Now it seems, that everything working correctly with no error. Closing since no reproducer available (comment 8 and comment 10). Please re-open if there's a way to reproduce this issue. |
Created attachment 962161 [details] engine-log Description of problem: After adding host rhev-hypervisor 7.0 to RHEVM 3.5, host change state to non-responsive. Version-Release number of selected component (if applicable): RHEVM 3.5.0-0.21.el6ev RHEVH rhev-hypervisor7-7.0-20141120.1152948.3 How reproducible: Always Steps to Reproduce: 1. Install rhevm 3.5 2. Install host -> rhev-hypervisor7 3. Try to add host to engine Actual results: Host after sucessful install, changed state to non-responsive Additional info: attached engine logs and logs from rhev-h