Learn more about these different git repos.
Other Git URLs
When a variant runs both buildinstall and ostree_installer phase, the outputs from the first lorax run are overwritten by the second one.
boot.iso
images/
isolinux/
<variant>/<arch>/os/
<variant>/<arch>/iso/
This leads to situation where people looking at os/images/boot.iso might expect netinst image, but actually see the ostree installer.
os/images/boot.iso
Related bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1477916
There's actually a much more important consequence of this than boot.iso not being the expected file (that's really not terribly important, since the real network install image is easily available from its normal location): the contents of os/images/ are from the OStree compose, not the network install compose, which is bad for anyone doing a PXE boot install or other direct kernel boot install. See https://bugzilla.redhat.com/show_bug.cgi?id=1477916#c3 .
Proposed workaround in #700: when there already is netinst content, Pungi will no longer copy the ostree installer files there. That however means they will not be shipped (other than the ISO itself).
We need a place where to put it, maybe <variant>/<arch>/ostree/ would work (except that there would only be the boot stuff, not the ostree itself)?
<variant>/<arch>/ostree/
We should either enforce a single buildinstall per variant, causing the Workstation Ostree to become its own variant, or we need to namespace secondary buildinstall runs
Using separate variant seems less disruptive than adding the namespace: the path to the files will change anyway, but the change is smaller. Also it's achievable without any code change: pungi-fedora#347
Pungi should however be changed to not allow the overwriting.
Metadata Update from @lsedlar: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Metadata Update from @lsedlar: - Issue tagged with: 4.1.19
Commit 7c237c2 relates to this ticket
Login to comment on this ticket.