This reverts commit 548e6c47cc.
Rolling back the deployment to the old version, which does not have the
necessary "wait-for-db" command which this hook uses.
Starting from the upcoming 0.8 release, Greenwave will query Bodhi to
find builds in an update. The default configuration has production
Bodhi, in staging we want to use staging Bodhi instead.
Greenwave 0.8+ has switched to Python 3, which means the fedmsg-hub
command for the fedmsg-consumers pod has to be fedmsg-hub-3 now.
This is in staging only for now.
In Greenwave 0.8 (not released yet) subject_type will replace
relevance_key and relevance_value:
https://docs.pagure.org/greenwave/release-notes.html#next-release
Add the appropriate subject_type keys to all policies so that we can
roll out the latest code to staging.
This is not wrapped in a conditional because older versions of Greenwave
will just ignore the new subject_type key, while newer versions of
Greenwave will ignore the relevance_key and relevance_value keys.
Later, once Greenwave 0.8 is released and rolled out in stage and prod,
we can remove the relevance_key and relevance_value from the policies.
We probably no longer need infra-tags repo on minions (and the existing
repo was outdated a non-working anyway). We don't need to override
fedora repos in local deployment, because they now use mirrormanager by
default.
This commit is just to make Ansible think these have changed.
I committed a change earlier and ran the playbook to apply it, but stg
OpenShift was down. So the templates were rendered into
/etc/openshift_apps but not successfully fed to `oc apply`. Now Ansible
thinks there is nothing to apply when I re-run the playbook. This will
trick it.
Nowadays we have an imagestream, which pulls pre-built waiverdb images
from quay.io, and a buildconfig, which then layers some
Fedora-infra-specific stuff on top.
When we have a new version to deploy, the imagestream should pick up the
new image from quay.io, which triggers a build of the buildconfig, which
triggers a deploy of the deploymentconfig. So we shouldn't need to
explicitly fire off start-build anymore.
We *shouldn't* need to explicitly fire off import-image either, because
it is set to "scheduled" pull policy. But I am not sure what the
schedule is. Right now it says it last polled 5 days ago... that may
itself be a bug. Regardless, this gives us a nice way to make it pull
the latest image.
This patch adds a new, very simple role "import-image" to fire off the
oc import-image command, following the precedent of the existing
"start-build" role.
