[ovirt-users] [QE][ACTION REQUIRED] oVirt 3.5.0 status - Go / No Go

Wed Oct 1 07:23:32 UTC 2014


----- Original Message -----
> From: "Sandro Bonazzola" <sbonazzo at redhat.com>
> To: Users at ovirt.org, devel at ovirt.org
> Sent: Tuesday, September 30, 2014 5:46:15 PM
> Subject: Re: [ovirt-users] [QE][ACTION REQUIRED] oVirt 3.5.0 status - Go /	No Go
> 
> Il 29/09/2014 08:34, Sandro Bonazzola ha scritto:
> > Hi,
> > We were supposed to start composing oVirt 3.5.0 GA today 2014-09-29 but we
> > still have 3 blockers.
> > 
> > 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 GA release please raise the issue as soon as
> > possible.
> > - If any packages need a rebase please raise the issue as soon as possible.
> > - Be aware that packages that doesn't need a rebase must be re-built with
> > final release versioning from the RC3 tag.
> > - Please provide ETA for new blockers for rescheduling an RC4 and a GA
> > release.
> > 
> > The bug tracker [1] shows 3 blockers:
> > Bug ID	Whiteboard	Status	Summary
> > 1147085	storage		POST	Memory volumes not deleted when removing a vm with
> > snapshots
> > 1146073	sla		POST	Failing to Attach a Storage Domain without Disk Profiles
> > to a Data Center 3.5
> > 1127460	storage		NEW	VM abnormal stop after LV refreshing when using thin
> > provisioning on block storage
> 
> Today we have:
> Bug ID	Whiteboard	Status	Summary
> 1127460	storage		POST	VM abnormal stop after LV refreshing when using thin
> provisioning on block storage
The proposed VDSM patch should work, but it does not resolve the situation properly wrt selinux.
A proper fix should be provided to the underlying layers (see BZ 1147923 for EL and BZ 1147910 for Fedora).
I'd like to hear more voices here, but IMHO, not supporting enabled selinux envs on EL7/F20 is a no-go for GA.

> 1147971	storage		NEW	Snapshot locked after successful live storage migration
This bug requires two (simple) patches, both of which are acked and verified on upstream/master.
I think they can be backported and merged by EOD, unless Daniel or Ravi (the respective patch authors) see a problem I don't.

> 
> ETA?
> 
> 
> 
> 
> > 
> > The following bugs are keyworded as Regression and not marked as
> > blockers[10]
> > 
> > Bug ID	Whiteboard	Status	Summary
> > 1142647	gluster		NEW	supervdsm leaks memory when using glusterfs
> > 1138144	storage		NEW	Failed to autorecover storage domain after unblocking
> > connection with host
We're unable to confirm this issue (seems as though it's caused by a bug that was there since 3.1, at least).
It's targeted for 3.5.1, and should not block the GA.

> > 1147085	storage		POST	Memory volumes not deleted when removing a vm with
> > snapshots
This is already MODIFIED.

> > 1118349	storage		NEW	[vdsm] Creating DataCenter 3.5 using master domain V1
> > fails with InquireNotSupportedError
This is an edge case of an edge case.
Although this technically is a regression, there's no real-world situation that would lead to this, 
and it should not block 3.5.0

> > 
> > 
> > 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 69 bugs [3] targeted to 3.5.0.
> > Excluding node and documentation bugs we still have 46 bugs [4] targeted to
> > 3.5.0.
> > 
> > More in detail [5]:
> > 
> > Whiteboard	NEW	ASSIGNED	POST	Total
> > docs		13	1		0	14
> > gluster		4	0		2	6
> > i18n		0	0		1	1
> > infra		1	0		0	1
> > integration	0	0		1	1
> > node		9	4		0	13
> > ppc		2	0		4	6
> > sla		10	0		3	13
> > storage		2	1		3	6
I did some scrubbing here. The only two remaining storage issues are the ones mentioned above, that are indeed blockers.

> > virt		3	1		4	8
> > Total		44	7		18	69
> > 
> > 
> > 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 results from Third Test Day on the etherpad [7] and on the
> > mailing lists
> > - 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:
> > - You're welcome to join us testing last release candidate or nightly
> > builds and getting involved in oVirt Quality Assurance[8]
> > 
> > [1] http://bugzilla.redhat.com/1073943
> > [2] http://goo.gl/4SuYdE
> > [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://etherpad.ovirt.org/p/3.5-testday-3
> > [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 at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>