Skip to content

Improve error handling when server-url setting is not populated #14415

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

Open
richard-cox opened this issue May 29, 2025 · 1 comment
Open

Improve error handling when server-url setting is not populated #14415

richard-cox opened this issue May 29, 2025 · 1 comment
Labels
kind/enhancement QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this
Milestone

Comments

@richard-cox
Copy link
Member

richard-cox commented May 29, 2025

  • When rancher has been automatically provisioned there are edge cases where server-url has not been supplied
  • The effects of this are opaque and not easy to tie back to the setting
    • for example missing parts of cluster registration command (token exists but not populated)
  • We should detect this and warn users when attempting to create or import a cluster
  • Lo-bar could be a banner on the cluster management list

Related to #14416

@richard-cox richard-cox added this to the v2.13.0 milestone May 29, 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 May 29, 2025
@nwmac
Copy link
Member

nwmac commented Jun 1, 2025

Suggest we go with the low bar

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement 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
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy