Date: Tue=2C 24 Sep 2013 13:28:26 +0100 From: danken@redhat.com To: cybertimber2000@hotmail.com CC: jbrooks@redhat.com=3B masayag@redhat.com=3B alonbl@redhat.com=3B us= ers@ovirt.org Subject: Re: [Users] Unable to finish AIO 3.3.0 - VDSM =20 =20 <snipped> =20 Here=2C Vdsm is trying to configure em1 with no ip address (because it found no ifcfg-em1 to begin with). But then=2C it fails to do so since NetworkManager is still running. =20 So if possible=2C make sure ifcfg-em1 exists (and has the correct BOOTPROT=3Ddhcp in it) and the NetworkManager is off before initiating installation. That's annoying=2C I know. It should be fix=2C for sure. = But currently it is a must. =20 Regards=2C Dan. Hopefully I didn't miss any other comments in that log snippet of log fil= e ^^=3B=3B It's good to know why it keeps failing. I'm just trying to figur= e > out how to move forward from here=2C and I'll take a crack at it this e= vening. I thought that NetworkManager only needs to be disabled if you are using = a static IP? I did try disabling NM before I realized it said only > > for = static and had a failure=2C but probably because of the interface/ifcfg iss= ue. I will try again this evening. =20 I'll try to jump into IRC by 5pm EDT if you happen to be around. =20 I did a mv /etc/sysconfig/network-scripts/ifcfg-enp4sp /etc/sysconfig/netwo= rk-scripts/ifcfg-em1=2C and then edited the file to say NAME=3D"em1" instea= d of NAME=3D"enp4s0"=2C even though ifconfig showed the "em1" interface alr= eady*. Rebooted and logged into the webadmin=2C reinstalled the VDSM host a= nd unchecked "configure firewall"=2C and VDSM came up. *It turns out that these interfaces (e.g. enp4s0) are called "aliases"=2C = so enp4s0 is em1 and apparently Fedora 19 is using it in some (but not all)= instances. Not sure what triggers it=2C but either creating the proper ifc= fg file=2C or moving/editing it to the correct interface name will help get=
--_5326598f-2da7-4968-9a83-e49ec223a451_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable things running. Thanks everyone! - Nick = --_5326598f-2da7-4968-9a83-e49ec223a451_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <html> <head> <style><!-- .hmmessage P { margin:0px=3B padding:0px } body.hmmessage { font-size: 12pt=3B font-family:Calibri } --></style></head> <body class=3D'hmmessage'><div dir=3D'ltr'>>=3B >=3B Date: Tue=2C 24 Se= p 2013 13:28:26 +0100<br>>=3B >=3B From: danken@redhat.com<br>>=3B &g= t=3B To: cybertimber2000@hotmail.com<br>>=3B >=3B CC: jbrooks@redhat.co= m=3B masayag@redhat.com=3B alonbl@redhat.com=3B users@ovirt.org<br>>=3B &= gt=3B Subject: Re: [Users] Unable to finish AIO 3.3.0 - VDSM<br>>=3B >= =3B <br>>=3B <br>>=3B <=3Bsnipped>=3B<br>>=3B >=3B <br>>=3B &= gt=3B Here=2C Vdsm is trying to configure em1 with no ip address (because i= t<br>>=3B >=3B found no ifcfg-em1 to begin with). But then=2C it fails = to do so since<br>>=3B >=3B NetworkManager is still running.<br>>=3B = >=3B <br>>=3B >=3B So if possible=2C make sure ifcfg-em1 exists (and = has the correct<br>>=3B >=3B BOOTPROT=3Ddhcp in it) and the NetworkMana= ger is off before initiating<br>>=3B >=3B installation. That's annoying= =2C I know. It should be fix=2C for sure. But<br>>=3B >=3B currently it= is a must.<br>>=3B >=3B <br>>=3B >=3B Regards=2C<br>>=3B >=3B = Dan.<br>>=3B Hopefully I didn't miss any other comments in that log snipp= et of log file ^^=3B=3B It's good to know why it keeps failing. I'm just tr= ying to figure >=3B out how to move forward from here=2C and I'll take a = crack at it this evening.<br>>=3B I thought that NetworkManager only need= s to be disabled if you are using a static IP? I did try disabling NM befor= e I realized it said only >=3B >=3B for static and had a failure=2C but= probably because of the interface/ifcfg issue. I will try again this eveni= ng.<br>>=3B <br>>=3B I'll try to jump into IRC by 5pm EDT if you happen= to be around.<br>>=3B <BR>I did a mv /etc/sysconfig/network-scripts/ifcf= g-enp4sp /etc/sysconfig/network-scripts/ifcfg-em1=2C and then edited the fi= le to say NAME=3D"em1" instead of NAME=3D"enp4s0"=2C even though ifconfig s= howed the "em1" interface already*. Rebooted and logged into the webadmin= =2C reinstalled the VDSM host and unchecked "configure firewall"=2C and VDS= M came up.<BR><div> =3B</div><div>*It turns out that these interfaces (= e.g. enp4s0) =3Bare called "aliases"=2C so enp4s0 is em1 and apparently= Fedora 19 is using it in some (but not all) instances. Not sure what trigg= ers it=2C but either creating the proper ifcfg file=2C or moving/editing it= to the correct interface name will help get things running.</div><div>&nbs= p=3B</div><div>Thanks everyone!</div><div> =3B</div><div>- Nick</div> = </div></body> </html>= --_5326598f-2da7-4968-9a83-e49ec223a451_--