Skip to content
This repository has been archived by the owner on Jun 28, 2024. It is now read-only.

"vagrant up fedora" does not work on Ubuntu 20.04 host #3942

Closed
wainersm opened this issue Sep 3, 2021 · 1 comment
Closed

"vagrant up fedora" does not work on Ubuntu 20.04 host #3942

wainersm opened this issue Sep 3, 2021 · 1 comment
Assignees
Labels
area/vagrant-local-ci bug Incorrect behaviour

Comments

@wainersm
Copy link
Contributor

wainersm commented Sep 3, 2021

The vagrant up fedora command fails on Ubuntu 20.04 with the following error:

Vagrant attempted to execute the capability 'reboot'
on the detect guest OS 'fedora', but the guest doesn't
support that capability. This capability is required for your
configuration of Vagrant. Please either reconfigure Vagrant to
avoid this capability or fix the issue by creating the capability.

@Jakob-Naucke reported the issue here: #3923 (comment)

Currently it is required to configure the Fedora guest with cgroups v1 and that requires a reboot. Vagrant on Ubuntu host seems unable to reboot guests (whether Fedora or Ubuntu guests doesn't matter, it still fails).

vagrant up ubuntu on Ubuntu host works fine as it doesn't require reboot.

Possible solutions:

  1. (mitigation actually) Mentions in https://github.com/kata-containers/tests/blob/main/README.md#using-vagrant-to-test-your-code-changes that vagrant up fedora on Ubuntu host is not supported.
  2. Setup an account on Vagrant cloud to store a version of the Fedora's box with cgroups v1 enabled, therefore we just fetch the image and no reboot is needed.
  3. Work to get the CI scripts running on Fedora with cgroups v2. That would be the best solution IMHO.
@wainersm wainersm added bug Incorrect behaviour needs-review Needs to be assessed by the team. area/vagrant-local-ci labels Sep 3, 2021
@cpmeadors cpmeadors removed the needs-review Needs to be assessed by the team. label Sep 7, 2021
@cpmeadors
Copy link

Removing need-reveiw and assigning to @wainersm

wainersm added a commit to wainersm/kc-tests that referenced this issue Sep 13, 2021
Fixes kata-containers#3942
Signed-off-by: Wainer dos Santos Moschetta <[email protected]>
wainersm added a commit to wainersm/kc-tests that referenced this issue Sep 13, 2021
Fixes kata-containers#3942
Signed-off-by: Wainer dos Santos Moschetta <[email protected]>
wainersm added a commit to wainersm/kc-tests that referenced this issue Sep 13, 2021
Fixes kata-containers#3942
Signed-off-by: Wainer dos Santos Moschetta <[email protected]>
wainersm added a commit to wainersm/kc-tests that referenced this issue Sep 14, 2021
Added on README.md a table with the combinations of tested host
versus guest so developers are aware of what is (or not) expected
to work.

Fixes kata-containers#3942
Signed-off-by: Wainer dos Santos Moschetta <[email protected]>
wainersm added a commit to wainersm/kc-tests that referenced this issue Sep 20, 2021
Added on README.md a table with the combinations of tested host
versus guest so developers are aware of what is (or not) expected
to work.

Fixes kata-containers#3942
Signed-off-by: Wainer dos Santos Moschetta <[email protected]>
wainersm added a commit to wainersm/kc-tests that referenced this issue Oct 27, 2021
Added on README.md a table with the combinations of tested host
versus guest so developers are aware of what is (or not) expected
to work.

Fixes kata-containers#3942
Signed-off-by: Wainer dos Santos Moschetta <[email protected]>
wainersm added a commit to wainersm/kc-tests that referenced this issue Oct 28, 2021
Added on README.md a table with the combinations of tested host
versus guest so developers are aware of what is (or not) expected
to work.

Fixes kata-containers#3942
Signed-off-by: Wainer dos Santos Moschetta <[email protected]>
wainersm added a commit to wainersm/kc-tests that referenced this issue Nov 4, 2021
Added on README.md a table with the combinations of tested host
versus guest so developers are aware of what is (or not) expected
to work.

Fixes kata-containers#3942
Signed-off-by: Wainer dos Santos Moschetta <[email protected]>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area/vagrant-local-ci bug Incorrect behaviour
Projects
None yet
Development

No branches or pull requests

2 participants