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.

Sign up for GitHub

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

Jump to bottom

[backport v2.9.6] Changing Rancher version breaks Private Registry CA #12969

Open
github-actions bot opened this issue Jan 3, 2025 · 0 comments
Open

[backport v2.9.6] Changing Rancher version breaks Private Registry CA #12969

github-actions bot opened this issue Jan 3, 2025 · 0 comments
Assignees
@torchiaf
Labels
JIRA kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this QA/None size/2 Size Estimate 2 status/backport-candidate
Milestone
v2.9.6

Comments

@github-actions
Copy link
Contributor

github-actions bot commented Jan 3, 2025

This is a backport issue for #12679, automatically created via GitHub Actions workflow initiated by @torchiaf

Original issue body:

Internal link SURE-9301

Setup

  • Rancher version: SUSE Rancher 2.9.2, SUSE Rancher 2.8.8
  • Rancher UI Extensions:
  • Browser type & version:

Describe the bug

Related issue: #10725

When attempting to upgrade from RKE2 1.25 to 1.26 with private registries, the UI changes the private registry CA and then passes invalid yaml to Rancher, causing the upgrade to fail.

Workaround: Check certificates are valid before trying to complete upgrade.

To Reproduce

Create downstream cluster on Rancher 2.7 with private registry
Upgrade to Rancher 2.8
Using Rancher UI, change Kubernetes version on cluster with private registry with private CA

Result

Private Registry CA gets corrupted

Screenshots

image

Additional context
@github-actions github-actions bot added JIRA kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this QA/None size/2 Size Estimate 2 status/backport-candidate labels Jan 3, 2025
@github-actions github-actions bot added this to the v2.9.6 milestone Jan 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@torchiaf torchiaf

Labels
JIRA kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this QA/None size/2 Size Estimate 2 status/backport-candidate
Projects
None yet
Milestone
v2.9.6
Development

No branches or pull requests
1 participant
@torchiaf