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

Secrets: SSH Key: Unable to create SSH Key due to missing fields on Create SSH Key form #13474

Open
yonasberhe23 opened this issue Feb 21, 2025 · 1 comment · May be fixed by #13520
Open

Secrets: SSH Key: Unable to create SSH Key due to missing fields on Create SSH Key form #13474

yonasberhe23 opened this issue Feb 21, 2025 · 1 comment · May be fixed by #13520
Assignees
Labels
kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this status/release-blocker
Milestone

Comments

@yonasberhe23
Copy link
Contributor

Setup

  • Rancher version: v2.11
  • Rancher UI Extensions:
  • Browser type & version: Chrome, FF

Describe the bug
User is unable to create SSH Key due to missing fields on Create SSH Key form.

To Reproduce

  1. go to Cluster Dashboard -> Storage -> Secrets
  2. click Create
  3. select SSH Key

Result
User is unable to create SSH Key due to missing fields on Create SSH Key form.

Expected Result
User is able to create SSH Key. All expected tabs/fields are present on Create SSH Key form.

Screenshots
2.10.2

Image

2.11

Image

Additional context

@yonasberhe23 yonasberhe23 added this to the v2.11.0 milestone Feb 21, 2025
@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 Feb 21, 2025
@yonasberhe23
Copy link
Contributor Author

found while testing #11236

@torchiaf torchiaf linked a pull request Feb 26, 2025 that will close this issue
7 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this status/release-blocker
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants