I think most folks using vagrant recently have hit this, which is that "vagrant up" explodes on the dnf upgrade provisioning step.
I've been poking at this off and on, and I have a diff that "fixes" it: --- $ diff -u Vagrantfile.example Vagrantfile --- Vagrantfile.example 2016-02-25 10:09:05.084514090 -0500 +++ Vagrantfile 2016-03-21 18:38:14.770621087 -0400 @@ -30,32 +28,32 @@ # end # Comment this line if you would like to disable the automatic update during provisioning - config.vm.provision "shell", inline: "sudo dnf upgrade -y" + config.vm.provision "shell", inline: "sudo dnf upgrade -y || sudo dnf upgrade -y" --- "Hey dnf, if you could go ahead and upgrade my system without prompting me, that'd be great. Hmm. Yeah. If that doesn't work, why don't you, y'know, go ahead and make sure you upgrade my system without prompting me. Yeeeaaaah. That'd be great. Thaaaanks."[0] I know there has to be a better "solution", but I found this one simultaneously useful and hilarious enough to share. It's better than a simple "|| true" in that it doesn't hide actual failures of a dnf upgrade, but for whatever reason it does suppress the failure that's currently annoying many vagrant users. Meanwhile...does anyone have a clue why dnf is behaving this way? [0]: https://www.youtube.com/watch?v=Fy3rjQGc6lA
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Pulp-list mailing list Pulp-list@redhat.com https://www.redhat.com/mailman/listinfo/pulp-list