Open Stack

 ---- On Fri, 13 Nov 2020 06:45:54 -0600 Herve Beraud <hberaud at redhat.com> wrote ----
 > 
 > 
 > Le ven. 13 nov. 2020 à 13:17, Radosław Piliszek <radoslaw.piliszek at gmail.com> a écrit :
 > On Fri, Nov 13, 2020 at 12:09 PM Herve Beraud <hberaud at redhat.com> wrote:
 > >
 > > Thanks for the heads up.
 > >
 > > Notice that I just submitted a series  of patches [1] to fix all masakari's stable branches, feel free to abandon these patches if they aren't needed anymore.
 > >
 > > [1] https://review.opendev.org/#/q/topic:fix-libvirt-focal+(status:open+OR+status:merged)
 > >
 > 
 > Ah, sorry, did not notice that.
 > I just went with [1] removing the pkg to avoid the naming issue altogether.
 > 
 > No problem 
 > 
 > My question is whether we could detect such issues more proactively?
 > 
 > Good question... I don't think that this kind of a check should be hosted on the release management side.Here our issue is more an environment issue, It's due to the fact that we decided to run the job `publish-openstack-artifacts` on ubuntu-focal, so to detect this kind of issue early I think that jobs on the projects side should rely on ubuntu-focal too. I'm not a Zuul expert and I don't know if it is possible to add a condition based on the branches (per example) to choose the right env (focal or not). By following this way I guess it could be possible to fail early on the project side, and it could allow you to fix this kind of issue well before proposing a new release. In other words, if projects's jobs env are aligned with release management our job we could catch them early.

 `publish-openstack-artifacts` job should not run for Focal for the stable gate and running it on Focal from Victoria onwards (like all other common jobs).

-gmann


 > We have other scenarios to consider. These are when no patches haven't been merged since a while on projects side, and where a release is proposed, in this case even if environments are aligned, in this case we aren't able to detect this kind of issue, and they will continue to occur during publication, as in this case.
 > It could be worth it to involve the infra team to see how to fail early.
 > Thoughts?
 > 
 > 
 > [1] https://review.opendev.org/762637
 > 
 > -yoctozepto
 > 
 > 
 > 
 > -- 
 > Hervé BeraudSenior Software Engineer at Red Hatirc: hberaudhttps://github.com/4383/https://twitter.com/4383hberaud
 > -----BEGIN PGP SIGNATURE-----
 > 
 > wsFcBAABCAAQBQJb4AwCCRAHwXRBNkGNegAALSkQAHrotwCiL3VMwDR0vcja10Q+
 > Kf31yCutl5bAlS7tOKpPQ9XN4oC0ZSThyNNFVrg8ail0SczHXsC4rOrsPblgGRN+
 > RQLoCm2eO1AkB0ubCYLaq0XqSaO+Uk81QxAPkyPCEGT6SRxXr2lhADK0T86kBnMP
 > F8RvGolu3EFjlqCVgeOZaR51PqwUlEhZXZuuNKrWZXg/oRiY4811GmnvzmUhgK5G
 > 5+f8mUg74hfjDbR2VhjTeaLKp0PhskjOIKY3vqHXofLuaqFDD+WrAy/NgDGvN22g
 > glGfj472T3xyHnUzM8ILgAGSghfzZF5Skj2qEeci9cB6K3Hm3osj+PbvfsXE/7Kw
 > m/xtm+FjnaywZEv54uCmVIzQsRIm1qJscu20Qw6Q0UiPpDFqD7O6tWSRKdX11UTZ
 > hwVQTMh9AKQDBEh2W9nnFi9kzSSNu4OQ1dRMcYHWfd9BEkccezxHwUM4Xyov5Fe0
 > qnbfzTB1tYkjU78loMWFaLa00ftSxP/DtQ//iYVyfVNfcCwfDszXLOqlkvGmY1/Y
 > F1ON0ONekDZkGJsDoS6QdiUSn8RZ2mHArGEWMV00EV5DCIbCXRvywXV43ckx8Z+3
 > B8qUJhBqJ8RS2F+vTs3DTaXqcktgJ4UkhYC2c1gImcPRyGrK9VY0sCT+1iA+wp/O
 > v6rDpkeNksZ9fFSyoY2o
 > =ECSj
 > -----END PGP SIGNATURE-----
 > 
 >