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] A specified parameter was not correct: entityId while applying Tanzu license to cluster #2471

Open
haydonryan opened this issue May 28, 2021 · 4 comments

Comments

@haydonryan
Copy link
Contributor

haydonryan commented May 28, 2021

Describe the bug
I'm trying to add and assign a Tanzu license to my cluster prior to enabling workload management. I'm able to add and assign licenses for the hosts and the vcsa, but get the following error when I try and apply the tanzu license to the cluster. I'm able to assign the license using the UI, so that should be ok.

govc license.assign -cluster Cluster  XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
govc: ServerFaultCode: A specified parameter was not correct: entityId

To Reproduce
Steps to reproduce the behavior:

  1. Create cluster named Cluster,
  2. Add a valid Tanzu License
  3. run the above command.

Expected behavior
I expect the license to apply to the cluster.

Affected version
govc v0.25.0
VMware-VCSA-all-7.0.1-16860138
Ubuntu 21.04 x86_64

@github-actions
Copy link
Contributor

Howdy 🖐   haydonryan ! Thank you for your interest in this project. We value your feedback and will respond soon.

If you want to contribute to this project, please make yourself familiar with the CONTRIBUTION guidelines.

@github-actions
Copy link
Contributor

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Mark as fresh by adding the comment /remove-lifecycle stale.

@haydonryan
Copy link
Contributor Author

Please keep open - Tanzu licenses are super important imo.

@github-actions
Copy link
Contributor

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Mark as fresh by adding the comment /remove-lifecycle stale.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants