K8s dashboard install fails under pybox VM instalallation method
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Low
|
Bruno Drugowick Muniz |
Bug Description
Brief Description
-----------------
When using the pybox installation method, the installation of the k8s dashboard fails.
Severity
--------
Provide the severity of the defect.
<Critical: System/Feature is not usable due to the defect>
Steps to Reproduce
------------------
Follow the pybox installation process https:/
When the installation process reaches the k8s dashboard installation step, it fails.
Expected Behavior
------------------
k8s dashboard should successfully install.
Actual Behavior
----------------
k8s dashboard is not installed.
Reproducibility
---------------
The issue is 100% reproducible.
System Configuration
-------
AIO-SX in a VirtualBox VM
Host OS - Ubuntu 22.04
VirtualBox - 6.38 installed from Ubuntu repo using apt
Timestamp/Logs
--------------
2023-07-11 21:52:47,778: sending incremental file list
2023-07-11 21:52:47,783: admin-login.yaml
2023-07-11 21:52:47,783: dashboard-
2023-07-11 21:52:47,826:
2023-07-11 21:52:47,826: sent 916 bytes received 54 bytes 1,940.00 bytes/sec
2023-07-11 21:52:47,826: total size is 724 speedup is 0.75
2023-07-11 21:52:47,827: ###### Adding port-forward rule for kubernetes dashboard ######
2023-07-11 21:52:47,827: Creating port-forwarding rule to: StarlingX-
2023-07-11 21:52:47,876: ###### Installing Kubernetes dashboard ######
2023-07-11 21:52:47,876: #### Running command over ssh: 'source /etc/platform/
2023-07-11 21:52:48,889: |Hang tight while we grab the latest from your chart repositories...
2023-07-11 21:52:48,890: |...Successfully got an update from the "starlingx" chart repository
2023-07-11 21:52:48,890: |...Successfully got an update from the "stx-platform" chart repository
2023-07-11 21:52:48,890: |Update Complete. ⎈ Happy Helming!⎈
2023-07-11 21:52:49,110: |"kubernetes-
2023-07-11 21:52:51,392: |Error: rendered manifests contain a resource that already exists. Unable to continue with install: CustomResourceD
2023-07-11 21:52:51,394: |
2023-07-11 21:52:51,395: Return code: 1
2023-07-11 21:52:51,395: Installation of Kubernetes dashboard failed, expecting exit code of 0 but got 1.
2023-07-11 21:52:51,395: INSTALL FAILED, ABORTING!
2023-07-11 21:52:51,395: =======
2023-07-11 21:52:51,395: Time in stage 'create-lab': 16.42s
2023-07-11 21:52:51,395: Time in stage 'install-
2023-07-11 21:52:51,395: Time in stage 'config-
2023-07-11 21:52:51,395: Time in stage 'rsync-config': 52.36s
2023-07-11 21:52:51,395: Time in stage 'lab-setup1': 1m 4.13s
2023-07-11 21:52:51,395: Time in stage 'unlock-
2023-07-11 21:52:51,395: Time in stage 'enable-
2023-07-11 21:52:51,395: Total time: 1h 4m 16.88s
2023-07-11 21:52:51,395: =======
2023-07-11 21:52:51,395: Exception details: Installation of Kubernetes dashboard failed, expecting exit code of 0 but got 1.
Traceback (most recent call last):
File "/home/
STAGE_
File "/home/
return func(*args, **kwargs)
File "/home/
raise Exception(msg)
Changed in starlingx: | |
assignee: | nobody → Bruno Drugowick Muniz (brunomuniz) |
tags: | added: virtual-deployment |
Changed in starlingx: | |
status: | New → In Progress |
Changed in starlingx: | |
status: | In Progress → Fix Released |
Changed in starlingx: | |
importance: | Undecided → Low |
tags: |
added: stx.virtual-deployment removed: virtual-deployment |
Thanks for the report.
It looks like the latest version of the Kubernetes Dashboard has a breaking change (see https:/ /github. com/kubernetes/ dashboard/ releases/ tag/v3. 0.0-alpha0). There's the following section there:
> "Kubernetes Dashboard now requires cert-manager and nginx-ingress- controller to work properly. Please make sure you have them installed in your cluster if you want to use a manifest-based installation path. The helm-based approach can install all required dependencies automatically for you if needed."
On their artifacthub.io it says it's possible to ignore cert-manager and nginx if you already have them installed, which allows us to install the latest version, but I'm making sure there are no other impacts (or improvements that we should consider).
So I might lock the versions to get this fixed and open a Task for the improvements if no one objects to that.