-
-
Notifications
You must be signed in to change notification settings - Fork 102
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
vagrant: Upgrade Fedora 35 vagrantfile to Fedora 40 #3663
Conversation
Ive temporarily changed the config of the VPC to pull from this branch. Running a fedora40 job https://ci.adoptium.net/view/Tooling/job/VagrantPlaybookCheck/1910/console |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks OK, VPC fails, I think due to a similar issue I've had with Ubuntu 24.04.. if an older version of Python is available, you could try setting that up on the Fedora Box as part of the Vagrant file, and specifying the perl interpreter.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, feel free to merge post VPC success.
Python2 seems to work but then I hit this error
The only available |
ansible/vagrant/Vagrantfile.Fedora40
Outdated
|
||
$script = <<SCRIPT | ||
|
||
# Install python2, make it the default python |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Comment seems incorrect?
I think ive hit a wall with this. I am not able to get passed the error in #3663 (comment) |
Eventhough
Trying the hack at https://dmsimard.com/2016/01/08/selinux-python-virtualenv-chroot-and-ansible-dont-play-nice/ of just copying the selinux directory over to the 3.8 library did not work
|
The wider solution is to update Ansible on the host, infrastructure-ibmcloud-vagrant-x64-1, so that it can use python3.12 |
Installing
|
Using
|
Superceded by #3761 |
Fixes #3662