nginx-ingress-controller apply-failed during setup of the StarlingX
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Critical
|
Reinildes Oliveira |
Bug Description
Brief Description
-----------------
nginx-ingress-
Severity
--------
<Critical: System/Feature is not usable due to the defect>
Steps to Reproduce
------------------
Try to install latest StarlingX image
Expected Behavior
------------------
StarlingX installation should work
Actual Behavior
----------------
Installation failed at the setup stage:
[sysadmin@
+------
| Alarm ID | Reason Text | Entity ID | Severity | Time Stamp |
+------
| 750.002 | Application Apply Failure | k8s_application
| | | ingress-controller | | 19.284945 |
| | | | | |
| 200.001 | controller-0 was administratively locked to take it out-of-service. | host=controller-0 | warning | 2022-05-06T11:21: |
| | | | | 02.657011 |
| | | | | |
+------
[sysadmin@
+------
| application | version | manifest name | manifest file | status | progress |
+------
| nginx-ingress-
+------
Reproducibility
---------------
100% reproducible
System Configuration
-------
all configurations are affected
Branch/Pull Time/Commit
-------
master-
Last Pass
---------
sorry, I don't remember exactly
Timestamp/Logs
--------------
will be attached
Test Activity
-------------
Sanity
Workaround
----------
-
Changed in starlingx: | |
assignee: | Ghada Khalil (gkhalil) → nobody |
Changed in starlingx: | |
assignee: | nobody → Reinildes Oliveira (rjosemat) |
@Alex, I believe the sanity systems use a private registry. Did you pull the new images as per this stx email thread: http:// lists.starlingx .io/pipermail/ starlingx- discuss/ 2022-May/ 012955. html