In 57985b08 nightly was updated, but not all the variants were updated
in the second sync. The first sync runs with --exclude repodata, then
the second one includes that and also does a --delete-after, but we only
updated the first one. This should clean up old artifacts.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
This update adds the various pieces for the UEFI side of things
and removes the old appliance build process including a few cleanups.
It also updates the sync process and cleans up a few bits here
while at it.
Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
aarch64 isn't hardlinked with the rest of primary
rawhide and branched aren't hardlinked together
* other bits more than likely aren't hardlinked.
So, lets try and hardlink content after we sync it here.
This may be too i/o intensive or slow to keep, but we can
try it for a few days and see how bad it is.
Signed-off-by: Kevin Fenzi kevin@scrye.com
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
This is to fix the composes sync to PDC as both the live_media and
live_images have same metadata and that is causing the sync issues
Signed-off-by: Mohan Boddu <mboddu@bhujji.com>
We really need to figure out whats grown here, but in the mean time we
just need to get a compose out, so increase the size here.
The aarch64 one went past 4gb.
see: https://koji.fedoraproject.org/koji/taskinfo?taskID=56316220
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
It was made failable in #382, back in 2017, as part of the
Modular Server effort that was eventually abandoned, with the
idea being that Modular Server would be blocking instead. But
when Modular Server was abandoned, we never reverted this change
to make Server non-failable again...
Signed-off-by: Adam Williamson <awilliam@redhat.com>
When not specified, subvariant defaults to the variant. This leads to
both armhfp appliance and image_build based raw.xz image to have
identical metadata. A file with such issue can not be loaded by
productmd parser.
Due to another issue (that should be fixed in next Pungi release), the
paths to image directories are not listed in composeinfo.json file. The
compose-partial-copy script therefore has to find out if images should
be copied from the image metadata. And since there's an error in it, it
doesn't see the images and doesn't copy them.
Signed-off-by: Lubomír Sedlář <lsedlar@redhat.com>
This reverts commit 4c5ce9fb5d.
This is a one time thing to test it out. We will add it back once the
change is approved
Signed-off-by: Mohan Boddu <mboddu@bhujji.com>
This will reduce both the BOOT.iso and the DVD medium size
This modification relates to the following change proposal:
https://fedoraproject.org/wiki/Category:Changes/OptimizeSquashFS
The new option should work for Pungi version 4.24 and above
Jira: RHELCMP-693
Signed-off-by: Bohdan Khomutskyi <bkhomuts@redhat.com>
It turns out koji doesn't know about `gce` even though ImageFactory
does. Really all we need is the output disk image to be a tar.gz so
let's try with the `tar-gz` format in koji, which looks like it was
intended for use with GCP.
Signed-off-by: Dusty Mabe <dusty@dustymabe.com>
We added this so we could eventually use the VMDK to optimize our
uploads to AWS but it turns out the VMDK created by imagefactory
isn't in the right format anyway.
```
SNAPSHOTTASKDETAIL 0.0 VMDK deleted ClientError: Disk validation failed [Unsupported VMDK File Format]
```
Let's drop them for now.
Signed-off-by: Dusty Mabe <dusty@dustymabe.com>
