Description of problem: Fedora 22 vagrant box is not very usable for the following reasons: 1) Missing rsync package This means each "vagrant up" takes an extra minute or so waiting for: "Installing rsync to the VM..." When a machine up normally takes 30s, 90 sec is too long. 2) Root pw not set to "vagrant" Necessary for when a user wants to jump in and hack on the machine. 3) Screen package not installed. This is critical for many tools which depend on this. Version-Release number of selected component (if applicable): Fedora-Cloud-Base-Vagrant-22-20150521.x86_64.vagrant-libvirt.box How reproducible: 100% Additional info:
FWIW, this patch should take 3 seconds to write for anyone with commit access.
The Oh-My-Vagrant project is a development environment for users who don't want to deal with all the little details and hassles of setting up vagrant and getting it working. As a result, I've added a workaround for #2: https://github.com/purpleidea/oh-my-vagrant/commit/42e66868ce712a325bf90a736e71f5bd9531fefb This isn't a substitute for fixing the above issues, especially #3, but it will ease some of the pain.
A similar bug (but for the Atomic box) is: https://bugzilla.redhat.com/show_bug.cgi?id=1225630
Similarly, it would be very handy if nfs-utils were preinstalled on the box for users who use NFS to share the code (especially since there is a Vagrant bug that breaks installation of NFS in Fedora).
James, I am sorry but this is definitely not the right place to report this issue. Please report the issues to Fedora Release Engineering [1]. [1] https://fedorahosted.org/rel-eng/
(In reply to Vít Ondruch from comment #5) > James, I am sorry but this is definitely not the right place to report this > issue. Please report the issues to Fedora Release Engineering [1]. > > > [1] https://fedorahosted.org/rel-eng/ I don't understand why there's a different tracker, and that this one is no good, but nevertheless, I've opened: https://fedorahosted.org/rel-eng/ticket/6192 If you can leave this open so bz folks can follow along until that rel-eng ticket is fixed, it would be nice. Cheers, James
(In reply to Vít Ondruch from comment #5) > James, I am sorry but this is definitely not the right place to report this > issue. Please report the issues to Fedora Release Engineering [1]. Vit: for future reference this isn't a rel-eng issue. The decision to which packages are included in the cloud builds is a issue for the Cloud WG, same for all other working groups. rel-eng produce the images, we don't define what's in them!
(In reply to Peter Robinson from comment #7) Can whoever has commit access please make the very small changes required? We spend so much time in trackers instead of writing patches. -- One of the unfortunate reasons github is so practical -- just make a pull request, which is a standard way to get patches into any project using github :)
(In reply to James (purpleidea) from comment #8) > (In reply to Peter Robinson from comment #7) > Can whoever has commit access please make the very small changes required? > > We spend so much time in trackers instead of writing patches. -- One of the > unfortunate reasons github is so practical -- just make a pull request, > which is a standard way to get patches into any project using github :) It's likely not there because the cloud WG didn't want it. I have the right access but it's not my decision to make. If you take it to the proper forum, like the mailing list, you wouldn't need to spend any time writing patches or in trackers!!
(In reply to Peter Robinson from comment #7) > Vit: for future reference this isn't a rel-eng issue. Asked on IRC before, nobody cared to answer ... (In reply to James (purpleidea) from comment #8) > We spend so much time in trackers instead of writing patches. -- One of the > unfortunate reasons github is so practical -- just make a pull request, > which is a standard way to get patches into any project using github :) First you always need to submit PR to the right project, which you would unfortunately failed.
(In reply to Peter Robinson from comment #9) > (In reply to James (purpleidea) from comment #8) > > (In reply to Peter Robinson from comment #7) > > Can whoever has commit access please make the very small changes required? > > > > We spend so much time in trackers instead of writing patches. -- One of the > > unfortunate reasons github is so practical -- just make a pull request, > > which is a standard way to get patches into any project using github :) > > It's likely not there because the cloud WG didn't want it. I have the right > access but it's not my decision to make. If you take it to the proper forum, > like the mailing list, you wouldn't need to spend any time writing patches > or in trackers!! Most time seems to be spent trying to find out how these cloud images are created, who is responsible and where to go when one needs an addition... E.g. which mailing list are you referrin to? Peter: If you could share some links/repos about the creation of these images, that would be highly appreciated! After all - which mailing list are you referring to? fedora-devel, or is there a specific one? Thanks - Michael
> After all - which mailing list are you referring to? fedora-devel, or is > there a specific one? Each Product/Edition (Cloud, Server, Workstation) as a Working Group and each WG has a mailing list. So in this case it would be cloud mailing list.
(In reply to Peter Robinson from comment #12) > > After all - which mailing list are you referring to? fedora-devel, or is > > there a specific one? > > Each Product/Edition (Cloud, Server, Workstation) as a Working Group and > each WG has a mailing list. So in this case it would be cloud mailing list. Thanks, Peter!
James, this is the code repo: git.fedorahosted.org/git/spin-kickstarts.git According to the git log, two of your three items are already solved: - root pw is vagrant - rsync is installed Cheers - Michael
(In reply to Michael Adam from comment #14) > James, > > this is the code repo: > > git.fedorahosted.org/git/spin-kickstarts.git > > According to the git log, two of your three items are already solved: > > - root pw is vagrant > - rsync is installed > > Cheers - Michael Still missing screen, and a rebuild for F22. Those fixes are only in F23.
(In reply to Michael Adam from comment #14) > According to the git log, two of your three items are already solved: > > - root pw is vagrant > - rsync is installed Can we get nfs_utils added as well?