My understanding of what's happening:
1. IPA deployment is working fine, packages installed and ipa configured:
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/481c0be/logs/supplemental/home/cloud-user/deploy_freeipa.log.txt.gz
2. In the next package installation attempt (part of the tripleo-ipa preparation script, it fails to reach the package mirrors:
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/481c0be/logs/supplemental/home/cloud-user/ipa_prep.sh.log.txt.gz
I'd say step 1 is the root cause, i guess it's changing dns configuration or something like that. Would it be possible to hold a node for that job to inspect the status of the server after the failure?
My understanding of what's happening:
1. IPA deployment is working fine, packages installed and ipa configured:
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/ 481c0be/ logs/supplement al/home/ cloud-user/ deploy_ freeipa. log.txt. gz
2. In the next package installation attempt (part of the tripleo-ipa preparation script, it fails to reach the package mirrors:
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/ 481c0be/ logs/supplement al/home/ cloud-user/ ipa_prep. sh.log. txt.gz
I'd say step 1 is the root cause, i guess it's changing dns configuration or something like that. Would it be possible to hold a node for that job to inspect the status of the server after the failure?