Bug 909174
| Summary: | [RHEVM] [backend] IP is not displayed in GUI if dhcp is used to obtain IP | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Martin Pavlik <mpavlik> | ||||||||||||
| Component: | ovirt-engine | Assignee: | Lior Vernia <lvernia> | ||||||||||||
| Status: | CLOSED WONTFIX | QA Contact: | Martin Pavlik <mpavlik> | ||||||||||||
| Severity: | medium | Docs Contact: | |||||||||||||
| Priority: | unspecified | ||||||||||||||
| Version: | 3.1.2 | CC: | acathrow, bazulay, dyasny, gklein, iheim, lpeer, masayag, myakove, Rhev-m-bugs, sgrinber, yeylon, ykaul | ||||||||||||
| Target Milestone: | --- | Keywords: | Regression | ||||||||||||
| 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 08:58:22 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: |
|
||||||||||||||
correction: Actual results: IP assigned to interface and NOT displayed in GUI Created attachment 695059 [details]
screenshot 1
it seems that IP is not displayed for any interface which is configured by DHCP. Logical Network/VLAN/Bridgeless Martin, Could you add vdsm.log and the output of 'vdsClient -s 0 getVdsCaps' so we can see the boot protocol is properly reported by vdsm ? Created attachment 698917 [details]
vdsm.log
Created attachment 698919 [details]
getVdsCaps
Created attachment 698920 [details]
sosreport-LogCollector-admin-20130218160340-066e.tar
(In reply to comment #5) > Martin, > > Could you add vdsm.log and the output of 'vdsClient -s 0 getVdsCaps' so we > can see the boot protocol is properly reported by vdsm ? all attached Martin, according to the screenshots of the logs and some testing I did on my environment, I suspect that the reason is that VDSM doesn't wait for the IP assignment before it returns from the setup networks command. To help me corroborate, may I ask you to please: 1. Reproduce the bug on your environment. 2. Put the host in maintenance and then activate it. 3. Move to a different subtab and then back to host network interfaces (to refresh display). 4. See if that indeed causes the IP address to be shown? Lior. (In reply to comment #10) > Martin, according to the screenshots of the logs and some testing I did on > my environment, I suspect that the reason is that VDSM doesn't wait for the > IP assignment before it returns from the setup networks command. > > To help me corroborate, may I ask you to please: > 1. Reproduce the bug on your environment. > 2. Put the host in maintenance and then activate it. > 3. Move to a different subtab and then back to host network interfaces (to > refresh display). > 4. See if that indeed causes the IP address to be shown? > > Lior. Yes, after step 3 IP is visible. So the problem is indeed that the engine doesn't wait for the DHCP to assign the IP address, and so the command finishes execution without having an IP address reported by VDSM. This is on purpose, because we don't want a holdup in the engine becuase of the DHCP, so it's not going to be fixed right now. There are two possible solutions in the future: 1. Most likely there will be a feature added to the engine to re-request host information from VDSM at will (perhaps by using the refresh button). Not sure if and when this will happen, but that should provide an adequate solution. 2. If we do decide in the future that we want to wait around for DHCP to finish assigning the IP address, then the VDSM allows that using a flag and it'll be a small fix on the engine side. |
Created attachment 695054 [details] sosreport-LogCollector-admin-20130208135410-3b4a.tar.xz Description of problem: IP is not displayed in GUI if dhcp is used on bridgeless interface (see screenshot) Version-Release number of selected component (if applicable): Red Hat Enterprise Virtualization Manager Version: 3.1.0-46.el6ev libvirt-0.10.2-18.el6.x86_64 qemu-img-rhev-0.12.1.2-2.348.el6.x86_64 vdsm-4.10.2-1.3.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1.create bridgeless network 2.assign the network to host and use DHCP for IP configuration Actual results: IP assigned to interface and displayed in GUI Expected results: IP assigned to interface and displayed in GUI Additional info: MainProcess|Thread-734::INFO::2013-02-08 13:04:59,041::configNetwork::899::root::(addNetwork) Adding network sw3 with vlan=None, bonding=None, nics=['em2'], bondingOptions=None, mtu=None, bridged=False, options={'bootproto': 'dhcp', 'implicitBonding': True} ifup-waiting-on-dhcp::DEBUG::2013-02-08 13:05:40,226::misc::83::Storage.Misc.excCmd::(<lambda>) SUCCESS: <err> = ''; <rc> = 0