oVirt 3.5.3 and Network Unified Persistence issues?
--_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 <html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr= osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:= //www.w3.org/TR/REC-html40"> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)"> <style><!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0cm; margin-bottom:.0001pt; font-size:11.0pt; font-family:"Calibri",sans-serif; mso-fareast-language:EN-US;} a:link, span.MsoHyperlink {mso-style-priority:99; color:#0563C1; text-decoration:underline;} a:visited, span.MsoHyperlinkFollowed {mso-style-priority:99; color:#954F72; text-decoration:underline;} span.EmailStyle17 {mso-style-type:personal-compose; font-family:"Calibri",sans-serif; color:windowtext;} .MsoChpDefault {mso-style-type:export-only; font-family:"Calibri",sans-serif; mso-fareast-language:EN-US;} @page WordSection1 {size:612.0pt 792.0pt; margin:72.0pt 72.0pt 72.0pt 72.0pt;} div.WordSection1 {page:WordSection1;} --></style><!--[if gte mso 9]><xml> <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" /> </xml><![endif]--><!--[if gte mso 9]><xml> <o:shapelayout v:ext=3D"edit"> <o:idmap v:ext=3D"edit" data=3D"1" /> </o:shapelayout></xml><![endif]--> </head> <body lang=3D"EN-GB" link=3D"#0563C1" vlink=3D"#954F72"> <div class=3D"WordSection1"> <p class=3D"MsoNormal">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.<o:p></o= :p></p> <p class=3D"MsoNormal"><o:p> </o:p></p> <p class=3D"MsoNormal">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.<o:p></o:p></p> <p class=3D"MsoNormal"><o:p> </o:p></p> <p class=3D"MsoNormal" style=3D"margin-left:36.0pt">root@host> grep -i o= nboot ifcfg* | grep -v bak<o:p></o:p></p> <p class=3D"MsoNormal" style=3D"margin-left:36.0pt">ifcfg-bond0:ONBOOT=3Dye= s<o:p></o:p></p> <p class=3D"MsoNormal" style=3D"margin-left:36.0pt">ifcfg-bond0.108:ONBOOT= =3Dyes<o:p></o:p></p> <p class=3D"MsoNormal" style=3D"margin-left:36.0pt">ifcfg-bond0.124:ONBOOT= =3Dno<o:p></o:p></p> <p class=3D"MsoNormal" style=3D"margin-left:36.0pt">ifcfg-bond0.192:ONBOOT= =3Dno<o:p></o:p></p> <p class=3D"MsoNormal" style=3D"margin-left:36.0pt">ifcfg-dev_office:ONBOOT= =3Dno<o:p></o:p></p> <p class=3D"MsoNormal" style=3D"margin-left:36.0pt">ifcfg-eth0:ONBOOT=3Dyes= <o:p></o:p></p> <p class=3D"MsoNormal" style=3D"margin-left:36.0pt">ifcfg-eth1:ONBOOT=3Dyes= <o:p></o:p></p> <p class=3D"MsoNormal" style=3D"margin-left:36.0pt">ifcfg-eth2:ONBOOT=3Dno<= o:p></o:p></p> <p class=3D"MsoNormal" style=3D"margin-left:36.0pt">ifcfg-eth3:ONBOOT=3Dno<= o:p></o:p></p> <p class=3D"MsoNormal" style=3D"margin-left:36.0pt">ifcfg-lo:ONBOOT=3Dyes<o= :p></o:p></p> <p class=3D"MsoNormal" style=3D"margin-left:36.0pt">ifcfg-ovirtmgmt:ONBOOT= =3Dyes<o:p></o:p></p> <p class=3D"MsoNormal" style=3D"margin-left:36.0pt">ifcfg-uatdev_ben:ONBOOT= =3Dno<o:p></o:p></p> <p class=3D"MsoNormal"><o:p> </o:p></p> <p class=3D"MsoNormal">The persistence configuration files are where they s= hould be (I think):<o:p></o:p></p> <p class=3D"MsoNormal"><o:p> </o:p></p> <p class=3D"MsoNormal" style=3D"margin-left:36.0pt">root@host> ls -l /va= r/lib/vdsm/persistence/netconf/nets/<o:p></o:p></p> <p class=3D"MsoNormal" style=3D"margin-left:36.0pt">total 12<o:p></o:p></p> <p class=3D"MsoNormal" style=3D"margin-left:36.0pt">-rw-r--r-- 1 root root = 121 Aug 24 22:44 dev_office<o:p></o:p></p> <p class=3D"MsoNormal" style=3D"margin-left:36.0pt">-rw-r--r-- 1 root root = 173 Aug 24 22:44 ovirtmgmt<o:p></o:p></p> <p class=3D"MsoNormal" style=3D"margin-left:36.0pt">-rw-r--r-- 1 root root = 121 Aug 24 22:44 uatdev_ben<o:p></o:p></p> <p class=3D"MsoNormal"><o:p> </o:p></p> <p class=3D"MsoNormal">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.= <o:p></o:p></p> <p class=3D"MsoNormal"><o:p> </o:p></p> <p class=3D"MsoNormal">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”?<o:p></o:p></p> <p class=3D"MsoNormal"><o:p> </o:p></p> <p class=3D"MsoNormal">My oVirt nodes are CentOS 6.5, I’m not using t= he node iso. <o:p> </o:p></p> <p class=3D"MsoNormal"><o:p> </o:p></p> <p class=3D"MsoNormal">Many thanks in advance for any assistance.<o:p></o:p=
</p> <p class=3D"MsoNormal"><o:p> </o:p></p> <p class=3D"MsoNormal">Regards,<o:p></o:p></p> <p class=3D"MsoNormal"><o:p> </o:p></p> <p class=3D"MsoNormal">Simon Barrett<o:p></o:p></p> </div> </body> </html>
--_000_D86C48DF8800164BBE50B87623F7AC9580A16459ln2wio001devtra_--
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@tradingscreen.com> To: users@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@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@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@ovirt.org http://lists.ovirt.org/mailman/listinfo/users -- Michael Burman RedHat Israel, RHEV-M QE Network Team Mobile: 054-5355725 IRC: mburman
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@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@tradingscreen.com> To: users@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@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@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@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@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- Thanks, Ido Barkan
Thanks for the info. Sadly, I'm seeing some inconsistency between different oVirt nodes as to how management interfaces are being handled. On one host, the ifcfg-bond0, ifcfg-eth0, ifcfg-eth1 interface files that the management interface is dependent on are being set with "ONBOOT=no". The --force on the restore-nets just re-instates those files with the incorrect "ONBOOT=no" configuration. On another host those same interfaces are left as ONBOOT=yes. I'm still trying to work out what the differences are between the two hosts. I was also looking to see if I could use vdsClient to manually add the config for ifcfg-bond0, ifcfg-eth0, ifcfg-eth1 so at least vdsm would know about them and apply the correct configuration. Not sure if this is a sensible approach or not. Thanks, Simon -----Original Message----- From: Ido Barkan [mailto:ibarkan@redhat.com] Sent: 01 September 2015 13:12 To: Michael Burman <mburman@redhat.com> Cc: Simon Barrett <Simon.Barrett@tradingscreen.com>; users@ovirt.org Subject: Re: [ovirt-users] oVirt 3.5.3 and Network Unified Persistence issues? 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@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@tradingscreen.com> To: users@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@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@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@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@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- Thanks, Ido Barkan
participants (3)
-
Ido Barkan -
Michael Burman -
Simon Barrett