Description of problem: vdsm insert gaps in the ifcfg file for every network update. For every network update, for example MTU, vdsm insert new gap in the ifcfg file. After few updates, you will have a huge gap in the ifcfg file. For exmaple - [root@orchid-vds2 ~]# cat /etc/sysconfig/network-scripts/ifcfg-mb1 # Generated by VDSM version 4.19.17-1.el7ev DEVICE=mb1 TYPE=Bridge DELAY=0 STP=off ONBOOT=yes DEFROUTE=no NM_CONTROLLED=no IPV6INIT=no MTU=1500[root@orchid-vds2 ~]# # Generated by VDSM version 4.19.17-1.el7ev DEVICE=mb1 TYPE=Bridge DELAY=0 STP=off ONBOOT=yes DEFROUTE=no NM_CONTROLLED=no IPV6INIT=no MTU=1500 Version-Release number of selected component (if applicable): vdsm-4.19.18-1.el7ev.x86_64 4.1.3.2-0.1.el7 How reproducible: 100% Steps to Reproduce: 1. Attach network to host 2. Via 'Networks' tab update the network with custom MTU=9000 3. Update the network back to default MTU=1500 4. Continue steps 2 and 3 few times, update the network with MTU Actual results: Huge gap in the ifcfg-* file. For every MTU update, new gap line is added in the ifcfg file Expected results: No gaps should be generated by vdsm into the ifcfg files
INFO: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason: [Tag 'v4.19.21' doesn't contain patch 'https://gerrit.ovirt.org/78900'] gitweb: https://gerrit.ovirt.org/gitweb?p=vdsm.git;a=shortlog;h=refs/tags/v4.19.21 For more info please contact: infra
The patch is in the v4.19.21 tag and we've identified an issue with moving vdsm bugs to ON_QA on last build, the problem will be fixed by next build.
Verified on - vdsm-4.19.21-1.el7ev.x86_64