registry.local:9001 access fails after changing of OAM IP

Bug #1920577 reported by Ghada Khalil
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
StarlingX
Triaged
Low
Ghada Khalil

Bug Description

Brief Description
-----------------
After changing the OAM IP address, the SANs for the registry.local is not updated. This results in failure to access the local registry

Severity
--------
TBD.
This may end up more of a procedural/documentation exercise where updating the OAM IP address requires manual steps to handle the registry.local certificate

Steps to Reproduce
------------------
(keystone_admin)]$ system host-lock controller-0
(keystone_admin)]$ system oam-modify oam_subnet=<xxxx> oam_ip=<yyyy> oam_gateway_ip=<zzzz>
(keystone_admin)]$ system host-unlock controller-0

Expected Behavior
------------------
Access to the local registry is still functional

Actual Behavior
----------------
Access to the local registry fails

Reproducibility
---------------
100% Reproducible

System Configuration
--------------------
Any

Branch/Pull Time/Commit
-----------------------
stx master, but likely a day 1 issue

Last Pass
---------
It doesn't appear that this was tested or noticed previously

Timestamp/Logs
--------------
Not needed. Issue is reproducible.

Test Activity
-------------
Functional testing

Workaround
----------
Re-issue the registry.local certificate

Tags: stx.security
Ghada Khalil (gkhalil)
Changed in starlingx:
importance: Undecided → Low
assignee: nobody → Ghada Khalil (gkhalil)
tags: added: stx.security
Ghada Khalil (gkhalil)
Changed in starlingx:
status: New → Triaged
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.