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] Unable to generate cluster registration url to import Harvester in Rancher v2.10.1-alpha1 after install the UI extension 1.0.1 #12863

Closed
TachunLin opened this issue Dec 11, 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

Comments

@TachunLin
Copy link

Rancher Server Setup

  • Rancher version: v2.10.1-alpha1
  • Installation option (Docker install/Helm Chart): Helm Chart
  • Harvester version: v1.4.0

User Information

  • What is the role of the user logged in: Admin

Describe the bug

After we install the Harvester UI extension on Rancher v2.10.1-alpha1.
And try to import Harvester from Rancher Virtualization Management.

There is no available cluster registration url created
image

The debug console shows index.1587706c.js:1 Error in fetch(): Error: Unknown schema for type: clusterregistrationtoken
image

To Reproduce

  1. Use helm to provision Rancher v2.10.1-alpha1
  2. Open extension
  3. Install Harvester UI extension 1.0.1
    image
  4. Reload the extension
  5. Open Virtualization Management
  6. Click import existing and input the Harvester cluster name
  7. Check the cluster registration url is created or not

Expected Result

Should be able to generate the cluster registration URL after import existing Harvester.
And can well import Harvester to Rancher correctly.

@torchiaf torchiaf transferred this issue from rancher/rancher Dec 11, 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 Dec 11, 2024
@torchiaf torchiaf self-assigned this Dec 11, 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

2 participants