#1126 createiso phase fails on ppc64le after lorax update in rawhide
Closed: Fixed 5 years ago by lsedlar. Opened 5 years ago by sharkcz.

As you can see in https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20190217.n.0/logs/ppc64le/createiso-Fedora-Server-dvd-ppc64le-Rawhide-20190217.n.0.iso.ppc64le.log the "full iso" creation fails on ppc64le.

I made some changes in lorax recently to omit generating stuff relevant only for Apple PPC machines, see https://github.com/weldr/lorax/commit/d35232d9cc0ea57e6c29a0af49172d31f1c07e6b
They were needed because lorax switched from genisoimage to xorrisofs and they are not 100% compatible with the command line options. And Apple stuff makes no sense on ppc64le.

I think the problem is that pungi runs on a F-29 machine in the infra and uses F-29 lorax to extract the "genisoimage" command for creating the full isos into the createiso-Fedora-Server-dvd-ppc64le-Rawhide-20190217.n.0.iso.sh script (similar for other arches). But the resulting script is then run in a F-30 runroot and fails.

A workaround might be to always re-build Rawhide lorax in "fXY-infra" tag and use it instead of the fXY lorax.

CC: @mohanboddu @kevin


The ISO is created in a runroot task in koji and in this particular case it was using lorax-30.15-1.fc30.

The build no longer provides /usr/share/lorax/templates.d/99-generic/config_files/ppc/mapping file, which is referenced by the genisoimage command.

Koji task: https://koji.fedoraproject.org/koji/taskinfo?taskID=32866466

How is the "genisoimage" command line generated? Am I right that it's from F-29 lorax templates, because pungi itself runs on a F-29 system?

I see, I'll send a PR for the same cleanup in pungi. And IMHO pungi should standardize on xorriso to be consistent with lorax.

The patch that allows disabling the options is included in pungi-4.1.33-2.fcX, which is now built in Koji for Rawhide and all supported versions of Fedora.

Metadata Update from @lsedlar:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

5 years ago

Metadata Update from @lsedlar:
- Issue set to the milestone: 4.1.34

5 years ago

Login to comment on this ticket.

Metadata