This uses the release number templates for the product_versions
blocks in the gating config, instead of hardcoding them. I tried
to include some flexibility so we can easily manually flip gating
on or off for Rawhide or Branched - for specific rules, or the
whole file - around branch time, if we need to (sometimes we do,
as we can get in catch-22 situations and stuff during branching).
Signed-off-by: Adam Williamson <awilliam@redhat.com>
Otherwise we risk a conflict with other automatically allocated users,
right now it is:
fatal: [copr-keygen-dev.aws.fedoraproject.org]: FAILED! => {"changed": false, "msg": "useradd: UID 992 is not unique\n", "name": "copr-signer", "rc": 4}
At first, I wanted to fix the current name and change it back to eth0 but it
seems this is a desired naming from now on and we should probably adopt it.
https://fedoraproject.org/wiki/Changes/EnableConsistentDeviceNamingCloud
This commit will probably break playbooks for the production instances but I
cannot do a "if devel" condition here. So hopefully, we will be fine.
This means we don't need to manually update the release numbers
at stable release and EOL times any more, only make sure the
relevant playbook is run.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
There was a typo in krb5 config for staging machines as the naming
convention is stg.iad2.fedoraproject.org and not iad2.stg.fedoraproject.org.
Signed-off-by: Michal Konecny <mkonecny@redhat.com>
will move project offboarding into separate playbook
add fasjson lookup for communishift project notifications
Signed-off-by: David Kirwan <davidkirwanirl@gmail.com>
On Fedora 41 /etc/systemd/journald.conf isn't shipped by default anymore.
Instead /usr/lib/systemd/journalc.conf is the default
On RHEL and older Fedora's we can just not set this and it will
find the default one.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
In Fedora libvirt switched to a collection of socket activated services
instead of a large single libvirtd service. Restarting that service
caused the socket activated ones to die and then libvirtd exited on
idle, leaving nothing handling virt connections.
So, lets stop trying to restart that and no need to notify other things
because they should idle out/restart on socket activation.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
In f41+ libvirt defaults to using nftables if both it and iptables
are installed, but it doesn't seem to work with imagefactory/oz
virt instances and our iptables setup.
So, lets revert back to iptables for now.
We can switch back if we can fix the incompatiblity, switch builders
to nftables, or stop using oz/IF
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
dnf5 requires neither python3-rpm nor python3-dnf, so we cannot
assume they are installed (as they always were before). ansible's
package_facts needs python3-rpm (even in the latest upstream
version), so we at least need that. The ansible in rhel9 (which
is what's on batcave01 currently) does not support dnf5 at all,
so we need python3-dnf installed so it can use its dnf3/4
support. python3-dnf relies on python3-rpm, so we can just
check for and install python3-dnf. Once batcave01 is updated to
an ansible that supports dnf5 we won't need python3-dnf, but we
*will* still need python3-rpm.
Stuffing this in yumrepos.yml as it runs on everything, early,
and is packaging-related. We could make it a separate task but
then we'd need to make every playbook include it...
Signed-off-by: Adam Williamson <awilliam@redhat.com>
