This commit makes the coreos-cincinnati setup look similar to the
other CoreOS/OSTree apps that we own. Notable changes:
- We are still building via commit, we only track a single commit
and not a separate deploy/build one.
- We are now just outputting to a coreos-cincinnati-img:latest
imagestream tag.
- We are now using a fedora:38 imagestream tag as the from: in our
build and triggering new builds based on imagestream updates,
which means we'll get security updates more regularly.
- A bunch of quoting (") in yaml files was removed as it clouded the
diffs between this app and other apps.
- Some minor diffs between playbooks and other files were removed.
As part of an effort to make coreos-cincinnati look like the rest
of the CoreOS Apps we'll move all files into the templates dir
(because even if they aren't templatized they still work there)
and rename `buildconfig-stub.yml` to `buildconfig.yml`.
With Flock around the corner, we need some email addresses for people to
reach the organizer team or for setting a reply-to alias for the new CFP
system we are introducing this year. All Flock aliases were disabled per
request of @mattdm in #10411 because of spam. It seems `flockinfo@` is
the problematic mail alias, so I took a conservative approach by only
enabling the `flock-staff@` and `flock-coc@` addresses.
I also added @shaunm to both aliases because he is also a part of the
core staff team for this year's Flock.
Signed-off-by: Justin W. Flory (he/him) <jwf@redhat.com>
We need this to try and relay in emails.
It turns out to be bordering on impossible to do this sanely with our
current setup, so make a fedora vm that lets us use saslauthdb to have a
specific (small) list of users that can authenticate and relay emails
via bastion and out. We can't do this on rhel, because they don't build
the saslauthdb backend. We can't use any of the other backends because
they either don't work or would allow any fedora user to relay, which we
do not want.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
See https://github.com/praiskup/resalloc-aws/pull/5
I was getting the following error:
An error occurred (SpotMaxPriceTooLow) when calling the RunInstances
operation: Your Spot request price of 0.102 is lower than the minimum
required Spot request fulfillment price of 0.1371.
So I am setting the price limit to the same value as for x86_64 builders.
We're using ifnames on this host right now (I don't recall why
or when that changed) so all the network setup stuff has the
wrong interface names, this is breaking tap tests.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
el7 hosts don't have python3 installed normally, so this fact fails. ;(
"failed_modules": {"python3_fact": {"failed": true, "module_stderr": "/usr/bin/env: python3: No such file or directory\n",
So, lets just disable for now until we can fix it.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
