[ovirt-devel] [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 docs5 0 15 dwh 1 0 1 external0 1 1 gluster 40 0 40 i18n2 0 2 infra 23 6 29 integration 0 1 1 network 27 1 28 node4 0 4 reports 1 0 1 sla 36 2 38 storage 49 9 58 ux 10 0 10 virt5 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-3.6.0 status%3Anew%2Cassigned%2Cpost [2] https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_milestone%3Aovirt-3.6.0%20status%3Anew%2Cassigned%2Cpost%20keyword%3Aregression [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 ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] [QE][ACTION REQUIRED] oVirt 3.6.0 status
On 15 Sep 2015, at 15:33, Sandro Bonazzola wrote: > Hi, > We planned to start composing oVirt 3.6.0 Beta6 on *2015-09-16 08:00 UTC* > from 3.6 branches. > > There are still 824 bugs [1] targeted to 3.6.0. > Maintainers should scrub them and start pushing non critical bugs to ZStream > releases. FYI since bugzilla finally has flags for ovirt bugs too there are quite a few 3.6 virt bugs flagged with Development Conditional NACK due to Capacity or other reason. I plan to keep it like that for one more week to give people a fair chance to review what RHEV and oVirt bugs we're planning to defer. > > There are still 37 bugs marked as blocker: > > Bug IDWhiteboard Status Summary > 1261296 integration ASSIGNEDiSCSI setup fails in hosted > engine > 1247942 integration NEW [hosted-engine-setup] Additional host > deployment fails with "Dirty Storage Domain: Cannot find master domain" over > block storage > 1220867 integration NEW all-in-one fails cause engine-setup > tries to add the local storage when the host is still not up > 1261822 integration NEW BUILD WGT 3.6 > 1244720 integration POSTpg_restore: [archiver (db)] could not > execute query: ERROR: language "plpgsql" already exists after upgrade > 1231507 network ASSIGNED[SR-IOV] REST API for SR-IOV > 1184497 network ASSIGNEDSetupNetworks> Can't change network > state from dhcp to static ip > 1247037 network ASSIGNED[new HostSetupNetworks] unmanaged > networks handling > 1262051 network NEW Host move from 'up' to 'connecting' and back to > 'up' from time to time > 1192778 network NEW Wrong BOOTPROTO displayed on setup networks GUI > and there is no way to change it via setup networks > 1250063 network NEW Host becomes non-operational when activating it > from maintenance mode, if you have a required network that was never used > 1247966 network NEW [userportal] Unable to add new nic to vm > 1257168 network NEW [Clusters] > 'Manage Networks' > 'required all' > and 'assigned all' checkboxes completely stopped working (in both of the > dialogs) > 1214805 network POSTDatacenterAdmin role on system can't add new DC > (missing CONFIGURE_MAC_POOL action group) > 1246060 network POST[New HostSetupNetworks] Remove > custom_properties from vds_interface table and VdsNetworkInterface entity > 1254713 network POSTVM stuck in down state on vdsm when powering > off VM with port mirroring > 1259000 network POSTHosts stuck in 'connecting' status while > running automation tests > 1242235 network POST[New HostSetupNetworksCommand] Marking > ipConfiguration and overridden QoS as out-of-sync > 1260430 network POSTREST | old SetupNetworks API | NPE when > attaching network to host NIC > 1095028 nodeNEW [3.5-7.0] Abort media check will cause system > halt > 1242215 sla NEW [HE] HE-vm not shown with unconfigured default > storage domain in ovirt 3.6 > 1258901 storage NEW [UX] Toggling wad property while vm is up > shouldn't be greyed out > 1261953 storage NEW [vdsm] Host fails to connect to storage pool > 'MiscBlockReadException: Internal block device read failure' > 1253790 storage NEW [BLOCKED] consume fix for "iscsi_session > recovery_tmo revert back to default when a path becomes active" > 1253640 storage NEW Some dirty LUNs are not usable in RHEV > 1257240 storage NEW Template's disk format is wrong > 1261980 storage NEW failed LSM due to connection lost with qemu > process > 1253975 storage NEW [vdsm] extendVolumeSize task is not cleared in > case of a live merge failure for a volume that was extended > 1238239 storage NEW Deployment of hosted engine failed on ISCSI > storage with 'Error block device action' > 1258465 storage NEW Different behavior of connectStorageServer and > prepareImage between iSCSI and NFS > 1251008 storage POST[BLOCKED] libvirt reports physical=0 for COW2 > volumes on block storage > 1219680 storage POSTwebadmin portal allows to add non-ascii > characters in the disk_description which causes false positive object > creation in log. > 1205697 ux NEW Can not assign tag to an entity from UI > 1261075 virtNEW hostdev_passthrough: VM with attached host USB > device failed to run. > 1260409 virtNEW Migration failed since libvirtError in > 'virDomainMigrateToURI2' > 1261812 virtPOST[ppc64le] VM startup takes too long when > hot-plug memory feature is enabled virt patches are ready, pending maintainers' attention Thanks, michal > 1261996 NEW [hosted-engine] Storage pool UUID is modified > when importing the HE storage domain to the setup. Hence, the HE VM dies > >
[ovirt-devel] [QE][ACTION REQUIRED] oVirt 3.6.0 status
Hi, We planned to start composing oVirt 3.6.0 Beta6 on *2015-09-16 08:00 UTC* from 3.6 branches. There are still 824 bugs [1] targeted to 3.6.0. Maintainers should scrub them and start pushing non critical bugs to ZStream releases. There are still 37 bugs marked as blocker: Bug ID Whiteboard Status Summary 1261296 integration ASSIGNED iSCSI setup fails in hosted engine 1247942 integration NEW [hosted-engine-setup] Additional host deployment fails with "Dirty Storage Domain: Cannot find master domain" over block storage 1220867 integration NEW all-in-one fails cause engine-setup tries to add the local storage when the host is still not up 1261822 integration NEW BUILD WGT 3.6 1244720 integration POST pg_restore: [archiver (db)] could not execute query: ERROR: language "plpgsql" already exists after upgrade 1231507 network ASSIGNED [SR-IOV] REST API for SR-IOV 1184497 network ASSIGNED SetupNetworks> Can't change network state from dhcp to static ip 1247037 network ASSIGNED [new HostSetupNetworks] unmanaged networks handling 1262051 network NEW Host move from 'up' to 'connecting' and back to 'up' from time to time 1192778 network NEW Wrong BOOTPROTO displayed on setup networks GUI and there is no way to change it via setup networks 1250063 network NEW Host becomes non-operational when activating it from maintenance mode, if you have a required network that was never used 1247966 network NEW [userportal] Unable to add new nic to vm 1257168 network NEW [Clusters] > 'Manage Networks' > 'required all' and 'assigned all' checkboxes completely stopped working (in both of the dialogs) 1214805 network POST DatacenterAdmin role on system can't add new DC (missing CONFIGURE_MAC_POOL action group) 1246060 network POST [New HostSetupNetworks] Remove custom_properties from vds_interface table and VdsNetworkInterface entity 1254713 network POST VM stuck in down state on vdsm when powering off VM with port mirroring 1259000 network POST Hosts stuck in 'connecting' status while running automation tests 1242235 network POST [New HostSetupNetworksCommand] Marking ipConfiguration and overridden QoS as out-of-sync 1260430 network POST REST | old SetupNetworks API | NPE when attaching network to host NIC 1095028 node NEW [3.5-7.0] Abort media check will cause system halt 1242215 sla NEW [HE] HE-vm not shown with unconfigured default storage domain in ovirt 3.6 1258901 storage NEW [UX] Toggling wad property while vm is up shouldn't be greyed out 1261953 storage NEW [vdsm] Host fails to connect to storage pool 'MiscBlockReadException: Internal block device read failure' 1253790 storage NEW [BLOCKED] consume fix for "iscsi_session recovery_tmo revert back to default when a path becomes active" 1253640 storage NEW Some dirty LUNs are not usable in RHEV 1257240 storage NEW Template's disk format is wrong 1261980 storage NEW failed LSM due to connection lost with qemu process 1253975 storage NEW [vdsm] extendVolumeSize task is not cleared in case of a live merge failure for a volume that was extended 1238239 storage NEW Deployment of hosted engine failed on ISCSI storage with 'Error block device action' 1258465 storage NEW Different behavior of connectStorageServer and prepareImage between iSCSI and NFS 1251008 storage POST [BLOCKED] libvirt reports physical=0 for COW2 volumes on block storage 1219680 storage POST webadmin portal allows to add non-ascii characters in the disk_description which causes false positive object creation in log. 1205697 ux NEW Can not assign tag to an entity from UI 1261075 virt NEW hostdev_passthrough: VM with attached host USB device failed to run. 1260409 virt NEW Migration failed since libvirtError in 'virDomainMigrateToURI2' 1261812 virt POST [ppc64le] VM startup takes too long when hot-plug memory feature is enabled 1261996 NEW [hosted-engine] Storage pool UUID is modified when importing the HE storage domain to the setup. Hence, the HE VM dies There are 21 bugs marked as test / automation blocker[2] There are 45 bugs marked as regressions[3] Given current bugs status, release criteria are not met [4] so we need to review bug status for planning the RC. Action items: - Developers: fix test / automation blockers, regressions and 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 [5] - Please test oVirt 3.6 nightly snapshot and check for regressions from 3.5 [1] https://goo.gl/YHm02x [2] https://goo.gl/hYFZCs [3] https://goo.gl/yHkfdv [4] http://www.ovirt.org/OVirt_3.6_Release_Management#Candidate_Release_Criteria [5] 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 ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
[ovirt-devel] [QE][ACTION REQUIRED] oVirt 3.6.0 status
Hi, We planned to start composing oVirt 3.6.0 RC on *2015-09-16 08:00 UTC* from 3.6 branches. There are still 855 bugs [1] targeted to 3.6.0. Maintainers should scrub them and start pushing non critical bugs to ZStream releases. There are still 34 bugs marked as blocker: Bug ID Status Whiteboard Summary 1259247 POST infra [7.2-3.6] Failed to approve RHEV-H in RHEV-M 3.5 1247942 NEW integration [hosted-engine-setup] Additional host deployment fails with "Dirty Storage Domain: Cannot find master domain" over block storage 1236600 NEW integration ovirt-hosted-engine-ha is missing logrotate configuration 1220867 NEW integration all-in-one fails cause engine-setup tries to add the local storage when the host is still not up 1244720 POST integration pg_restore: [archiver (db)] could not execute query: ERROR: language "plpgsql" already exists after upgrade 1254671 POST integration Fail HE install when closing the install 1242235 ASSIGNED network [New HostSetupNetworksCommand] Marking ipConfiguration and overridden QoS as out-of-sync 1231507 ASSIGNED network [SR-IOV] REST API for SR-IOV 1184497 ASSIGNED network SetupNetworks> Can't change network state from dhcp to static ip 1246060 NEW network [New HostSetupNetworks] Remove custom_properties from vds_interface table and VdsNetworkInterface entity 1192778 NEW network Wrong BOOTPROTO displayed on setup networks GUI and there is no way to change it via setup networks 1257168 NEW network [Clusters] > 'Manage Networks' > 'required all' and 'assigned all' checkboxes completely stopped working (in both of the dialogs) 1250063 NEW network Host becomes non-operational when activating it from maintenance mode, if you have a required network that was never used 1214805 POST network DatacenterAdmin role on system can't add new DC (missing CONFIGURE_MAC_POOL action group) 1247037 POST network [new HostSetupNetworks] unmanaged networks handling 1259000 POST network Vdsm must keep defaultRoute=True heuristic for older clusterLevels 1260430 POST network REST | old SetupNetworks API | NPE when attaching network to host NIC 1254713 POST network VM stuck in down state on vdsm when powering off VM with port mirroring 1196640 POST network [Monitoring] Network utilisation is not shown for the VM 1095028 NEW node [3.5-7.0] Abort media check will cause system halt 1260470 NEW node Failed to setup Hosted Engine on RHEV-H 7.2 1259220 NEW node [TUI] There is error report when click "Set Console Path" 1242215 NEW sla [HE] HE-vm not shown with unconfigured default storage domain in ovirt 3.6 1251742 POST sla Affinity balancing stop work after first migration 1253975 NEW storage [vdsm] extendVolumeSize task is not cleared in case of a live merge failure for a volume that was extended 1253790 NEW storage [BLOCKED] consume fix for "iscsi_session recovery_tmo revert back to default when a path becomes active" 1258465 NEW storage Different behavior of connectStorageServer and prepareImage between iSCSI and NFS 1258901 NEW storage [UX] Toggling wad property while vm is up shouldn't be greyed out 1257240 NEW storage Template's disk format is wrong 1238239 NEW storage Deployment of hosted engine failed on ISCSI storage with 'Error block device action' 1253640 NEW storage Some dirty LUNs are not usable in RHEV 1205697 NEW ux Can not assign tag to an entity from UI 1252012 ASSIGNED virt balloon enabled at cluster level cause NPE in VMs monitoring 1260409 NEW virt Migration failed since libvirtError in 'virDomainMigrateToURI2' There are 18 bugs marked as test / automation blocker[2] There are 43 bugs marked as regressions[3] Given current bugs status, release criteria are not met [4] so I suggest to go with another beta on 2015-09-16 and review bug status next week. I'm postponing RC by one week in the mean time. Action items: - Developers: fix test / automation blockers, regressions and 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 [5] - Please test oVirt 3.6 nightly snapshot and check for regressions from 3.5 [1] https://goo.gl/YHm02x [2] https://goo.gl/hYFZCs [3] https://goo.gl/yHkfdv [4] http://www.ovirt.org/OVirt_3.6_Release_Management#Candidate_Release_Criteria [5] 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 ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
[ovirt-devel] [QE][ACTION REQUIRED] oVirt 3.6.0 status
Hi, here's an update on 3.6 status on integration / rel-eng side Schedule for 3.6.0 has been published[1] and external project schedules have been updated[2]. The tracker bug for 3.6.0 [3] currently shows no blockers. There are 561 bugs [4] targeted to 3.6.0. Excluding node and documentation bugs we have 514 bugs [5] targeted to 3.6.0. NEW ASSIGNEDPOSTTotal docs11 0 0 11 gluster 30 2 1 33 i18n2 0 0 2 infra 83 8 5 96 integration 61 6 4 71 network 32 2 9 43 node27 3 3 33 ppc 0 0 1 1 sla 53 3 0 56 spice 1 0 0 1 storage 74 4 5 83 ux 34 0 8 42 virt73 6 10 89 Total 481 34 46 561 Features submission is still open until 2015-04-22 as per current release schedule. Be sure to have your features tracked in the google doc[6] >From integration side, Hosted Engine support for FC is available in nightly >builds for testing. [1] http://www.ovirt.org/OVirt_3.6_Release_Management#Key_Milestones [2] http://www.ovirt.org/OVirt_3.6_Release_Management#External_Project_Schedules [3] https://bugzilla.redhat.com/show_bug.cgi?id=1155425 [4] https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_release%3A3.6.0%20Product%3AoVirt%20status%3Anew%2Cassigned%2Cpost [5] http://goo.gl/ZbUiMc [6] http://goo.gl/9X3G49 -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
[ovirt-devel] [QE][ACTION REQUIRED] oVirt 3.6.0 status
Hi, here's an update on 3.6 status on integration / rel-eng side ACTION: Feature proposed for 3.6.0 must now be collected in the 3.6 Google doc [1] and reviewed by maintainers. Finished the review process, the remaining key milestones for this release will be scheduled. For reference, external project schedules we're tracking are: Fedora 22: 2015-05-19 Fedora 20 End Of Life:2015-06-19 (1 month after Fedora 22 release) Foreman 1.8.0: 2015-04-01 GlusterFS 3.7: 2015-04-29 OpenStack Kilo: 2015-04-30 QEMU 2.3.0: 2015-03-27 The tracker bug for 3.6.0 [2] currently shows no blockers. There are 552 bugs [3] targeted to 3.6.0. Excluding node and documentation bugs we have 510 bugs [4] targeted to 3.6.0. NEW ASSIGNEDPOSTTotal docs11 0 0 11 gluster 28 2 1 31 i18n2 0 0 2 infra 82 10 4 96 integration 56 5 4 65 network 30 2 9 41 node25 3 3 31 ppc 0 0 1 1 sla 56 3 1 60 spice 1 0 0 1 storage 75 4 5 84 ux 36 1 3 40 virt74 6 9 89 Total 476 36 40 552 oVirt Live for 3.6 has been rebased on EL7. Nightly builds are available here: http://jenkins.ovirt.org/job/ovirt_live_create_iso/ [1] http://goo.gl/9X3G49 [2] https://bugzilla.redhat.com/show_bug.cgi?id=1155425 [3] https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_release%3A3.6.0%20Product%3AoVirt%20status%3Anew%2Cassigned%2Cpost [4] http://goo.gl/ZbUiMc -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
[ovirt-devel] [QE][ACTION REQUIRED] oVirt 3.6.0 status
Hi, here's an update on 3.6 status on integration / rel-eng side ACTION: Feature proposed for 3.6.0 must now be collected in the 3.6 Google doc [1] and reviewed by maintainers. Finished the review process, the remaining key milestones for this release will be scheduled. For reference, external project schedules we're tracking are: Fedora 22: 2015-05-19 Fedora 20 End Of Life:2015-06-19 (1 month after Fedora 22 release) Foreman 1.8.0: 2015-04-01 GlusterFS 3.7: 2015-04-29 OpenStack Kilo: 2015-04-30 QEMU 2.3.0: 2015-03-27 The tracker bug for 3.6.0 [2] currently shows no blockers. There are 545 bugs [3] targeted to 3.6.0. Excluding node and documentation bugs we have 503 bugs [4] targeted to 3.6.0. NEW ASSIGNEDPOSTTotal 1 0 0 1 docs11 0 0 11 gluster 25 2 1 28 i18n2 0 0 2 infra 80 10 3 93 integration 59 4 2 65 network 29 2 8 39 node26 2 3 31 ppc 0 0 1 1 sla 56 3 1 60 spice 1 0 0 1 storage 76 4 5 85 ux 35 1 3 39 virt74 6 9 89 Total 475 34 36 545 oVirt Live for 3.6 has been rebased on EL7. Nightly builds are available here: http://jenkins.ovirt.org/job/ovirt_live_create_iso/ [1] http://goo.gl/9X3G49 [2] https://bugzilla.redhat.com/show_bug.cgi?id=1155425 [3] https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_release%3A3.6.0%20Product%3AoVirt%20status%3Anew%2Cassigned%2Cpost [4] http://goo.gl/ZbUiMc -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
[ovirt-devel] [QE][ACTION REQUIRED] oVirt 3.6.0 status
Hi, here's an update on 3.6 status on integration / rel-eng side ACTION: Feature proposed for 3.6.0 must now be collected in the 3.6 Google doc [1] and reviewed by maintainers. Finished the review process, the remaining key milestones for this release will be scheduled. For reference, external project schedules we're tracking are: Fedora 22: 2015-05-19 Fedora 20 End Of Life: 2015-06-19 (1 month after Fedora 22 release) Foreman 1.8.0: 2015-03-01 GlusterFS 3.7: 2015-04-29 OpenStack Kilo: 2015-04-30 QEMU 2.3.0: 2015-03-27 The tracker bug for 3.6.0 [2] currently shows no blockers. There are 548 bugs [3] targeted to 3.6.0. Excluding node and documentation bugs we have 506 bugs [4] targeted to 3.6.0. oVirt 3.6 cluster compatibility status in nightly builds: VDSM patch introducing 3.6 compatibility[5] has not been merged yet, waiting for CentOS and RHEL 7.1 to be released for getting libvirt support. CentOS and RHEL 6.z won't have 3.6 compatibility by design [6]. Fedora 20 won't have 3.6 compatibility level since virt maintainers are going to maintain latest libvirt rpms only in latest stable Fedora release (currently Fedora 21). There's no point in providing Fedora 20 packages on oVirt side since Fedora 20 will go EOL before oVirt 3.6.0 GA. Fedora 21 will be able to support 3.6 compatibility once VDSM patch[5] will be merged. Fedora 22 may not be able to support VDSM at all since it will run Python 3 instead of Python 2 as default python interpreter[7], so more work will be needed there. [1] http://goo.gl/9X3G49 [2] https://bugzilla.redhat.com/show_bug.cgi?id=1155425 [3] https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_release%3A3.6.0%20Product%3AoVirt%20status%3Anew%2Cassigned%2Cpost [4] http://goo.gl/ZbUiMc [5] http://gerrit.ovirt.org/37384 [6] http://lists.ovirt.org/pipermail/users/2014-September/027421.html [7] https://fedoraproject.org/wiki/Releases/22/ChangeSet -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
[ovirt-devel] [QE][ACTION REQUIRED] oVirt 3.6.0 status
Hi, I haven't many news for 3.6 this week: ACTION: Feature proposed for 3.6.0 must now be collected in the 3.6 Google doc [1] and reviewed by maintainers. Finished the review process, the remaining key milestones for this release will be scheduled. For reference, external project schedules we're tracking are: Fedora 22: 2015-05-19 Foreman 1.8.0: 2015-03-01 GlusterFS 3.7: 2015-04-29 OpenStack Kilo: 2015-04-30 QEMU 2.3.0: 2015-03-27 The tracker bug for 3.6.0 [2] currently shows no blockers. There are 530 bugs [3] targeted to 3.6.0. Excluding node and documentation bugs we have 489 bugs [4] targeted to 3.6.0. [1] http://goo.gl/9X3G49 [2] https://bugzilla.redhat.com/show_bug.cgi?id=1155425 [3] https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_release%3A3.6.0%20Product%3AoVirt%20status%3Anew%2Cassigned%2Cpost [4] http://goo.gl/ZbUiMc -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
[ovirt-devel] [QE][ACTION REQUIRED] oVirt 3.6.0 status
Hi, I haven't many news for 3.6 this week: ACTION: Feature proposed for 3.6.0 must now be collected in the 3.6 Google doc [1] and reviewed by maintainers. Finished the review process, the remaining key milestones for this release will be scheduled. For reference, external project schedules we're tracking are: Fedora 21: 2014-12-09 (RELEASED) Fedora 22: 2015-05-19 Foreman 1.8.0: 2015-03-01 GlusterFS 3.7: 2015-04-29 OpenStack Kilo: 2015-04-30 QEMU 2.1.3: 2014-01-21 QEMU 2.2.0: 2014-12-09 (RELEASED) QEMU 2.3.0: 2015-03-27 The tracker bug for 3.6.0 [2] currently shows no blockers. There are 502 bugs [3] targeted to 3.6.0. Excluding node and documentation bugs we have 454 bugs [4] targeted to 3.6.0. [1] http://goo.gl/9X3G49 [2] https://bugzilla.redhat.com/show_bug.cgi?id=1155425 [3] https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_release%3A3.6.0%20Product%3AoVirt%20status%3Anew%2Cassigned%2Cpost [4] http://goo.gl/ZbUiMc -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
[ovirt-devel] [QE][ACTION REQUIRED] oVirt 3.6.0 status
Hi, I haven't many news for 3.6 this week: ACTION: Feature proposed for 3.6.0 must now be collected in the 3.6 Google doc [1] and reviewed by maintainers. Finished the review process, the remaining key milestones for this release will be scheduled. For reference, external project schedules we're tracking are: Fedora 21: 2014-12-09 (RELEASED) Fedora 22: 2015-05-19 Foreman 1.8.0: 2015-03-01 GlusterFS 3.7: 2015-04-29 OpenStack Kilo: 2015-04-30 QEMU 2.1.3: 2014-01-21 QEMU 2.2.0: 2014-12-09 (RELEASED) QEMU 2.3.0: 2015-03-27 The tracker bug for 3.6.0 [2] currently shows no blockers. There are 480 bugs [3] targeted to 3.6.0. Excluding node and documentation bugs we have 454 bugs [4] targeted to 3.6.0. [1] http://goo.gl/9X3G49 [2] https://bugzilla.redhat.com/show_bug.cgi?id=1155425 [3] http://goo.gl/zwkF3r [4] http://goo.gl/ZbUiMc -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
[ovirt-devel] [QE][ACTION REQUIRED] oVirt 3.6.0 status
Hi, I haven't many news for 3.6 this week: ACTION: Feature proposed for 3.6.0 must now be collected in the 3.6 Google doc [1] and reviewed by maintainers. Finished the review process, the remaining key milestones for this release will be scheduled. For reference, external project schedules we're tracking are: Fedora 21: 2014-12-09 (RELEASED) Fedora 22: no earlier than 2015-05-19 Foreman 1.8.0: 2015-03-01 GlusterFS 3.7: 2015-04-29 OpenStack Kilo: 2015-04-30 QEMU 2.1.3: 2014-12-29 (DELAYED) QEMU 2.2.0: 2014-12-09 (RELEASED) The tracker bug for 3.6.0 [2] currently shows no blockers. There are 466 bugs [3] targeted to 3.6.0. Excluding node and documentation bugs we have 440 bugs [4] targeted to 3.6.0. [1] http://goo.gl/9X3G49 [2] https://bugzilla.redhat.com/show_bug.cgi?id=1155425 [3] http://goo.gl/zwkF3r [4] http://goo.gl/ZbUiMc -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
[ovirt-devel] [QE][ACTION REQUIRED] oVirt 3.6.0 status
Hi, Release management for 3.6.0 [1] has been updated following the new release process[2]. ACTION: Feature proposed for 3.6.0 must now be collected in the 3.6 Google doc [3] and reviewed by maintainers. Finished the review process, the remaining key milestones for this release will be scheduled. For reference, external project schedules we're tracking are: Fedora 21: 2014-12-09 (RELEASED) Fedora 22: no earlier than 2015-05-19 Foreman 1.8.0: 2015-03-01 GlusterFS 3.7: 2015-04-29 OpenStack Kilo: 2015-04-30 QEMU 2.1.3: 2014-12-29 QEMU 2.2.0: 2014-12-09 (RELEASED) The tracker bug for 3.6.0 [4] currently shows no blockers. There are 461 bugs [5] targeted to 3.6.0. Excluding node and documentation bugs we have 438 bugs [6] targeted to 3.6.0. [1] http://www.ovirt.org/OVirt_3.6_Release_Management [2] http://www.ovirt.org/Release_process [3] http://goo.gl/9X3G49 [4] https://bugzilla.redhat.com/show_bug.cgi?id=1155425 [5] http://goo.gl/zwkF3r [6] http://goo.gl/ZbUiMc -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
[ovirt-devel] [QE][ACTION REQUIRED] oVirt 3.6.0 status
Hi, Release criteria discussion has been closed and wiki has been updated accordingly by Brian [1][2]. Release management for 3.6.0 [3] has been updated with the accepted changes in release criteria. ACTION: Feature proposed for 3.6.0 must now be collected in the 3.6 Google doc [4] and reviewed by maintainers. Finished the review process, the remaining key milestones for this release will be scheduled. For reference, external project schedules we're tracking are: Fedora 21: 2014-12-09 (RELEASED) Fedora 22: no earlier than 2015-05-19 Foreman 1.8.0: 2015-03-01 GlusterFS 3.7: 2015-04-29 OpenStack Kilo: 2015-04-30 Two different proposals have been made about above scheduling [5]: 1) extend the cycle to 10 months for allowing to include a large feature set 2) reduce the cycle to less than 6 months and split features over 3.6 and 3.7 and we can also add 3) keep current 6 months cycle The tracker bug for 3.6.0 [6] currently shows no blockers. There are 460 bugs [7] targeted to 3.6.0. Excluding node and documentation bugs we have 436 bugs [8] targeted to 3.6.0. [1] http://www.ovirt.org/Release_Criteria_Template [2] http://www.ovirt.org/Release_process [3] http://www.ovirt.org/OVirt_3.6_Release_Management [4] http://goo.gl/9X3G49 [5] http://lists.ovirt.org/pipermail/users/2014-November/028875.html [6] https://bugzilla.redhat.com/show_bug.cgi?id=1155425 [7] http://goo.gl/zwkF3r [8] http://goo.gl/ZbUiMc -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
[ovirt-devel] [QE][ACTION REQUIRED] oVirt 3.6.0 status
Hi, Release criteria discussion has been closed with last week oVirt sync meeting [1]. Release management for 3.6.0 [2] will soon be updated with the accepted changes in release criteria. The remaining key milestones for this release must now be scheduled. For reference, external project schedules we're tracking are: Fedora 21: 2014-12-09 Fedora 22: 2015-XX-XX GlusterFS 3.7: 2015-04-29 OpenStack Kilo: 2015-04-30 Two different proposals have been made about above scheduling [3]: 1) extend the cycle to 10 months for allowing to include a large feature set 2) reduce the cycle to less than 6 months and split features over 3.6 and 3.7 Feature proposed for 3.6.0 must now be collected in the 3.6 Google doc [4] and reviewed by maintainers. The tracker bug for 3.6.0 [5] currently shows no blockers. There are 453 bugs [6] targeted to 3.6.0. Excluding node and documentation bugs we have 430 bugs [7] targeted to 3.6.0. [1] http://resources.ovirt.org/meetings/ovirt/2014/ovirt.2014-11-26-15.07.log.html [2] http://www.ovirt.org/OVirt_3.6_Release_Management [3] http://lists.ovirt.org/pipermail/users/2014-November/028875.html [4] http://goo.gl/9X3G49 [5] https://bugzilla.redhat.com/show_bug.cgi?id=1155425 [6] http://goo.gl/zwkF3r [7] http://goo.gl/ZbUiMc -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
[ovirt-devel] [QE][ACTION REQUIRED] oVirt 3.6.0 status
Hi, Release criteria discussion started on 2014-10-22 and will end today 2014-11-26 as discussed in last oVirt sync meeting [1]. If no objections will be raised, the proposed changes [2] will be accepted. Release management for 3.6.0 has been created [3] The key milestones for this release must be scheduled: Key Milestones Release criteria discussion start: 2014-10-22 Release criteria ready: 2014-11-26 Feature freeze: 60 Days before release First Test Day: 45 days before release Release Candidate: 30 days before release Release: 6 months after oVirt 3.5.0 release External Project Schedules Fedora 21: 2014-12-09 Fedora 22: 2015-XX-XX GlusterFS 3.7: 2015-04-29 OpenStack Kilo: 2015-04-30 Two different proposals have been made about above scheduling [4]: 1) extend the cycle to 10 months for allowing to include a large feature set 2) reduce the cycle to less than 6 months and split features over 3.6 and 3.7 Feature proposed for 3.6.0 must now be collected in the 3.6 google doc [8] and reviewed by maintainers. A tracker bug for 3.6.0 has been created [5] and currently shows no blockers. There are 439 bugs [6] targeted to 3.6.0. Excluding node and documentation bugs we have 419 bugs [7] targeted to 3.6.0. [1] http://resources.ovirt.org/meetings/ovirt/2014/ovirt.2014-11-19-15.01.log.html [2] http://lists.ovirt.org/pipermail/devel/2014-September/008695.html [3] http://www.ovirt.org/OVirt_3.6_Release_Management [4] http://lists.ovirt.org/pipermail/users/2014-November/028875.html [5] https://bugzilla.redhat.com/show_bug.cgi?id=1155425 [6] http://goo.gl/zwkF3r [7] http://goo.gl/ZbUiMc [8] http://goo.gl/9X3G49 -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
[ovirt-devel] [QE][ACTION REQUIRED] oVirt 3.6.0 status
Hi, Release criteria discussion started on 2014-10-22 and should have ended last week as per current release process [1]. Since oVirt sync meeting wasn't held last week, it has been postponed to today 2014-11-19. Current options are: 1) keeping the same release criteria we had for 3.5 [2] 2) review the proposed changes [3] and prepare new release criteria for 3.6 Release management for 3.6.0 has been created [4] The key milestones for this release must be scheduled: Key Milestones Release criteria discussion start: 2014-10-22 Release criteria ready: 2014-11-19 Feature freeze: 60 Days before release First Test Day: 45 days before release Release Candidate: 30 days before release Release: 6 months after oVirt 3.5.0 release External Project Schedules Fedora 21: 2014-12-09 Fedora 22: 2015-XX-XX GlusterFS 3.7: 2015-04-29 OpenStack Kilo: 2015-04-30 Two different proposals have been made about above scheduling [5]: 1) extend the cycle to 10 months for allowing to include a large feature set 2) reduce the cycle to less than 6 months and split features over 3.6 and 3.7 Feature proposed for 3.6.0 must now be collected in the 3.6 google doc [9] and reviewed by maintainers. A tracker bug for 3.6.0 has been created [6] and currently shows no blockers. There are 412 bugs [7] targeted to 3.6.0. Excluding node and documentation bugs we have 392 bugs [8] targeted to 3.6.0. [1] http://www.ovirt.org/Release_process [2] http://www.ovirt.org/OVirt_3.5_release-management#Release_Criteria [3] http://lists.ovirt.org/pipermail/devel/2014-September/008695.html [4] http://www.ovirt.org/OVirt_3.6_Release_Management [5] http://lists.ovirt.org/pipermail/users/2014-November/028875.html [6] https://bugzilla.redhat.com/show_bug.cgi?id=1155425 [7] http://goo.gl/zwkF3r [8] http://goo.gl/ZbUiMc [9] http://goo.gl/9X3G49 -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
[ovirt-devel] [QE][ACTION REQUIRED] oVirt 3.6.0 status
Hi, Release criteria discussion started on 2014-10-22 and should end today as per current release process [1]. Current options are: 1) keeping the same release criteria we had for 3.5 [2] 2) review the proposed changes [3] and prepare new release criteria for 3.6 Release management for 3.6.0 has been created [4] The key milestones for this release must be scheduled: Key Milestones Release criteria discussion start: 2014-10-22 Release criteria ready: 2014-11-12 Feature freeze: 60 Days before release First Test Day: 45 days before release Release Candidate: 30 days before release Release: 6 months after oVirt 3.5.0 release Two different proposals have been made about above scheduling [5]: 1) extend the cycle to 10 months for allowing to include a large feature set 2) reduce the cycle to less than 6 months and split features over 3.6 and 3.7 Feature proposed for 3.6.0 must now be collected in the 3.6 google doc [9] and reviewed by maintainers. A tracker bug for 3.6.0 has been created [6] and currently shows no blockers. There are 399 bugs [7] targeted to 3.6.0. Excluding node and documentation bugs we have 379 bugs [8] targeted to 3.6.0. [1] http://www.ovirt.org/Release_process [2] http://www.ovirt.org/OVirt_3.5_release-management#Release_Criteria [3] http://lists.ovirt.org/pipermail/devel/2014-September/008695.html [4] http://www.ovirt.org/OVirt_3.6_Release_Management [5] http://lists.ovirt.org/pipermail/users/2014-November/028875.html [6] https://bugzilla.redhat.com/show_bug.cgi?id=1155425 [7] http://goo.gl/zwkF3r [8] http://goo.gl/ZbUiMc [9] http://goo.gl/9X3G49 -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
[ovirt-devel] [QE][ACTION REQUIRED] oVirt 3.6.0 status
Hi, Release criteria discussion started on 2014-10-22 and should end on 2014-11-12 as per current release process [1]. Current options are: 1) keeping the same release criteria we had for 3.5 [2] 2) review the proposed changes [3] and prepare new release criteria for 3.6 Release management for 3.6.0 has been created [4] The key milestones for this release must be scheduled: Key Milestones Release criteria discussion start: 2014-10-22 Release criteria ready: 2014-11-12 Feature freeze: 60 Days before release First Test Day: 45 days before release Release Candidate: 30 days before release Release: 6 months after oVirt 3.5.0 release Two different proposals have been meed about above scheduling [5]: 1) extend the cycle to 10 months for allowing to include a large feature set 2) reduce the cycle to less than 6 months and split features over 3.6 and 3.7 A tracker bug for 3.6.0 has been created [6] and currently shows no blockers. There are 395 bugs [7] targeted to 3.6.0. Excluding node and documentation bugs we have 375 bugs [8] targeted to 3.6.0. [1] http://www.ovirt.org/Release_process [2] http://www.ovirt.org/OVirt_3.5_release-management#Release_Criteria [3] http://lists.ovirt.org/pipermail/devel/2014-September/008695.html [4] http://www.ovirt.org/OVirt_3.6_Release_Management [5] http://lists.ovirt.org/pipermail/users/2014-November/028875.html [6] https://bugzilla.redhat.com/show_bug.cgi?id=1155425 [7] http://goo.gl/zwkF3r [8] http://goo.gl/ZbUiMc -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
[ovirt-devel] [QE][ACTION REQUIRED] oVirt 3.6.0 status - release criteria
Hi, according to oVirt Release Process [1], a week after the n-1 release is out, a release criteria for the new release should be discussed. Release criteria will include MUST items and SHOULD items (held in wiki) MUST items will DELAY the release in any case. SHOULD items will include less critical flows and new features. SHOULD items will be handled as "best-effort" by component owners Component owners (e.g. Node, engine-core, vdsm) must ACK the criteria suggested. Release criteria discussions shouldn't take more then 2 weeks Progress on MUST items should be review every month, during the weekly meeting This means that starting today, we should define release criteria for November 12th. A couple of email have been already posted about this: * LINK: http://lists.ovirt.org/pipermail/devel/2014-August/008533.html * LINK: http://lists.ovirt.org/pipermail/devel/2014-September/008695.html as starting point for the discussion. Release management for 3.6.0 has been created [2] The key milestones for this release must be scheduled: Key Milestones Release criteria discussion start: 2014-10-22 Release criteria ready: 2014-11-12 Feature freeze: 60 Days before release First Test Day: 45 days before release Release Candidate: 30 days before release Release: 6 months after oVirt 3.5.0 release A tracker bug for 3.6.0 has been created [3] and currently show no blockers. There are 384 bugs [4] targeted to 3.6.0. Excluding node and documentation bugs we have 364 bugs [5] targeted to 3.6.0. [1] http://www.ovirt.org/Release_process [2] http://www.ovirt.org/OVirt_3.6_Release_Management [3] https://bugzilla.redhat.com/show_bug.cgi?id=1155425 [4] http://goo.gl/zwkF3r [5] http://goo.gl/ZbUiMc -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
