Re: [Users] Adding oVirt Node Fails

2012-05-08 Thread Nicholas Kesick


 > Date: Tue, 8 May 2012 11:11:36 +0300
> From: dfedi...@redhat.com
> To: cybertimber2...@hotmail.com
> CC: mbu...@redhat.com; users@ovirt.org
> Subject: Re: [Users] Adding oVirt Node Fails
> 
> On 08/05/12 06:06, Nicholas Kesick wrote:
> > Results of testing, round 3 (trying to get [Errno 16] Device or resource 
> > busy '/etc/pki/vdsm/certs/cacert.pem' error.)
> > Variable: no symlink to /etc/system-release
> >  
> > 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".
> > On the manager, clicked the host, clicked approve, and clicked ok (on power 
> > management warning)
> > And we passed the cert install!  And everything worked up until I hit 
> > the cpuFlags issue.
> > 
> > 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.
> > 
> > Not sure where this leaves this topic. Seems I can properly add a node now 
> > without a cert or bridge renaming issue.
> > - Nick
> 
> Nick,
> Thanks for taking the time to do this.
> Can you just verify you used the same ovirt-node ISO for all your tests?
> 
> Confirmed, I used the same ovirt-node ISO for all of my tests.The ISO was 
> extracted to a 4GB USB flash drive and installed from it. - Nick
> > -----------!
>  ---
> > From: cybertimber2...@hotmail.com
> > To: dfedi...@redhat.com; mbu...@redhat.com
> > Date: Mon, 7 May 2012 18:53:39 -0400
> > CC: users@ovirt.org
> > Subject: Re: [Users] Adding oVirt Node Fails
> > 
> > Results of testing, round 2 (trying to get [Errno 16] Device or resource 
> > busy '/etc/pki/vdsm/certs/cacert.pem' error.)
> >  
> > 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). 
> > 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. 
> > Ovirt prompts to confirm fingerprint, accepted. (quickly a message about 
> > pki and "persisted" appears on screen).
> > Created a new host in ovirt-manager, host went to "Pending Approval".
> > 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 bet

Re: [Users] Adding oVirt Node Fails

2012-05-08 Thread Doron Fediuck
On 08/05/12 06:06, Nicholas Kesick wrote:
> Results of testing, round 3 (trying to get [Errno 16] Device or resource busy 
> '/etc/pki/vdsm/certs/cacert.pem' error.)
> Variable: no symlink to /etc/system-release
>  
> 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".
> On the manager, clicked the host, clicked approve, and clicked ok (on power 
> management warning)
> And we passed the cert install!  And everything worked up until I hit the 
> cpuFlags issue.
> 
> 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.
> 
> Not sure where this leaves this topic. Seems I can properly add a node now 
> without a cert or bridge renaming issue.
> - Nick

Nick,
Thanks for taking the time to do this.
Can you just verify you used the same ovirt-node ISO for all your tests?


> ---!
 ---
> From: cybertimber2...@hotmail.com
> To: dfedi...@redhat.com; mbu...@redhat.com
> Date: Mon, 7 May 2012 18:53:39 -0400
> CC: users@ovirt.org
> Subject: Re: [Users] Adding oVirt Node Fails
> 
> Results of testing, round 2 (trying to get [Errno 16] Device or resource busy 
> '/etc/pki/vdsm/certs/cacert.pem' error.)
>  
> 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). 
> 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. 
> Ovirt prompts to confirm fingerprint, accepted. (quickly a message about pki 
> and "persisted" appears on screen).
> Created a new host in ovirt-manager, host went to "Pending Approval".
> 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.))
> On the manager, clicked the host, clicked approve, and clicked ok (on power 
> management warning)
> Ended at missing cpuFlags.
>  
> 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.
>  
> - Nick
>  
> -----------!
 ---
> From: cybertimber2...@ho

Re: [Users] Adding oVirt Node Fails

2012-05-07 Thread Nicholas Kesick




