Vagrant based tests are failing

[saschagrunert]

The ubuntu vagrant based tests are consistently failing with:

==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'generic/ubuntu2204' version '4.3.4' is up to date...
==> default: Setting the name of the VM: security-profiles-operator_default_1698229641020_98957
Vagrant is currently configured to create VirtualBox synced folders with
the `SharedFoldersEnableSymlinksCreate` option enabled. If the Vagrant
guest is not trusted, you may want to disable this option. For more
information on this option, please refer to the VirtualBox manual:

  https://www.virtualbox.org/manual/ch04.html#sharedfolders

This option can be disabled globally with an environment variable:

  VAGRANT_DISABLE_VBOXSYMLINKCREATE=1

or on a per folder basis within the Vagrantfile:

  config.vm.synced_folder '/host/path', '/guest/path', SharedFoldersEnableSymlinksCreate: false
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2222
    default: SSH username: vagrant
    default: SSH auth method: private key
The guest machine entered an invalid state while waiting for it
to boot. Valid states are 'starting, running'. The machine is in the
'gurumeditation' state. Please verify everything is configured
properly and try again.

If the provider you're using has a GUI that comes with it,
it is often helpful to open that and watch the machine, since the
GUI often has more helpful error messages than Vagrant can retrieve.
For example, if you're using VirtualBox, run `vagrant up` while the
VirtualBox GUI is open.

The primary issue for this error is that the provider you're using
is not properly configured. This is very rarely a Vagrant issue.
make: *** [vagrant-up-ubuntu] Error 1

I'm not exactly sure how we can approach a fix here.

cc @kubernetes-sigs/security-profiles-operator-maintainers

[saschagrunert]

It looks like that this version works:

Image: macos-12
  Version: 20230921.4

but those not

Image: macos-12
  Version: 20230921.1

maybe we just have to wait until the issue magically disappears.

[saschagrunert]

It starts to fail again on version 20231017.6, see https://github.com/kubernetes-sigs/security-profiles-operator/actions/runs/6673326514?pr=1945

[ccojocar]

It looks like a vagrant and virtualbox update in the macos github runner. I would try to see which vagrant and virtualbox is used by th github action runner in version 20231017.6 and try to reproduce it locally with the same versions.

[Vincent056]

I see the same behavior, it fails on

Operating System
  macOS
  12.6.9

[Vincent056]

Is there a way to specify the version in the workflow file?

[saschagrunert]

Is there a way to specify the version in the workflow file?

I don't think so. We may find a substitution for vagrant.

[Vincent056]

it is weird some tests are launched in different versions

…

Message ID: ***@***.*** com>

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[saschagrunert]

/remove-lifecycle stale

The SELinux tests on Fedora are still failing:

security-profiles-operator/hack/ci/e2e-fedora.sh

Lines 19 to 20 in 329bc33

	# TODO: re-enable when SELinux tests are fixed
	export E2E_TEST_SELINUX=false

[saschagrunert]

cc @kubernetes-sigs/security-profiles-operator-maintainers maybe one would like to look into them 🙃

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[saschagrunert]

This is done 🥳