<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>
<br> <BR><div id="SkyDrivePlaceholder"></div><div>> Date: Tue, 8 May 2012 11:11:36 +0300<br>> From: dfediuck@redhat.com<br>> To: cybertimber2000@hotmail.com<br>> CC: mburns@redhat.com; users@ovirt.org<br>> Subject: Re: [Users] Adding oVirt Node Fails<br>> <br>> On 08/05/12 06:06, Nicholas Kesick wrote:<br>> > Results of testing, round 3 (trying to get [Errno 16] Device or resource busy '/etc/pki/vdsm/certs/cacert.pem' error.)<br>> > Variable: no symlink to /etc/system-release<br>> > <br>> > I started with a reinstall of ovirt-engine and ovirt-node-2.3.0 (formatted drive, reinstalled), enabled network (via logical network breth0 through device eth0), and set the Ovirt Engine Admin Password on the node.<br>> > Created a new host in ovirt-manager, host went to "Pending Approval".<br>> > On the manager, clicked the host, clicked approve, and clicked ok (on power management warning)<br>> > And.... we passed the cert install! And everything worked up until I hit the cpuFlags issue.<br>> > <br>> > So... it wasn't the sym-link. Borked install? I guess the only think I did different these times from before was I used a Fedora 16 disk to format the drive between each attempt, instead of using the ovirt-node disk and performing a reinstall, as well as rebuilding ovirt-manager.<br>> > <br>> > Not sure where this leaves this topic. Seems I can properly add a node now without a cert or bridge renaming issue.<br>> > - Nick<br>> <br>> Nick,<br>> Thanks for taking the time to do this.<br>> Can you just verify you used the same ovirt-node ISO for all your tests?<br>> <br>> </div><div>Confirmed, I used the same ovirt-node ISO for all of my tests.</div><div>The ISO was extracted to a 4GB USB flash drive and installed from it.</div><div> </div><div>- Nick</div><div><br>> > ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------!<br>> ---<br>> > From: cybertimber2000@hotmail.com<br>> > To: dfediuck@redhat.com; mburns@redhat.com<br>> > Date: Mon, 7 May 2012 18:53:39 -0400<br>> > CC: users@ovirt.org<br>> > Subject: Re: [Users] Adding oVirt Node Fails<br>> > <br>> > Results of testing, round 2 (trying to get [Errno 16] Device or resource busy '/etc/pki/vdsm/certs/cacert.pem' error.)<br>> > <br>> > Again, I started with a reinstall of ovirt-engine and ovirt-node-2.3.0 (formatted drive with F16 disk, reinstalled), enabled network (logical = breth0, device = eth0). <br>> > This time, I set the management server (by IP address and default port), with the [*] Connect to oVirt Engine and Validate Certificate set, and entered the oVirt Engine Admin Password. <br>> > Ovirt prompts to confirm fingerprint, accepted. (quickly a message about pki and "persisted" appears on screen).<br>> > Created a new host in ovirt-manager, host went to "Pending Approval".<br>> > On the node shell, performed "ln -s /etc/system-release /etc/rhev-hypervisor-release" ((note: not sure this make an effect yet, I think it's the validating certificate part, but did so that only ONE thing changed between first and second test.))<br>> > On the manager, clicked the host, clicked approve, and clicked ok (on power management warning)<br>> > Ended at missing cpuFlags.<br>> > <br>> > So we are at the same point as before, which means my idea on what caused it (validate certificate) didn't cause it. Now for testing without the sym-link that Doron suggested.<br>> > <br>> > - Nick<br>> > <br>> > ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------!<br>> ---<br>> > From: cybertimber2000@hotmail.com<br>> > To: dfediuck@redhat.com; mburns@redhat.com<br>> > Date: Mon, 7 May 2012 18:32:34 -0400<br>> > CC: users@ovirt.org<br>> > Subject: Re: [Users] Adding oVirt Node Fails<br>> > <br>> > Ok so here is the results of testing:<br>> > I started with a reinstall of ovirt-engine and ovirt-node-2.3.0 (formatted drive, reinstalled), enabled network (via logical network breth0 through device eth0), and set the Ovirt Engine Admin Password on the node. Created a new host in ovirt-manager, host went to "Pending Approval".<br>> > On the node shell, performed "ln -s /etc/system-release /etc/rhev-hypervisor-release"<br>> > On the manager, clicked the host, clicked approve, and clicked ok (on power management warning)<br>> > Ended at missing cpuFlags.<br>> > <br>> > SO: We are at the same point that I was at with the plain Fedora16 + VDSM install, which is good. No issue with failing to install the cert! <br>> > <br>> > But I think I know what has been causing the OSError: [Errno 16] Device or resource busy '/etc/pki/vdsm/certs/cacert.pem' error.<br>> > Working through that now, will post the step by step when I have it.<br>> > <br>> > - Nick<br>> > <br>> >> To: mburns@redhat.com; abaron@redhat.com; cybertimber2000@hotmail.com<br>> >> From: dfediuck@redhat.com<br>> >> CC: users@ovirt.org<br>> >> Date: Mon, 7 May 2012 17:28:20 -0400<br>> >> Subject: Re: [Users] Adding oVirt Node Fails<br>> >><br>> >> Nicholas,<br>> >> The code I saw is testing for this file to verify it's a nods platform,<br>> >> and if it's missing the behaviour changes. So the code will try to<br>> >> unlink the file, which will give<br>> >> you this result in a mounted file.<br>> >><br>> >> Sent from my Android phone. Please ignore typos.<br>> >><br>> >> -----Original Message-----<br>> >> From: Nicholas Kesick [cybertimber2000@hotmail.com]<br>> >> Received: Tuesday, 08 May 2012, 0:08<br>> >> To: mburns@redhat.com, abaron@redhat.com<br>> >> CC: oVirt Mailing List [users@ovirt.org]<br>> >> Subject: Re: [Users] Adding oVirt Node Fails<br>> >><br>> >><br>> >> Ayal, did you see something in the code that made you want me to try the sym-link to /etc/rhev-hypervisor-release?Mike, is there any harm in linking it? - Nick<br>> >> > Subject: Re: [Users] Adding oVirt Node Fails<br>> >> > From: mburns@redhat.com<br>> >> > To: abaron@redhat.com<br>> >> > CC: cybertimber2000@hotmail.com; users@ovirt.org<br>> >> > Date: Sun, 6 May 2012 21:26:08 -0400<br>> >> ><br>> >> > On Sat, 2012-05-05 at 16:39 -0400, Ayal Baron wrote:<br>> >> > ><br>> >> > > ----- Original Message -----<br>> >> > > ><br>> >> > > ><br>> >> > > > > Date: Sat, 5 May 2012 12:29:20 +0300<br>> >> > > > > From: dfediuck@redhat.com<br>> >> > > > > To: cybertimber2000@hotmail.com<br>> >> > > > > CC: mburns@redhat.com; users@ovirt.org<br>> >> > > > > Subject: Re: [Users] Adding oVirt Node Fails<br>> >> > > > ><br>> >> > > > > On 04/05/12 02:49, Nicholas Kesick wrote:<br>> >> > > > > > Fri, 27 Apr 2012 05:22:24 DEBUG instCert: try to delete old<br>> >> > > > > > certificates<br>> >> > > > > > Fri, 27 Apr 2012 05:22:24 DEBUG instCert: failed.<br>> >> > > > > > Traceback (most recent call last):<br>> >> > > > > > File "/usr/share/vdsm-reg/deployUtil.py", line 1133, in instCert<br>> >> > > > > > File "/usr/share/vdsm-reg/deployUtil.py", line 1098, in<br>> >> > > > > > pkiCleanup<br>> >> > > > > > OSError: [Errno 16] Device or resource busy:<br>> >> > > > > > '/etc/pki/vdsm/certs/cacert.pem'<br>> >> > > > ><br>> >> > > > ><br>> >> > > > > Nicholas,<br>> >> > > > > I think I got it;<br>> >> > > > > Please check if this file exists: '/etc/rhev-hypervisor-release'.<br>> >> > > > > If not, try to create a sym-link in this name to<br>> >> > > > > /etc/system-release,<br>> >> > > > > and restart vdsm-reg service.<br>> >> ><br>> >> > No, /etc/rhev-hypervisor-release should not exist. It doesn't have to.<br>> >> > We went through significant effort before the 3.0 release making sure<br>> >> > that vdsm used /etc/ovirt-node-image-release for determining if the<br>> >> > machine is ovirt-node based or not.<br>> >> ><br>> >> > There should not be any need for anything that says "rhev" in<br>> >> > ovirt-node.<br>> >> ><br>> >> > Mike<br>> >> ><br>> >> > > > ><br>> >> > > > > Also please provide the rpm information for vdsm-reg and vdsm as<br>> >> > > > > well.<br>> >> > > > > --<br>> >> > > > ><br>> >> > > > > /d<br>> >> > > > ><br>> >> > > > > "Common sense is not so common." --Voltaire, Dictionnaire<br>> >> > > > > Philosophique (1764)<br>> >> > > ><br>> >> > > > Just to make sure I do it right, can you specify which you wanted<br>> >> > > > done on the node, and which you wanted on the manager? I have the<br>> >> > > > feeling you wanted it all done on the node.<br>> >> > ><br>> >> > > you are correct, all on node.<br>> >> > ><br>> <br>> -- <br>> <br>> /d<br>> <br>> "Email returned to sender -- insufficient voltage."<br></div> </div></body>
</html>