rancher: UI is stuck on saving "custom" cluster info in 2.4.3 - Note: Clusters can still be upgraded with docker command
After upgrading from rancher 2.3.6 to 2.4.3 kubernetes upgrade is stalling and not completing.
| Useful | Info |
|---|---|
| Versions | Rancher v2.4.3 UI: v2.4.22 |
| Route | undefined |
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 27 (11 by maintainers)
Commits related to this issue
- Improving how we handle a failure to get a scanConfig It appears that sometimes the cisscanconfig schema isn't present (I haven't been able to consistently reproduce) which causes the UI to prevent t... — committed to codyrancher/ui by codyrancher 4 years ago
- Improving how we handle a failure to get a scanConfig It appears that sometimes the cisscanconfig schema isn't present (I haven't been able to consistently reproduce) which causes the UI to prevent t... — committed to codyrancher/ui by codyrancher 4 years ago
- Make the default scheduledClusterScan.enabled to be a boolean Enabled was being set to 'false' instead of false but this was being masked by the execution of initScheduledClusterScan. When the KDM va... — committed to codyrancher/ui by codyrancher 4 years ago
- Make the default scheduledClusterScan.enabled to be a boolean Enabled was being set to 'false' instead of false but this was being masked by the execution of initScheduledClusterScan. When the KDM va... — committed to codyrancher/ui by codyrancher 4 years ago
Reproduced reliably with the following steps:
sudo docker run -d --restart=unless-stopped -p 80:80 -p 443:443 -e "CATTLE_RKE_METADATA_CONFIG={\"refresh-interval-minutes\":\"144000\",\"url\":\"https://raw.githubusercontent.com/rancher-max/rke-data/master/data.json\"}" rancher/rancher:master-headValidated in both master-head and v2.4-head using UI index
latest2andlatest-2.4respectivelyDefault value is set to
Nofor Scheduled CIS Scan EnabledCreating cluster does not stall. Creates successfully
Upgrading cluster is successful
No error occurs in console logs
NOTE: This fixes cluster creation/upgrade, but the error of having no CIS Scan Profiles is still present. #27005 will address that.