search

lavabit / robox

The tools needed to robotically create/configure/provision a large number of operating systems, for a variety of hypervisors, using packer.
620 stars 140 forks source link

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

Open rbrunckhorst opened 7 months ago

rbrunckhorst commented 7 months ago

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 commented 7 months ago

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.