I think we are now clear of this. Network component promoted [1] commit_hash: dcdab7b480e4fc62b567a08d16879bea82a74967
Latest run of the integration line today [2] has no examples (compared to yesterday see comment #6 above).
However I still don't see a green run on the network FS1 job for which this bug was filed in the first place - all red currently at [3]. Holding on closing this out for now and especially, how did we promote network without that job?
I think we are now clear of this. Network component promoted [1] commit_hash: dcdab7b480e4fc6 2b567a08d16879b ea82a74967
Latest run of the integration line today [2] has no examples (compared to yesterday see comment #6 above).
However I still don't see a green run on the network FS1 job for which this bug was filed in the first place - all red currently at [3]. Holding on closing this out for now and especially, how did we promote network without that job?
Will catchup with dasm & rlandy later and update.
Trying a testproject for now at [4]
[1] https:/ /trunk. rdoproject. org/centos9- master/ component/ network/ promoted- components/ commit. yaml /review. rdoproject. org/zuul/ buildset/ af8e6da8e7b2461 9957694aa2a6299 1f /review. rdoproject. org/zuul/ builds? job_name= periodic- tripleo- ci-centos- 9-ovb-3ctlr_ 1comp-featurese t001-network- master /review. rdoproject. org/r/c/ testproject/ +/42489
[2] https:/
[3] https:/
[4] https:/