Hi @ctyrider - thanks for opening this issue. Do you wish to take a stab at the PR?

Hi @ctyrider - thanks for opening this issue. Do you wish to take a stab at the PR?

I've raised a PR #4853 This is my first time raising a PR for AVD, and I am having a small issue locally running Molecule in venv environment - getting an exception "The error was: importlib.metadata.PackageNotFoundError: No package metadata was found for pyavd" when running Molecule:

Perhaps you could give me a pointer as to what's causing the issue and how to resolve? I've installed local Python packages, as instructed by "Development Tooling" article: pip3 install -r ansible_collections/arista/avd/requirements-dev.txt --upgrade

Exact error is below:

(avd-venv) ➜  avd git:(issue4848) molecule converge -s eos_cli_config_gen
INFO     eos_cli_config_gen scenario test matrix: syntax, converge
INFO     Performing prerun with role_name_check=0...
INFO     Running eos_cli_config_gen > syntax

playbook: /root/git_projects/avd/ansible_collections/arista/avd/molecule/eos_cli_config_gen/converge.yml
INFO     Running eos_cli_config_gen > converge

PLAY [Converge] ****************************************************************

TASK [arista.avd.eos_cli_config_gen : Verify Requirements] *********************
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: importlib.metadata.PackageNotFoundError: No package metadata was found for pyavd
fatal: [host_inline_jinja -> localhost]: FAILED! => {"msg": "Unexpected failure during module execution: No package metadata was found for pyavd", "stdout": ""}

Hi apologies for answering this late

So this is an unforeseen change of one of my recent improvements it seems (will tackle this)
here is what you need to do:

# From the root of the folder
cd python-avd
make pyavd-build

It will create the necessary metadata for Verify Requirements to work

Hi apologies for answering this late

So this is an unforeseen change of one of my recent improvements it seems (will tackle this) here is what you need to do:

# From the root of the folder
cd python-avd
make pyavd-build

It will create the necessary metadata for Verify Requirements to work

I worked around this by installing pyavd 4.10.2 locally:

(avd-venv) ➜  avd git:(issue4848) pip3 list | grep pyavd
pyavd                     4.10.2

Molecule runs now.

@gmuloc
#4853 ready to merge - please review

Hi apologies for answering this late
So this is an unforeseen change of one of my recent improvements it seems (will tackle this) here is what you need to do:

# From the root of the folder
cd python-avd
make pyavd-build

It will create the necessary metadata for Verify Requirements to work

I worked around this by installing pyavd 4.10.2 locally:

(avd-venv) ➜  avd git:(issue4848) pip3 list | grep pyavd
pyavd                     4.10.2

Molecule runs now.

yeah the piece of code just need to be able to run any metadata but it should gracefully ignore it it can't find any.
molecule should not use this pyavd version you have installed as it would be running from source but I would recommend installing pyavd 5.1.0 still.