Results of testing, round 3 (trying to get [Errno 16] Device or resource busy 
'/etc/pki/vdsm/certs/cacert.pem' error.)
Variable: no symlink to /etc/system-release
 
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".On the manager, clicked the 
host, clicked approve, and clicked ok (on power management warning)
And we passed the cert install!  And everything worked up until I hit the 
cpuFlags issue.
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.
Not sure where this leaves this topic. Seems I can properly add a node now 
without a cert or bridge renaming issue.- NickFrom: cybertimber2...@hotmail.com
To: dfedi...@redhat.com; mbu...@redhat.com
Date: Mon, 7 May 2012 18:53:39 -0400
CC: users@ovirt.org
Subject: Re: [Users] Adding oVirt Node Fails





Results of testing, round 2 (trying to get [Errno 16] Device or resource busy 
'/etc/pki/vdsm/certs/cacert.pem' error.)
 
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). 
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. 
Ovirt prompts to confirm fingerprint, accepted. (quickly a message about pki 
and "persisted" appears on screen).
Created a new host in ovirt-manager, host went to "Pending Approval".
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.))
On the manager, clicked the host, clicked approve, and clicked ok (on power 
management warning)
Ended at missing cpuFlags.
 
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.
 
- Nick
 
From: cybertimber2...@hotmail.com
To: dfedi...@redhat.com; mbu...@redhat.com
Date: Mon, 7 May 2012 18:32:34 -0400
CC: users@ovirt.org
Subject: Re: [Users] Adding oVirt Node Fails





Ok so here is the results of testing:
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".
On the node shell, performed "ln -s /etc/system-release 
/etc/rhev-hypervisor-release"
On the manager, clicked the host, clicked approve, and clicked ok (on power 
management warning)
Ended at missing cpuFlags.
 
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!  
 
But I think I know what has been causing the OSError: [Errno 16] Device or 
resource busy '/etc/pki/vdsm/certs/cacert.pem' error.
Working through that now, will post the step by step when I have it.
 - Nick > To: mbu...@redhat.com; aba...@redhat.com; cybertimber2...@hotmail.com
> From: dfedi...@redhat.com
> CC: users@ovirt.org
> Date: Mon, 7 May 2012 17:28:20 -0400
> Subject: Re: [Users] Adding oVirt Node Fails
> 
> 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 [cybertimber2...@hotmail.com]
> Received: Tuesday, 08 May 2012, 0:08
> To: mbu...@redhat.com, aba...@redhat.com
> CC: oVirt Mailing List [users@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: mbu...@redhat.com
> > To: aba...@redhat.com
> > CC: cybertimber2...@hotmail.com; users@ovirt.org
> > Date: Sun, 6 May 2012 21:26:08 -0400
> > 
> > On Sat, 2012-05-05 at 16:39 -0400, Ayal Baron wrote:
> > > 
> > > 

Re: [Users] Adding oVirt Node Fails

2012-05-07 Thread Nicholas Kesick

Results of testing, round 2 (trying to get [Errno 16] Device or resource busy 
'/etc/pki/vdsm/certs/cacert.pem' error.) 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). 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. Ovirt prompts to confirm fingerprint, accepted. (quickly a message 
about pki and "persisted" appears on screen).Created a new host in 
ovirt-manager, host went to "Pending Approval".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.))On the manager, clicked 
the host, clicked approve, and clicked ok (on power management warning)
Ended at missing cpuFlags. 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. - Nick From: 
cybertimber2...@hotmail.com
To: dfedi...@redhat.com; mbu...@redhat.com
Date: Mon, 7 May 2012 18:32:34 -0400
CC: users@ovirt.org
Subject: Re: [Users] Adding oVirt Node Fails





Ok so here is the results of testing:
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".
On the node shell, performed "ln -s /etc/system-release 
/etc/rhev-hypervisor-release"
On the manager, clicked the host, clicked approve, and clicked ok (on power 
management warning)
Ended at missing cpuFlags.
 
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!  
 
