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

Edit Container Name of a pod makes the UI show a long json error - only on first try #12212

Open
izaac opened this issue Oct 10, 2024 · 0 comments
Assignees
Labels
kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this
Milestone

Comments

@izaac
Copy link
Contributor

izaac commented Oct 10, 2024

Setup

  • Rancher version: v2.10-6075394bf1e6524183451a0e272521e4e4cf5e80-head
  • Rancher UI Extensions: master 7a296a5
  • Browser type & version: Chrome

Describe the bug
A json error is shown when attempting to edit the Container Name of a recently created pod.

To Reproduce
Describing the exact scenario. Project and Namespace might not be related.

  1. New test Project
  2. New namespace in Project of Step 1
  3. Add a new Pod to the namespace of Step 2 (name is arbitrary) The image name was nginx:alpine
  4. Wait for the pod to be listed in the Pods list/table
  5. Edit the pod
  6. Clear the Container Name field and click Save

Result

A json error is shown (check attached image)

Expected Result
An error letting the user know the field is empty and an error occurred.

Screenshots

Screenshot from 2024-10-10 12-05-03

@izaac izaac added the kind/bug label Oct 10, 2024
@izaac izaac added this to the v2.10.0 milestone Oct 10, 2024
@izaac izaac self-assigned this Oct 10, 2024
@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 Oct 10, 2024
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
Projects
None yet
Development

No branches or pull requests

1 participant