Skip to content
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

The "Gathering Facts" task has been taking too much of my time, and I haven't been able to complete it in a few days. #315

Open
gusechuisheng opened this issue Dec 8, 2024 · 3 comments

Comments

@gusechuisheng
Copy link

TASK [Gathering Facts] ******************************************************************************************************************************************************
ok: [dc03]
ok: [srv03]
ok: [dc02]
ok: [dc01]
ok: [srv02]
[started TASK: common : Force a DNS on the adapter {{nat_adapter}} on dc01]
[started TASK: common : Force a DNS on the adapter {{nat_adapter}} on dc02]
[started TASK: common : Force a DNS on the adapter {{nat_adapter}} on dc03]
[started TASK: common : Force a DNS on the adapter {{nat_adapter}} on srv02]
[started TASK: common : Force a DNS on the adapter {{nat_adapter}} on srv03]
[started TASK: common : Set a proxy for specific protocols on dc01]
[started TASK: common : Set a proxy for specific protocols on dc02]
[started TASK: common : Set a proxy for specific protocols on dc03]
[started TASK: common : Set a proxy for specific protocols on srv02]
[started TASK: common : Set a proxy for specific protocols on srv03]
[started TASK: common : Configure IE to use a specific proxy per protocol on dc01]
[started TASK: common : Configure IE to use a specific proxy per protocol on dc02]
[started TASK: common : Configure IE to use a specific proxy per protocol on dc03]
[started TASK: common : Configure IE to use a specific proxy per protocol on srv02]
[started TASK: common : Configure IE to use a specific proxy per protocol on srv03]
[started TASK: common : Upgrade module PowerShellGet to fix accept license issue on last windows ansible version on dc01]
[started TASK: common : Upgrade module PowerShellGet to fix accept license issue on last windows ansible version on dc02]
[started TASK: common : Upgrade module PowerShellGet to fix accept license issue on last windows ansible version on dc03]
[started TASK: common : Upgrade module PowerShellGet to fix accept license issue on last windows ansible version on srv02]
[started TASK: common : Upgrade module PowerShellGet to fix accept license issue on last windows ansible version on srv03]

@Mayfly277
Copy link
Collaborator

i bet you are on windows 11 no ?
has i saw windows 11 use virtualbox on top of hyper-v. this made the script and the vms super slow and it finish with timeout.
The only workaround i have for that is turning down hyper-v (but doing that will remove some security features on windows 11, so i guess is not a good idea).

See this post about virtualbox with/without hyper-v: https://forums.virtualbox.org/viewtopic.php?f=25&t=99390

@sandsoncosta
Copy link

You can start a linux-live-usb, configure virtualbox or vmware, configure all the dependencies and start the lab installation.
Then just start Windows normally and import the vms.
Virtualbox: click on .vbox, create a new network interface and configure the lab's network interface.
VmWare: Configure the new network interface, click on .vmx and configure the interface in the vm.

It worked for me.
@Mayfly277 Would it be interesting to put it as a new tutorial or a tshoot?

@Mayfly277
Copy link
Collaborator

Maybe oneday i will push the complete lab to vagrant and it will be up directly after the download ^^

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants