Description of problem: After adding an IP address to a logical network, which has newly been added to an Interface (bond) the previously bound IP address to the formerly sole logical network vanished. Version-Release number of selected component (if applicable): Ovirt 4.2.4.5 CentOS Linux release 7.5.1804 (Core) How reproducible: 100% Steps to Reproduce: 1. Create a bond (bond0) 2. Assign logical network (non-VM) to bond (foo -> bond0) 3. Assign IP address to said logical network (10.10.10.10 -> foo) 4. Check with ip a, find bond0 has the 10.10.10.10, as no bridge has been deployed, all fine. 5. Add logical network (VM, vlan tagged) (bar -> bond0.10) 6. Bridge "bar" gets created, all fine so far 7. Assign an static IP address to the logical network (10.20.20.20 -> bar) Actual results: The new IP address gets set correctly to the bridge "bar", but the IP address from the former network "foo" is lost, as is the connectivity in case that network was needed. Expected results: Both IP addresses should be set correctly. Additional info: I added the ip manually to the bond0 on the host to get it back. After that an update/reinstall fixed the issue.
Would you please attach engine.log as well as supervdsm.log from the host during the time of the said setupNetwork operation? Please specify rpm versions of ovirt-engine and vdsm.rpm.
ovirt-engine-4.2.4.5-1.el7.noarch vdsm-4.20.35-1.el7.x86_64 The logs I can't provide due to privacy protection of our customers. If you can't reproduce the problem I might be able to clear the relevant information, but that's quite a task. Is there a script/tool to clear all those informations?
(In reply to Michael Waiblinger from comment #2) > ovirt-engine-4.2.4.5-1.el7.noarch > vdsm-4.20.35-1.el7.x86_64 > > The logs I can't provide due to privacy protection of our customers. If you > can't reproduce the problem I might be able to clear the relevant > information, but that's quite a task. Is there a script/tool to clear all > those informations? Please do that, we don't have a script for it. You can also share the log with privately and then only the oVirt devs will be able to see them.
Hi I can't reproduce the issue described above. I followed the steps as described. Both IPs set correctly.
Please reopen if you can provide the needed info. Closing for now.
I sent you the logs via email.
The exact way to reproduce this bug is : 1. Create a bond (bond0) 2. Attach non-VM network to the bond0 ('foo' -> bond0) and VM vlan tagged network ('bar' -> bond0.10) and assign IP address to the non-vm network (10.10.10.10 -> foo), now approve operation 3. Check with ip a, find bond0 has the 10.10.10.10 4. Edit the vlan tagged network 'bar' and set static IP address (10.20.20.20 -> bar) Result: The IP address 10.10.10.10 is gone from network 'foo' and it is now out-of-sync
Edy, I'm testing this bug on 4.2 u/s vdsm-4.20.43-4.gitb76af64.el7.x86_64 and i'm concern that this fix has created a new regression bug. My flow as described in comment#8 doesn't work as it should. 1. Create a bond (bond0) 2. Attach non-VM network to the bond0 ('foo' -> bond0) and VM vlan tagged network ('bar' -> bond0.10) and assign IP address to the non-vm network (10.10.10.10 -> foo), now approve operation 3. Check with ip a, find bond0 has the 10.10.10.10 - FAIL! Because the IP address doesn't applied on the non-VM network and reported as out-of-sync in the engine. No IP address on bond0. This wasn't the result before this fix. Please check this out
Ignore, i had an issue on one of my hosts. Verified upstream on - vdsm-4.20.43-4.gitb76af64.el7.x86_64 and 4.2.8-0.0.master.20181101130712.git326ea78.el7
INFO: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason: [Tag 'v4.20.44' doesn't contain patch 'https://gerrit.ovirt.org/94697'] gitweb: https://gerrit.ovirt.org/gitweb?p=vdsm.git;a=shortlog;h=refs/tags/v4.20.44 For more info please contact: infra
Missing patch is a test-only one. no need to backport it.
This bugzilla is included in oVirt 4.2.8 release, published on January 22nd 2019. Since the problem described in this bug report should be resolved in oVirt 4.2.8 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.