[QE][ACTION REQUIRED] oVirt 3.6.0 status
Hi, We planned to start composing next milestone of oVirt 3.6.0 on *2015-10-12 08:00 UTC* from 3.6 branches. There are still 234 bugs [1] targeted to 3.6.0. Whiteboard RC GA Total docs 5 0 15 dwh 1 0 1 external 0 1 1 gluster 40 0 40 i18n 2 0 2 infra 23 6 29 integration 0 1 1 network 27 1 28 node 4 0 4 reports 1 0 1 sla 36 2 38 storage 49 9 58 ux 10 0 10 virt 5 1 6 Total 213 21 234 Maintainers must scrub them and push non critical bugs to ZStream releases. There is 1 acknowledged blocker for 3.6.0: Bug 1196640 - [Monitoring] Network utilisation is not shown for the VM And there are 21 bugs suggested as blockers for 3.6.0: Bug ID Status Whiteboard Summary 1259441 NEW gluster Can't create new Gluster storage domain - Permission denied 1261822 NEW integration BUILD WGT 3.6 1259468 NEW network Setupnetworks fails from time to time with error 'Failed to bring interface up' 1262026 NEW network Host booted up after upgrading it 3.5.4->3.6 with rhevm bridge with DEFROUTE=no. 1262051 NEW network Host move from 'up' to 'connecting' and back to 'up' from time to time 1243811 POST sla vm with dedicate host fails to run on other host, if dedicated host is in maintenance 1262293 POST sla Creating a VM with Foreman fails if cluster has more than one CPU profile 1239297 ASSIGNED storage Logical disk name is not showing up 1118349 NEW storage [vdsm] Creating DataCenter 3.5 using master domain V1 fails with InquireNotSupportedError 1250540 NEW storage Re-attaching fresh export domain fails - hsm::2543::Storage.HSM::(disconnectStorageServer) Could not disconnect from storageServer 1253790 NEW storage [BLOCKED] consume fix for "iscsi_session recovery_tmo revert back to default when a path becomes active" 1253975 NEW storage [vdsm] extendVolumeSize task is not cleared in case of a live merge failure for a volume that was extended 1151838 NEW storage [vdsm] Scan alignment fails with a VirtAlignError 1238239 NEW storage Deployment of hosted engine failed on ISCSI storage with 'Error block device action' 1257240 NEW storage Template's disk format is wrong 1261953 NEW storage [vdsm] Host fails to connect to storage pool 'MiscBlockReadException: Internal block device read failure' 1261980 NEW storage failed LSM due to connection lost with qemu process 1138144 NEW storage [BLOCKED]Failed to autorecover storage domain after unblocking connection with host 1253756 POST storage [BLOCKED] libvirt reports physical=0 for COW2 volumes on block storage 1251008 POST storage [BLOCKED] libvirt reports physical=0 for COW2 volumes on block storage 1258901 POST storage [UX] Toggling wad property while vm is up shouldn't be greyed out There are 17 bugs marked as regressions to be solved in 3.6.0 [2] Given current bugs status, release criteria are not met [3] so we need to review bug status for planning the RC. Action items: - Developers: check suggested blockers, fix acknowledged blockers, regressions and re-target remaining blockers. - Please check Jenkins status for 3.6 jobs and sync with relevant maintainers if there are issues. - Please fill release notes, the page has been created here [4] - Please test oVirt 3.6 nightly snapshot and check for regressions from 3.5 [1] https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_milestone%3Aovirt... status%3Anew%2Cassigned%2Cpost [2] https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_milestone%3Aovirt... [3] http://www.ovirt.org/OVirt_3.6_Release_Management#Candidate_Release_Criteria [4] http://www.ovirt.org/OVirt_3.6_Release_Notes -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
On Thu, Oct 01, 2015 at 02:44:50PM +0200, Sandro Bonazzola wrote:
Hi, We planned to start composing next milestone of oVirt 3.6.0 on *2015-10-12 08:00 UTC* from 3.6 branches.
There are still 234 bugs [1] targeted to 3.6.0.
Whiteboard RC GA Total docs 5 0 15 dwh 1 0 1 external 0 1 1 gluster 40 0 40 i18n 2 0 2 infra 23 6 29 integration 0 1 1 network 27 1 28 node 4 0 4 reports 1 0 1 sla 36 2 38 storage 49 9 58 ux 10 0 10 virt 5 1 6 Total 213 21 234
Maintainers must scrub them and push non critical bugs to ZStream releases.
There is 1 acknowledged blocker for 3.6.0: Bug 1196640 - [Monitoring] Network utilisation is not shown for the VM
The patch solving this bug has been merged to the ovirt-3.6.0 two days ago, and would be part of an rc2 build of ovirt-engine. Until our bugzilla bots are functional again, developers are asked to pet their bugs more often, and move the MODIFIED after merge. Marcin, can you tend to this bug?
And there are 21 bugs suggested as blockers for 3.6.0:
1259468 NEW network Setupnetworks fails from time to time with error 'Failed to bring interface up'
Annoys automated QA, but not seen in manual checks. I'm not sure it should block ovirt-3.6.0. I'd love to hear if a lot of ovirt users use automated scripts with no retries to setup host networking.
1262026 NEW network Host booted up after upgrading it 3.5.4->3.6 with rhevm bridge with DEFROUTE=no.
May cause a lot of pain if proven real. However, initial attempts did not reproduce. Have any rc-tester bumped into something like that?
1262051 NEW network Host move from 'up' to 'connecting' and back to 'up' from time to time
I'm not sure that this is a release blocker, even though it is a regression.
Action items: - Developers: check suggested blockers, fix acknowledged blockers, regressions and re-target remaining blockers. - Please check Jenkins status for 3.6 jobs and sync with relevant maintainers if there are issues. - Please fill release notes, the page has been created here [4] - Please test oVirt 3.6 nightly snapshot and check for regressions from 3.5
[1] https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_milestone%3Aovirt... status%3Anew%2Cassigned%2Cpost [2] https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_milestone%3Aovirt... [3] http://www.ovirt.org/OVirt_3.6_Release_Management#Candidate_Release_Criteria [4] http://www.ovirt.org/OVirt_3.6_Release_Notes
On 02.10.2015 13:19, Dan Kenigsberg wrote:
Annoys automated QA, but not seen in manual checks. I'm not sure it should block ovirt-3.6.0. I'd love to hear if a lot of ovirt users use automated scripts with no retries to setup host networking.
Yes, of course I do. And I don't see a reason to retry a failed automatic setup automatically. this way lies madness. kind regards Sven
On Sun, Oct 04, 2015 at 02:37:35PM +0200, Sven Kieske wrote:
On 02.10.2015 13:19, Dan Kenigsberg wrote:
Annoys automated QA, but not seen in manual checks. I'm not sure it should block ovirt-3.6.0. I'd love to hear if a lot of ovirt users use automated scripts with no retries to setup host networking.
Yes, of course I do.
And I don't see a reason to retry a failed automatic setup automatically. this way lies madness.
Point taken!
Hi, we think this bug is caused by systemd bug [1], which was solved in systemd v220, unfortunately, this version is not available for EL7. As soon as we proof the issue, we should ask systemd guys for backporting the solution. [1] https://bugs.freedesktop.org/show_bug.cgi?id=86520 2015-10-06 15:11 GMT+02:00 Dan Kenigsberg <danken@redhat.com>:
On Sun, Oct 04, 2015 at 02:37:35PM +0200, Sven Kieske wrote:
On 02.10.2015 13:19, Dan Kenigsberg wrote:
Annoys automated QA, but not seen in manual checks. I'm not sure it should block ovirt-3.6.0. I'd love to hear if a lot of ovirt users use automated scripts with no retries to setup host networking.
Yes, of course I do.
And I don't see a reason to retry a failed automatic setup automatically. this way lies madness.
Point taken! _______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
participants (4)
-
Dan Kenigsberg -
Petr Horacek -
Sandro Bonazzola -
Sven Kieske