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

2014-10-09 Thread Sandro Bonazzola
Il 09/10/2014 11:01, Sandro Bonazzola ha scritto:
> Hi,
> We are going to start composing oVirt 3.5.0 RC5 today 2014-10-09 as soon as 
> the ovirt-engine package finish to build.
> 
> The bug tracker [1] shows no blockers:

Due to a new blocker (Bug 1150555 - ovirt-engine webpages aren't showing 
correctly) RC5 will be delayed until the bug will be fixed.


> The bugs keyworded as Regression have been reviewed by maintainers and not 
> marked as blockers[4]
> Features completed are marked in green on Features Status Table [2]
> 
> There are still 34 bugs [3] targeted to 3.5.0 which will be moved 
> automatically to 3.5.1 once the build will be released.
> 
> Maintainers / Assignee:
> If you're aware of something that should block the release, please raise it 
> as soon as possible.
> 
> [1] http://bugzilla.redhat.com/1073943
> [2] http://goo.gl/4SuYdE
> [3] http://red.ht/1pVEk7H
> [4] 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


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

2014-10-09 Thread Sandro Bonazzola
Hi,
We are going to start composing oVirt 3.5.0 RC5 today 2014-10-09 as soon as the 
ovirt-engine package finish to build.

The bug tracker [1] shows no blockers:
The bugs keyworded as Regression have been reviewed by maintainers and not 
marked as blockers[4]
Features completed are marked in green on Features Status Table [2]

There are still 34 bugs [3] targeted to 3.5.0 which will be moved automatically 
to 3.5.1 once the build will be released.

Maintainers / Assignee:
If you're aware of something that should block the release, please raise it as 
soon as possible.

[1] http://bugzilla.redhat.com/1073943
[2] http://goo.gl/4SuYdE
[3] http://red.ht/1pVEk7H
[4] 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


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

2014-10-07 Thread Sandro Bonazzola
Hi,
We started composing oVirt 3.5.0 GA yesterday 2014-10-06 and we finished 
collecting rpms this morning.
While we would have liked to be able to release it, bugzilla shows 2 new fresh 
blockers, so it's another No Go.

The bug tracker [1] shows 2 blockers:

Bug ID  Whiteboard  Status  Summary
1149637 virtASSIGNEDCannot start VM with attached ISO
1149705 storage NEW VM abnormal stop after LV refreshing 
when using thin provisioning on block storage

This means a RC5 build will be issued once the above 2 bugs will be fixed and 
GA will follow after testing.
Please provide an ETA for above bugs.

The bugs keyworded as Regression have been reviewed by maintainers and not 
marked as blockers[4]
Features completed are marked in green on Features Status Table [2]

There are still 33 bugs [3] targeted to 3.5.0 which will be moved automatically 
to 3.5.1 once the build will be released.

Maintainers / Assignee:
If you're aware of something that should block the release, please raise it as 
soon as possible.

[1] http://bugzilla.redhat.com/1073943
[2] http://goo.gl/4SuYdE
[3] http://red.ht/1pVEk7H
[4] 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


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

2014-10-05 Thread Sandro Bonazzola
Hi,
We are going to start composing oVirt 3.5.0 GA today 2014-10-06 as soon as the 
ovirt-engine package finish to build.

The bug tracker [1] shows no blockers:
The bugs keyworded as Regression have been reviewed by maintainers and not 
marked as blockers[4]
Features completed are marked in green on Features Status Table [2]

There are still 34 bugs [3] targeted to 3.5.0 which will be moved automatically 
to 3.5.1 once the build will be released.

Maintainers / Assignee:
If you're aware of something that should block the release, please raise it as 
soon as possible.

[1] http://bugzilla.redhat.com/1073943
[2] http://goo.gl/4SuYdE
[3] http://red.ht/1pVEk7H
[4] 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


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

