[Users] [QE] oVirt 3.3.2 beta status
Hi, we're going to branch and build oVirt 3.3.2 beta TODAY. A bug tracker is available at [1] and it shows only 3 bugs still blocking the release: Whiteboard Bug ID Summary storage 1022961 Running a VM from a gluster domain uses mount instead of gluster URI virt 1025829 sysprep floppy is not attached to Windows 2008 R2 machine - even when specifically checked in Run Once virt 1029885 cloud-init testcase does not work in engine 3.3.1 Please provide an ETA for the above bugs. The following is a list of the non-blocking bugs still open with target 3.3.2: Whiteboard Bug ID Summary infra 1017267 Plaintext user passwords in async_tasks database infra 987982 When adding a host through the REST API, the error message says that "rootPassword" is required,... infra 1020344 Power Managent with cisco_ucs problem integration 1022440 AIO - configure the AIO host to be a gluster cluster/host integration 902979 ovirt-live - firefox doesn't trust the installed engine integration 1021805 oVirt Live - use motd to show the admin password integration 1026930 Package virtio-win and put it in ovirt repositories integration 1026933 pre-populate ISO domain with virtio-win ISO network 1019818 Support OpenStack Havana layer 2 agent integration network 987999 [oVirt] [provider] Add button shouldn't appear on specific provider network 987916 [oVirt] [provider] Dialog doesn't update unless focus lost network 906313 [oVirt-webadmin] [setupNetworks] "No valid Operation for <network_name> and Unassigned Logical Networks panel" network 1023722 [oVirt-webadmin][network] Network roles in cluster management should be radio buttons network 997197 Some AppErrors messages are grammatically incorrect (singular vs plural) storage 1029069 Live storage migration snapshot removal fails, probably due to unexpected qemu-img output storage 987917 [oVirt] [glance] API version not specified in provider dialog storage 1016118 async between masterVersion : can't connect to StoragePool ux 906394 [oVirt-webadmin] [network] Loading animation in network main tab 'hosts' and 'vms' subtab is stuck on first view... virt 1007940 Cannot clone from snapshot while using GlusterFS as POSIX Storage Domain Please add the bugs to the tracker if you think that 3.3.2 should not be released without them fixed. For those who want to help testing the bugs, I suggest to add yourself as QA contact for the bug and add yourself to the testing page [2]. Maintainers are welcomed to start filling release notes, the page has been created here [3] [1] https://bugzilla.redhat.com/1027349 [2] http://www.ovirt.org/Testing/Ovirt_3.3.2_testing [3] http://www.ovirt.org/OVirt_3.3.2_release_notes Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
On Nov 27, 2013, at 11:29 , Sandro Bonazzola <sbonazzo@redhat.com> wrote:
Hi,
we're going to branch and build oVirt 3.3.2 beta TODAY. A bug tracker is available at [1] and it shows only 3 bugs still blocking the release:
Whiteboard Bug ID Summary storage 1022961 Running a VM from a gluster domain uses mount instead of gluster URI virt 1025829 sysprep floppy is not attached to Windows 2008 R2 machine - even when specifically checked in Run Once
hopefully end of week we will know more. Should not be hard though
virt 1029885 cloud-init testcase does not work in engine 3.3.1
this is about current CentOS containing a quite dated version of cloud-init. There's little we can do except encourage people to build/use 0.7.2+ Awaiting reporter's feedback Thanks, michal
Please provide an ETA for the above bugs.
The following is a list of the non-blocking bugs still open with target 3.3.2:
Whiteboard Bug ID Summary infra 1017267 Plaintext user passwords in async_tasks database infra 987982 When adding a host through the REST API, the error message says that "rootPassword" is required,... infra 1020344 Power Managent with cisco_ucs problem integration 1022440 AIO - configure the AIO host to be a gluster cluster/host integration 902979 ovirt-live - firefox doesn't trust the installed engine integration 1021805 oVirt Live - use motd to show the admin password integration 1026930 Package virtio-win and put it in ovirt repositories integration 1026933 pre-populate ISO domain with virtio-win ISO network 1019818 Support OpenStack Havana layer 2 agent integration network 987999 [oVirt] [provider] Add button shouldn't appear on specific provider network 987916 [oVirt] [provider] Dialog doesn't update unless focus lost network 906313 [oVirt-webadmin] [setupNetworks] "No valid Operation for <network_name> and Unassigned Logical Networks panel" network 1023722 [oVirt-webadmin][network] Network roles in cluster management should be radio buttons network 997197 Some AppErrors messages are grammatically incorrect (singular vs plural) storage 1029069 Live storage migration snapshot removal fails, probably due to unexpected qemu-img output storage 987917 [oVirt] [glance] API version not specified in provider dialog storage 1016118 async between masterVersion : can't connect to StoragePool ux 906394 [oVirt-webadmin] [network] Loading animation in network main tab 'hosts' and 'vms' subtab is stuck on first view... virt 1007940 Cannot clone from snapshot while using GlusterFS as POSIX Storage Domain
Please add the bugs to the tracker if you think that 3.3.2 should not be released without them fixed.
For those who want to help testing the bugs, I suggest to add yourself as QA contact for the bug and add yourself to the testing page [2].
Maintainers are welcomed to start filling release notes, the page has been created here [3]
[1] https://bugzilla.redhat.com/1027349 [2] http://www.ovirt.org/Testing/Ovirt_3.3.2_testing [3] http://www.ovirt.org/OVirt_3.3.2_release_notes
Thanks,
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com _______________________________________________ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
On 11/27/2013 05:42 PM, Michal Skrivanek wrote:
virt 1029885 cloud-init testcase does not work in engine 3.3.1 this is about current CentOS containing a quite dated version of cloud-init. There's little we can do except encourage people to build/use 0.7.2+ Awaiting reporter's feedback
as rhel 6.5 GA'd and has these properly, shouldn't be an issue, and should be in CentOS 6.5 as well.
[resent, accidentally took out the list] On Nov 28, 2013, at 08:30 , Itamar Heim <iheim@redhat.com> wrote:
On 11/27/2013 05:42 PM, Michal Skrivanek wrote:
virt 1029885 cloud-init testcase does not work in engine 3.3.1 this is about current CentOS containing a quite dated version of cloud-init. There's little we can do except encourage people to build/use 0.7.2+ Awaiting reporter's feedback
as rhel 6.5 GA'd and has these properly, shouldn't be an issue, and should be in CentOS 6.5 as well.
Yes, but this still leaves older guests without a solution. Maybe we should really push for virt-sysprep as it is much more mature in sense of legacy compatibility, nothing extra needed inside the guest. At least a simple passthrough of some basic stuff (we have only a basic stuff in cloud-init anyway). It's slightly different approcha than cloud-init, but may be really worth it even long term...
Am 28.11.2013 11:10, schrieb Michal Skrivanek:
[resent, accidentally took out the list]
On Nov 28, 2013, at 08:30 , Itamar Heim <iheim@redhat.com> wrote:
On 11/27/2013 05:42 PM, Michal Skrivanek wrote:
virt 1029885 cloud-init testcase does not work in engine 3.3.1 this is about current CentOS containing a quite dated version of cloud-init. There's little we can do except encourage people to build/use 0.7.2+ Awaiting reporter's feedback
as rhel 6.5 GA'd and has these properly, shouldn't be an issue, and should be in CentOS 6.5 as well.
Yes, but this still leaves older guests without a solution. Maybe we should really push for virt-sysprep as it is much more mature in sense of legacy compatibility, nothing extra needed inside the guest. At least a simple passthrough of some basic stuff (we have only a basic stuff in cloud-init anyway). It's slightly different approcha than cloud-init, but may be really worth it even long term...
Well, I reported the cloud-init bug. atm I write a helper script to parse the cloud-init data myself. virt-sysprep cannot set IP-Information beside the MAC out of the box, so this is also no solution. I feel like there must be made some huge efforts to be able to automate vm deployment. I can't believe I'm the only one who needs this features. how do you deploy vms? set everything up by hand? do you always install $latest_OS_version with selfcompiled software? that's not always possible, especially for production environments. See also my other mail regarding IPv6 Support in Cloud-Init and no proper static networking support. -- Mit freundlichen Grüßen / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH & Co. KG Königsberger Straße 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Geschäftsführer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen
On 11/28/2013 12:31 PM, Sven Kieske wrote:
Am 28.11.2013 11:10, schrieb Michal Skrivanek:
[resent, accidentally took out the list]
On Nov 28, 2013, at 08:30 , Itamar Heim <iheim@redhat.com> wrote:
On 11/27/2013 05:42 PM, Michal Skrivanek wrote:
virt 1029885 cloud-init testcase does not work in engine 3.3.1 this is about current CentOS containing a quite dated version of cloud-init. There's little we can do except encourage people to build/use 0.7.2+ Awaiting reporter's feedback
as rhel 6.5 GA'd and has these properly, shouldn't be an issue, and should be in CentOS 6.5 as well.
Yes, but this still leaves older guests without a solution. Maybe we should really push for virt-sysprep as it is much more mature in sense of legacy compatibility, nothing extra needed inside the guest. At least a simple passthrough of some basic stuff (we have only a basic stuff in cloud-init anyway). It's slightly different approcha than cloud-init, but may be really worth it even long term...
Well, I reported the cloud-init bug.
atm I write a helper script to parse the cloud-init data myself.
virt-sysprep cannot set IP-Information beside the MAC out of the box, so this is also no solution.
I feel like there must be made some huge efforts to be able to automate vm deployment.
I can't believe I'm the only one who needs this features. how do you deploy vms? set everything up by hand? do you always install $latest_OS_version with selfcompiled software?
I expect most use dhcp for ip management, rather than allocate them. or provision from tools like foreman, that orchestrate the mac/ip association for the provisioned vm. cloud-init solves other interesting problems as well, like setting the ssh key for root access.
that's not always possible, especially for production environments.
See also my other mail regarding IPv6 Support in Cloud-Init and no proper static networking support.
for el6 guests, i think using cloud-init based on the rhel 6.5 versions should work now?
participants (4)
-
Itamar Heim -
Michal Skrivanek -
Sandro Bonazzola -
Sven Kieske