Re: [ovirt-users] [ovirt-devel] [QE][ACTION REQUIRED] oVirt 3.5.0 status - Go / No Go
On 26 Sep 2014, at 10:50, Sandro Bonazzola wrote: > 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 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 > 1118349 storage NEW [vdsm] Creating DataCenter 3.5 using > master domain V1 fails with InquireNotSupportedError > 1138314 virtPOSTFail to start vm with payload. this one is set to 3.5.1. Important, but not a blocker for 3.5 > > 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]: > > 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 (3.5.0 Tracker) > node 8 4 0 12 > ppc 2 0 4 6 > sla 12 0 2 14 > storage 1 0 2 3 > virt 3 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 > ___ > Devel mailing list > de...@ovirt.org > http://lists.ovirt.org/mailman/listinfo/devel ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] [ovirt-devel] [QE][ACTION REQUIRED] oVirt 3.5.0 status - Go / No Go
- Original Message - > From: "Oved Ourfali" > To: "Sandro Bonazzola" > Cc: Users@ovirt.org, de...@ovirt.org > Sent: Monday, September 22, 2014 2:28:15 PM > Subject: Re: [ovirt-users] [ovirt-devel] [QE][ACTION REQUIRED] oVirt 3.5.0 > status - Go / No Go > > > > - Original Message - > > From: "Yaniv Dary" > > To: "Oved Ourfali" > > Cc: Users@ovirt.org, de...@ovirt.org > > Sent: Monday, September 22, 2014 11:07:37 AM > > Subject: Re: [ovirt-users] [ovirt-devel] [QE][ACTION REQUIRED] oVirt 3.5.0 > > status - Go / No Go > > > > > > > > - Original Message - > > > From: "Oved Ourfali" > > > To: "Sandro Bonazzola" > > > Cc: Users@ovirt.org, de...@ovirt.org > > > Sent: Monday, September 22, 2014 11:03:07 AM > > > Subject: Re: [ovirt-devel] [ovirt-users] [QE][ACTION REQUIRED] oVirt > > > 3.5.0 > > > status - Go / No Go > > > > > > > > > > > > - 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 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 > > > > > > I expect both infra issues to be merged by the end of the day. > > > > > Both bugs are now on MODIFIED. > > > > > 1142256 integration NEW remote engine-reports-setup > > > > does not write > > > > conf > > > > file > > > > to allow accessing reports from engine > > > > This is only for 3.5.1. > > > > > > 1144079 integration ASSIGNEDlocal engine-reports-setup does > > > > not write > > > > conf > > > > file to allow accessing reports from engine > > > > This is pending verification from didi. > > > > > > > > > > > > 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. >
Re: [ovirt-users] [ovirt-devel] [QE][ACTION REQUIRED] oVirt 3.5.0 status - Go / No Go
- Original Message - > From: "Yaniv Dary" > To: "Oved Ourfali" > Cc: Users@ovirt.org, de...@ovirt.org > Sent: Monday, September 22, 2014 11:07:37 AM > Subject: Re: [ovirt-users] [ovirt-devel] [QE][ACTION REQUIRED] oVirt 3.5.0 > status - Go / No Go > > > > - Original Message - > > From: "Oved Ourfali" > > To: "Sandro Bonazzola" > > Cc: Users@ovirt.org, de...@ovirt.org > > Sent: Monday, September 22, 2014 11:03:07 AM > > Subject: Re: [ovirt-devel] [ovirt-users] [QE][ACTION REQUIRED] oVirt 3.5.0 > > status - Go / No Go > > > > > > > > - 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. > > Both bugs are now on MODIFIED. > > > 1142256 integration NEW remote engine-reports-setup > > > does not write conf > > > file > > > to allow accessing reports from engine > > This is only for 3.5.1. > > > > 1144079 integration ASSIGNEDlocal engine-reports-setup does > > > not write > > > conf > > > file to allow accessing reports from engine > > This is pending verification from didi. > > > > > > > > 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
Re: [ovirt-users] [ovirt-devel] [QE][ACTION REQUIRED] oVirt 3.5.0 status - Go / No Go
- Original Message - > From: "Oved Ourfali" > To: "Sandro Bonazzola" > Cc: Users@ovirt.org, de...@ovirt.org > Sent: Monday, September 22, 2014 11:03:07 AM > Subject: Re: [ovirt-devel] [ovirt-users] [QE][ACTION REQUIRED] oVirt 3.5.0 > status - Go / No Go > > > > - 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 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 > > 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 This is only for 3.5.1. > > 1144079 integration ASSIGNEDlocal engine-reports-setup does > > not write conf > > file to allow accessing reports from engine This is pending verification from didi. > > > > 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. >
Re: [ovirt-users] [ovirt-devel] [QE][ACTION REQUIRED] oVirt 3.5.0 status
- Original Message - > From: "Sandro Bonazzola" > To: Users@ovirt.org, de...@ovirt.org > Sent: Friday, September 19, 2014 9:54:00 AM > Subject: [ovirt-devel] [QE][ACTION REQUIRED] oVirt 3.5.0 status > > Hi, > We are going to start composing oVirt 3.5.0 GA (or RC3, depending on Monday > morning Go / No go Meeting decisions) on Monday 2014-09-22. > > 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 > 1144079 integration POSTlocal engine-reports-setup does not > write conf file > to allow accessing reports from engine > 1138340 sla POSTvdsm relies on unsupported > 'min_guarantee' VM configuration > parameter > 1143873 network NEW firewall-cmd gets stuck when run as > superVDSM > subsubprocess > 1142256 integration NEW remote engine-reports-setup does not > write conf file > to allow accessing reports from engine > > > And the following dependencies still open: > Bug 1041569 - [NFR] libvirt: Returning the watermark for all the images > opened for writing > > The following bugs are keyworded as Regression and not marked as blockers[10] > > Bug IDWhiteboard Status Summary > 1142709 infra 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 > 1110444 ux POSTbookmark selection does not work on first try 3.5 patch fully acked, ready for merge, BZ still POST but should be MODIFIED once merge. > 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 86 bugs [3] targeted to 3.5.0. > Excluding node and documentation bugs we still have 62 bugs [4] targeted to > 3.5.0. > > More in detail [5]: > > WhiteboardNEW ASSIGNEDPOSTTotal > docs 13 1 0 14 > gluster 8 4 2 14 > i18n 0 0 1 1 > infra 0 1 2 3 > integration 3 1 2 6 > network 0 1 0 1 > node 7 4 0 11 > ppc 2 0 4 6 > sla 12 0 7 19 > virt 8 0 3 11 > Total 53 12 21 86 > > > > 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 > ___ > Devel mailing list > de...@ovirt.org > http://lists.ovirt.org/mailman/listinfo/devel > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] [ovirt-devel] [QE][ACTION REQUIRED] oVirt 3.5.0 status
On 09/19/2014 11:37 AM, Dan Kenigsberg wrote: On Fri, Sep 19, 2014 at 09:54:00AM +0200, Sandro Bonazzola wrote: Hi, We are going to start composing oVirt 3.5.0 GA (or RC3, depending on Monday morning Go / No go Meeting decisions) on Monday 2014-09-22. 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 1144079 integration POSTlocal engine-reports-setup does not write conf file to allow accessing reports from engine 1138340 sla POSTvdsm relies on unsupported 'min_guarantee' VM configuration parameter I've just merged the last patch by Martin Sivak to fix this issue. It should be solved on vdsm GA's build. 1143873 network NEW firewall-cmd gets stuck when run as superVDSM subsubprocess I've removed the above from the blocker. This issue has been release-noted in http://www.ovirt.org/OVirt_3.5_Release_Notes#Fedora_and_EL7_hosts and should be solved on selinux. Hi, I'm reading the Networking part for EL7 host and see puppet doesn't support masking/unmasking services yet: https://tickets.puppetlabs.com/browse/PUP-1253 As we're using The Foreman to deploy the hosts this would be nice. I have lots of ways to execute the "systemctl mask" command off course, but can people please help by voting for it? It's not on their radar as something important it appears. Kind regards, Jorick Astrego Netbulae B.V. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] [ovirt-devel] [QE][ACTION REQUIRED] oVirt 3.5.0 status
On Fri, Sep 19, 2014 at 09:54:00AM +0200, Sandro Bonazzola wrote: > Hi, > We are going to start composing oVirt 3.5.0 GA (or RC3, depending on Monday > morning Go / No go Meeting decisions) on Monday 2014-09-22. > > 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 > 1144079 integration POSTlocal engine-reports-setup does not > write conf file to allow accessing reports from engine > 1138340 sla POSTvdsm relies on unsupported > 'min_guarantee' VM configuration parameter I've just merged the last patch by Martin Sivak to fix this issue. It should be solved on vdsm GA's build. > 1143873 network NEW firewall-cmd gets stuck when run as > superVDSM subsubprocess I've removed the above from the blocker. This issue has been release-noted in http://www.ovirt.org/OVirt_3.5_Release_Notes#Fedora_and_EL7_hosts and should be solved on selinux. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] [ovirt-devel] [QE][ACTION REQUIRED] oVirt 3.5.0 status
On Wed, Sep 17, 2014 at 09:12:28AM -0400, Oved Ourfali wrote: > > > - Original Message - > > From: "Sandro Bonazzola" > > To: "Oved Ourfali" > > Cc: Users@ovirt.org, de...@ovirt.org > > Sent: Wednesday, September 17, 2014 4:10:33 PM > > Subject: Re: [ovirt-users] [ovirt-devel] [QE][ACTION REQUIRED] oVirt 3.5.0 > > status > > > > Il 17/09/2014 15:09, Oved Ourfali ha scritto: > > >> Bug ID Whiteboard Status Summary > > >> > 1135909infra POST[Event log] Wrong warning about > > >> > available swap > > >> > memory of > > >> > host [1023MB], when actually host has [1024MB] memory size > > > We're still discussing whether to address that on engine/VDSM side. > > > Doesn't seem urgent, though, so I wouldn't consider that as a blocker. > > > We didn't see any change with regards to that, so I'm surprised it is a > > > Regression at all... > > > > > > > If it's not a regression, please remove the keyword :-) > > > > Well... the reporter claims it is... we haven't tested it yet due to other > more urgent issues. In particular, real-life installation should use much more thatn 1GiB of swap space, so this problem is moot. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] [ovirt-devel] [QE][ACTION REQUIRED] oVirt 3.5.0 status
Il 17/09/2014 16:36, Bob Doolittle ha scritto: > Hi, > > I just reviewed the Release Notes, and came across this cryptic passage at > http://www.ovirt.org/OVirt_3.5_Release_Notes#What_does_this_change_mean_for_the_admin.3F > : > >> Thus, it is of utmost importance that *if you have ifcfg handmade >> customizations that you port those changes to be use custom network >> properties and >> write a hook to apply them*. > > I have no idea what this means, and suspect I'm not alone among the readers. > Some examples and/or links would be very helpful here. Antoni, do you mind adding some examples and/or links here? > > Thanks, > Bob > > On 09/17/2014 07:46 AM, Sandro Bonazzola wrote: >> Hi, >> We are going to start composing oVirt 3.5.0 GA (or RC3, depending on Test >> Day results and oVirt Sync Meeting decisions) on Monday 2014-09-22. >> >> 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 >> 1142256 integration POSTengine-setup does not write conf file >> to allow accessing reports >> >> 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 >> 1135909 infra POST[Event log] Wrong warning about >> available swap memory of host [1023MB], when actually host has [1024MB] >> memory size >> 1118349 storage NEW [vdsm] Creating DataCenter 3.5 using >> master domain V1 fails with InquireNotSupportedError >> 1110444 ux POSTbookmark selection does not work on >> first try >> 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 83 bugs [3] targeted to 3.5.0. >> Excluding node and documentation bugs we still have 58 bugs [4] targeted to >> 3.5.0. >> >> More in detail [5]: >> >> Whiteboard NEW ASSIGNEDPOSTTotal >> docs 14 1 0 15 >> gluster 9 4 2 15 >> i18n 0 0 1 1 >> integration 1 1 1 3 >> node 6 4 0 10 >> ppc 2 0 4 6 >> sla 5 0 8 13 >> storage 0 0 3 3 >> virt 12 0 5 17 >> Total49 10 24 83 >> >> >> 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 [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: >> - 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://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] [ovirt-devel] [QE][ACTION REQUIRED] oVirt 3.5.0 status
Hi, I just reviewed the Release Notes, and came across this cryptic passage at http://www.ovirt.org/OVirt_3.5_Release_Notes#What_does_this_change_mean_for_the_admin.3F : Thus, it is of utmost importance that *if you have ifcfg handmade customizations that you port those changes to be use custom network properties and write a hook to apply them*. I have no idea what this means, and suspect I'm not alone among the readers. Some examples and/or links would be very helpful here. Thanks, Bob On 09/17/2014 07:46 AM, Sandro Bonazzola wrote: Hi, We are going to start composing oVirt 3.5.0 GA (or RC3, depending on Test Day results and oVirt Sync Meeting decisions) on Monday 2014-09-22. 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 1142256 integration POSTengine-setup does not write conf file to allow accessing reports 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 1135909 infra POST[Event log] Wrong warning about available swap memory of host [1023MB], when actually host has [1024MB] memory size 1118349 storage NEW [vdsm] Creating DataCenter 3.5 using master domain V1 fails with InquireNotSupportedError 1110444 ux POSTbookmark selection does not work on first try 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 83 bugs [3] targeted to 3.5.0. Excluding node and documentation bugs we still have 58 bugs [4] targeted to 3.5.0. More in detail [5]: Whiteboard NEW ASSIGNEDPOSTTotal docs14 1 0 15 gluster 9 4 2 15 i18n0 0 1 1 integration 1 1 1 3 node6 4 0 10 ppc 2 0 4 6 sla 5 0 8 13 storage 0 0 3 3 virt12 0 5 17 Total 49 10 24 83 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 [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: - 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://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, ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] [ovirt-devel] [QE][ACTION REQUIRED] oVirt 3.5.0 status
- Original Message - > From: "Sandro Bonazzola" > To: "Oved Ourfali" > Cc: Users@ovirt.org, de...@ovirt.org > Sent: Wednesday, September 17, 2014 4:10:33 PM > Subject: Re: [ovirt-users] [ovirt-devel] [QE][ACTION REQUIRED] oVirt 3.5.0 > status > > Il 17/09/2014 15:09, Oved Ourfali ha scritto: > >> Bug ID Whiteboard Status Summary > >> > 1135909 infra POST[Event log] Wrong warning about > >> > available swap > >> > memory of > >> > host [1023MB], when actually host has [1024MB] memory size > > We're still discussing whether to address that on engine/VDSM side. > > Doesn't seem urgent, though, so I wouldn't consider that as a blocker. > > We didn't see any change with regards to that, so I'm surprised it is a > > Regression at all... > > > > If it's not a regression, please remove the keyword :-) > Well... the reporter claims it is... we haven't tested it yet due to other more urgent issues. > -- > 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
Re: [ovirt-users] [ovirt-devel] [QE][ACTION REQUIRED] oVirt 3.5.0 status
Il 17/09/2014 15:09, Oved Ourfali ha scritto: >> Bug ID Whiteboard Status Summary >> > 1135909infra POST[Event log] Wrong warning about >> > available swap memory of >> > host [1023MB], when actually host has [1024MB] memory size > We're still discussing whether to address that on engine/VDSM side. > Doesn't seem urgent, though, so I wouldn't consider that as a blocker. > We didn't see any change with regards to that, so I'm surprised it is a > Regression at all... > If it's not a regression, please remove the keyword :-) -- 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] [ovirt-devel] [QE][ACTION REQUIRED] oVirt 3.5.0 status
- Original Message - > From: "Sandro Bonazzola" > To: de...@ovirt.org, Users@ovirt.org > Sent: Wednesday, September 17, 2014 2:46:10 PM > Subject: [ovirt-devel] [QE][ACTION REQUIRED] oVirt 3.5.0 status > > Hi, > We are going to start composing oVirt 3.5.0 GA (or RC3, depending on Test Day > results and oVirt Sync Meeting decisions) on Monday 2014-09-22. > > 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 > 1142256 integration POSTengine-setup does not write conf file > to allow > accessing reports > > 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 IDWhiteboard Status Summary > 1135909 infra POST[Event log] Wrong warning about > available swap memory of > host [1023MB], when actually host has [1024MB] memory size We're still discussing whether to address that on engine/VDSM side. Doesn't seem urgent, though, so I wouldn't consider that as a blocker. We didn't see any change with regards to that, so I'm surprised it is a Regression at all... > 1118349 storage NEW [vdsm] Creating DataCenter 3.5 using > master domain V1 > fails with InquireNotSupportedError > 1110444 ux POSTbookmark selection does not work on > first try > 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 83 bugs [3] targeted to 3.5.0. > Excluding node and documentation bugs we still have 58 bugs [4] targeted to > 3.5.0. > > More in detail [5]: > > WhiteboardNEW ASSIGNEDPOSTTotal > docs 14 1 0 15 > gluster 9 4 2 15 > i18n 0 0 1 1 > integration 1 1 1 3 > node 6 4 0 10 > ppc 2 0 4 6 > sla 5 0 8 13 > storage 0 0 3 3 > virt 12 0 5 17 > Total 49 10 24 83 > > > 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 [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: > - 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://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 > ___ > Devel mailing list > de...@ovirt.org > http://lists.ovirt.org/mailman/listinfo/devel > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
