Skip to content

[chore][ansible] Extend vm boot timeout #6242

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

Closed
wants to merge 14 commits into from

Conversation

crobert-1
Copy link
Contributor

Description:

From failed test:

fatal: [localhost]: FAILED! => {"changed": false, "cmd": ["/usr/bin/vagrant", "up", "--no-provision"], "msg": "Failed to start the VM(s): See log file '/home/runner/.cache/molecule/ansible/default/vagrant.err'", "rc": 1, "stderr": "### 2025-05-19 00:37:04 ###
### 2025-05-19 00:37:07 ###
### 2025-05-19 00:37:07 ###
Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured (\"config.vm.boot_timeout\" value) time period.

If you look above, you should be able to see the error(s) that
Vagrant had when attempting to connect to the machine. These errors
are usually good hints as to what may be wrong.

If you're using a custom box, make sure that networking is properly
working and you're able to connect to the machine. It is a common
problem that networking isn't setup properly in these boxes.
Verify that authentication configurations are also setup properly,
as well.

If the box appears to be booting properly, you may want to increase
the timeout (\"config.vm.boot_timeout\") value.
", "stderr_lines": ["### 2025-05-19 00:37:04 ###", "### 2025-05-19 00:37:07 ###", "### 2025-05-19 00:37:07 ###", "Timed out while waiting for the machine to boot. This means that", "Vagrant was unable to communicate with the guest machine within", "the configured (\"config.vm.boot_timeout\" value) time period.", "", "If you look above, you should be able to see the error(s) that", "Vagrant had when attempting to connect to the machine. These errors", "are usually good hints as to what may be wrong.", "", "If you're using a custom box, make sure that networking is properly", "working and you're able to connect to the machine. It is a common", "problem that networking isn't setup properly in these boxes.", "Verify that authentication configurations are also setup properly,", "as well.", "", "If the box appears to be booting properly, you may want to increase", "the timeout (\"config.vm.boot_timeout\") value."]}

Config option documentation

Copy link

codecov bot commented May 20, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 44.36%. Comparing base (8049f0f) to head (bdc89b9).

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #6242      +/-   ##
==========================================
- Coverage   44.42%   44.36%   -0.06%     
==========================================
  Files         390      390              
  Lines       26986    26986              
==========================================
- Hits        11988    11973      -15     
- Misses      14156    14167      +11     
- Partials      842      846       +4     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@crobert-1
Copy link
Contributor Author

Changes have been included in #6222

@crobert-1 crobert-1 closed this May 21, 2025
@github-actions github-actions bot locked and limited conversation to collaborators May 21, 2025
@crobert-1 crobert-1 reopened this May 21, 2025
@crobert-1 crobert-1 force-pushed the fix_ansible_windows branch from bdc89b9 to 91927ad Compare May 21, 2025 23:03
@crobert-1
Copy link
Contributor Author

Closing in favor of #6245

@crobert-1 crobert-1 closed this May 23, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant