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

BUG: sealos reset nil pointer #5007

Open
zijiren233 opened this issue Aug 29, 2024 · 4 comments
Open

BUG: sealos reset nil pointer #5007

zijiren233 opened this issue Aug 29, 2024 · 4 comments
Labels
kind/bug Something isn't working response-expired

Comments

@zijiren233
Copy link
Contributor

Sealos Version

v5.0.0

How to reproduce the bug?

sealos reset

What is the expected behavior?

No response

What do you see instead?

img_v3_02e7_f295c4c1-12ee-405a-aecf-79ce047fe78g

Operating environment

- Sealos version: v5.0.0
- Kubernetes version: v1.27.11

Additional information

No response

@zijiren233 zijiren233 added the kind/bug Something isn't working label Aug 29, 2024
@yangxggo
Copy link
Contributor

yangxggo commented Sep 4, 2024

You need to provide more descriptions, such as:

  1. The status of the cluster before reset.
  2. The number of master and node nodes.
  3. Which version of sealos was used to initialize and install the cluster?
  4. Have the cluster and sealos versions been updated?

@yangxggo
Copy link
Contributor

Did you specify master or node by --masters or --nodes when you running sealos reset?

@zijiren233
Copy link
Contributor Author

Did you specify master or node by --masters or --nodes when you running sealos reset?运行 sealos reset 时,您是否通过 --masters 或 --nodes 指定了主节点或节点?

No, Just run sealos reset

Copy link

stale bot commented Nov 13, 2024

This issue has been automatically closed because we haven't heard back for more than 60 days, please reopen this issue if necessary.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working response-expired
Projects
None yet
Development

No branches or pull requests

2 participants