Login to local registry failed while re-applying platform-integ-apps after changing OAM IP

Bug #1881260 reported by Yatindra Shashi
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
StarlingX
Triaged
Medium
David Sullivan

Bug Description

Brief Description
-----------------
I changed the OAM IP of the Stx host and tried to re-apply the platform-integ-app which end failing and error in the sysinv.log is that unable to login to local registry because of x509 certificate was invalid for the changed OAM IP.

Severity
--------
Provide the severity of the defect.
<Major: If the OAM IP changed >

Steps to Reproduce
------------------
Change the OAM IP and re-apply the applications

Expected Behavior
------------------
Applying platform-intgration app should have been successfull.

Actual Behavior
----------------
platform integ-app failed to apply

Reproducibility
---------------

System Configuration
--------------------
SimpleX- AIO config

Branch/Pull Time/Commit
-----------------------
STX 3.0

Last Pass
---------

Timestamp/Logs
--------------

After changing OAM IP to 192.168.49.80 from 172.28.235.202, Issue is as below.

2020-05-27 16:06:04.220 90332 ERROR sysinv.conductor.kube_app KubeAppApplyFailure: Deployment of application platform-integ-apps (1.0-8) failed: failed to download one or more image(s).
2020-05-27 16:06:04.220 90332 ERROR sysinv.conductor.kube_app
sysinv 2020-05-27 16:06:04.370 90332 ERROR sysinv.conductor.kube_app [-] Image registry.local:9001/docker.io/starlingx/ceph-config-helper:v1.15.0 download failed from local registry: 500 Server Error: Internal Server Error ("Get https://registry.local:9001/v2/docker.io/starlingx/ceph-config-helper/manifests/v1.15.0: Get https://192.168.49.80:9002/token/?account=admin&scope=repository%3Adocker.io%2Fstarlingx%2Fceph-config-helper%3Apull&service=192.168.204.1%3A9001: x509: certificate is valid for 192.168.204.1, 172.28.235.202, not 192.168.49.80"): APIError: 500 Server Error: Internal Server Error ("Get https://registry.local:9001/v2/docker.io/starlingx/ceph-config-helper/manifests/v1.15.0: Get https://192.168.49.80:9002/token/?account=admin&scope=repository%3Adocker.io%2Fstarlingx%2Fceph-config-helper%3Apull&service=192.168.204.1%3A9001: x509: certificate is valid for 192.168.204.1, 172.28.235.202, not 192.168.49.80")
sysinv 2020-05-27 16:06:04.375 90332 ERROR sysinv.conductor.kube_app [-] Application apply aborted!.: KubeAppApplyFailure: Deployment of application platform-integ-apps (1.0-8) failed: failed to download one or more image(s).
sysinv 2020-05-27 16:06:04.376 90332 INFO sysinv.conductor.kube_app [-] Deregister the abort status of app platform-integ-apps
sysinv 2020-05-27 16:06:04.376 90332 ERROR sysinv.openstack.common.rpc.amqp [-] Exception during message handling: KubeAppApplyFailure: Deployment of application platform-integ-apps (1.0-8) failed: failed to download one or more image(s).
2020-05-27 16:06:04.376 90332 ERROR sysinv.openstack.common.rpc.amqp Traceback (most recent call last):
2020-05-27 16:06:04.376 90332 ERROR sysinv.openstack.common.rpc.amqp File "/usr/lib64/python2.7/site-packages/sysinv/openstack/common/rpc/amqp.py", line 437, in _process_data

TASK [common/push-docker-images : Log in to local registry] ********************
fatal: [localhost]: FAILED! => {"changed": false, "msg": "Logging into registry.local:9001 for user admin failed - 500 Server Error: Internal Server Error (\"Get https://registry.local:9001/v2/: Get https://192.168.49.80:9002/token/?account=admin&client_id=docker&offline_token=true&service=192.168.204.1%3A9001: x509: certificate is valid for 192.168.204.1, 172.28.235.202, not 192.168.49.80\")"}

Test Activity
-------------

 Workaround
 ----------
 Describe workaround if available

Revision history for this message
Yatindra Shashi (yshashi) wrote :
Revision history for this message
Ghada Khalil (gkhalil) wrote :
Changed in starlingx:
status: New → Triaged
importance: Undecided → Medium
assignee: nobody → David Sullivan (dsullivanwr)
tags: added: stx.4.0 stx.config
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

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