Closed ansiblejunky closed 9 months ago
This and #432 seem related. Reeks of a bug in Virtualbox 7.0.10
Issue was also happening with Virtualbox 7.0.8
I was able to install vb guest additions with an Ansible Role that I found on Github. So that proves to me that the issue is NOT with VirtualBox but rather with how vbguest plugin chooses to install it.
It would be quite useful to know how that Ansible role does it that ;)
https://github.com/PeterMosmans/ansible-role-virtualbox-guest
If you run this Role with ansible 2.14 (current) you'll hit an issue with the role using old unsupported argument (warn
). Removing them makes it all work. One thing I hit, the install command returned error code 2, but it seems that's a common problem with vbox guest additions and not impacting the install itself. I ran vagrant vbguest --status
and it returned the correct and latest version of guest additions from the box.
Getting errors when it attempts to upgrade the vbguest additions using the
vagrant-vbguest
plugin. I've tried different vagrant boxes and same problem.Steps to start box:
Versions:
Debug output: