-
Notifications
You must be signed in to change notification settings - Fork 787
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
Error Launching via Python on Windows #280
Comments
I force upgraded python and pip and they are both on 3.12, re-ran the requirements and ensured rich was installed, this works to allow me to access the console. Progress! However, I did end up with this error:
It generates the vagrantfile and I can get the VMs up with
Line 102-117 for reference
Just to add, I am very impressed with the change to V3, it is clear that you have put a lot of work into this. |
Ok i didn't manage the fact that you use the wrong provisioning method, i will change that. Please use the provisionning method
or in goad interactive prompt do |
I wiped all workspaces and set up with VM method for VirtualBox, all 6 VMs start but the following error occurs
|
Hum weird, vagrant should have created a private key in workspace<workspaceid>\provider\.vagrant\machines\PROVISIONING\virtualbox\private_key but in your capture there is "not found", so the key wasn't created. may be you can delete the vm provisionning then :
|
The private key file exists and there is a key generated within the begin and end
|
can you try again and give me the error ? |
Deleted all files, fresh clone and install, ran requirements etc.
|
ok here the error is the provisioning vm doesn't get internet access or have trouble with dns resolution.
can you try to login to the provisioning vm to understand why the apt update fail ? |
I have changed the DNS settings and can now ping google.com and so I have manually updated and this has worked but I am still getting
Manually opening port on PROVISIONING gets me to the point of running playbooks
|
almost there, just launch the lab provisioning with |
The provisioning partially works, I can get some workbooks completed on DC03 and SRV03, getting unreachable with the others so I'm going to try again from the beginning, with setting up a DNS server and opening the ports on the PROVISIONING vm as that seemed to be the cause of some issues. I tried the restart_vm command but these did not work on any of the VMs so i had to use stop_vm and start-vm each time, not a major issue but the restart command is listed under the help |
hum ok i have to fix the restart_vm command ^^ |
So, I have done git pull and tried again with fresh labs.
|
I keep getting the following error when trying to launch on windows host (I was having issues with ansible on linux and VM on Windows)
goad.py
log.py
config.py
noansible_requirements.yml installed and checked.
Python 3.12.4
Plugins installed (vagrant-reload vagrant-vbguest winrm winrm-fs winrm-elevated)
visual c++ 2019 updated
For reference, issues running ansible on linux host #59 (comment)
The text was updated successfully, but these errors were encountered: