---- On Wed, 20 Nov 2019 10:15:10 -0600 Ghanshyam Mann gmann@ghanshyammann.com wrote ----
---- On Wed, 20 Nov 2019 04:30:06 -0600 Andreas Jaeger aj@suse.com wrote ----
On 20/11/2019 09.08, Ghanshyam Mann wrote:
[...]
- barbican- https://review.opendev.org/#/c/695052/
- Some strange behaviour is happening in this, barbican grenade job run stable/train run.yaml always which is stoping this job to move to py3
Devstck patch is merged now and it defaults to py3.
below are the pending fix for grenade jobs which will fail now. Request the corresponding project to merge them.
- https://review.opendev.org/#/q/topic:drop-py27-support-devstack-default-py3+...
If any other job starts failing then below are the options to fix them:
Option1: migrate the failing py2 jobs to py3 with 'USE_PYTHON3: True in zuulv3 jobs' and 'DEVSTACK_GATE_USE_PYTHON3=True in legacy jobs'.
Options2: If the migration to py3 takes time due to any reason then restore those jobs to py2 by explicitly disabled the py3 via above variables.
-gmann
AFAIU, the stable jobs have a branch matcher, see https://opendev.org/openstack/barbican/src/branch/stable/train/.zuul.yaml#L1...
- and thus apply.
You need https://review.opendev.org/689458 and friends merged for all branches to fix this,
Thanks Andreas, that was something i was suspecting but could not understand how zuul picked the job inventory from stable/train every time and not from master where the master is branchless so should be eligible for the master gate.
One more thing, only run.yaml is taken from stable/train and rest all like pre.yaml etc is from the master branch. This is another the mystery I would like to learn :).
-gmann
Andreas
Andreas Jaeger aj@suse.com Twitter: jaegerandi SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D 90409 Nürnberg (HRB 36809, AG Nürnberg) GF: Felix Imendörffer GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126