Re: [ovirt-users] [ovirt-devel] [ANN] oVirt 3.5.2 First Release Candidate is now available for testing
- Original Message - From: Dan Kenigsberg dan...@redhat.com To: Nir Soffer nsof...@redhat.com Cc: Sandro Bonazzola sbona...@redhat.com, annou...@ovirt.org, Users@ovirt.org, de...@ovirt.org, Allon Mureinik amure...@redhat.com, Francesco Romani from...@redhat.com Sent: Saturday, February 28, 2015 12:43:02 AM Subject: Re: [ovirt-users] [ovirt-devel] [ANN] oVirt 3.5.2 First Release Candidate is now available for testing On Fri, Feb 27, 2015 at 03:48:22PM -0500, Nir Soffer wrote: - Original Message - From: Nir Soffer nsof...@redhat.com To: Sandro Bonazzola sbona...@redhat.com Cc: annou...@ovirt.org, Users@ovirt.org, de...@ovirt.org Sent: Friday, February 27, 2015 10:35:52 PM Subject: Re: [ovirt-users] [ovirt-devel] [ANN] oVirt 3.5.2 First Release Candidate is nowavailable for testing - Original Message - From: Sandro Bonazzola sbona...@redhat.com To: annou...@ovirt.org, de...@ovirt.org, Users@ovirt.org Sent: Friday, February 27, 2015 12:00:10 PM Subject: [ovirt-devel] [ANN] oVirt 3.5.2 First Release Candidate is now available for testing -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The oVirt team is pleased to announce that the 3.5.2 First Release Candidate is now available for testing as of Feb 27th 2015. The release candidate is available now for Fedora 20... Do we support Fedora 21? I don't recall a formal statement about it, but I surely WANT to support it, as nowadays it is the run-of-the-mill Fedora version. May be also relevant for Fedora 20 with virt-preview repository. Note also that we cannot use libvirt 1.2.8 on Fedora 20, since it contains critical bug that breaks live storage migration. This bug was fixed in libvirt 1.2.9. See https://bugzilla.redhat.com/1176673 Summary: - Fedora 20 is ok since it uses libvirt 1.1.3. - Fefora 20 with virt-preview must provide libvirt = 1.2.9 and vdsm must include the patch bellow virt-preview provides 1.2.9: https://fedorapeople.org/groups/virt/virt-preview/fedora-22/rpms/ - Fedora 21 provides libvirt 1.2.9 and vdsm must include the patch bellow. These requirement are not enforced in vdsm spec yet. If we do, then this fix _must_ be included in 3.5.2: https://gerrit.ovirt.org/38201 vm: Fix LSM when using libvirt = 1.2.8 Please mark the relevant bug as a blocker of the 3.5.2 tracker. That would make sure we don't release without it. Added Nir ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] hosted-engine : how to shutdown hosts?
Hi, just a minor problem I guess: I have a small test environment with 2 hosts and a hosted engine on a separate NFS3 share, all running CentOS7. The VMs are running from an iSCSI storage. When I want to shutdown the environment I: - shutdown VMs - enable global maintenance mode - shutdown -h now on the hosted engine vm - shutdown -h now on the hosts The problem: instead of shutting down, the hosts perform a reboot after a short while. Is this the expected behaviour or a known bug? How can I cleanly shutdown my OVirt-environment? Thank you, Uwe ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] DevConf talks about oVirt and Foreman integration
Hey guys, Apparently DevConf uploaded records for my sessions last month at devConf, you are welcome to check that out https://www.youtube.com/watch?v=XmF6kV73XRY https://www.youtube.com/watch?v=D0nitrAKToMspfreload=1 As users you probably familiar with most of what I say there, especially in the general overview, but it's still good for refreshment if you have spare 40 minutes.. jump directly to minute 5-7 Regards, -- Yaniv Bronhaim. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] ipv6 export domain (was: Can't put export/iso domain in maintenance mode)
- Original Message - From: Nathanaël Blanchet blanc...@abes.fr To: users@ovirt.org Sent: Friday, February 27, 2015 7:22:38 PM Subject: Re: [ovirt-users] Can't put export/iso domain in maintenance mode I found the issue, all my el7 hosts were blocking in resolving ipv6 fqdn. I deactivated ipv6 with sysctl -w net.ipv6.conf.all.disable_ipv6 = 1 and all my troubles have gone away (sysctl -w net.ipv6.conf.all.disable_ipv6 = 1 in sysctl.conf for persistent effect) Thanks for the report! I have a question reslating to this : why does el7 hosts deal with ipv6 in ovirt? otopi should deactivate it at the installation step, shouldn't it? Why? I didn't try ipv6 with ovirt but a quick search shows it seems to be at least partially working. If the above-mentioned blocking was due to default conf/setup, it's probably a bug. Le 27/02/2015 15:59, Nathanaël Blanchet a écrit : Hi all, I use the same export domain for two different datacenter and I can't anymore put it in a maintenance mode so as to detach it for reattaching to the second datacenter. It says Preparing for maintenance and it stays in that state with no ending. Is this operation supposed to be long before being able to detach the datacenter? ___ 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 Best regards, -- Didi ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] hosted-engine : how to shutdown hosts?
- Original Message - From: Uwe Laverenz u...@laverenz.de To: users@ovirt.org Sent: Saturday, February 28, 2015 3:41:55 PM Subject: [ovirt-users] hosted-engine : how to shutdown hosts? Hi, just a minor problem I guess: I have a small test environment with 2 hosts and a hosted engine on a separate NFS3 share, all running CentOS7. The VMs are running from an iSCSI storage. When I want to shutdown the environment I: - shutdown VMs - enable global maintenance mode - shutdown -h now on the hosted engine vm - shutdown -h now on the hosts The problem: instead of shutting down, the hosts perform a reboot after a short while. The hosts? Did you look at their console and see that they actually reboot after a short while? Or perhaps they do not shutdown at all and reboot instead? Is this the expected behaviour or a known bug? How can I cleanly shutdown my OVirt-environment? I think that before shutting down a host you should move it to local maintenance. Not sure, however, how it was started back. Please try and report back. Thanks! Also: Do you have fencing enabled? You wrote 'shutdown -h now on the hosts'. What happens if you shutdown just one of them and then wait a bit? Does it get started too? Are you certain that 'shutdown -h now' worked on these hosts before the setup - that it's not some kernel/bios/etc issue? Best, -- Didi ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
