Description of problem: assign a detail to a network card and vagrant breaks Version-Release number of selected component (if applicable): 1.8.5-2.fc25 How reproducible: Steps to Reproduce: install vagrant mkdir ~/vagranttest cd vagranttest create a minimal Vagrantfile cat > Vagrantfile <<EOF # -*- mode: ruby -*- Vagrant.configure("2") do |config| config.vm.network :private_network, ip: '192.168.121.2', netmask: '255.255.255.0' config.vm.box = "centos/7" end EOF start the vagrant machine with 'vagrant up' and wait for it to fail Actual results: It fails to configure the nic Expected results: It should configure the nic Additional info: looks a bit like this one: https://github.com/vagrant-libvirt/vagrant-libvirt/issues/645 cause if you check /etc/sysconfig/network-scripts/ifcfg-eth1 you will see the concatenated mac-addresses while /etc/sysconfig/network-scripts/ifcfg-eth0 has none
Testing this on Rawhide with vagrant-1.9.1-1.fc26 and vagrant-libvirt-0.0.37-3.fc26, I can't see any issue except of the concatenated mac-addresses in ifcfg-eth1. Applying the patch patch from the issue you referenced, there is no mac listed in ifcfg-eth1 at all. Anyway, this should be F25 build with the patch form the upstream ticket applied: https://koji.fedoraproject.org/koji/taskinfo?taskID=18030137 If it works for you, I can apply it in F25.
Ok, I was able to reproduce this error on Rawhide using Vagrant 1.8.7 and vagrant-libvirt 0.37.0 and it seem the patch is fixing the issue.
Hello, After applying the patch from https://github.com/vagrant-libvirt/vagrant-libvirt/commit/5ed93bd90878166beaceaf9c88724eaac231719c It works for me as well. Rob Verduijn
Is it supposed to create an aditional network card ? Or is that normal behaviour ? Rob Verduijn
I am not expert on this matter, but as far as I can tell, it should create additional card. Anyway, with this configuration I have two network interfaces with or without the patch, so I believe it does not break anything :)
vagrant-libvirt-0.0.35-3.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2017-0720d8dce9
hi, looking forward to the patch. the second card is in the same subnet as the first, so unless you want to try bonding/teaming, an additional network for this card would be a wise thing. Rob Verduijn
vagrant-libvirt-0.0.35-3.fc25 has been pushed to the Fedora 25 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-2017-0720d8dce9
I can't test it. The build has failed on the lint check. Rob Verduijn
(In reply to rob.verduijn from comment #9) > I can't test it. > The build has failed on the lint check. Could you please be more specific? I am not sure if I understand your references to "build" and "lint check" ...
Hello, I followed the link to the build service to see why the rpm was not yet in testing: https://bodhi.fedoraproject.org/updates/FEDORA-2017-0720d8dce9 On that page The automated build results give a fail on the test dist.rpmlint: https://taskotron.fedoraproject.org/artifacts/all/d0820a7e-faa5-11e6-9ed0-5254008e42f6/task_output/vagrant-libvirt-0.0.35-3.fc25.log Because the build service refused to build the rpm due to lint errors, I can't test the new rpm to see if it works. Rob Verduijn
(In reply to rob.verduijn from comment #11) Ah, ok, thx for explanation. I don't think the rpmlint is of any concern. The builds are actually done and available in the build system [1]. The limiting factory is always how quickly is the compose done and how fast are the updates propagated to the mirrors. But doing "dnf update https://kojipkgs.fedoraproject.org//packages/vagrant-libvirt/0.0.35/3.fc25/noarch/vagrant-libvirt-0.0.35-3.fc25.noarch.rpm" should allow you to update and test in any case. [1] https://koji.fedoraproject.org/koji/buildinfo?buildID=861777
Hello, The rpm from updates-testing works fine for me. Rob Verduijn
vagrant-libvirt-0.0.35-3.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.
(In reply to rob.verduijn from comment #13) Glad to heard that. Thank you for your feedback.