python errors from the VagrantPlaybookCheck job runs

[sxa]

VPC does not look happy at the moment. Many jobs are failing with an error such as this:

12:33:02 ++ ansible-playbook -i playbooks/AdoptOpenJDK_Unix_Playbook/hosts.unx -u vagrant -b --skip-tags adoptopenjdk,jenkins,nvidia_cuda_toolkit,MSVS_2013,MSVS_2017,MSVS_2019,MSVS_2010,VS2010_SP1,MSVS_2013,MSVS_2017,MSVS_2019 playbooks/AdoptOpenJDK_Unix_Playbook/main.yml
12:33:02 Traceback (most recent call last):
12:33:02   File "/usr/lib/python3.12/importlib/metadata/__init__.py", line 397, in from_name
12:33:02     return next(cls.discover(name=name))
12:33:02            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
12:33:02 StopIteration
12:33:02 
12:33:02 During handling of the above exception, another exception occurred:

(Example from Ubuntu 20.04 but that's not the only one that's failing)

[steelhead31]

Python error related to apt install python3-jinja2 & python3-winrm packages not being present, installed with

apt install python3-jinja2 python3-winrm

[steelhead31]

Quick test of VPC for Ubu 24 : https://ci.adoptium.net/job/VagrantPlaybookCheck/2043/OS=Ubuntu2404,label=vagrant/console

[sxa]

@steelhead31 I see you're still running some VPCs this morning so I won't kick one off, but if you're able to schedule/test with #3870 (which is branch uptime_diff from the sxa fork of infrastructure) including a build test that would be appreciated to verify that removing curl isn't going to break any "installed from scratch" machines.
Only the RPM based distros should be affected by this one.

[steelhead31]

All the below have been run on your #3870 branch..

✔ Centos 8 : https://ci.adoptium.net/job/VagrantPlaybookCheck/2051/OS=CentOS8,label=vagrant/
✔ Centos 7 : https://ci.adoptium.net/job/VagrantPlaybookCheck/2051/OS=CentOS7,label=vagrant/

Vagrant Playbook Check technical issues have been resolved. I'll investigate issues that are specific to certain platforms.