| Summary: | SetupNetworks fails during host installation | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Moti Asayag <masayag> | ||||||
| Component: | ovirt-engine | Assignee: | Mike Kolesnik <mkolesni> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Martin Pavlik <mpavlik> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | high | ||||||||
| Version: | 3.3.0 | CC: | acathrow, alonbl, gklein, iheim, lpeer, Rhev-m-bugs, ybronhei, yeylon | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | 3.3.0 | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | network | ||||||||
| Fixed In Version: | is13 | Doc Type: | Bug Fix | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2014-01-21 22:18:52 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | Network | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Attachments: |
|
||||||||
Created attachment 788820 [details]
supervdsm log
A specific scenario should be tested with this fix: Installing ovirt-node-3.3 into a 3.2 cluster. In ovirt-node 3.3 the pre-created bridge devices (breth*) are no longer created. There is a need to assure the host deploy creates the management network as a bridge on that node. over automation 3.3 compatible rhev-h is not available yet verified, RHEV Hypervisor - 6.5 - 20130910.2.el6 (vdsm-4.12.0-127.gitedb88bf.el6ev) properly added in 3.2 cluster on is14 Closing - RHEV 3.3 Released Closing - RHEV 3.3 Released |
Created attachment 788819 [details] vdsm log Description of problem: On fresh rhel-6.4 installation, the setup networks fails since the supervdsm service isn't ready to accept requests. Version-Release number of selected component (if applicable): vdsm-4.10.2-23.0.el6ev.x86_64 How reproducible: not always. Steps to Reproduce: 1. Add new host to 3.2 cluster (the destination vdsm should be 3.2 as well) Actual results: Creating the management network using setupNetworks fails due to: AttributeError: 'ProxyCaller' object has no attribute 'setupNetworks' (the entire log is attached) Expected results: Management network should be installed properly on the host using setupNetworks. Additional info: The supervdsm service isn't ready to accept calls from the vdsm, as appear in the log. It seems the reattempt to send the setupNetworks should succeed.