R5.0:RHOSP13: overcloud is not able to pull images from insecure registry apart from undercloud 192.168.24.1:8787

Bug #1806828 reported by alok kumar
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
Status tracked in Trunk
R5.0
New
High
alexey-mr
Trunk
New
High
alexey-mr

Bug Description

contrail insecure registry is not getting added in /etc/sysconfig/docker on the overcloud.

only below entry is found:
[heat-admin@overcloud-contrailcontroller-1 ~]$ cat /etc/sysconfig/docker| grep INSECURE_REGISTRY
INSECURE_REGISTRY="--insecure-registry 192.168.24.1:8787"

Registry config in contrail-services.yaml:

ContrailRegistryInsecure: true
DockerInsecureRegistryAddress: 192.168.24.1:8787
ContrailRegistry: 10.204.217.152:5010

If we are not pulling the contrail images to undercloud and want to pull directly from insecure registry 10.204.217.152:5010 on the overcloud, then it fails probably due to above mentioned reason.

Error seen while stack deployement:

overcloud.AllNodesDeploySteps.ContrailControllerDeployment_Step3.0:
  resource_type: OS::Heat::StructuredDeployment
  physical_resource_id: 146235be-44da-4fae-8dc7-64b612393d83
  status: CREATE_FAILED
  status_reason: |
    Error: resources[0]: Deployment to server failed: deploy_status_code : Deployment exited with non-zero status code: 2
  deploy_stdout: |
    ...
            "stderr: Get https://10.204.217.152:5010/v1/_ping: http: server gave HTTP response to HTTPS client",
            "Error pulling 10.204.217.152:5010/contrail-external-zookeeper:rhel-queens-5.0-388. [1]",
            "stdout: Trying to pull repository 10.204.217.152:5010/contrail-external-zookeeper ... "

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.