Apps secrets to access the controller registry are not created consistently
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
Tee Ngo |
Bug Description
Brief Description
-----------------
K8S pod and app secrets to access the controller registry are not named consistently and are not created the same way. For instance, default-
Severity
--------
Major
Steps to Reproduce
------------------
Scenario #1
Bring up a DC system without oidc-auth-apps
Deploy a subcloud with Redfish install option
Scenario #2
In a running DC system with oidc-auth-apps where no subcloud has been deployed with Redfish install before
Swact to controller-1
Remove the app
Deploy a subcloud with Redfish install option
Expected Behavior
------------------
Subcloud is deployed successfully
Actual Behavior
----------------
Due to the dependency on the default-
Each app should create its own secrets and not depend on the existence of another app especially an optional one in order to function.
Reproducibility
---------------
Reproducible
System Configuration
-------
Distributed Cloud
Branch/Pull Time/Commit
-------
Nov. 29th master load
Last Pass
---------
I think this is a test escape
Timestamp/Logs
--------------
N/A
Test Activity
-------------
Code inspection
Workaround
----------
Manually create a registry secret in rvmc namespace
Changed in starlingx: | |
assignee: | nobody → Tee Ngo (teewrs) |
tags: | added: stx.apps stx.containers |
Changed in starlingx: | |
importance: | Undecided → Medium |
status: | New → Triaged |
tags: | added: stx.5.0 |
Fixed by: https:/ /review. opendev. org/c/starlingx /config/ +/766377
Merged on 2020-12-15