This leads to some exception being raised instead of by-pass safely.
It was useful at some point because pagure would not log error to
its logs otherwise but Patrick has since fixed it and I believe it
may be triggering some errors now.
Signed-off-by: Pierre-Yves Chibon <pingou@pingoured.fr>
So in out dist-git setup the git hook have a dedicated configuration
file which only contains a read-only access to the database.
This is because of the way our dist-git is setup where every packager
actually has a shell account on the machine and the hook are run by
that account.
So if the packager manages to get a shell access, they will be able to
read this configuration file and we do not want to give them read/write
access to the database.
Pagure however in the default hook tries to update the database, among
other it tries to clear the cached merge status of the open PR when a
commit is pushed.
For a nice UX, it does this within the hook process, this way there is
no race-condition and users accessing a PR right after a push will get
an up to date merge status (as it will be re-generated).
But we cannot do this in dist-git since we cannot update the database
directly, so instead, with this hotfix, we move the process of cleaning
up the merge status to an async job that will have read/write access
and there may be some race-condition in displaying the merge status
but so be it.
Signed-off-by: Pierre-Yves Chibon <pingou@pingoured.fr>
This leads to some exception being raised instead of by-pass safely.
It was useful at some point because pagure would not log error to
its logs otherwise but Patrick has since fixed it and I believe it
may be triggering some errors now.
Signed-off-by: Pierre-Yves Chibon <pingou@pingoured.fr>
For unclear reason ansible seems to have issues with mode expressed
in integer while it seems to work much more nicely if they are
provided as string.
So moving to this for now.
Signed-off-by: Pierre-Yves Chibon <pingou@pingoured.fr>
The certificates are in pki/issued while the keys are in pki/private.
The location to the CA cert is correct though.
Signed-off-by: Pierre-Yves Chibon <pingou@pingoured.fr>
The certificates are resultsdb.crt in prod while they are resultsdb.stg.crt in
staging so by using the ansible variable {{ env_suffix }} we're able to support
both files in one line.
Signed-off-by: Pierre-Yves Chibon <pingou@pingoured.fr>
Per averi, cloud.gnome.org is to be removed.
This host has no impact on fedora releases and shouldn't freeze.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
Gnome folks have a gnome-backups01 vm that has a netapp volume for backups.
They manage it via our ansible repo and playbooks.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
