Bug 1097713
| Summary: | Can't register rhevh to rhevm 3.4 when using bond as rhevh network | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | wanghui <huiwa> | ||||
| Component: | vdsm | Assignee: | Douglas Schilling Landgraf <dougsland> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | Meni Yakove <myakove> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | unspecified | CC: | alonbl, bazulay, cshao, danken, fdeutsch, gklein, gouyang, guasun, hadong, hateya, huiwa, iheim, jboggs, leiwang, lpeer, pstehlik, rbarry, yaniwang, ycui, yeylon | ||||
| Target Milestone: | --- | Keywords: | TestBlocker, Triaged | ||||
| Target Release: | 3.4.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | network | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2014-05-14 20:31:18 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: |
|
||||||
Please ignore RHN info in bug description. invalid info of RHN in this bug. Ok, I can see in vdsm-reg.log: MainThread::DEBUG::2014-05-14 09:44:40,205::deployUtil::442::root::_getMGTIface: using host name 10.66.111.236 strIP= 10.66.111.236 MainThread::DEBUG::2014-05-14 09:44:40,205::deployUtil::449::root::_getMGTIface IP=10.66.111.236 strIface=bond5 MainThread::DEBUG::2014-05-14 09:44:40,205::deployUtil::1055::root::makeBridge found the following bridge paramaters: ['BONDING_OPTS=mode=balance-rr miimon=100', 'BOOTPROTO=dhcp', 'ONBOOT=yes', 'PEERDNS=no', 'PEERNTP=yes'] MainThread::ERROR::2014-05-14 09:44:40,207::deployUtil::982::root::_getRHELBridgeParams Found bonding: bond5.This network configuration is notsupported! Please configure rhevm bridgemanually and re-install. Hi Alon, if I recall correctly you worked on this/similar issue in the past. Any thought? Thanks! (In reply to Douglas Schilling Landgraf from comment #2) > > Hi Alon, if I recall correctly you worked on this/similar issue in the past. > Any thought? > > Thanks! This will be supported after we retire vdsm-reg. For now, perform the host-deploy initiated by engine in these cases, do not use the registration via the TUI. *** This bug has been marked as a duplicate of bug 994451 *** (In reply to Alon Bar-Lev from comment #3) > (In reply to Douglas Schilling Landgraf from comment #2) > > > > Hi Alon, if I recall correctly you worked on this/similar issue in the past. > > Any thought? > > > > Thanks! > > This will be supported after we retire vdsm-reg. > > For now, perform the host-deploy initiated by engine in these cases, do not > use the registration via the TUI. for host-deploy initiated by engine. adding rhevh host with bond network in rhevm admin portal still failed, the error info is the same as bug 1097818. |
Created attachment 895464 [details] vdsm-reg.log Description of problem: This issue can be triggered as follow steps. Frist, register to satellite. Second just select the RHN type without provide login and password. After step2, it will shows RHN as the current registration status. Version-Release number of selected component (if applicable): rhevh-6.5-20140513.1.el6ev.iso ovirt-node-plugin-vdsm-0.1.1-19.el6ev.noarch ovirt-node-3.0.1-18.el6_5.10.noarch Red Hat Enterprise Virtualization Manager Version: 3.4.0-0.20.el6ev How reproducible: 100% Steps to Reproduce: 1. Install rhevh-6.5-20140513.1.el6ev.iso 2. Create bond1 and enable it with ipv4 dhcp type. 3. Register to rhevm3.4.0-0.20.el6ev Actual results: 1. After step3, it can't register to rhevm av 9.1. And the vdsm-reg.log file reports error when makeBridge. Expected results: 1. After step3, it should can register to rhevm av. Additional info: