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

Several setup tasks not executed for fedora38|39 with provider vmware #290

Open
rbrunckhorst opened this issue Dec 10, 2023 · 1 comment

Comments

@rbrunckhorst
Copy link

There is no ~/vagrant/.ssh directory created which results in 'default: Warning: Authentication failure. Retrying...' in an endless loop when starting such an OS (fedora38|39).
fedora37 and older are working.

For me it seems that several scripts are not executed in generic-vmware-x64.json for fedora38|39
like it is done for instance for fedora37:
{
"type": "shell",
"timeout": "120m",
"scripts": [
"scripts/fedora37/kernel.sh",
"scripts/fedora37/updatedb.sh",
"scripts/fedora37/vga.sh",
"scripts/fedora37/virtualbox.sh",
"scripts/fedora37/parallels.sh",
"scripts/fedora37/vmware.sh",
"scripts/fedora37/qemu.sh",
"scripts/fedora37/vagrant.sh",
"scripts/fedora37/tuning.sh",
"scripts/fedora37/cleanup.sh"
],
"pause_before": "120s",
"start_retry_timeout": "15m",
"expect_disconnect": "true",
"only": [
"generic-fedora37-vmware-x64"
]
},

@dlouzan
Copy link

dlouzan commented Dec 14, 2023

Just experienced this on molecule vagrant runs, we have automated tests for fedora, debian and amazonlinux; none of fedora 38 & 39 worked, and had to switch to the official fedora cloud base images to be able to perform some runs.

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

No branches or pull requests

2 participants