2014-10-01 Thread Sandro Bonazzola
Il 02/10/2014 00:53, Dan Kenigsberg ha scritto:
> On Tue, Sep 30, 2014 at 08:42:34PM -0400, Nir Soffer wrote:
>> - Original Message -
>>> From: "Sandro Bonazzola" 
>>> To: Users@ovirt.org, de...@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
>>>> 1147085storage POSTMemory volumes not deleted when 
>>>> removing a vm with
>>>> snapshots
>>>> 1146073sla POSTFailing to Attach a Storage Domain 
>>>> without Disk Profiles
>>>> to a Data Center 3.5
>>>> 1127460storage NEW VM abnormal stop after LV refreshing 
>>>> when using thin
>>>> provisioning on block storage
>>>
>>> Today we have:
>>> Bug ID  Whiteboard  Status  Summary
>>> 1127460 storage POSTVM abnormal stop after LV refreshing 
>>> when using thin
>>> provisioning on block storage
>>
>> Basically this is an issue with systemd, not with ovirt. However we have a 
>> workaround
>> that we can consume in the short term.
>>
>> Patch for RHEL7: http://gerrit.ovirt.org/33492
>>
>> We believe that we can get the real fix for the underlying component for 
>> Fedora quickly.
>> If not, we have a patch ready for enabling the workaround on Fedora.
>>
>> Patch for Fedora: http://http://gerrit.ovirt.org/33555
>>
>>> 1147971 storage NEW Snapshot locked after successful live 
>>> storage migration
>>
>> This is an ifra issue, handled by Ravi.
>>
>>> ETA?
>>
>> Dan?
> 
> We still have nasty selinux-related issues on el7, such as
> 
> 1142454 sanlock not allowed to send SIGTERM or SIGKILL signals
> 
> and surprizes with el6.6 beta
> 
> 1148467 Fail to start VM: libvirtError: Child quit during startup 
> handshake: Input/output error
> 1148432 vdsm fails to start if there is a virbr0 that's attached to 
> an interface
> 
> but I've tagged vdsm v4.16.6 for rc4. Sandro could you take a snapshot
> based on it? (We still have an issue building 3.5's vdsm on Fedora for
> ARM)
> 

Ok, I'll take it, 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


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

2014-10-01 Thread Dan Kenigsberg
On Tue, Sep 30, 2014 at 08:42:34PM -0400, Nir Soffer wrote:
> - Original Message -
> > From: "Sandro Bonazzola" 
> > To: Users@ovirt.org, de...@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 IDWhiteboard  Status  Summary
> > > 1147085   storage POSTMemory volumes not deleted when 
> > > removing a vm with
> > > snapshots
> > > 1146073   sla POSTFailing 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 POSTVM abnormal stop after LV refreshing 
> > when using thin
> > provisioning on block storage
> 
> Basically this is an issue with systemd, not with ovirt. However we have a 
> workaround
> that we can consume in the short term.
> 
> Patch for RHEL7: http://gerrit.ovirt.org/33492
> 
> We believe that we can get the real fix for the underlying component for 
> Fedora quickly.
> If not, we have a patch ready for enabling the workaround on Fedora.
> 
> Patch for Fedora: http://http://gerrit.ovirt.org/33555
> 
> > 1147971 storage NEW Snapshot locked after successful live 
> > storage migration
> 
> This is an ifra issue, handled by Ravi.
> 
> > ETA?
> 
> Dan?

We still have nasty selinux-related issues on el7, such as

1142454 sanlock not allowed to send SIGTERM or SIGKILL signals

and surprizes with el6.6 beta

1148467 Fail to start VM: libvirtError: Child quit during startup 
handshake: Input/output error
1148432 vdsm fails to start if there is a virbr0 that's attached to an 
interface

but I've tagged vdsm v4.16.6 for rc4. Sandro could you take a snapshot
based on it? (We still have an issue building 3.5's vdsm on Fedora for
ARM)
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


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

2014-10-01 Thread Allon Mureinik


- Original Message -
> From: "Sandro Bonazzola" 
> To: Users@ovirt.org, de...@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 POSTMemory volumes not deleted when 
> > removing a vm with
> > snapshots
> > 1146073 sla POSTFailing 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 IDWhiteboard  Status  Summary
> 1127460   storage POSTVM 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 POSTMemory 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 ASSIGNEDPOSTTotal
> > docs13  1   0   14
> > gluster 4   0   2   6
> > i18n0   0   1   1
> > infra   1   0   0   1
> > integration 0   0   1   1
> > node9   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.

> > virt3   1   4   8
> > Total   44  7   18  69
> > 
> > 
> > Maintainers / Assignee:
&

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

2014-09-30 Thread Sandro Bonazzola
Il 01/10/2014 02:42, Nir Soffer ha scritto:
> - Original Message -
>> From: "Sandro Bonazzola" 
>> To: Users@ovirt.org, de...@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 POSTMemory volumes not deleted when 
>>> removing a vm with
>>> snapshots
>>> 1146073 sla POSTFailing 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 POSTVM abnormal stop after LV refreshing 
>> when using thin
>> provisioning on block storage
> 
> Basically this is an issue with systemd, not with ovirt. However we have a 
> workaround
> that we can consume in the short term.
> 
> Patch for RHEL7: http://gerrit.ovirt.org/33492
> 
> We believe that we can get the real fix for the underlying component for 
> Fedora quickly.
> If not, we have a patch ready for enabling the workaround on Fedora.
> 
> Patch for Fedora: http://http://gerrit.ovirt.org/33555

