[Users] [QE] 3.3.2 Release tracker
sbonazzo at redhat.com
Wed Nov 6 16:11:10 UTC 2013
as you may know, we're planning to build oVirt 3.3.2 beta really soon and release 3.3.2 by early December.
I have created a tracker bug (https://bugzilla.redhat.com/show_bug.cgi?id=1027349) for this release.
Beta build will be composed in 2 weeks.
The following is a list of the bugs with target 3.3.2 or 3.3:
Whiteboard Bug ID Summary
infra 987982 When adding a host through the REST API, the error message says that "rootPassword" is required...
infra 1017267 Plaintext user passwords in async_tasks database
infra 992883 VdsManager.OnTimer loads VDS instead of VdsDynamic
infra 1020344 Power Managent with cisco_ucs problem
infra 1009899 exportDbSchema scripts generates output file with wrong name
integration 1022440 AIO - configure the AIO host to be a gluster cluster/host
integration 1026926 engine-cleanup (and possible engine-setup) does not affect runtime value of shmmax
integration 902979 ovirt-live - firefox doesn't trust the installed engine
integration 1021805 oVirt Live - use motd to show the admin password
network 1019818 Support OpenStack Havana layer 2 agent integration
network 988002 [oVirt] [network] Add button shouldn't appear on specific network
network 987916 [oVirt] [provider] Dialog doesn't update unless focus lost
network 987999 [oVirt] [provider] Add button shouldn't appear on specific provider
storage 915753 Deadlock detected during creation vms in pool
storage 987917 [oVirt] [glance] API version not specified in provider dialog
storage 1024449 Check the performance with lvm-2.02.100-7
virt 1007940 Cannot clone from snapshot while using GlusterFS as POSIX Storage Domain
? 991267 [RFE] Add TUI information to log file.
Please set the target to 3.3.2 and add the bug to the tracker if you think that 3.3.2 should not be released without it fixed.
Please also update the target to 3.3.3 or any next release for bugs that won't be in 3.3.2: it will ease gathering the blocking bugs for next releases.
For those who want to help testing the bugs, I suggest to add yourself as QA contact for the bug.
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
More information about the Users