stable
FEDORA-2022-3039cd1634 created by ngompa 9 months ago for Fedora 36

Drop dependency on NetworkManager-config-server to fix Vagrant machines.

Reboot Required
After installing this update it is required that you reboot your system to ensure the changes supplied by this update are applied properly.

How to install

sudo dnf upgrade --refresh --advisory=FEDORA-2022-3039cd1634

This update has been submitted for testing by ngompa.

9 months ago

This update's test gating status has been changed to 'ignored'.

9 months ago

ngompa edited this update.

9 months ago
User Icon dustymabe commented & provided feedback 9 months ago

the rawhide vagrant build that happened with cloud-init-22.1-3.fc37 works for me.

BZ#2060045 Issues with networking in the latest Rawhide Vagrant (libvirt) boxes
User Icon dustymabe provided feedback 9 months ago
karma
User Icon mhayden commented & provided feedback 9 months ago
karma

Works fine on OpenStack (Vexxhost).

This update has been submitted for stable by bodhi.

9 months ago
User Icon davdunc commented & provided feedback 9 months ago

I am stuck at the same place in the deployment. I am using 2.2.16 fc35 build of vagrant, but still here:

==> rawhide_selinux: Creating shared folders metadata...
==> rawhide_selinux: Starting domain.
==> rawhide_selinux: Waiting for domain to get an IP address...
==> rawhide_selinux: Waiting for SSH to become available...

If I move to another terminal, I can find it running, but not set up with SSH

davdunc@davdunc-xps Jenkins]$ virsh list 
 Id   Name                          State
---------------------------------------------
 4    fedora-test_rawhide_selinux   running

[davdunc@davdunc-xps Jenkins]$ virsh console 4 
Connected to domain 'fedora-test_rawhide_selinux'
Escape character is ^] (Ctrl + ])

fedora login: fedora
Password: 

$ vagrant ssh The provider for this Vagrant-managed machine is reporting that it is not yet ready for SSH. Depending on your provider this can carry different meanings. Make sure your machine is created and running and try again. Additionally, check the output of vagrant status to verify that the machine is in the state that you expect. If you continue to get this error message, please view the documentation for the provider you're using. ```

BZ#2060045 Issues with networking in the latest Rawhide Vagrant (libvirt) boxes
User Icon mrc0mmand commented & provided feedback 9 months ago
karma

Our systemd/SELinux Vagrant job is functional once again, so adding my +1, thanks!

BZ#2060045 Issues with networking in the latest Rawhide Vagrant (libvirt) boxes

This update has been pushed to stable.

9 months ago

Please login to add feedback.

Metadata
Type
bugfix
Severity
high
Karma
3
Signed
Content Type
RPM
Test Gating
Settings
Unstable by Karma
-3
Stable by Karma
2
Stable by Time
3 days
Dates
submitted
9 months ago
in stable
9 months ago
modified
9 months ago
BZ#2060045 Issues with networking in the latest Rawhide Vagrant (libvirt) boxes
-1
1

Automated Test Results