Story #2612
closed
As a developer, I `vagrant up` into a rawhide box
0%
Description
Recently we needed to do some development against Rawhide for dependency reasons. I couldn't easily figure out how to have the 'most recent Rawhide' compose be the basis for our vagrant VM.
I can see the composes for Rawhide here[0]. I can also see a latest one[1]. I would like the Rawhide link to be a commented line in our Vagrantfile.example. There is an entry for Rawhide in our Vagrantfile.example already, but it is broken[2]. This suggests that they used to publish a .box format, but now they don't.
[0]: https://kojipkgs.fedoraproject.org/compose/rawhide/
[1]: https://kojipkgs.fedoraproject.org/compose/rawhide/latest-Fedora-Rawhide/
[2]: https://github.com/pulp/devel/blob/master/Vagrantfile.example#L29
Related issues
Updated by bmbouter almost 8 years ago
Through an in-person chat with @maxamillion, I learned that vagrant boxes should be produced with every rawhide compose and should be available from here [0]. If they are not present, it means that that portion of the rawhide build failed for whatever reason. A more comprehensive list of 'successful' builds is available via a URL that I need to get from @maxamillion.
Given ^ I think the fix for this is to:
1. Add the link [0] into the Vagranfile.example as a commented out line
2. Include a section on the dev docs that identify that booting into Rawhide is an option which can be enabled.
3. Give some docs on how to use the 'recent builds URL' from @maxamillion to find a url in the instance where the vagrant libvirtd box failed to build.
Updated by amacdona@redhat.com over 7 years ago
- Related to Story #2555: As a developer, I should be able to vagrant up into CentOS7 or a Support Fedora. added
Updated by bmbouter over 5 years ago
- Status changed from NEW to CLOSED - WONTFIX
Updated by bmbouter over 5 years ago
Pulp 2 is approaching maintenance mode, and this Pulp 2 ticket is not being actively worked on. As such, it is being closed as WONTFIX. Pulp 2 is still accepting contributions though, so if you want to contribute a fix for this ticket, please reopen or comment on it. If you don't have permissions to reopen this ticket, or you want to discuss an issue, please reach out via the developer mailing list.
.