Just to be sure, what happens if the workaround is in place and the fix on 
systemd is provided?
If everything still continue to work, please merge both patches on 3.5 and move 
the bug to modified so we can try to start composing RC4 as soon as
the following is closed too:

> 
>> 1147971  storage NEW Snapshot locked after successful live 
>> storage migration
> 
> This is an ifra issue, handled by Ravi.
> 
>> ETA?
> 
> Dan?

I've seen it has been moved to POST and infra. Can we get it verified and moved 
to modified in a couple of hours?


> 
> Nir
> 


-- 
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


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

2014-09-30 Thread Nir Soffer
- Original Message -
> From: "Sandro Bonazzola" 
> To: Users@ovirt.org, de...@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 POSTMemory volumes not deleted when 
> > removing a vm with
> > snapshots
> > 1146073 sla POSTFailing 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 IDWhiteboard  Status  Summary
> 1127460   storage POSTVM abnormal stop after LV refreshing 
> when using thin
> provisioning on block storage

Basically this is an issue with systemd, not with ovirt. However we have a 
workaround
that we can consume in the short term.

Patch for RHEL7: http://gerrit.ovirt.org/33492

We believe that we can get the real fix for the underlying component for Fedora 
quickly.
If not, we have a patch ready for enabling the workaround on Fedora.

Patch for Fedora: http://http://gerrit.ovirt.org/33555

> 1147971   storage NEW Snapshot locked after successful live 
> storage migration

This is an ifra issue, handled by Ravi.

> ETA?

Dan?

Nir
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


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

2014-09-30 Thread Sandro Bonazzola
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 IDWhiteboard  Status  Summary
> 1147085   storage POSTMemory volumes not deleted when 
> removing a vm with snapshots
> 1146073   sla POSTFailing 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 POSTVM abnormal stop after LV refreshing when using 
thin provisioning on block storage
1147971 storage NEW Snapshot locked after successful live storage 
migration

ETA?




> 
> The following bugs are keyworded as Regression and not marked as blockers[10]
> 
> Bug IDWhiteboard  Status  Summary
> 1142647   gluster NEW supervdsm leaks memory when using 
> glusterfs
> 1138144   storage NEW Failed to autorecover storage domain 
> after unblocking connection with host
> 1147085   storage POSTMemory volumes not deleted when 
> removing a vm with snapshots
> 1118349   storage NEW [vdsm] Creating DataCenter 3.5 using 
> master domain V1 fails with InquireNotSupportedError
> 
> 
> 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]:
> 
> WhiteboardNEW ASSIGNEDPOSTTotal
> 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
> 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@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


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

2014-09-28 Thread Sandro Bonazzola
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 POSTMemory volumes not deleted when removing a vm 
with snapshots
1146073 sla POSTFailing 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

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
1147085 storage POSTMemory volumes not deleted when removing a vm 
with snapshots
1118349 storage NEW [vdsm] Creating DataCenter 3.5 using master 
domain V1 fails with InquireNotSupportedError


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 ASSIGNEDPOSTTotal
docs13  1   0   14
gluster 4   0   2   6
i18n0   0   1   1
infra   1   0   0   1
integration 0   0   1   1
node9   4   0   13
ppc 2   0   4   6
sla 10  0   3   13
storage 2   1   3   6
virt3   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@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


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

2014-09-26 Thread Sandro Bonazzola
Hi,
We are supposed to start composing oVirt 3.5.0 GA on Monday 2014-09-29.

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.

And then:
- Please build your packages with final release versioning for Monday 
2014-09-29 10:00 UTC if we agree on releasing GA.

The bug tracker [1] shows no blockers.

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
1118349 storage NEW [vdsm] Creating DataCenter 3.5 using master 
domain V1 fails with InquireNotSupportedError
1138314 virtPOSTFail 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 66 bugs [3] targeted to 3.5.0.
Excluding node and documentation bugs we still have 43 bugs [4] targeted to 
3.5.0.

More in detail [5]:

