Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Editing a cluster config gives error "Cannot read properties of null (reading 'save')" / "a.config is null" #13181

Open
osklil opened this issue Jan 23, 2025 · 4 comments
Labels
area/vsphere kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this
Milestone

Comments

@osklil
Copy link

osklil commented Jan 23, 2025

Setup

  • Rancher version: 2.10.1
  • Rancher UI Extensions: none
  • Browser type & version: Mozilla Firefox 134.0.2 (64-bit)

Describe the bug
Trying to edit cluster config gives the error "a.config is null" (in Firefox) and "Cannot read properties of null (reading 'save')" in Chrome.

To Reproduce

  1. Log on to the Rancher web interface.
  2. Go Cluster Management (/dashboard/c/_/manager/provisioning.cattle.io.cluster)
  3. Click on the ⋮ menu to the right of a cluster, then Edit Config
  4. Click Save

Result
The red error "a.config is null" is displayed at top. The "Save" button briefly turns to "Error"

Expected Result
There should be no error.

@github-actions github-actions bot added the QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this label Jan 23, 2025
@osklil
Copy link
Author

osklil commented Jan 23, 2025

It turned out to be an empty/partially configured Machine Pool. I deleted it, and now it works. I believe these empty/partial Machine Pool worked with previous versions of Rancher (2.8.5 but not 2.9.3 and later).

@richard-cox
Copy link
Member

@osklil can you provide information on the type of cluster and how it was originally created, and the role of the user that was editing the cluster?

@richard-cox richard-cox added this to the v2.12.0 milestone Jan 23, 2025
@osklil
Copy link
Author

osklil commented Jan 23, 2025

The Provider of cluster is VMware vSphere. It was set up from a Local RKE2 cluster. The user role is a Global Administrator.

@osklil
Copy link
Author

osklil commented Jan 24, 2025

Here is the scenario. With Rancher 2.6.x or 2.7x, additional machine pools were created. They were scaled down to zero nodes. Then the upgrade to 2.8.x, 2.9.x, and 2.10.x was made.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/vsphere kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this
Projects
None yet
Development

No branches or pull requests

2 participants