But I think I know what has been causing the OSError: [Errno 16] Device or 
resource busy '/etc/pki/vdsm/certs/cacert.pem' error.
Working through that now, will post the step by step when I have it.
 - Nick > To: mbu...@redhat.com; aba...@redhat.com; cybertimber2...@hotmail.com
> From: dfedi...@redhat.com
> CC: users@ovirt.org
> Date: Mon, 7 May 2012 17:28:20 -0400
> Subject: Re: [Users] Adding oVirt Node Fails
> 
> 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 [cybertimber2...@hotmail.com]
> Received: Tuesday, 08 May 2012, 0:08
> To: mbu...@redhat.com, aba...@redhat.com
> CC: oVirt Mailing List [users@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: mbu...@redhat.com
> > To: aba...@redhat.com
> > CC: cybertimber2...@hotmail.com; users@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: dfedi...@redhat.com
> > > > > To: cybertimber2...@hotmail.com
> > > > > CC: mbu...@redhat.com; users@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;
> &g

Re: [Users] Adding oVirt Node Fails

2012-05-07 Thread Nicholas Kesick

Ok so here is the results of testing: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".On the node shell, performed "ln -s /etc/system-release 
/etc/rhev-hypervisor-release"On the manager, clicked the host, clicked approve, 
and clicked ok (on power management warning)Ended at missing cpuFlags. 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!   But I think I know 
what has been causing the OSError: [Errno 16] Device or resource busy 
'/etc/pki/vdsm/certs/cacert.pem' error.Working through that now, will post the 
step by step when I have it. - Nick > To: mbu...@redhat.com; aba...@redhat.com; 
cybertimber2...@hotmail.com
> From: dfedi...@redhat.com
> CC: users@ovirt.org
> Date: Mon, 7 May 2012 17:28:20 -0400
> Subject: Re: [Users] Adding oVirt Node Fails
> 
> 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 [cybertimber2...@hotmail.com]
> Received: Tuesday, 08 May 2012, 0:08
> To: mbu...@redhat.com, aba...@redhat.com
> CC: oVirt Mailing List [users@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: mbu...@redhat.com
> > To: aba...@redhat.com
> > CC: cybertimber2...@hotmail.com; users@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: dfedi...@redhat.com
> > > > > To: cybertimber2...@hotmail.com
> > > > > CC: mbu...@redhat.com; users@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@ovirt.org
> > > > http://lists.ovirt.org/mailman/listinfo/users
> > > > 
> > > ___
> > > Users mailing list
> > > Users@ovirt.org
> > > http://lists.ovirt.org/mailman/listinfo/users
> > 
> > 
> 
> 
> Sent from my Android phone. Please ignore typos.
  ___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] Adding oVirt Node Fails

2012-05-07 Thread Doron Fediuck
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 [cybertimber2...@hotmail.com]
Received: Tuesday, 08 May 2012, 0:08
To: mbu...@redhat.com, aba...@redhat.com
CC: oVirt Mailing List [users@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: mbu...@redhat.com
> To: aba...@redhat.com
> CC: cybertimber2...@hotmail.com; users@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: dfedi...@redhat.com
> > > > To: cybertimber2...@hotmail.com
> > > > CC: mbu...@redhat.com; users@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@ovirt.org
> > > http://lists.ovirt.org/mailman/listinfo/users
> > > 
> > ___
> > Users mailing list
> > Users@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/users
> 
> 
  

Sent from my Android phone. Please ignore typos.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] Adding oVirt Node Fails

2012-05-07 Thread Ayal Baron


- Original Message -
> 
> Ayal, did you see something in the code that made you want me to try
> the sym-link to /etc/rhev-hypervisor-release?

Actually it was Doron who directed you, I just commented that it is all 
relevant to the node and not to the engine.

> Mike, is there any harm in linking it?
> 
> - Nick
> 
> 
> 
> > Subject: Re: [Users] Adding oVirt Node Fails
> > From: mbu...@redhat.com
> > To: aba...@redhat.com
> > CC: cybertimber2...@hotmail.com; users@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: dfedi...@redhat.com
> > > > > To: cybertimber2...@hotmail.com
> > > > > CC: mbu...@redhat.com; users@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@ovirt.org
> > > > http://lists.ovirt.org/mailman/listinfo/users
> > > > 
> > > ___
> > > Users mailing list
> > > Users@ovirt.org
> > > http://lists.ovirt.org/mailman/listinfo/users
> > 
> > 
> 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] Adding oVirt Node Fails

2012-05-07 Thread Nicholas Kesick

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: mbu...@redhat.com
> To: aba...@redhat.com
> CC: cybertimber2...@hotmail.com; users@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: dfedi...@redhat.com
> > > > To: cybertimber2...@hotmail.com
> > > > CC: mbu...@redhat.com; users@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@ovirt.org
> > > http://lists.ovirt.org/mailman/listinfo/users
> > > 
> > ___
> > Users mailing list
> > Users@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/users
> 
> 
  ___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] Adding oVirt Node Fails

2012-05-06 Thread Mike Burns
On Sat, 2012-05-05 at 16:39 -0400, Ayal Baron wrote:
> 
> - Original Message -
> > 
> > 
> > > Date: Sat, 5 May 2012 12:29:20 +0300
> > > From: dfedi...@redhat.com
> > > To: cybertimber2...@hotmail.com
> > > CC: mbu...@redhat.com; users@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@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/users
> > 
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] Adding oVirt Node Fails

2012-05-05 Thread Doron Fediuck
R
this should be done on the node machine.

Sent from my Android phone. Please ignore typos.

-Original Message-
From: Nicholas Kesick [cybertimber2...@hotmail.com]
Received: Saturday, 05 May 2012, 21:55
To: dfedi...@redhat.com
CC: mbu...@redhat.com, oVirt Mailing List [users@ovirt.org]
Subject: RE: [Users] Adding oVirt Node Fails


> Date: Sat, 5 May 2012 12:29:20 +0300
> From: dfedi...@redhat.com
> To: cybertimber2...@hotmail.com
> CC: mbu...@redhat.com; users@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 DEBUGinstCert: try to delete old certificates
> > Fri, 27 Apr 2012 05:22:24 DEBUGinstCert: 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.
> 
> 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.
  

Sent from my Android phone. Please ignore typos.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] Adding oVirt Node Fails

2012-05-05 Thread Ayal Baron


- Original Message -
> 
> 
> > Date: Sat, 5 May 2012 12:29:20 +0300
> > From: dfedi...@redhat.com
> > To: cybertimber2...@hotmail.com
> > CC: mbu...@redhat.com; users@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.
> > 
> > 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@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
> 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] Adding oVirt Node Fails

2012-05-05 Thread Nicholas Kesick

> Date: Sat, 5 May 2012 12:29:20 +0300
> From: dfedi...@redhat.com
> To: cybertimber2...@hotmail.com
> CC: mbu...@redhat.com; users@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 DEBUGinstCert: try to delete old certificates
> > Fri, 27 Apr 2012 05:22:24 DEBUGinstCert: 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.
> 
> 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.
  ___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] Adding oVirt Node Fails

2012-05-05 Thread Doron Fediuck
On 04/05/12 02:49, Nicholas Kesick wrote:
> Fri, 27 Apr 2012 05:22:24 DEBUGinstCert: try to delete old certificates
> Fri, 27 Apr 2012 05:22:24 DEBUGinstCert: 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.

Also please provide the rpm information for vdsm-reg and vdsm as well.
-- 

/d

"Common sense is not so common." --Voltaire, Dictionnaire Philosophique (1764)
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] Adding oVirt Node Fails

2012-05-03 Thread Mike Burns
On Thu, 2012-05-03 at 10:29 +0300, Doron Fediuck wrote:
> On 03/05/12 06:40, Itamar Heim wrote:
> > On 05/03/2012 04:29 AM, Nicholas Kesick wrote:
> >> Update: Please see my previous email and attachments as that may provide
> >> more info still.
> >>
> >> I manually renamed the bridge from breth0 to ovirtmgmt (edited
> >> /etc/sysconfig/network-scripts/ifcfg-eth0, copied
> >> /etc/sysconfig/network-scripts/ifcfg-breth0 to ifcfg-ovirtmgmt) then
> >> connected the network in the TUI and it came up correctly. Added the
> >> host, then tried approving it. So the error about not being able to
> >> rename the bridge disappeared, and it now shows in vdsm-reg.log that it
> >> got as far as copying engine.ssh.key.txt... but the manager still
> >> reports that "Failed to install Host Fedora16: Step: instCert", "Host
> >> Fedora16 was successfully approved" and host status of "Install failed".
> >>
> >> I've attached the contents of /var/log/vdsm-reg/* and /tmp/vds_* and a
> >> screenshot of the event log from the manager.
> > 
> > this seems the relevant part from log:
> > Thu, 26 Apr 2012 06:57:04 DEBUGinstCert: 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'
> > 
> > have you tried rebooting the host between tries to clear potential issues?
> > doron?
> > 
> Good observation.
> Added Mike, as this is a node issue.
> I suggest you reboot and check if the same issue occurs.
> If so, you'll need Mike's help on that.

This is node, yes, but it appears to be purely in the vdsm-reg area.
I've been watching the issues, but it seems to fall more on the vdsm
team to handle, not node team.  If we need a fix in the node for this,
I'm happy to help fix it, but so far it seems to all be vdsm.

Mike

> 
> >>
> >> - Nick
> >> 
> >> From: cybertimber2...@hotmail.com
> >> To: dfedi...@redhat.com
> >> Date: Wed, 2 May 2012 17:59:08 -0400
> >> CC: users@ovirt.org
> >> Subject: Re: [Users] Adding oVirt Node Fails
> >>
> >> Douglas,
> >>
> >> This happens after the approval part. So after I click approve is when
> >> it says the install cert failed, then reports that the approval suceeded
> >> (in events), but that the installation failed (in host status).
> >> Looking into the SSH keys, but I have attached the /var/log/vdsm-reg/*
> >> files from the node in question. It still seems to imply issues with
> >> renaming the bridge, so I'm looking into that now.
> >>
> >> I also cleared out and reset /root/.ssh/authorized_keys on the node, but
> >> no dice there. Maybe the first time it wasn't populated, hence the
> >> failed to read?
> >>
> >> - Nick
> >>
> >>
> >>  > Date: Wed, 2 May 2012 13:28:26 +0300
> >>  > From: dfedi...@redhat.com
> >>  > To: cybertimber2...@hotmail.com
> >>  > CC: dougsl...@redhat.com; users@ovirt.org
> >>  > Subject: Re: [Users] Adding oVirt Node Fails
> >>  >
> >>  > Hi Nick,
> >>  > You managed to add one log which complains about:
> >>  > Tue, 01 May 2012 18:00:18 DEBUG Failed to read 
> >> /root/.ssh/authorized_keys
> >

Re: [Users] Adding oVirt Node Fails

2012-05-03 Thread Doron Fediuck
On 03/05/12 06:40, Itamar Heim wrote:
> On 05/03/2012 04:29 AM, Nicholas Kesick wrote:
>> Update: Please see my previous email and attachments as that may provide
>> more info still.
>>
>> I manually renamed the bridge from breth0 to ovirtmgmt (edited
>> /etc/sysconfig/network-scripts/ifcfg-eth0, copied
>> /etc/sysconfig/network-scripts/ifcfg-breth0 to ifcfg-ovirtmgmt) then
>> connected the network in the TUI and it came up correctly. Added the
>> host, then tried approving it. So the error about not being able to
>> rename the bridge disappeared, and it now shows in vdsm-reg.log that it
>> got as far as copying engine.ssh.key.txt... but the manager still
>> reports that "Failed to install Host Fedora16: Step: instCert", "Host
>> Fedora16 was successfully approved" and host status of "Install failed".
>>
>> I've attached the contents of /var/log/vdsm-reg/* and /tmp/vds_* and a
>> screenshot of the event log from the manager.
> 
> this seems the relevant part from log:
> Thu, 26 Apr 2012 06:57:04 DEBUGinstCert: 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'
> 
> have you tried rebooting the host between tries to clear potential issues?
> doron?
> 
Good observation.
Added Mike, as this is a node issue.
I suggest you reboot and check if the same issue occurs.
If so, you'll need Mike's help on that.

>>
>> - Nick
>> ------------
>> From: cybertimber2...@hotmail.com
>> To: dfedi...@redhat.com
>> Date: Wed, 2 May 2012 17:59:08 -0400
>> CC: users@ovirt.org
>> Subject: Re: [Users] Adding oVirt Node Fails
>>
>> Douglas,
>>
>> This happens after the approval part. So after I click approve is when
>> it says the install cert failed, then reports that the approval suceeded
>> (in events), but that the installation failed (in host status).
>> Looking into the SSH keys, but I have attached the /var/log/vdsm-reg/*
>> files from the node in question. It still seems to imply issues with
>> renaming the bridge, so I'm looking into that now.
>>
>> I also cleared out and reset /root/.ssh/authorized_keys on the node, but
>> no dice there. Maybe the first time it wasn't populated, hence the
>> failed to read?
>>
>> - Nick
>>
>>
>>  > Date: Wed, 2 May 2012 13:28:26 +0300
>>  > From: dfedi...@redhat.com
>>  > To: cybertimber2...@hotmail.com
>>  > CC: dougsl...@redhat.com; users@ovirt.org
>>  > Subject: Re: [Users] Adding oVirt Node Fails
>>  >
>>  > Hi Nick,
>>  > You managed to add one log which complains about:
>>  > Tue, 01 May 2012 18:00:18 DEBUG Failed to read /root/.ssh/authorized_keys
>>  >
>>  > Can you check this file inside your host?
>>  >
>>  > Also, it seems that you're adding it via the UI (New host), while
>> such hosts
>>  > in most cases will register if properly configured, and show up with
>> PendingApproval
>>  > status in the UI.
>>  > So please add the logs you have in the host under /var/log/vdsm-reg/
>>  >
>>  >
>>  > On 02/05/12 01:12, Nicholas Kesick wrote:
>>  > > Douglas,
>>  > >
>>  > > VDSM is version 3.9.3.3. I'm not sure which error message you are
>> refering to, but I attached the events from oVirt Manager as well as
>> /tmp/vds_* from the node.
>>  > >
>>  > > Thanks,
>>  > > - Nick
>>  > >
>>  > >
>>  > >
>> -----------

Re: [Users] Adding oVirt Node Fails

2012-05-02 Thread Itamar Heim

On 05/03/2012 04:29 AM, Nicholas Kesick wrote:

Update: Please see my previous email and attachments as that may provide
more info still.

I manually renamed the bridge from breth0 to ovirtmgmt (edited
/etc/sysconfig/network-scripts/ifcfg-eth0, copied
/etc/sysconfig/network-scripts/ifcfg-breth0 to ifcfg-ovirtmgmt) then
connected the network in the TUI and it came up correctly. Added the
host, then tried approving it. So the error about not being able to
rename the bridge disappeared, and it now shows in vdsm-reg.log that it
got as far as copying engine.ssh.key.txt... but the manager still
reports that "Failed to install Host Fedora16: Step: instCert", "Host
Fedora16 was successfully approved" and host status of "Install failed".

I've attached the contents of /var/log/vdsm-reg/* and /tmp/vds_* and a
screenshot of the event log from the manager.


this seems the relevant part from log:
Thu, 26 Apr 2012 06:57:04 DEBUGinstCert: 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'


have you tried rebooting the host between tries to clear potential issues?
doron?



- Nick

From: cybertimber2...@hotmail.com
To: dfedi...@redhat.com
Date: Wed, 2 May 2012 17:59:08 -0400
CC: users@ovirt.org
Subject: Re: [Users] Adding oVirt Node Fails

Douglas,

This happens after the approval part. So after I click approve is when
it says the install cert failed, then reports that the approval suceeded
(in events), but that the installation failed (in host status).
Looking into the SSH keys, but I have attached the /var/log/vdsm-reg/*
files from the node in question. It still seems to imply issues with
renaming the bridge, so I'm looking into that now.

I also cleared out and reset /root/.ssh/authorized_keys on the node, but
no dice there. Maybe the first time it wasn't populated, hence the
failed to read?

- Nick


 > Date: Wed, 2 May 2012 13:28:26 +0300
 > From: dfedi...@redhat.com
 > To: cybertimber2...@hotmail.com
 > CC: dougsl...@redhat.com; users@ovirt.org
 > Subject: Re: [Users] Adding oVirt Node Fails
 >
 > Hi Nick,
 > You managed to add one log which complains about:
 > Tue, 01 May 2012 18:00:18 DEBUG Failed to read /root/.ssh/authorized_keys
 >
 > Can you check this file inside your host?
 >
 > Also, it seems that you're adding it via the UI (New host), while
such hosts
 > in most cases will register if properly configured, and show up with
PendingApproval
 > status in the UI.
 > So please add the logs you have in the host under /var/log/vdsm-reg/
 >
 >
 > On 02/05/12 01:12, Nicholas Kesick wrote:
 > > Douglas,
 > >
 > > VDSM is version 3.9.3.3. I'm not sure which error message you are
refering to, but I attached the events from oVirt Manager as well as
/tmp/vds_* from the node.
 > >
 > > Thanks,
 > > - Nick
 > >
 > >
 > >
---------------!
 > ---
 > > Date: Tue, 1 May 2012 00:53:52 -0400
 > > From: dougsl...@redhat.com
 > > To: users@ovirt.org
 > > CC: cybertimber2...@hotmail.com
 > > Subject: Re: [Users] Adding oVirt Node Fails
 > >
 > > Hi Nicholas,
 > >
 > > On 04/30/2012 10:56 PM, Nicholas Kesick wrote:
 > >
 > > It's called "breth0". I've been tempted to rename it manually, but
my understanding is that it's not persistant. Worth testing though.
 > > dougsland, jboggs said you may know something about this being a
bug in the stable version and is fixed in nightlies?
 > >
 > >
 > > Can you please share your vdsm version and the full error message?
/tmp/

Re: [Users] Adding oVirt Node Fails

2012-05-02 Thread Doron Fediuck
Hi Nick,
You managed to add one log which complains about:
Tue, 01 May 2012 18:00:18 DEBUGFailed to read /root/.ssh/authorized_keys

Can you check this file inside your host?

Also, it seems that you're adding it via the UI (New host), while such hosts
in most cases will register if properly configured, and show up with 
PendingApproval
status in the UI.
So please add the logs you have in the host under /var/log/vdsm-reg/


On 02/05/12 01:12, Nicholas Kesick wrote:
> Douglas,
>  
> VDSM is version 3.9.3.3.  I'm not sure which error message you are refering 
> to, but I attached the events from oVirt Manager as well as /tmp/vds_* from 
> the node.
>  
> Thanks,
> - Nick
>  
>  
> ---!
 ---
> Date: Tue, 1 May 2012 00:53:52 -0400
> From: dougsl...@redhat.com
> To: users@ovirt.org
> CC: cybertimber2...@hotmail.com
> Subject: Re: [Users] Adding oVirt Node Fails
> 
> Hi Nicholas,
> 
> On 04/30/2012 10:56 PM, Nicholas Kesick wrote:
> 
> It's called "breth0". I've been tempted to rename it manually, but my 
> understanding is that it's not persistant. Worth testing though.
> dougsland, jboggs said you may know something about this being a bug in 
> the stable version and is fixed in nightlies?
> 
> 
> Can you please share your vdsm version and the full error message? /tmp/vds_* 
> files would be nice too
> 
> Here a patch that might help: 
> http://gerrit.ovirt.org/#patch,sidebyside,3615,5,vdsm/configNetwork.py 
> <http://gerrit.ovirt.org/#patch%2csidebyside%2c3615%2c5%2cvdsm/configNetwork.py>
>  (already merged into vdsm tree)
> 
> 
> Thanks!
> 
> -- 
> Cheers
> Douglas
> 
> 
> 
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users


-- 

/d

"Willyoupleasehelpmefixmykeyboard?Thespacebarisbroken!"
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] Adding oVirt Node Fails

2012-04-30 Thread Douglas Landgraf

Hi Nicholas,

On 04/30/2012 10:56 PM, Nicholas Kesick wrote:
It's called "breth0". I've been tempted to rename it manually, but my 
understanding is that it's not persistant. Worth testing though.
dougsland, jboggs said you may know something about this being a bug 
in the stable version and is fixed in nightlies?




Can you please share your vdsm version and the full error message? 
/tmp/vds_* files would be nice too


Here a patch that might help: 
http://gerrit.ovirt.org/#patch,sidebyside,3615,5,vdsm/configNetwork.py 
(already merged into vdsm tree)



Thanks!

--
Cheers
Douglas

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] Adding oVirt Node Fails

2012-04-30 Thread Nicholas Kesick

It's called "breth0". I've been tempted to rename it manually, but my 
understanding is that it's not persistant. Worth testing though.dougsland, 
jboggs said you may know something about this being a bug in the stable version 
and is fixed in nightlies?
Date: Mon, 30 Apr 2012 21:56:16 -0400
Subject: Re: [Users] Adding oVirt Node Fails
From: virtually...@gmail.com
To: cybertimber2...@hotmail.com

I would go to /etc/sysconfig/network-scripts/ and see what your bridge is 
called on both machines.  They should both be ifcfg-ovirtmgmt I believe.

On Mon, Apr 30, 2012 at 5:58 PM, Nicholas Kesick  
wrote:








I'm having trouble adding a oVirt Node to the oVirt Manager.
The node is powered by the oVirt Node 2.3.0 image (installed to local storage).
The engine is powered by Fedora 16 + oVirt-engine package from YUM.

 
When I add the host, install goes ok, and when I go to activate it everything 
goes ok until near step 2.  
Step: Install RHEV_INSTALL completes
Step: instCert fails
Then it says (in events) that the host was installed successfully, while the 
manager says "Install Failed".

 
Looking at the logs on the node, VDSM Registration Log seems to imply it can't 
rename the bridge.
 
Anyone have any advice?
 
Thanks,
- Nick
  

___

Users mailing list

Users@ovirt.org

http://lists.ovirt.org/mailman/listinfo/users




-- 
Gary Scarborough

IST Lab Manager

Rochester Institute of Technology

Rochester NY
  ___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[Users] Adding oVirt Node Fails

2012-04-30 Thread Nicholas Kesick




I'm having trouble adding a oVirt Node to the oVirt Manager.The node is powered 
by the oVirt Node 2.3.0 image (installed to local storage).The engine is 
powered by Fedora 16 + oVirt-engine package from YUM. When I add the host, 
install goes ok, and when I go to activate it everything goes ok until near 
step 2.  Step: Install RHEV_INSTALL completesStep: instCert failsThen it says 
(in events) that the host was installed successfully, while the manager says 
"Install Failed". Looking at the logs on the node, VDSM Registration Log seems 
to imply it can't rename the bridge. Anyone have any advice? Thanks,- Nick  
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users