[ovirt-users] oVirt 3.5.3 and Network Unified Persistence issues?

[Ido Barkan]

Hi Simon.
In the meantime (until 3.5.4 is out) you can run "vdsm-tool
restore-nets --force" to solve this after "service network restart".
Vdsm will skip restoration if this was done since last boot. The
--force flags will skip this check.
Ido

On Tue, Aug 25, 2015 at 7:45 PM, Michael Burman <mburman at redhat.com> wrote:
> Hi Simon,
>
> This issue will be fixed on 3.5.4
> see - https://bugzilla.redhat.com/show_bug.cgi?id=1203422
>
> On 3.5.3, vdsm generating all ifcfg-* files to ONBOOT=NO by default, except the management network and the interface it is attached to. In your case bond (bond0,bond.108 and the slaves).
> - You can configure your ifcfg-* files manually to ONBOOT=yes and restart network service as a workaround for now.
>
> Kind regards,
> Michael B
>
> ----- Original Message -----
> From: "Simon Barrett" <Simon.Barrett at tradingscreen.com>
> To: users at ovirt.org
> Sent: Monday, August 24, 2015 5:01:45 PM
> Subject: [ovirt-users] oVirt 3.5.3 and Network Unified Persistence issues?
>
>
>
> I’m running into a problem with my upgrades to oVirt 3.5.3 and wanted to check if the following is a known issue.
>
>
>
> I have multiple vlan tagged interfaces configured. The files are being generated as expected by vdsm. The vlan 108 interface below is used by the ovirtmgmt bridge. The uatdev_ben, bond0.192, dev_office, bond0.124 interface definitions all have ONBOOT=no.
>
>
>
> root at host> grep -i onboot ifcfg* | grep -v bak
>
> ifcfg-bond0:ONBOOT=yes
>
> ifcfg-bond0.108:ONBOOT=yes
>
> ifcfg-bond0.124:ONBOOT=no
>
> ifcfg-bond0.192:ONBOOT=no
>
> ifcfg-dev_office:ONBOOT=no
>
> ifcfg-eth0:ONBOOT=yes
>
> ifcfg-eth1:ONBOOT=yes
>
> ifcfg-eth2:ONBOOT=no
>
> ifcfg-eth3:ONBOOT=no
>
> ifcfg-lo:ONBOOT=yes
>
> ifcfg-ovirtmgmt:ONBOOT=yes
>
> ifcfg-uatdev_ben:ONBOOT=no
>
>
>
> The persistence configuration files are where they should be (I think):
>
>
>
> root at host> ls -l /var/lib/vdsm/persistence/netconf/nets/
>
> total 12
>
> -rw-r--r-- 1 root root 121 Aug 24 22:44 dev_office
>
> -rw-r--r-- 1 root root 173 Aug 24 22:44 ovirtmgmt
>
> -rw-r--r-- 1 root root 121 Aug 24 22:44 uatdev_ben
>
>
>
> If I were to do a “service network restart” on the node, the uatdev_ben, dev_office, bond0.124 & bond0.192 are removed and then not restored as the “ONBOOT=no”. I assumed that vdsmd would re-create the dev_office and uatdev_ben interfaces so restarted vdsmd but they were not restored. I tried a “vdsm-tool restore-nets” to see if that would restore the interfaces but no joy.
>
>
>
> Am I missing something? Is there another method I should use to recover the missing interfaces? Should the ifcfg files all be configured with “ONBOOT=yes” just in case someone does run a “service network restart”?
>
>
>
> My oVirt nodes are CentOS 6.5, I’m not using the node iso.
>
>
>
> Many thanks in advance for any assistance.
>
>
>
> Regards,
>
>
>
> Simon Barrett
>
> _______________________________________________
> Users mailing list
> Users at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
> --
> Michael Burman
> RedHat Israel, RHEV-M QE Network Team
>
> Mobile: 054-5355725
> IRC: mburman
> _______________________________________________
> Users mailing list
> Users at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users



-- 
Thanks,
Ido Barkan