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] Virtualization Management has no option to delete cluster(s) from rancher #2574

Closed
slickwarren opened this issue Jul 26, 2022 · 2 comments
Assignees
Labels
area/rancher Rancher related issues area/ui kind/bug Issues that are defects reported by users or that we know have reached a real release not-require/test-plan Skip to create a e2e automation test issue priority/0 Must be fixed in this release reproduce/always Reproducible 100% of the time severity/1 Function broken (a critical incident with very high impact)
Milestone

Comments

@slickwarren
Copy link

slickwarren commented Jul 26, 2022

Describe the bug
there is no option to delete a cluster through virtualization management

To Reproduce
Steps to reproduce the behavior:

  1. import a harvester cluster through virtualization management (in rancher)
  2. try to delete the cluster

Expected behavior
you should have the option to delete a cluster through rancher

Support bundle
supportbundle_06891336-f7b4-4869-8c05-43e7d679310d_2022-07-26T19-39-29Z.zip

Environment

  • Harvester ISO version: 1.0.3-rc1
  • Underlying Infrastructure (e.g. Baremetal with Dell PowerEdge R630): dell poweredge 510

Additional context
related to rancher/rancher#38429
Screen Shot 2022-07-26 at 12 31 02 PM

@slickwarren slickwarren added kind/bug Issues that are defects reported by users or that we know have reached a real release severity/1 Function broken (a critical incident with very high impact) area/rancher Rancher related issues reproduce/always Reproducible 100% of the time labels Jul 26, 2022
@slickwarren slickwarren added this to the v1.0.3 milestone Jul 26, 2022
@slickwarren slickwarren self-assigned this Jul 26, 2022
@n313893254 n313893254 self-assigned this Jul 27, 2022
@n313893254 n313893254 added priority/0 Must be fixed in this release not-require/test-plan Skip to create a e2e automation test issue area/ui labels Jul 27, 2022
@harvesterhci-io-github-bot
Copy link

harvesterhci-io-github-bot commented Jul 27, 2022

Pre Ready-For-Testing Checklist

* [ ] If labeled: require/HEP Has the Harvester Enhancement Proposal PR submitted?
The HEP PR is at:

  • Where is the reproduce steps/test steps documented?
    The reproduce steps/test steps are at:

Verify Steps:

  • Install rancher v2.6.4-rc4
  • Check as reproduced steps

* [ ] Is there a workaround for the issue? If so, where is it documented?
The workaround is at:

  • If labeled: area/ui Has the UI issue filed or ready to be merged?
    The UI issue/PR is at:

* [ ] If labeled: require/doc, require/knowledge-base Has the necessary document PR submitted or merged?
The documentation/KB PR is at:

* [ ] If NOT labeled: not-require/test-plan Has the e2e test plan been merged? Have QAs agreed on the automation test case? If only test case skeleton w/o implementation, have you created an implementation issue?
- The automation skeleton PR is at:
- The automation test case PR is at:

* [ ] If the fix introduces the code for backward compatibility Has a separate issue been filed with the label release/obsolete-compatibility?
The compatibility issue is filed at:

@noahgildersleeve noahgildersleeve self-assigned this Jul 28, 2022
@noahgildersleeve
Copy link

Tested with Harvester v1.0.3-rc1 and Rancher v2.6.7-rc5. Verified as fixed.

Verification Steps

  1. import a harvester cluster through virtualization management (in rancher)
  2. Delete cluster

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/rancher Rancher related issues area/ui kind/bug Issues that are defects reported by users or that we know have reached a real release not-require/test-plan Skip to create a e2e automation test issue priority/0 Must be fixed in this release reproduce/always Reproducible 100% of the time severity/1 Function broken (a critical incident with very high impact)
Projects
None yet
Development

No branches or pull requests

4 participants