Bug 1651499 - [clean-traffic-gateway filter] VM DHCP IP does not recover when network operation is done from Guest
Summary: [clean-traffic-gateway filter] VM DHCP IP does not recover when network opera...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Network
Version: 4.3.0
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Ales Musil
QA Contact: Michael Burman
URL:
Whiteboard:
Depends On: 1725166 1848971
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-11-20 08:44 UTC by Roni
Modified: 2022-03-22 13:18 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-12-25 10:33:36 UTC
oVirt Team: Network
Embargoed:
sbonazzo: ovirt-4.3-


Attachments (Terms of Use)
'systemctl restart network' error (7.03 KB, text/plain)
2018-11-20 08:44 UTC, Roni
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHV-45387 0 None None None 2022-03-22 13:18:13 UTC

Description Roni 2018-11-20 08:44:43 UTC
Created attachment 1507366 [details]
'systemctl restart network' error

Description of problem:
VMs with 'clean-traffic-gateway' filter will not recover their DHCP IP
when Network is restating from Guest, e.g.: 'systemctl restart network', ifdown | ifup to NIC, or reboot


Version-Release number of selected component (if applicable):
4.3.0-0.0.master.20181116185756.gite19db6e.el7

How reproducible:
100%

Steps to Reproduce:
1. Start two VMs
2. Run 'route -n' and then 'arp -an' to see their gateway MAC address
3. Add new vNIC profile
4. Choose: Network='ovirtmgmt', Network Filter='clean-traffic-gateway'
5. At both VMs: 
   Go to Compute | Virtual Machines | Click the VM name | 
   Network Interfaces tab | edit the NIC
   Change their profile to the newly created profile from section #3 above
   Add Network Filter Parameter GATEWAY_MAC=[GW NAC from section #2 above]
6. From Guest run: 
   6.1 'systemctl restart network', 
   6.2 'ifdown eth0| ifup eth0' 
   6.3 'reboot'

Actual results:
6.1: network restart does not perform, an error occurs, see attached error
6.2: NIC will be stopped successfully, but will not get an IP after start
6.3: NIC will not get the IP after boot

Expected results:
6.1: 'network' should restart successfully
6.2: NIC should start and NIC should get an IP from DHCP
6.3: NIC should get an IP from DHCP after boot


Additional info:
Note that IP is successfully recovered When unplug/plug the NIC, or when
shutdown & run VM from Engine WebUI

Comment 1 Dan Kenigsberg 2018-12-25 10:33:36 UTC
We are likely to address this only if it trouble real customer use cases.


Note You need to log in before you can comment on or make changes to this bug.