Description of problem: When trying to bring up machine with fedora/29-cloud-base box I get: Redirecting to /bin/systemctl restart network.service Failed to restart network.service: Unit network.service not found. Version-Release number of selected component (if applicable): vagrant-2.0.2-2.fc28.noarch How reproducible: Always. Steps to Reproduce: 1. vagrant up machine with fedora/29-cloud-base box Actual results: Redirecting to /bin/systemctl restart network.service Failed to restart network.service: Unit network.service not found. Expected results: Guest starts successfully. Additional info: Full output: Bringing machine 'client' up with 'libvirt' provider... ==> client: Creating image (snapshot of base box volume). ==> client: Creating domain with the following settings... ==> client: -- Name: sssd-test-suite_client ==> client: -- Domain type: kvm ==> client: -- Cpus: 1 ==> client: -- Feature: acpi ==> client: -- Feature: apic ==> client: -- Feature: pae ==> client: -- Memory: 2048M ==> client: -- Management MAC: ==> client: -- Loader: ==> client: -- Base box: fedora/29-cloud-base ==> client: -- Storage pool: default ==> client: -- Image: /mnt/vm/qemu/sssd-test-suite_client.img (41G) ==> client: -- Volume Cache: default ==> client: -- Kernel: ==> client: -- Initrd: ==> client: -- Graphics Type: vnc ==> client: -- Graphics Port: 5900 ==> client: -- Graphics IP: 127.0.0.1 ==> client: -- Graphics Password: Not defined ==> client: -- Video Type: cirrus ==> client: -- Video VRAM: 9216 ==> client: -- Sound Type: ==> client: -- Keymap: en-us ==> client: -- TPM Path: ==> client: -- INPUT: type=mouse, bus=ps2 ==> client: Creating shared folders metadata... ==> client: Starting domain. ==> client: Waiting for domain to get an IP address... ==> client: Waiting for SSH to become available... client: client: Vagrant insecure key detected. Vagrant will automatically replace client: this with a newly generated keypair for better security. client: client: Inserting generated public key within guest... client: Removing insecure key from the guest if it's present... client: Key inserted! Disconnecting and reconnecting using new SSH key... ==> client: Setting hostname... #<Thread:0x0000562aeef9d3e0@/mnt/vm/vagrant/gems/2.5.1/gems/logging-2.2.2/lib/logging/diagnostic_context.rb:471 run> terminated with exception (report_on_exception is true): Traceback (most recent call last): 70: from /mnt/vm/vagrant/gems/2.5.1/gems/logging-2.2.2/lib/logging/diagnostic_context.rb:474:in `block in create_with_logging_context' 69: from /usr/share/vagrant/gems/gems/vagrant-2.0.2/lib/vagrant/batch_action.rb:82:in `block (2 levels) in run' 68: from /usr/share/vagrant/gems/gems/vagrant-2.0.2/lib/vagrant/machine.rb:188:in `action' 67: from /usr/share/vagrant/gems/gems/vagrant-2.0.2/lib/vagrant/machine.rb:188:in `call' 66: from /usr/share/vagrant/gems/gems/vagrant-2.0.2/lib/vagrant/environment.rb:592:in `lock' 65: from /usr/share/vagrant/gems/gems/vagrant-2.0.2/lib/vagrant/machine.rb:202:in `block in action' 64: from /usr/share/vagrant/gems/gems/vagrant-2.0.2/lib/vagrant/machine.rb:227:in `action_raw' 63: from /usr/share/vagrant/gems/gems/vagrant-2.0.2/lib/vagrant/action/runner.rb:66:in `run' 62: from /usr/share/vagrant/gems/gems/vagrant-2.0.2/lib/vagrant/util/busy.rb:19:in `busy' 61: from /usr/share/vagrant/gems/gems/vagrant-2.0.2/lib/vagrant/action/runner.rb:66:in `block in run' 60: from /usr/share/vagrant/gems/gems/vagrant-2.0.2/lib/vagrant/action/builder.rb:116:in `call' 59: from /usr/share/vagrant/gems/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call' 58: from /usr/share/vagrant/gems/gems/vagrant-sshfs-1.3.1/lib/vagrant-sshfs/action_hostpath_fixup.rb:102:in `call' 57: from /usr/share/vagrant/gems/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call' 56: from /usr/share/vagrant/gems/gems/vagrant-2.0.2/lib/vagrant/action/builtin/config_validate.rb:25:in `call' 55: from /usr/share/vagrant/gems/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call' 54: from /usr/share/vagrant/gems/gems/vagrant-sshfs-1.3.1/lib/vagrant-sshfs/action_hostpath_fixup.rb:125:in `call' 53: from /usr/share/vagrant/gems/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call' 52: from /usr/share/vagrant/gems/gems/vagrant-2.0.2/lib/vagrant/action/builtin/call.rb:53:in `call' 51: from /usr/share/vagrant/gems/gems/vagrant-2.0.2/lib/vagrant/action/runner.rb:66:in `run' 50: from /usr/share/vagrant/gems/gems/vagrant-2.0.2/lib/vagrant/util/busy.rb:19:in `busy' 49: from /usr/share/vagrant/gems/gems/vagrant-2.0.2/lib/vagrant/action/runner.rb:66:in `block in run' 48: from /usr/share/vagrant/gems/gems/vagrant-2.0.2/lib/vagrant/action/builder.rb:116:in `call' 47: from /usr/share/vagrant/gems/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call' 46: from /usr/share/vagrant/gems/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:95:in `block in finalize_action' 45: from /usr/share/vagrant/gems/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call' 44: from /usr/share/vagrant/gems/gems/vagrant-libvirt-0.0.40/lib/vagrant-libvirt/action/set_name_of_domain.rb:35:in `call' 43: from /usr/share/vagrant/gems/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call' 42: from /usr/share/vagrant/gems/gems/vagrant-libvirt-0.0.40/lib/vagrant-libvirt/action/handle_storage_pool.rb:52:in `call' 41: from /usr/share/vagrant/gems/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call' 40: from /usr/share/vagrant/gems/gems/vagrant-2.0.2/lib/vagrant/action/builtin/handle_box.rb:56:in `call' 39: from /usr/share/vagrant/gems/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call' 38: from /usr/share/vagrant/gems/gems/vagrant-libvirt-0.0.40/lib/vagrant-libvirt/action/handle_box_image.rb:113:in `call' 37: from /usr/share/vagrant/gems/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call' 36: from /usr/share/vagrant/gems/gems/vagrant-libvirt-0.0.40/lib/vagrant-libvirt/action/create_domain_volume.rb:82:in `call' 35: from /usr/share/vagrant/gems/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call' 34: from /usr/share/vagrant/gems/gems/vagrant-libvirt-0.0.40/lib/vagrant-libvirt/action/create_domain.rb:308:in `call' 33: from /usr/share/vagrant/gems/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call' 32: from /usr/share/vagrant/gems/gems/vagrant-2.0.2/lib/vagrant/action/builtin/provision.rb:80:in `call' 31: from /usr/share/vagrant/gems/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call' 30: from /usr/share/vagrant/gems/gems/vagrant-libvirt-0.0.40/lib/vagrant-libvirt/action/prepare_nfs_valid_ids.rb:12:in `call' 29: from /usr/share/vagrant/gems/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call' 28: from /usr/share/vagrant/gems/gems/vagrant-2.0.2/plugins/synced_folders/nfs/action_cleanup.rb:25:in `call' 27: from /usr/share/vagrant/gems/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call' 26: from /usr/share/vagrant/gems/gems/vagrant-2.0.2/lib/vagrant/action/builtin/synced_folder_cleanup.rb:28:in `call' 25: from /usr/share/vagrant/gems/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call' 24: from /usr/share/vagrant/gems/gems/vagrant-2.0.2/lib/vagrant/action/builtin/synced_folders.rb:87:in `call' 23: from /usr/share/vagrant/gems/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call' 22: from /usr/share/vagrant/gems/gems/vagrant-libvirt-0.0.40/lib/vagrant-libvirt/action/prepare_nfs_settings.rb:18:in `call' 21: from /usr/share/vagrant/gems/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call' 20: from /usr/share/vagrant/gems/gems/vagrant-libvirt-0.0.40/lib/vagrant-libvirt/action/share_folders.rb:20:in `call' 19: from /usr/share/vagrant/gems/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call' 18: from /usr/share/vagrant/gems/gems/vagrant-libvirt-0.0.40/lib/vagrant-libvirt/action/create_networks.rb:83:in `call' 17: from /usr/share/vagrant/gems/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call' 16: from /usr/share/vagrant/gems/gems/vagrant-libvirt-0.0.40/lib/vagrant-libvirt/action/create_network_interfaces.rb:176:in `call' 15: from /usr/share/vagrant/gems/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call' 14: from /usr/share/vagrant/gems/gems/vagrant-libvirt-0.0.40/lib/vagrant-libvirt/action/set_boot_order.rb:78:in `call' 13: from /usr/share/vagrant/gems/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call' 12: from /usr/share/vagrant/gems/gems/vagrant-libvirt-0.0.40/lib/vagrant-libvirt/action/start_domain.rb:298:in `call' 11: from /usr/share/vagrant/gems/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call' 10: from /usr/share/vagrant/gems/gems/vagrant-libvirt-0.0.40/lib/vagrant-libvirt/action/wait_till_up.rb:77:in `call' 9: from /usr/share/vagrant/gems/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call' 8: from /usr/share/vagrant/gems/gems/vagrant-libvirt-0.0.40/lib/vagrant-libvirt/action/forward_ports.rb:29:in `call' 7: from /usr/share/vagrant/gems/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call' 6: from /usr/share/vagrant/gems/gems/vagrant-2.0.2/lib/vagrant/action/builtin/set_hostname.rb:21:in `call' 5: from /usr/share/vagrant/gems/gems/vagrant-2.0.2/lib/vagrant/guest.rb:43:in `capability' 4: from /usr/share/vagrant/gems/gems/vagrant-2.0.2/lib/vagrant/capability_host.rb:111:in `capability' 3: from /usr/share/vagrant/gems/gems/vagrant-2.0.2/lib/vagrant/capability_host.rb:111:in `call' 2: from /usr/share/vagrant/gems/gems/vagrant-2.0.2/plugins/guests/redhat/cap/change_host_name.rb:10:in `change_host_name' 1: from /usr/share/vagrant/gems/gems/vagrant-2.0.2/plugins/communicators/ssh/communicator.rb:267:in `sudo' /usr/share/vagrant/gems/gems/vagrant-2.0.2/plugins/communicators/ssh/communicator.rb:257:in `execute': The following SSH command responded with a non-zero exit status. (Vagrant::Errors::VagrantError) Vagrant assumes that this means the command failed! # Update sysconfig sed -i 's/\(HOSTNAME=\).*/\1master.client.vm/' /etc/sysconfig/network # Update DNS sed -i 's/\(DHCP_HOSTNAME=\).*/\1"master"/' /etc/sysconfig/network-scripts/ifcfg-* # Set the hostname - use hostnamectl if available echo 'master.client.vm' > /etc/hostname if command -v hostnamectl; then hostnamectl set-hostname --static 'master.client.vm' hostnamectl set-hostname --transient 'master.client.vm' else hostname -F /etc/hostname fi # Prepend ourselves to /etc/hosts grep -w 'master.client.vm' /etc/hosts || { sed -i'' '1i 127.0.0.1\tmaster.client.vm\tmaster' /etc/hosts } # Restart network service network restart Stdout from the command: /usr/bin/hostnamectl Stderr from the command: Redirecting to /bin/systemctl restart network.service Failed to restart network.service: Unit network.service not found. The following SSH command responded with a non-zero exit status. Vagrant assumes that this means the command failed! # Update sysconfig sed -i 's/\(HOSTNAME=\).*/\1master.client.vm/' /etc/sysconfig/network # Update DNS sed -i 's/\(DHCP_HOSTNAME=\).*/\1"master"/' /etc/sysconfig/network-scripts/ifcfg-* # Set the hostname - use hostnamectl if available echo 'master.client.vm' > /etc/hostname if command -v hostnamectl; then hostnamectl set-hostname --static 'master.client.vm' hostnamectl set-hostname --transient 'master.client.vm' else hostname -F /etc/hostname fi # Prepend ourselves to /etc/hosts grep -w 'master.client.vm' /etc/hosts || { sed -i'' '1i 127.0.0.1\tmaster.client.vm\tmaster' /etc/hosts } # Restart network service network restart Stdout from the command: /usr/bin/hostnamectl Stderr from the command: Redirecting to /bin/systemctl restart network.service Failed to restart network.service: Unit network.service not found.
Hello, thank you for the report. It's a clone of Bug 1624068, but just for F28. I'm working on this, but the backport is a bit complicated, so it takes time. I'll create a PR, later today. You can check it afterwards, here: https://src.fedoraproject.org/rpms/vagrant/pull-requests In the meantime you can try Vagrant from my COPR with latest (Rawhide) Vagrant: https://copr.fedorainfracloud.org/coprs/pvalena/vagrant/
vagrant-2.0.2-5.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-66659d070f
vagrant-2.0.2-5.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-66659d070f
vagrant-2.0.2-5.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.