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

Clusters can be created/edited with broken add-on config yaml file #12323

Closed
IsaSih opened this issue Oct 22, 2024 · 11 comments · Fixed by #13017
Closed

Clusters can be created/edited with broken add-on config yaml file #12323

IsaSih opened this issue Oct 22, 2024 · 11 comments · Fixed by #13017
Assignees
Labels
kind/bug kind/design QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this release-note size/3 Size Estimate 3 status/backport-candidate
Milestone

Comments

@IsaSih
Copy link
Contributor

IsaSih commented Oct 22, 2024

Setup

  • Rancher version: v2.9-50aecc403a523ef45c90de73e99ec2cde182f627-head

Describe the bug
Found while testing #12067
Clusters can be created/edited with broken add-on yaml files. We need a yaml validator for the add-on config as they are now displayed in separate tabs.

To Reproduce
1- From the Clusters Management in the UI, hit Create
2- Select rke2, Input your cloud credentials, fill all the mandatory fields, then select a container network add-on
3- Navigate to the container network tab, and brake the yaml file
4- Hit create

Result
UI allows clusters to be created with broken add-on yaml files.

Expected Result
UI must have a yaml validator for the add-on config file, that displays an error message and prevents a cluster to be created if the yaml files are broken. Same behavior should be applied for the edit form.

Screen.Recording.2024-10-22.at.10.24.14.mov
@IsaSih
Copy link
Contributor Author

IsaSih commented Oct 22, 2024

Observed that the yaml file is overwritten during the provisioning and the cluster gets created with no errors. But the validator brings a better UX.

@gaktive gaktive added this to the v2.10.0 milestone Oct 22, 2024
@github-actions github-actions bot added QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this and removed release-note status/backport-candidate labels Oct 22, 2024
@gaktive
Copy link
Member

gaktive commented Oct 22, 2024

It doesn't sound like a blocker but we'll release note it for 2.9.3 and fix for 2.10.0 & 2.9.4

@gaktive
Copy link
Member

gaktive commented Oct 22, 2024

/backport v2.9.4

@IsaSih
Copy link
Contributor Author

IsaSih commented Oct 22, 2024

/backport v2.8.10

@kwwii
Copy link
Contributor

kwwii commented Oct 23, 2024

We should show the errors in the yaml file view also in the tab for the add-on config so that users are aware of the errors when viewing another tab. As long as there are errors the submit action should be disabled.

@gaktive gaktive added the size/3 Size Estimate 3 label Oct 23, 2024
@mantis-toboggan-md
Copy link
Member

This is effectively blocked by #12418; the content of these tabs changes unexpectedly when the user navigates away/back to the tab.

@gaktive gaktive modified the milestones: v2.10.0, v2.11.0 Oct 30, 2024
@nwmac nwmac modified the milestones: v2.12.0, v2.11.0 Nov 1, 2024
@gaktive
Copy link
Member

gaktive commented Nov 1, 2024

/backport v.2.10.1

Copy link
Contributor

github-actions bot commented Nov 1, 2024

Not creating port issue, milestone v.2.10.1 does not exist or is not an open milestone

@gaktive
Copy link
Member

gaktive commented Nov 1, 2024

/backport v2.10.1

@gaktive
Copy link
Member

gaktive commented Nov 1, 2024

As noted, blocked. We'd need to prioritize #12418 and then figure out its backports.

@yonasberhe23
Copy link
Contributor

User is unable to save/create cluster with broken config yaml

Tested in:

  • Rancher v2.11-2053ce644a31cd8053d1f58e2487154b0b8513b6-head
  • Dashboard master 0c6eb64

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug kind/design QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this release-note size/3 Size Estimate 3 status/backport-candidate
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants