Bug 913155
| Summary: | [RHEVM] [vdsm-reg-setup] no rhevm bridge created when adding RHEVH host into RHEVM over VLAN | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Martin Pavlik <mpavlik> | ||||||
| Component: | vdsm | Assignee: | Igor Lvovsky <ilvovsky> | ||||||
| Status: | CLOSED WONTFIX | QA Contact: | Martin Pavlik <mpavlik> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 3.1.3 | CC: | abaron, bazulay, danken, gklein, hateya, iheim, lpeer, masayag, sgrinber, ykaul | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | 3.2.0 | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | network | ||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2013-02-28 09:26:05 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: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
Created attachment 700053 [details]
vdsm-reg.log
Are you sure that this has ever worked? In which version of vdsm? The deployUtil.py code expects to find a bridge at the tip of the host connection (ovirt node uses brethXX by default). If you are manually playing with ifcfg files, I'd expect that you add such a bridge on top of em1.172. (In reply to comment #3) > Are you sure that this has ever worked? In which version of vdsm? > > The deployUtil.py code expects to find a bridge at the tip of the host > connection (ovirt node uses brethXX by default). If you are manually playing > with ifcfg files, I'd expect that you add such a bridge on top of em1.172. I am not sure, it was an assumption made based on test case. In such case rhevm could mentioned that this is something what is not supported, that I should configure rhevm bridge myself. Same way as it does with bond that has no rhevm bridge on top. There is one more thing. If I do this with normal interface (rhevm bridge removed, ordinary interface configured in host). Host gets successfully added without rhevm bridge, but I can add it via Setup Networks. In case of VLAN this does not work. RHEVM complaints that he cannot assign rhevm interface. So probably the best way would be to fail such install and leave clear explanation in log. (In reply to comment #4) > (In reply to comment #3) > > Are you sure that this has ever worked? In which version of vdsm? > > I am not sure, it was an assumption made based on test case. Ok, I'm removing the Regression tag, as it should not be used excessively. (In reply to comment #0) > How reproducible: > 100% > > Steps to Reproduce: > 1. Install RHEVH host - do not add it into rhevm > 2. remove rhevm bridge > 3. configure interface em1 (see config files bellow) > 4. configure interface em1.172 (see config files bellow) > 5. dhclient -v on em1.172 > 6. add host to RHEVM over ip assigned on em1.172 > Playing with RHEV-H configuration is unsupported. You should only add VLAN from the TUI and then it's suppose to be configured correctly. RHEL hosts are different story, in the past I don't think there was a problem when the host had a VLAN configured, actually this is the requirement if you want to have VLAN on your rhevm network (the bootstrup did had issues with doing bridge over bond so in this case and only this case you needed to do this manually) Indeed, I do not see an urgent need to handle this use case. Hopefully, it would be automagically solved if and when alonbl rewrite the registration process. |
Created attachment 700052 [details] sosreport-LogCollector-admin-20130220152301-8fc3.tar.xz Description of problem: Cannot add new RHEVH host into setup over VLAN interface. Version-Release number of selected component (if applicable): Red Hat Enterprise Virtualization Manager Version: 3.1.0-46.el6ev vdsm-bootstrap-4.10.2-1.5.el6.noarch RHEVH 6.4 (20130214.0.el6) vdsm-4.10.2-1.5.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1. Install RHEVH host - do not add it into rhevm 2. remove rhevm bridge 3. configure interface em1 (see config files bellow) 4. configure interface em1.172 (see config files bellow) 5. dhclient -v on em1.172 6. add host to RHEVM over ip assigned on em1.172 Actual results: host gets added into RHEVM and goes non-operational because of Host dell-07 does not comply with the cluster AAAA networks, the following networks are missing on host: 'rhevm' rhevm bridge is not created on host Expected results: 14:20:15,728::deployUtil::898::root::_getOvirtBridgeParams Failed to get bridge data: MainThread::ERROR::2013-02-20 14:20:15,728::deployUtil::899::root::Traceback (most recent call last): File "/usr/share/vdsm-reg/deployUtil.py", line 894, in _getOvirtBridgeParams File "/usr/lib64/python2.6/site-packages/vdsm/netinfo.py", line 212, in getVlanBondingNic ValueError: unknown bridge em1.172 cat /etc/sysconfig/network-scripts/ifcfg-em1 NM_CONTROLLED="no" BOOTPROTO="none" DEVICE="em1" ONBOOT="yes" USERCTL=no cat /etc/sysconfig/network-scripts/ifcfg-em1.172 DEVICE=em1.172 VLAN=yes BOOTPROTO=dhcp NM_CONTROLLED=no [root@dell-r210ii-07 ~]# ip a l 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: p1p1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000 link/ether 90:e2:ba:04:29:88 brd ff:ff:ff:ff:ff:ff 3: p1p2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000 link/ether 90:e2:ba:04:29:89 brd ff:ff:ff:ff:ff:ff 4: em1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000 link/ether d0:67:e5:f0:82:44 brd ff:ff:ff:ff:ff:ff inet6 fe80::d267:e5ff:fef0:8244/64 scope link valid_lft forever preferred_lft forever 5: em2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000 link/ether d0:67:e5:f0:82:45 brd ff:ff:ff:ff:ff:ff 10: bond0: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noop state DOWN link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff 11: bond4: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noop state DOWN link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff 12: em1.172@em1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP link/ether d0:67:e5:f0:82:44 brd ff:ff:ff:ff:ff:ff inet 10.34.67.65/27 brd 10.34.67.95 scope global em1.172 inet6 fe80::d267:e5ff:fef0:8244/64 scope link valid_lft forever preferred_lft forever 14: bond1: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noop state DOWN link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff