[Users] Host setup for 3.1 beta
Hi, is there a working way to add a host with the current beta code? I tried the latest node iso and also a plain Fedora 17 with the latest vdsm packages but in both cases the registration seems to succeed but the installation seems to fail. Regards, Dennis
On Mon, Jun 18, 2012 at 10:24:51PM +0200, Dennis Jacobfeuerborn wrote:
Hi, is there a working way to add a host with the current beta code? I tried the latest node iso and also a plain Fedora 17 with the latest vdsm packages but in both cases the registration seems to succeed but the installation seems to fail.
Could you provide more information about the failure? is this the issue reported by Trey Dockendorf in http://lists.ovirt.org/pipermail/users/2012-June/002466.html
On 06/18/2012 10:27 PM, Dan Kenigsberg wrote:
On Mon, Jun 18, 2012 at 10:24:51PM +0200, Dennis Jacobfeuerborn wrote:
Hi, is there a working way to add a host with the current beta code? I tried the latest node iso and also a plain Fedora 17 with the latest vdsm packages but in both cases the registration seems to succeed but the installation seems to fail.
Could you provide more information about the failure? is this the issue reported by Trey Dockendorf in http://lists.ovirt.org/pipermail/users/2012-June/002466.html
Actually after seeing the "/tmp/vds_bootstrap.64713.log" bit in that mail I was able to find out what the problem was and fix it. Logs should really go into /var/log that where I was trying to find information on what was going on. The installation seems to succeed now and the Host is displayed as "Up". I got stuck almost 5 minutes in the state "Reboot" though even though the node was up in a few seconds after the reboot. What exactly is causing this long delay? Is the engine trying to contact vdsm or is the engine waiting for vdsm to connect to the engine? Regards, Dennis
On Mon, Jun 18, 2012 at 4:58 PM, Dennis Jacobfeuerborn <dennisml@conversis.de> wrote:
On 06/18/2012 10:27 PM, Dan Kenigsberg wrote:
On Mon, Jun 18, 2012 at 10:24:51PM +0200, Dennis Jacobfeuerborn wrote:
Hi, is there a working way to add a host with the current beta code? I tried the latest node iso and also a plain Fedora 17 with the latest vdsm packages but in both cases the registration seems to succeed but the installation seems to fail.
Could you provide more information about the failure? is this the issue reported by Trey Dockendorf in http://lists.ovirt.org/pipermail/users/2012-June/002466.html
Actually after seeing the "/tmp/vds_bootstrap.64713.log" bit in that mail I was able to find out what the problem was and fix it. Logs should really go into /var/log that where I was trying to find information on what was going on.
The installation seems to succeed now and the Host is displayed as "Up". I got stuck almost 5 minutes in the state "Reboot" though even though the node was up in a few seconds after the reboot. What exactly is causing this long delay? Is the engine trying to contact vdsm or is the engine waiting for vdsm to connect to the engine?
Regards, Dennis _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
I noticed the same delay and it could be due to the log being in /tmp. I got an SELinux denial of /sbin/shutdown trying to write to the /tmp/vps_bootstrap* file. Just a guess. I also noticed that the vdsm.conf file had context of the tmp directory and not etc_t. After doing numerous restorecon on files I cleared my SELinux audit log, If I see it again I'll report as it may cause some problems. - Trey
Hard coded time out. The system waits five min before tiring. Thanks Robert On 06/18/2012 05:58 PM, Dennis Jacobfeuerborn wrote:
On 06/18/2012 10:27 PM, Dan Kenigsberg wrote:
On Mon, Jun 18, 2012 at 10:24:51PM +0200, Dennis Jacobfeuerborn wrote:
Hi, is there a working way to add a host with the current beta code? I tried the latest node iso and also a plain Fedora 17 with the latest vdsm packages but in both cases the registration seems to succeed but the installation seems to fail. Could you provide more information about the failure? is this the issue reported by Trey Dockendorf in http://lists.ovirt.org/pipermail/users/2012-June/002466.html
Actually after seeing the "/tmp/vds_bootstrap.64713.log" bit in that mail I was able to find out what the problem was and fix it. Logs should really go into /var/log that where I was trying to find information on what was going on.
The installation seems to succeed now and the Host is displayed as "Up". I got stuck almost 5 minutes in the state "Reboot" though even though the node was up in a few seconds after the reboot. What exactly is causing this long delay? Is the engine trying to contact vdsm or is the engine waiting for vdsm to connect to the engine?
Regards, Dennis _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
On 06/19/2012 01:00 AM, Robert Middleswarth wrote:
Hard coded time out. The system waits five min before tiring.
Thanks Robert
On 06/18/2012 05:58 PM, Dennis Jacobfeuerborn wrote:
On 06/18/2012 10:27 PM, Dan Kenigsberg wrote:
On Mon, Jun 18, 2012 at 10:24:51PM +0200, Dennis Jacobfeuerborn wrote:
Hi, is there a working way to add a host with the current beta code? I tried the latest node iso and also a plain Fedora 17 with the latest vdsm packages but in both cases the registration seems to succeed but the installation seems to fail. Could you provide more information about the failure? is this the issue reported by Trey Dockendorf in http://lists.ovirt.org/pipermail/users/2012-June/002466.html
Actually after seeing the "/tmp/vds_bootstrap.64713.log" bit in that mail I was able to find out what the problem was and fix it. Logs should really go into /var/log that where I was trying to find information on what was going on.
The installation seems to succeed now and the Host is displayed as "Up". I got stuck almost 5 minutes in the state "Reboot" though even though the node was up in a few seconds after the reboot. What exactly is causing this long delay? Is the engine trying to contact vdsm or is the engine waiting for vdsm to connect to the engine?
Yes I figured as much but why does it time out? Who is responsible for re-establishing the connection after the reboot and why is that timing out? Regards, Dennis
----- Original Message -----
From: "Dennis Jacobfeuerborn" <dennisml@conversis.de> To: users@ovirt.org Sent: Monday, June 18, 2012 10:12:07 PM Subject: Re: [Users] Host setup for 3.1 beta
On 06/19/2012 01:00 AM, Robert Middleswarth wrote:
Hard coded time out. The system waits five min before tiring.
Thanks Robert
On 06/18/2012 05:58 PM, Dennis Jacobfeuerborn wrote:
On 06/18/2012 10:27 PM, Dan Kenigsberg wrote:
On Mon, Jun 18, 2012 at 10:24:51PM +0200, Dennis Jacobfeuerborn wrote:
Hi, is there a working way to add a host with the current beta code? I tried the latest node iso and also a plain Fedora 17 with the latest vdsm packages but in both cases the registration seems to succeed but the installation seems to fail. Could you provide more information about the failure? is this the issue reported by Trey Dockendorf in http://lists.ovirt.org/pipermail/users/2012-June/002466.html
Actually after seeing the "/tmp/vds_bootstrap.64713.log" bit in that mail I was able to find out what the problem was and fix it. Logs should really go into /var/log that where I was trying to find information on what was going on.
The installation seems to succeed now and the Host is displayed as "Up". I got stuck almost 5 minutes in the state "Reboot" though even though the node was up in a few seconds after the reboot. What exactly is causing this long delay? Is the engine trying to contact vdsm or is the engine waiting for vdsm to connect to the engine?
Yes I figured as much but why does it time out? Who is responsible for re-establishing the connection after the reboot and why is that timing out?
ovirt-engine will wait for "ServerRebootTimeout" before trying to connect to the host. IIRC that defaults to 5 minutes, but you can obviously change it. We need to change the mechanism to be more optimistic - eg. rather than wait for ServerRebootTimeout seconds, waiting for 30 seconds, try to connect and then retry every 30 seconds until ServerRebootTimeout expires.
Regards, Dennis _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
On 06/18/2012 04:24 PM, Dennis Jacobfeuerborn wrote:
Hi, is there a working way to add a host with the current beta code? I tried the latest node iso and also a plain Fedora 17 with the latest vdsm packages but in both cases the registration seems to succeed but the installation seems to fail.
Regards, Dennis _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users Ovirt-node-iso 2.4.0 has known issue with regestration and is waiting for a few bug fixes it isn't ready for testing or at least as of Friday wasn't.
F17 works but I had to get the network off network manager and using a bridge 1st that was much harder to get done on F17 then it was on both F16 and centos. Thanks Robert
participants (5)
-
Andrew Cathrow -
Dan Kenigsberg -
Dennis Jacobfeuerborn -
Robert Middleswarth -
Trey Dockendorf