Deployment of overcloud fails while trying to connect to registry.redhat.io

Solution In Progress - Updated -

Issue

  • The deployment fails while trying to connect to the registry. The node can ping the registry from the command line but cannot connect while running the playbook.

  • The deployment installs the OS but appears to get stuck trying to connect to the registry. I had thought this would pull from the director but it's going to redhat instead. It should be able to connect regardless and looks like it's being blocked somewhere. The host networking is all up and I can ping the gateway on the external interface.

  • Overcloud is deployed using the following:

openstack overcloud deploy --templates \
-n /home/stack/templates/network_data.yaml \
-e /home/stack/templates/custom-domain.yaml \
-e /usr/share/openstack-tripleo-heat-templates/environments/network-isolation.yaml \
-e /usr/share/openstack-tripleo-heat-templates/environments/network-environment.yaml \
-e /home/stack/templates/network-environment-overrides.yaml \
-e /home/stack/containers-prepare-parameter.yaml \
--ntp-server net-ntp00.localdomain
  • Overcloud deployment fails with the following error:
TASK [Run podman login] ********************************************************
Saturday 16 May 2020  14:29:43 -0500 (0:00:01.213)       0:02:56.927 **********

TASK [tripleo-podman : Perform container registry login(s)] ********************
Saturday 16 May 2020  14:29:44 -0500 (0:00:00.233)       0:02:57.160 **********
failed: [overcloud-controller-0] (item={'key': 'registry.redhat.io', 'value': {'username': 'xxx'}}) => {"ansible_loop_var": "item", "changed": true, "cmd": "podman login --username=$REGISTRY_USERNAME             --password=$REGISTRY_PASSWORD             --tls-verify=True             $REGISTRY", "delta": "0:01:00.128299", "end": "2020-05-16 15:30:44.876233", "item": {"key": "registry.redhat.io", "value": {"username": "xxx"}}, "msg": "non-zero return code", "rc": 125, "start": "2020-05-16 15:29:44.747934", "stderr": "Error: error authenticating creds for \"registry.redhat.io\": error pinging docker registry registry.redhat.io: Get https://registry.redhat.io/v2/: dial tcp 104.126.177.170:443: i/o timeout", "stderr_lines": ["Error: error authenticating creds for \"registry.redhat.io\": error pinging docker registry registry.redhat.io: Get https://registry.redhat.io/v2/: dial tcp 104.126.177.170:443: i/o timeout"], "stdout": "", "stdout_lines": []}


NO MORE HOSTS LEFT *************************************************************

PLAY RECAP *********************************************************************
overcloud-controller-0     : ok=109  changed=39   unreachable=0    failed=1    skipped=47   rescued=0    ignored=0  
overcloud-novacompute-0    : ok=59   changed=12   unreachable=0    failed=0    skipped=24   rescued=0    ignored=0  
undercloud                 : ok=6    changed=1    unreachable=0    failed=0    skipped=0    rescued=0    ignored=0  

Saturday 16 May 2020  14:30:44 -0500 (0:01:00.812)       0:03:57.973 **********

Environment

  • Red Hat OpenStack Platform 16.0 (RHOSP)

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In