The oVirt team is pleased to announce that the 3.4.0 Release Candidate is now available for testing.
Release notes and information on the changes for this update are still being worked on and will be available soon on the wiki[1]. Please ensure to follow install instruction from release notes if you're going to test it. The existing repository ovirt-3.4.0-prerelease has been updated for delivering this release candidate and future refreshes until final release.
An oVirt Node iso is already available, unchanged from third beta.
You're welcome to join us testing this release candidate in next week test day [2] scheduled for 2014-03-06!
[1] http://www.ovirt.org/OVirt_3.4.0_release_notes [2] http://www.ovirt.org/OVirt_3.4_Test_Day
Started testing this on two self-hosted clusters, with mixed results. There were updates from 3.4.0 beta 3.
On both, got informed the system was going to reboot in 2 minutes while it was still installing yum updates.
On the faster system, the whole update process finished before the 2 minutes were up, the VM restarted, and all appears normal.
On the other, slower cluster, the 2 minutes hit while the yum updates were still being installed, and the system rebooted. It continued rebooting every 3 minutes or so, and the engine console web pages are not available because the engine doesn’t start. it did this at least 3 times before I went ahead and reran engine-setup, which completed successfully. The system stopped restarting and the web interface was available again. A quick perusal of system logs and engine-setup logs didn’t reveal what requested the reboot.
That was rather impolite of something to do that without warning :) At least it was recoverable. Seems like scheduling the reboot while the yum updates were still running seems like a poor idea as well.
-Darrell
On Feb 28, 2014, at 10:11 AM, Sandro Bonazzola sbonazzo@redhat.com wrote:
The oVirt team is pleased to announce that the 3.4.0 Release Candidate is now available for testing.
Release notes and information on the changes for this update are still being worked on and will be available soon on the wiki[1]. Please ensure to follow install instruction from release notes if you're going to test it. The existing repository ovirt-3.4.0-prerelease has been updated for delivering this release candidate and future refreshes until final release.
An oVirt Node iso is already available, unchanged from third beta.
You're welcome to join us testing this release candidate in next week test day [2] scheduled for 2014-03-06!
[1] http://www.ovirt.org/OVirt_3.4.0_release_notes [2] http://www.ovirt.org/OVirt_3.4_Test_Day
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
----- Original Message -----
From: "Darrell Budic" darrell.budic@zenfire.com To: "Sandro Bonazzola" sbonazzo@redhat.com Cc: announce@ovirt.org, "engine-devel" engine-devel@ovirt.org, "arch" arch@ovirt.org, Users@ovirt.org, "VDSM Project Development" vdsm-devel@lists.fedorahosted.org Sent: Saturday, March 1, 2014 1:56:23 AM Subject: Re: [vdsm] [Users] [ANN] oVirt 3.4.0 Release Candidate is now available
Started testing this on two self-hosted clusters, with mixed results. There were updates from 3.4.0 beta 3.
On both, got informed the system was going to reboot in 2 minutes while it was still installing yum updates.
On the faster system, the whole update process finished before the 2 minutes were up, the VM restarted, and all appears normal.
On the other, slower cluster, the 2 minutes hit while the yum updates were still being installed, and the system rebooted. It continued rebooting every 3 minutes or so, and the engine console web pages are not available because the engine doesn’t start. it did this at least 3 times before I went ahead and reran engine-setup, which completed successfully. The system stopped restarting and the web interface was available again. A quick perusal of system logs and engine-setup logs didn’t reveal what requested the reboot.
That was rather impolite of something to do that without warning :) At least it was recoverable. Seems like scheduling the reboot while the yum updates were still running seems like a poor idea as well.
Can you please post relevant logs? hosts: /var/log/ovirt-hosted-engine-setup/*, /var/log/ovirt-hosted-engine-ha/*, /var/log/vdsm/* engine: /var/log/ovirt-engine/setup/*, /var/log/ovirt-engine/*
You can of course open a bug on bugzilla and attach there logs if you want.
Thanks, and thanks for the report!
Sounds like your hosts were not in maintenance mode while you were upgrading the engine which explains the 2 min reboot.
This should be revealed by logs
Regards Liviu
On Sun, Mar 2, 2014 at 10:32 PM, Yedidyah Bar David didi@redhat.com wrote:
----- Original Message -----
From: "Darrell Budic" darrell.budic@zenfire.com To: "Sandro Bonazzola" sbonazzo@redhat.com Cc: announce@ovirt.org, "engine-devel" engine-devel@ovirt.org, "arch"
arch@ovirt.org, Users@ovirt.org, "VDSM
Project Development" vdsm-devel@lists.fedorahosted.org Sent: Saturday, March 1, 2014 1:56:23 AM Subject: Re: [vdsm] [Users] [ANN] oVirt 3.4.0 Release Candidate is now
available
Started testing this on two self-hosted clusters, with mixed results.
There
were updates from 3.4.0 beta 3.
On both, got informed the system was going to reboot in 2 minutes while
it
was still installing yum updates.
On the faster system, the whole update process finished before the 2
minutes
were up, the VM restarted, and all appears normal.
On the other, slower cluster, the 2 minutes hit while the yum updates
were
still being installed, and the system rebooted. It continued rebooting
every
3 minutes or so, and the engine console web pages are not available
because
the engine doesn't start. it did this at least 3 times before I went
ahead
and reran engine-setup, which completed successfully. The system stopped restarting and the web interface was available again. A quick perusal of system logs and engine-setup logs didn't reveal what requested the
reboot.
That was rather impolite of something to do that without warning :) At
least
it was recoverable. Seems like scheduling the reboot while the yum
updates
were still running seems like a poor idea as well.
Can you please post relevant logs? hosts: /var/log/ovirt-hosted-engine-setup/*, /var/log/ovirt-hosted-engine-ha/*, /var/log/vdsm/* engine: /var/log/ovirt-engine/setup/*, /var/log/ovirt-engine/*
You can of course open a bug on bugzilla and attach there logs if you want.
Thanks, and thanks for the report!
Didi _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
vdsm-devel@lists.fedorahosted.org