| Summary: | Cannot add a rhev-h host to RHEV-M due to change in /etc/rhev-hypervisor-release file | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Mike Burns <mburns> | ||||
| Component: | rhev-hypervisor6 | Assignee: | Mike Burns <mburns> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | Virtualization Bugs <virt-bugs> | ||||
| Severity: | urgent | Docs Contact: | |||||
| Priority: | urgent | ||||||
| Version: | 6.3 | CC: | abaron, bazulay, cshao, danken, gouyang, iheim, leiwang, masayag, mburns, moli, ovirt-maint, ycui, ykaul | ||||
| Target Milestone: | beta | Keywords: | Regression | ||||
| Target Release: | 6.2 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2011-10-27 13:38:57 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
MainThread::ERROR::2011-10-26 23:08:23,219::deployUtil::785::root::makeBridge found existing bridge named: breth4
shows up only if fIsBridgeDevice and not fIsOvirt.
Could it be that os.path.exists('/etc/rhev-hypervisor-release') returns false?
Yes, it does it does. Rename from rhev-hypervisor to rhev-hypervisor6 had the unintended consequence of changing the file to /etc/rhev-hypervisor6-release. Moving to rhev-hypervisor6 component to be fixed. *** This bug has been marked as a duplicate of bug 748005 *** |
Created attachment 530402 [details] vdsm-reg.log Description of problem: Approval of RHEV-H hosts fail due to an inability to change the name of the breth0 bridge to rhevm. Version-Release number of selected component (if applicable): vdsm-4.9-110 How reproducible: Always Steps to Reproduce: 1.Install RHEV-H 2.Add to rhev-m either through RHEV-M Add Host or through RHEV-H TUI 3. Actual results: if RHEV-M add host, sits in pending when it should auto-approve if rhev-h tui, then fails to ever show up in rhev-m Expected results: add is completed successfully Additional info: