been digging a bit here but the main problem is we have no/few logs when we actually hit RETRY e.g. at [1] no logs there besides the main out.txt
the failing task is happening *very* early, before any of undercloud or overcloud deployment. In fact this is before we execute any tripleo/quickstart code - it happens during configure-mirrors role invocation [2] which is in zuul-jobs. The failing task specifically is at [3]
This is why i thought 10.0.0.250 came from vexx but according to guilhemesp on IRC it is not the case.
been digging a bit here but the main problem is we have no/few logs when we actually hit RETRY e.g. at [1] no logs there besides the main out.txt
the failing task is happening *very* early, before any of undercloud or overcloud deployment. In fact this is before we execute any tripleo/quickstart code - it happens during configure-mirrors role invocation [2] which is in zuul-jobs. The failing task specifically is at [3]
This is why i thought 10.0.0.250 came from vexx but according to guilhemesp on IRC it is not the case.
[1] https:/ /logserver. rdoproject. org/openstack- periodic- integration- stable1/ opendev. org/openstack/ tripleo- ci/master/ periodic- tripleo- ci-centos- 9-ovb-3ctlr_ 1comp_1supp- featureset039- wallaby/ d2eb845/ logs/ /opendev. org/zuul/ zuul-jobs/ src/branch/ master/ roles/configure -mirrors/ tasks /opendev. org/zuul/ zuul-jobs/ src/commit/ 2bc6d7b9c30c27c f9e7a1b53cb8a12 8a493d89af/ roles/configure -mirrors/ handlers/ main.yaml# L10
[2] https:/
[3] https:/