Comment 7 for bug 1907657

Revision history for this message
Sagi (Sergey) Shnaidman (sshnaidm) wrote :

OK, so child job got wrong IP of container registry.

Content provider is running on 217.182.141.2:
https://6891a4bea265420bbf27-75977e1da0623c0b07e405a8a7f1a45b.ssl.cf5.rackcdn.com/765964/4/gate/tripleo-ci-centos-8-content-provider/9527caf/job-output.txt

Running podman registry and repository on 217.182.141.21 for branch master and DLRN tag no tag

Child job tripleo-ci-centos-8-scenario000-multinode-oooq-container-updates gets from zuul:
    provider_job_branch: master
    registry_ip_address_branch:
      master: 10.4.70.228
https://7a89c7d607922873abcd-a2a9d29289e3c443a1047aebafc6ba1b.ssl.cf2.rackcdn.com/765964/4/gate/tripleo-ci-centos-8-scenario000-multinode-oooq-container-updates/f02eecd/zuul-info/inventory.yaml

So zuul passed wrong IP address to child jobs. The same issue appears in other jobs in this bug, wrong IP is passed to child job.