Images should include signed bits, so we need to block the compose until
the commit is signed.
Related: https://pagure.io/pungi/issue/650
Signed-off-by: Lubomír Sedlář <lsedlar@redhat.com>
(cherry picked from commit 968f8fdf5222696c2b075a0325c844032ba8d427)
Signed-off-by: Dusty Mabe <dusty@dustymabe.com>
Dropping shim because we decided to ship the traditional, signed Fedora
version in this release. Adding hardware-support, which carries
dependencies for the installer, and adding perl, which is required by
hardware-support.
Also reordering the list so it's easier to read.
Signed-off-by: Petr Šabata <contyk@redhat.com>
Creating the image requires running lorax. There is however already one
lorax instance being run in the buildinstall phase. When the second one
runs, it overwrites the outputs from first one and people expecting to
boot netinst over PXE are instead getting ostree workstation.
Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1477916
Relates: https://pagure.io/pungi/issue/695
Signed-off-by: Lubomír Sedlář <lsedlar@redhat.com>
See https://pagure.io/pungi/pull-request/727
Once that is merged, released, and deployed, this change will let us see
New and Fascinating Details about the compose process.
Signed-off-by: Ralph Bean <rbean@redhat.com>
Signed-off-by: Adam Miller <maxamillion@fedoraproject.org>
(cherry picked from commit 2a565c78bc4c79798bdb91779994dde74b7c5e9a)
Signed-off-by: Dusty Mabe <dusty@dustymabe.com>
composes were failing because the 2nd image build task
for the minimal image (copied from fedora.conf) didn't
have some variables defined. In fedora.conf the global_*
vars are defined, so let's do that here too.
Signed-off-by: Dusty Mabe <dusty@dustymabe.com>
(cherry picked from commit 6a859299436cd1e664136c451121465a5cb689b2)
We don't create a repo during this pungi run. We need to pull
from a repo that was already created.
This was a copy/paste error from f6e7f69.
Signed-off-by: Dusty Mabe <dusty@dustymabe.com>
(cherry picked from commit c4169526585144e44a6a99466e55a64cad2a9b03)
The nightly scripts try to send an announcement about compose starting.
As this happens before Pungi even started, the compose ID is not known
and can not be included in the message. The message about starting rsync
sent later will contain the ID correctly.
Without the json defined there is a traceback in the cron output, but
the errors are not logged anywhere else (but don't actually block
anything in the compose process).
Relates: https://pagure.io/pungi/issue/698
Signed-off-by: Lubomír Sedlář <lsedlar@redhat.com>
Since we are currently building atomic host media every night using
the cloud variant then we need to add ostree-support group if we
want to pull in new ostree tools into the ISO installer images.
Signed-off-by: Dusty Mabe <dusty@dustymabe.com>