Whiteboard  NEW ASSIGNEDPOSTTotal
docs13  1   0   14
gluster 4   0   2   6
i18n0   0   1   1
infra   1   0   0   1
integration 0   0   1   1 (3.5.0 Tracker)
node8   4   0   12
ppc 2   0   4   6
sla 12  0   2   14
storage 1   0   2   3
virt3   1   4   8
Total   44  6   16  66



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@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


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

2014-09-22 Thread Oved Ourfali


- Original Message -
> From: "Sandro Bonazzola" 
> To: de...@ovirt.org, Users@ovirt.org
> Sent: Monday, September 22, 2014 9:38:13 AM
> Subject: [ovirt-users] [QE][ACTION REQUIRED] oVirt 3.5.0 status - Go / No Go
> 
> Hi,
> We are supposed to start composing oVirt 3.5.0 GA (or RC3, depending on this
> morning Go / No go Meeting decisions)
> I think we can use this email for discussing / voting 3.5.0 GA release.
> Looking at bugzilla status, I vote no go. I also think we should move the
> build to Wed allowing maintainers to fix pending 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 RC2 tag.
> 
> The bug tracker [1] shows the following proposed blockers to be reviewed:
> 
> Bug IDWhiteboard  Status  Summary
> 1143042   infra   POSTRepeated error "Failed to 
> create VM external-test" when
> starting new VM
> 1143860   infra   POSTMarshaling issue in fencing 
> policy using jsonrpc

I expect both infra issues to be merged by the end of the day.

> 1142256   integration NEW remote engine-reports-setup 
> does not write conf file
> to allow accessing reports from engine
> 1144079   integration ASSIGNEDlocal engine-reports-setup does 
> not write conf
> file to allow accessing reports from engine
> 
> The following bugs are keyworded as Regression and not marked as blockers[10]
> 
> Bug IDWhiteboard  Status  Summary
> 1142709   integration NEW Trying to deploy hosted-engine via 
> iSCSI device fails
> 1138144   storage NEW Failed to autorecover storage domain 
> after unblocking
> connection with host
> 1118349   storage NEW [vdsm] Creating DataCenter 3.5 using 
> master domain V1
> fails with InquireNotSupportedError
> 1138314   virtNEW 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 77 bugs [3] targeted to 3.5.0.
> Excluding node and documentation bugs we still have 53 bugs [4] targeted to
> 3.5.0.
> 
> More in detail [5]:
> 
> WhiteboardNEW ASSIGNEDPOSTTotal
> docs  13  1   0   14
> gluster   8   2   2   12
> i18n  0   0   1   1
> infra 1   0   3   4
> integration   1   2   1   4
> node  7   4   0   11
> ppc   2   0   4   6
> sla   12  0   7   19
> virt  3   0   3   6
> Total 47  9   21  77
> 
> 
> 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@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
> 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


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

2014-09-21 Thread Sandro Bonazzola
Hi,
We are supposed to start composing oVirt 3.5.0 GA (or RC3, depending on this 
morning Go / No go Meeting decisions)
I think we can use this email for discussing / voting 3.5.0 GA release.
Looking at bugzilla status, I vote no go. I also think we should move the build 
to Wed allowing maintainers to fix pending 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 RC2 tag.

The bug tracker [1] shows the following proposed blockers to be reviewed:

Bug ID  Whiteboard  Status  Summary
1143042 infra   POSTRepeated error "Failed to create VM 
external-test" when starting new VM
1143860 infra   POSTMarshaling issue in fencing policy 
using jsonrpc
1142256 integration NEW remote engine-reports-setup does not 
write conf file to allow accessing reports from engine
1144079 integration ASSIGNEDlocal engine-reports-setup does not 
write conf file to allow accessing reports from engine

The following bugs are keyworded as Regression and not marked as blockers[10]

Bug ID  Whiteboard  Status  Summary
1142709 integration NEW Trying to deploy hosted-engine via iSCSI device 
fails
1138144 storage NEW Failed to autorecover storage domain after 
unblocking connection with host
1118349 storage NEW [vdsm] Creating DataCenter 3.5 using master 
domain V1 fails with InquireNotSupportedError
1138314 virtNEW 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 77 bugs [3] targeted to 3.5.0.
Excluding node and documentation bugs we still have 53 bugs [4] targeted to 
3.5.0.

More in detail [5]:

Whiteboard  NEW ASSIGNEDPOSTTotal
docs13  1   0   14
gluster 8   2   2   12
i18n0   0   1   1
infra   1   0   3   4
integration 1   2   1   4
node7   4   0   11
ppc 2   0   4   6
sla 12  0   7   19
virt3   0   3   6
Total   47  9   21  77


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@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users