Open Stack

Sorry for top posting but I don't have a precise quote to reply to.
What I wish to say is that I am trying to get Debian tested in CI but
it looks like python3.9 might be playing tricks.
I would appreciate it if someone more knowledgeable in Nova and
Neutron internals could take a look at failures in
https://review.opendev.org/c/openstack/devstack/+/789083
Do note slightly different tests fail each run.

-yoctozepto

On Tue, Sep 7, 2021 at 7:40 PM Sean Mooney <smooney at redhat.com> wrote:
>
> On Tue, 2021-09-07 at 11:44 -0500, Ghanshyam Mann wrote:
> >  ---- On Tue, 07 Sep 2021 11:03:09 -0500 Jeremy Stanley <fungi at yuggoth.org> wrote ----
> >  > On 2021-09-07 10:38:12 -0500 (-0500), Ghanshyam Mann wrote:
> >  > [...]
> >  > > Definitely we can move to 3.9 as official testing runtime if any
> >  > > of the currently supporting distro support it as default.
> >  > [...]
> >  >
> >  > I don't think it needs to be the default Python in a release so long
> >  > as it's available. To quote from
> >  > https://governance.openstack.org/tc/resolutions/20181024-python-update-process.html#unit-tests
> >  >
> >  >     "Prior to the beginning of each release cycle, the TC will
> >  >     designate the minor versions of Python 3 that will be tested in
> >  >     that release using the following criteria:
> >  >     [...]
> >  >     The latest released version of Python 3 that is available in any
> >  >     distribution we can feasibly use for testing. It need not be a
> >  >     long-term-supported release, but could be a non-LTS version of
> >  >     Ubuntu, Fedora, openSUSE Leap, or even a rolling release
> >  >     distribution (such as Debian Testing or openSUSE Tumbleweed) if
> >  >     necessary."
> >  >
> >  > I recall clearly that this was added so that we would attempt to
> >  > test the latest available version of Python in order to help avoid
> >  > having software which is clearly non-functional on distributions
> >  > which are working in parallel to update their defaults (and so might
> >  > reasonably want to ship OpenStack with an interpreter version which
> >  > was not their default at the time we started development for that
> >  > coordinated release).
> >
> > Sure, and by seeing the current py39 job it is mostly passing
> > - https://zuul.openstack.org/builds?job_name=openstack-tox-py39
> >
> > Let's discuss it in PTG and hopefully by then we might see centos9
> > release or closure plan to release dates and as discussed during
> > defining the Yoga tetsing runtime, we can update it once if
> > centos9 is there then update centos versionb as well as the py version
> > otherwise we can disucss only making py39 jobs voting which are running
> > on ubuntu focal.
> not sure if centos 9 will be avaiable by ptg but i hope so.
> in anycaes ubuntu 21.04 default to python 3.9 and debian 11 "bullseye" which is the latest
> __stable__ debian release also default to python 3.9 as does fedora 34 but that a much bigger moving target.
>
> in general 3.9 is avaiable if not default in several distro which is why i would like to include it for
> required testing e.g. move the current non voting jobs to voting for unit and functest at least.
> it woudl be nice if we could have at least on tempst job on py39 too but sure lets pick this up at the ptg.
>
> im not agaisnt keeping support for phython 3.6 and centos 8 stream for yoga but i would like to be abel to
> do at least some smoke tests with centos 9 stream if its avaiable.
>
> the none stream version fo centos 8 i think is end of life at the end of this year? but the centos 8 stream
> release will continue untile rhel 8 is eol so that shoudl still be supproted to some degree for the full yoga cycle.
> the none stream version however wont be supported when yoga releases.
>
>
> >
> > -gmann
> >
> >  > --
> >  > Jeremy Stanley
> >  >
> >
>
>
>