--_000_D86C48DF8800164BBE50B87623F7AC9580A16459ln2wio001devtra_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I'm running into a problem with my upgrades to oVirt 3.5.3 and wanted to ch= eck if the following is a known issue. I have multiple vlan tagged interfaces configured. The files are being gen= erated as expected by vdsm. The vlan 108 interface below is used by the ovi= rtmgmt bridge. The uatdev_ben, bond0.192, dev_office, bond0.124 interface d= efinitions all have ONBOOT=3Dno. root@host> grep -i onboot ifcfg* | grep -v bak ifcfg-bond0:ONBOOT=3Dyes ifcfg-bond0.108:ONBOOT=3Dyes ifcfg-bond0.124:ONBOOT=3Dno ifcfg-bond0.192:ONBOOT=3Dno ifcfg-dev_office:ONBOOT=3Dno ifcfg-eth0:ONBOOT=3Dyes ifcfg-eth1:ONBOOT=3Dyes ifcfg-eth2:ONBOOT=3Dno ifcfg-eth3:ONBOOT=3Dno ifcfg-lo:ONBOOT=3Dyes ifcfg-ovirtmgmt:ONBOOT=3Dyes ifcfg-uatdev_ben:ONBOOT=3Dno The persistence configuration files are where they should be (I think): root@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, de= v_office, bond0.124 & bond0.192 are removed and then not restored as the "O= NBOOT=3Dno". 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 "v= dsm-tool restore-nets" to see if that would restore the interfaces but no j= oy. 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= =3Dyes" 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 --_000_D86C48DF8800164BBE50B87623F7AC9580A16459ln2wio001devtra_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
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 configu=
red. The files are being generated as expected by vdsm. The vlan 108 interf=
ace below is used by the ovirtmgmt bridge. The uatdev_ben, bond0.192, dev_o=
ffice, bond0.124 interface definitions
all have ONBOOT=3Dno.
root@host> grep -i o=
nboot ifcfg* | grep -v bak
ifcfg-bond0:ONBOOT=3Dye=
s
ifcfg-bond0.108:ONBOOT=
=3Dyes
ifcfg-bond0.124:ONBOOT=
=3Dno
ifcfg-bond0.192:ONBOOT=
=3Dno
ifcfg-dev_office:ONBOOT=
=3Dno
ifcfg-eth0:ONBOOT=3Dyes=
ifcfg-eth1:ONBOOT=3Dyes=
ifcfg-eth2:ONBOOT=3Dno<= o:p>
ifcfg-eth3:ONBOOT=3Dno<= o:p>
ifcfg-lo:ONBOOT=3Dyes
ifcfg-ovirtmgmt:ONBOOT=
=3Dyes
ifcfg-uatdev_ben:ONBOOT=
=3Dno
The persistence configuration files are where they s=
hould be (I think):
root@host> ls -l /va=
r/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 restartR=
21; on the node, the uatdev_ben, dev_office, bond0.124 & bond0.192 are =
removed and then not restored as the “ONBOOT=3Dno”. I assumed t=
hat 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 sh=
ould use to recover the missing interfaces? Should the ifcfg files all be c=
onfigured with “ONBOOT=3Dyes” just in case someone does run a &=
#8220;service network restart”?
My oVirt nodes are CentOS 6.5, I’m not using t=
he node iso.
Many thanks in advance for any assistance.
Regards,
Simon Barrett