<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>> > Date: Tue, 24 Sep 2013 13:28:26 +0100<br>> > From: danken@redhat.com<br>> > To: cybertimber2000@hotmail.com<br>> > CC: jbrooks@redhat.com; masayag@redhat.com; alonbl@redhat.com; users@ovirt.org<br>> > Subject: Re: [Users] Unable to finish AIO 3.3.0 - VDSM<br>> > <br>> <br>> <snipped><br>> > <br>> > Here, Vdsm is trying to configure em1 with no ip address (because it<br>> > found no ifcfg-em1 to begin with). But then, it fails to do so since<br>> > NetworkManager is still running.<br>> > <br>> > So if possible, make sure ifcfg-em1 exists (and has the correct<br>> > BOOTPROT=dhcp in it) and the NetworkManager is off before initiating<br>> > installation. That's annoying, I know. It should be fix, for sure. But<br>> > currently it is a must.<br>> > <br>> > Regards,<br>> > Dan.<br>> Hopefully I didn't miss any other comments in that log snippet of log file ^^;; It's good to know why it keeps failing. I'm just trying to figure > out how to move forward from here, and I'll take a crack at it this evening.<br>> 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, but probably because of the interface/ifcfg issue. I will try again this evening.<br>> <br>> I'll try to jump into IRC by 5pm EDT if you happen to be around.<br>> <BR>I did a mv /etc/sysconfig/network-scripts/ifcfg-enp4sp /etc/sysconfig/network-scripts/ifcfg-em1, and then edited the file to say NAME="em1" instead of NAME="enp4s0", even though ifconfig showed the "em1" interface already*. Rebooted and logged into the webadmin, reinstalled the VDSM host and unchecked "configure firewall", and VDSM came up.<BR><div> </div><div>*It turns out that these interfaces (e.g. enp4s0) are called "aliases", so enp4s0 is em1 and apparently Fedora 19 is using it in some (but not all) instances. Not sure what triggers it, but either creating the proper ifcfg file, or moving/editing it to the correct interface name will help get things running.</div><div> </div><div>Thanks everyone!</div><div> </div><div>- Nick</div> </div></body>
</html>