vmodl directory missing in v9.0.0.0

[IvarVirusiim]

Describe the bug

When installing the pyvmomi package version 9.0.0.0, the vmodl directory doesn't come with it.

Repository structure:

Structure locally:

When importing:

Reproduction steps

1. Install latest pyvmomi
2. Import something from vmodl
3. Receive error message: "Cannot find reference 'vmodl' in 'init.py' "

Expected behavior

vmodl is imported without issues

Additional context

No response

[Solaris17]

I was struck with this today when my playbooks stopped working over the US holiday.

I have reverted to 8.0.3.0.1.

@DanielDraganov

[DanielDraganov]

I was struck with this today when my playbooks stopped working over the US holiday.

I have reverted to 8.0.3.0.1.

@DanielDraganov

Hello. Could you elaborate on your scenario? The vmodl folder contains only type hints so it's interesting to find another use case.

[Solaris17]

I was struck with this today when my playbooks stopped working over the US holiday.
I have reverted to 8.0.3.0.1.
@DanielDraganov

Hello. Could you elaborate on your scenario? The vmodl folder contains only type hints so it's interesting to find another use case.

Apologies I should have lead with that.

I can try and induce the specific error again in the next few days.

I have several playbooks used to move and manipulate custom workloads in vmware 7 u3.

• Network connect/disconnect
• CPU & RAM configuration
• vMotion to and from specific compute hosts

All of this runs on Ansible Semaphore which uses Ansible version 2.18.1 (Current).

When attempting to run a playbook on 9.0.0.0 pyvmomi faults when attempting to use one of the modules.

Removing and rolling back to 8.0.3.0.1 restores usability immediately.

[DanielDraganov]

Got it. I don't think the issue is due to missing type hints.
Since 9.0 is a major release, it introduced several breaking changes - rare, but you might’ve just hit one.
When you get a chance, please share the error and traceback so we can confirm.