Login to local registry failed while re-applying platform-integ-apps after changing OAM IP
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.
2020-05-27 16:06:04.220 90332 ERROR sysinv.
sysinv 2020-05-27 16:06:04.370 90332 ERROR sysinv.
sysinv 2020-05-27 16:06:04.375 90332 ERROR sysinv.
sysinv 2020-05-27 16:06:04.376 90332 INFO sysinv.
sysinv 2020-05-27 16:06:04.376 90332 ERROR sysinv.
2020-05-27 16:06:04.376 90332 ERROR sysinv.
2020-05-27 16:06:04.376 90332 ERROR sysinv.
TASK [common/
fatal: [localhost]: FAILED! => {"changed": false, "msg": "Logging into registry.local:9001 for user admin failed - 500 Server Error: Internal Server Error (\"Get https:/
Test Activity
-------------
Workaround
----------
Describe workaround if available
This is a duplicate of LP: https:/ /bugs.launchpad .net/starlingx/ +bug/1878451