[release] Pungi 4.3.7
by Ondrej Nosek
Pungi development team is pleased to announce the availability of Pungi
4.3.7. The updates are waiting in the updates-testing repo. Rawhide is
Here are the changes of 4.3.7:
- osbuild: support specifying upload_options (thozza)
Since version 9, the `koji-osbuild` plugin supports specifying upload
options as part of a Koji build. This enables one to upload the built image
directly to the cloud environment as part of the image build in Koji.
- osbuild: accept only a single image type in the configuration (thozza)
Modify the osbuild configuration schema to accept only an array with a
single value as the `image_types`, in addition to a single string. The
single string was supported by the schema also before, but this fact was
not mentioned in the documentation, nor it was supported by the
`koji-osbuild` plugin of a version lower than `9`.
- osbuild: support specifying `package_sets` for repos (thozza)
The `koji-osbuild` plugin supports additional formats for the `repo`
property since v4 . Specifically, a repo can be specified as a
dictionary with `baseurl` key and `package_sets` list containing specific
package set names, that the repository should be used for.
- osbuild: update schema and config documentation (thozza)
Adjust the schema in Pungi to reflect changes in `koji-osbuild`. For
more information on the changes in `koji-osbuild`, see:
- osbuild: don't use `util.get_repo_urls()` (thozza)
Implement osbuild-specific variant to resolve provided repositories.
The reason is that the function from `utils` transforms repositories
defined as dicts to strings, which is undesired for osbuild. The
requirement for osbuild is to preserve the dict as is, just to resolve the
string in `baseurl` to the actual repository URL.
- createiso: Create Joliet tree with xorriso (lsedlar)
This structure is important for isoinfo -J, which is in turn called by
virt-install. This can be tested by using a bootable ISO by modifying it
with a dummy additional file and preserving boot records.
- Speed up tests by 30 seconds (lsedlar)
The retry test for CTS doesn't actually need to wait. Let's mock the
- Stop sending compose paths to CTS (lsedlar)
The tracking service will reject it as it's not an HTTP URL. Let's not
- Report errors from CTS (lsedlar)
If the service returns a status code indicating a user error, report
that and do not retry.
- init: Filter comps for modular variants with tags (lsedlar)
Modular variants can either be specified by a list of modules, or by a
list of Koji tags. In terms of comps preprocessing there should not be any
difference between the two.
- Retry failed cts requests (hlin)
- Ignore existing kerberos ticket for CTS auth (lsedlar)
When there is an existing Kerberos ticket, it gets precedence over the
environment variable with a path to a keytab. That is not expected and the
user ticket can possibly lack permissions in CTS to be able to run the
This patch fixes that by setting KRB5CCNAME to a fresh path. That way
there will not be any valid ticket, since the credentials cache does not
- Add Jenkinsfile for CI (hlin)
- profiler: Flush stdout before printing (lsedlar)
Apparently redirecting stderr to the same pipe as stdout does not
guarantee that the data will not be mangled together. Flushing stdout
before the profiler data is printed should ensure that it does not end up
in the middle of some RPM path.
Big thanks to everyone involved in this release.
Refer to the documentation  for details on what configuration options
If you encounter problems or need general help, stop by #fedora-releng
IRC channel or file issues in Pagure.
5 months, 3 weeks