---- On Wed, 13 Mar 2019 13:34:29 -0500 Graham Hayes <gr@ham.ie> wrote ----
On 13/03/2019 18:27, Ghanshyam Mann wrote:
---- On Wed, 13 Mar 2019 00:21:46 -0500 Ghanshyam Mann <gmann@ghanshyammann.com> wrote ----
---- On Mon, 11 Mar 2019 01:03:51 -0500 Ghanshyam Mann <gmann@ghanshyammann.com> wrote ---- Updates: [...] *FAILING PROJECTS: NEED ACTION* nova - testing with tls-proxy disable - https://review.openstack.org/#/c/639017/ cinder - https://bugs.launchpad.net/cinder/+bug/1819819 designate - https://review.openstack.org/#/c/642319/
---- On Mon, 11 Mar 2019 22:04:55 -0500 Ghanshyam Mann <gmann@ghanshyammann.com> wrote ---- trove -https://review.openstack.org/#/c/642329/ zaqar - https://review.openstack.org/#/c/642349/ networking-midonet - https://review.openstack.org/#/c/639990/ freezer - not able to connect elasticsearch service - https://review.openstack.org/#/c/642610/ https://review.openstack.org/#/c/642607/ https://review.openstack.org/#/c/642608/ https://review.openstack.org/#/c/642605/
As Next step for all the projects listed above, either check if you can fix the failure otherwise make the failed job as n-v so that this migration which is going to happen tomorrow would not block your gate.
*Testing not started*: 4 Loci Openstack-Helm Rally
I am planning to merge the base patches in another 2.5 hours (21:00 UTC today). Try to check your gate failure (mentioned above) before that, otherwise, as last option I will push the patch to make failed jobs as n-v.
-gmann
We (designate) think we have the fix for ours [1] and I have a patch up to test it as well [2].
Don't worry about setting our jobs to n-v - it is a blocker for us, so nothing should merge until it is fixed.
1 - https://review.openstack.org/643119/ 2 - https://review.openstack.org/643127
ACK, thanks. Cinder also testing the fixes so I leave Cinder also from making job as n-v. - https://review.openstack.org/#/c/643130/ - https://review.openstack.org/#/c/641926/ -gmann
-gmann
*Testing Started *: 36 projects QA Nova Placement Cinder Glance Keystone Neutron Ironic Manila Designate Monasca Sahara Vitrage Congress Heat Kuryr Mistral: OK Murano Octavia: OK Trove Watcher Oslo Barbican Blazar Ec2-Api Cyborg Karbor Magnum Masakari Telemetry Zaqar Zun kolla Requirements Tricircle Freezer
#OK. no legacy xenial jobs so no action required Qinling Searchlight Senlin Solum Storlets Winstackers Adjutant Release Management I18n Horizon Documentation Cloudkitty Packaging-Rpm Powervmstackers Chef Openstack Tripleo Openstack Charms Openstackclient Openstacksdk Puppet Openstack Openstackansible Swift
*Testing not started*: 4 Loci Openstack-Helm Rally Tacker
- https://etherpad.openstack.org/p/legacy-job-bionic
-gmann
---- On Thu, 07 Mar 2019 20:34:57 -0600 Ghanshyam Mann <gmann@ghanshyammann.com> wrote ----
Updates on planning and dadlines: Legacy jobs to bionic.
I today TC ad hoc meeting on python3 transition & planning[1], we discussed about next steps on legacy jobs migration. Also you have seen the Zane's email about the agreement of moving the legacy jobs in Stein [2] which will help us to drop the py35 testing.
NEW DEADLINE: March 13th, we will merge the base pacthes which move legacy base jobs nodeset to bionic. ~70% of the project legacy jobs which depends on their parent job nodeset will start running on bionic.
DO NOT BLOCK GATE: After deadline (when base nodeset is bionic) if any of the your legacy jobs are failing then, make those jobs non voting and keep working on fix.
How to test your project's legacy jobs : I have updated the base patches which move the legacy base jobs to bionic and ready for projects to tets their gate. Detailed steps and testing pacthes example are in this etherpad- https://etherpad.openstack.org/p/legacy-job-bionic
For quick reference, I am writting the steps to test your legacy jobs on bionic: -------------------------------------------------- Step 1. Push the testing DNM patch on your project owned repos with: - Depends-On: https://review.openstack.org/#/c/641886/ -Remove or change the nodeset to Bionic from your repo owned legacy jobs (if any of the legacy jobs has overridden the nodeset from parent job) Example: https://review.openstack.org/#/c/639017
Step 2. If you have any legacy job not derived from base jobs then, you need to migrate their nodeset to bionic which are defined in - https://review.openstack.org/#/c/639018/ Example - https://review.openstack.org/#/c/639361/
Step3. if any of the job start failing on bionic then, either fix it before deadline of March 13th or make failing job as n-v and fix later. --------------------------------------------------
Feel free to ping me for any query or help.
[1] http://eavesdrop.openstack.org/meetings/tc_python3/2019/tc_python3.2019-03-0... [2] http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003610.htm...
-gmann
---- On Thu, 07 Mar 2019 10:55:50 -0600 Ghanshyam Mann <gmann@ghanshyammann.com> wrote ---- > Thanks all who volunteer for their project and testing the jobs on bionic. > > Reminder for all other projects to plan for this activity. Only 5-6 projects have started the testing. > I request PTL to plan someone for this activity. Feel free to ping me on #openstack-qa for any clarification. > > Thanks. > > -gmann > > ---- On Mon, 25 Feb 2019 09:05:47 -0600 Ghanshyam Mann <gmann@ghanshyammann.com> wrote ---- > > Hi Everyone, > > > > During Dec/Jan month, we have migrated the devstack jobs (zuulv3 native jobs) from Xenial to Bionic. [1]. > > > > But that did not move all gate job to Bionic as there are a large number of jobs are still the legacy job. All the legacy job still use Xenial as nodeset. > > As per the decided runtime for Stein, we need to test everything on OpenStack CI/CD on Bionic - https://governance.openstack.org/tc/reference/runtimes/stein.html > > This is something we discussed TC meeting as one of the Stein items to finish in openstack community[2]. > > > > I am starting this ML thread to coordinate the work to move all the legacy jobs to Bionic. I have created the > > Etherpad to include more details and status check for each project gate- https://etherpad.openstack.org/p/legacy-job-bionic > > > > The approach is the same as we did for previous migration for devstack jobs. > > 1. Push patch which migrates the legacy base jobs to bionic - 1. https://review.openstack.org/#/c/639096/ > > 2. Each Project team, add the testing patch with Depends-on on base patch (example 639096) and confirm the status > > of their gate on etherpad - Example: https://review.openstack.org/#/c/639017 > > 3. Project jobs not using base job as parent, need to migrate their legacy job to bionic by own. > > > > Please add yourself as your project volunteer in etherpad and update the status accordingly. I am tagging [ptl] in this thread so that they can assign > > someone from their team if no volunteer. > > > > Deadline: 1st April to merge the base legacy job to bionic. That gives around 1 month to test the jobs which I feel enough for each project. > > let me know if more time is needed, we can adjust the same. The goal is to finish this activity before Stein release. > > > > > > [1] http://lists.openstack.org/pipermail/openstack-discuss/2018-December/000837.... > > https://etherpad.openstack.org/p/devstack-bionic > > > > [2] http://eavesdrop.openstack.org/meetings/tc/2019/tc.2019-02-07-14.00.html > > > > > > -gmann > > > > > > > >