[goals][Drop Python 2.7 Support] Week R-13 Update (we are at deadline)

Ghanshyam Mann gmann at ghanshyammann.com
Mon Feb 17 14:06:05 UTC 2020


 ---- On Mon, 17 Feb 2020 02:19:53 -0600 Akihiro Motoki <amotoki at gmail.com> wrote ----
 > On Mon, Feb 17, 2020 at 1:02 PM Ghanshyam Mann <gmann at ghanshyammann.com> wrote:
 > >
 > > Hello Everyone,
 > >
 > > Below is the progress on "Drop Python 2.7 Support" at end of R-13 week.
 > >
 > > Schedule: https://governance.openstack.org/tc/goals/selected/ussuri/drop-py27.html#schedule
 > >
 > >
 > > Highlights:
 > > ========
 > > * Deadline was M-2 (R-13 week).
 > >
 > > * Things are breaking and being fixed daily.
 > >
 > > * Do not worry about the gate failure, it is better to break it now and fix so that we can smoothly release Ussuri.
 > >
 > > * Tempest has dropped the py2 and stop running the py2 jobs and so does devstack.
 > >
 > > * tempest-full job has been moved to py2 (it started running on py3 when devstack default to py3). This job is not supposed
 > > to run on master gate (except d-g which should keep running on py2 jobs). tempest-full-py3 is the py3 version of it. But few
 > > master jobs derived from tempest-full needs to either start using tempest-full-py3 or explicitly enable py3. I will be working
 > > on those next week.
 > >
 > > * Bugs & Status:  No open bugs as of now. Below is the status of last week's bugs.
 > 
 > There is another bug fixed. The release notes job in stable branches
 > was broken as the job is run against the master branch but it was run
 > with python 2.7.
 > The project-template in openstack-zuul-jobs was updated [1] and
 > build-openstack-releasenotes job now runs with python3 in all stable
 > branches.
 > If there are jobs in stable branches which runs using the master
 > branch, the similar change might be needed.
 > [1] https://review.opendev.org/#/c/706825/

Thanks amotoki for updates and fix. This is very helpful. 

Yeah, we need to switch the master related jobs on py3 irrespective where they run.

-gmann 

 > 
 > >
 > > ** QA dropped py3.5 support also from many tooling like stackviz etc which are branchless and should keep working on
 > > stable py3.5 env. We have reverted the dropping py3.5 and working now.
 > >
 > > ** Nova stable branches are still falling for the u-c reason on nova-live-migration. Fixes are up[2]
 > > *** Fixed and gate is green.
 > >
 > > * * Tempest tox 'all-plugin' usage issue[3]
 > > *** Fixed and gate is green.
 > >
 > > ** neutron-vpass in-tree plugin issue
 > > *** Fixed and gate is green.
 > >
 > > NOTE: I know few py2.7 drop patches are failing on few projects, I will continue debugging those. Help from the failing project will be greatly appreciated to meet the deadline.
 > >
 > >
 > > Project wise status and need reviews:
 > > ============================
 > > Phase-1 status:
 > > The OpenStack services have not merged the py2 drop patches:
 > > NOTE: This was supposed to be completed by milestone-1 (Dec 13th, 19).
 > >
 > > * Adjutant
 > > ** https://review.opendev.org/#/c/706723/
 > > * Masakari
 > > ** https://review.opendev.org/#/c/694551/
 > > * Qinling
 > > **  https://review.opendev.org/#/c/694687/
 > >
 > > Phase-2 status:
 > > By today, we should be completing the phase-2 work which is nothing but drop py2 from everything except requirement repo.
 > > But we have few repos to merge the patches on priority.
 > >
 > > * Open review: https://review.opendev.org/#/q/topic:drop-py27-support+status:open
 > >
 > >
 > > How you can help:
 > > ==============
 > > - Review the patches. Push the patches if I missed any repo.
 > >
 > > [1] http://lists.openstack.org/pipermail/openstack-discuss/2020-February/012463.html
 > > [2] https://review.opendev.org/#/q/I8190f93e0a754fa59ed848a3a230d1ef63a06abc
 > > [3] https://bugs.launchpad.net/tempest/+bug/1862240
 > > [4] https://review.opendev.org/#/q/topic:bug/1862240+(status:open+OR+status:merged)
 > >
 > > -gmann
 > >
 > >
 > 



More information about the openstack-discuss mailing list