[Users] Adding oVirt Node Fails

Doron Fediuck dfediuck at redhat.com
Mon May 7 17:28:20 EDT 2012


Nicholas,
The code I saw is testing for this file to verify it's a nods platform,
and if it's missing the behaviour changes. So the code will try to
unlink the file, which will give
you this result in a mounted file.

Sent from my Android phone. Please ignore typos.

-----Original Message-----
From: Nicholas Kesick [cybertimber2000 at hotmail.com]
Received: Tuesday, 08 May 2012, 0:08
To: mburns at redhat.com, abaron at redhat.com
CC: oVirt Mailing List [users at ovirt.org]
Subject: Re: [Users] Adding oVirt Node Fails


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
 > Subject: Re: [Users] Adding oVirt Node Fails
> From: mburns at redhat.com
> To: abaron at redhat.com
> CC: cybertimber2000 at hotmail.com; users at ovirt.org
> Date: Sun, 6 May 2012 21:26:08 -0400
> 
> On Sat, 2012-05-05 at 16:39 -0400, Ayal Baron wrote:
> > 
> > ----- Original Message -----
> > > 
> > > 
> > > > Date: Sat, 5 May 2012 12:29:20 +0300
> > > > From: dfediuck at redhat.com
> > > > To: cybertimber2000 at hotmail.com
> > > > CC: mburns at redhat.com; users at ovirt.org
> > > > Subject: Re: [Users] Adding oVirt Node Fails
> > > > 
> > > > On 04/05/12 02:49, Nicholas Kesick wrote:
> > > > > Fri, 27 Apr 2012 05:22:24 DEBUG instCert: try to delete old
> > > > > certificates
> > > > > Fri, 27 Apr 2012 05:22:24 DEBUG instCert: failed.
> > > > > Traceback (most recent call last):
> > > > > File "/usr/share/vdsm-reg/deployUtil.py", line 1133, in instCert
> > > > > File "/usr/share/vdsm-reg/deployUtil.py", line 1098, in
> > > > > pkiCleanup
> > > > > OSError: [Errno 16] Device or resource busy:
> > > > > '/etc/pki/vdsm/certs/cacert.pem'
> > > > 
> > > > 
> > > > Nicholas,
> > > > I think I got it;
> > > > Please check if this file exists: '/etc/rhev-hypervisor-release'.
> > > > If not, try to create a sym-link in this name to
> > > > /etc/system-release,
> > > > and restart vdsm-reg service.
> 
> No, /etc/rhev-hypervisor-release should not exist.  It doesn't have to.
> We went through significant effort before the 3.0 release making sure
> that vdsm used /etc/ovirt-node-image-release for determining if the
> machine is ovirt-node based or not.  
> 
> There should not be any need for anything that says "rhev" in
> ovirt-node.
> 
> Mike
> 
> > > > 
> > > > Also please provide the rpm information for vdsm-reg and vdsm as
> > > > well.
> > > > --
> > > > 
> > > > /d
> > > > 
> > > > "Common sense is not so common." --Voltaire, Dictionnaire
> > > > Philosophique (1764)
> > > 
> > > Just to make sure I do it right, can you specify which you wanted
> > > done on the node, and which you wanted on the manager? I have the
> > > feeling you wanted it all done on the node.
> > 
> > you are correct, all on node.
> > 
> > > 
> > > 
> > > 
> > > _______________________________________________
> > > Users mailing list
> > > Users at ovirt.org
> > > http://lists.ovirt.org/mailman/listinfo/users
> > > 
> > _______________________________________________
> > Users mailing list
> > Users at ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/users
> 
> 
 		 	   		  

Sent from my Android phone. Please ignore typos.


More information about the Users mailing list