Hi, We were supposed to start composing oVirt 3.5.0 RC2 today from 3.5 branch, however we still have blockers open so we should postpone the build. In order to re-schedule the build I need ETA on the open blockers, please provide it.
Maintainers: - Please be sure that 3.5 snapshot satisfy release criteria[9] - Please be sure that no pending patches are going to block the release - If any patch must block the RC release please raise the issue as soon as possible. The bug tracker [1] shows the following proposed blockers to be reviewed: Bug ID Whiteboard Status Summary 1138986 infra NEW UploadStreamVDSCommand fails using JsonRpc 1136843 network NEW NetworkManager ifups VDSM's dummy bond 1138731 network NEW firewall-cmd gets stuck when run as superVDSM subsubprocess 1138340 sla NEW vdsm relies on unsupported 'min_guarantee' VM configuration parameter 1129261 sla POST prepareImage api call fails with [Errno 2] No such file or directory And the following dependencies still open: Bug 1041569 - [NFR] libvirt: Returning the watermark for all the images opened for writing Bug 1102881 - virDomainBlockCommit fails with live snapshots on oVirt block storage The following bugs are keyworded as Regression and not marked as blockers[10] Bug ID Whiteboard Status Summary 1138983 NEW [CLI] Update template is not actually updating template. 1106435 infra NEW [AAA] builtin kerbldap provider does not show error if search fails 1138981 network POST no validation before calling to AddSubnetToProvider 1136895 network NEW Import VmTemplate fails 1116572 storage NEW [engine-backend] Storage domain activation isn't executed as part of storage domain creation 1138144 storage NEW Failed to autorecover storage domain after unblocking connection with host 1110444 ux POST bookmark selection does not work on first try 1133995 virt POST vm name field is misaligned on "new vm" pop up window 1138564 virt NEW Cloud-init files are ignored 1138314 virt NEW Fail to start vm with payload. Feature freeze is now effective, and branch has been created. All new patches must be backported to 3.5 branch too. Features completed are marked in green on Features Status Table [2] There are still 177 bugs [3] targeted to 3.5.0. Excluding node and documentation bugs we still have 148 bugs [4] targeted to 3.5.0. More in detail [5]: Whiteboard NEW ASSIGNED POST Total <unassigned> 8 1 0 9 gluster 10 4 1 15 i18n 0 0 1 1 infra 10 1 6 17 integration 6 2 3 11 network 4 1 9 14 node 12 4 4 20 ppc 2 0 4 6 sla 5 0 11 16 storage 18 3 5 26 ux 16 2 3 21 virt 10 2 9 21 Total 101 20 56 177 Maintainers / Assignee: - Please ensure that completed features are marked in green on Features Status Table [2] - If you find a blocker bug please remember to add it to the tracker [1] - Please fill release notes, the page has been created here [6] - Please review and add test cases to oVirt 3.5 Third Test Day [7] - Please update the target to 3.5.1 or later for bugs that won't be in 3.5.0: it will ease gathering the blocking bugs for next releases. Community: - Due to the RC2 delay, the 3rd test day will be postponed, new date will be decided once ETA for closing current blockers is known. - You're welcome to join us testing next release candidate and getting involved in oVirt Quality Assurance[8] [1] http://bugzilla.redhat.com/1073943 [2] http://bit.ly/17qBn6F [3] http://red.ht/1pVEk7H [4] http://red.ht/1zT2mSq [5] http://red.ht/1q7SqNL [6] http://www.ovirt.org/OVirt_3.5_Release_Notes [7] http://www.ovirt.org/OVirt_3.5_TestDay [8] http://www.ovirt.org/OVirt_Quality_Assurance [9] http://www.ovirt.org/OVirt_3.5_release-management#Release_Criteria_.28WIP.29 [10] http://goo.gl/uavikG Thanks, -- 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
