MKS Ticket Not Acquirable on ESXi 8
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start at the AcquireTicket entry point and inspect how the VMOMI TicketType value for MKS is represented and validated. Reproduce the request against ESXi 8 and compare it with the working ESXi 7 behavior; done means generating usable MKS ticket details without the TypeError.
Written by the indexing model from the issue text.
Description
Describe the bug
We have an on-prem ESXi 8 server environment deployed which hosts our customers VMs, we make those VMs airnmeccessible via a VMRC, we generate the VMRC link based on a ticket that is granted from the AcquireTicket function, the function accepts either a paremeter of MKS (Mouse, Keyboard, Screen) or clone which makes VMRC inherit the permissions of the user who initiated the session.
When acquiring a ticket of type MKS we're getting a TypeError from VMOMI saying we provided an invalid type to a variable called TicketType, the problem is we don't see any reference for said variable either in code or in changelogs.
We have an ESXi 7 server environment which the feature actually works in, but in the environment described above we fail to generate said ticket, we used the latest PyVmomi 8.0.2.
Reproduction steps
- Host an ESXi 8 server
- Create a SOAP session via the PyVmomi 8.0.2 SDK.
- Try to generate a MKS Ticket for VMRC via the AcquireTicket function.
Expected behavior
I expect the SDK to generate me usable MKS ticket details for VMRC usage.
Additional context
No response
- Dominant language
- Python
- Stars
- 2.3k
- Forks
- 763
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from vmware/pyvmomi
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100