DevHeads.net

Can't push to batched an Fedora 30 update?

<a href="https://bodhi.fedoraproject.org/updates/FEDORA-2019-fd699ee2ea" title="https://bodhi.fedoraproject.org/updates/FEDORA-2019-fd699ee2ea">https://bodhi.fedoraproject.org/updates/FEDORA-2019-fd699ee2ea</a>

"This update has reached 3 days in testing and can be pushed to stable
now if the maintainer wishes"

Yes I'd like to, but there's no push to batched button!
I guess this is something to do with "Failed to talk to Greenwave."?

Rich.

Comments

Re: Can't push to batched an Fedora 30 update?

By Randy Barlow at 03/11/2019 - 12:21

This should be resolved now. Sorry for the issues!

Re: Can't push to batched an Fedora 30 update?

By Randy Barlow at 03/11/2019 - 10:35

On Mon, 2019-03-11 at 08:22 +0000, Richard W.M. Jones wrote:
I noticed this on one of my packages too today. I'm going to look into
it now. My guess is that the front end was not updated with the
configuration change when Fedora 30 was added to Bodhi, but I am not
sure yet.

This is a separate issue:

<a href="https://pagure.io/greenwave/issue/388" title="https://pagure.io/greenwave/issue/388">https://pagure.io/greenwave/issue/388</a>

Re: Can't push to batched an Fedora 30 update?

By Randy Barlow at 03/11/2019 - 10:46

On Mon, 2019-03-11 at 10:35 -0400, Randy Barlow wrote:
I have confirmed that the frontend has not been restarted since Fedora
30 was added, which would cause this problem. I've filed a freeze break
request to get permission to rebuild the frontend containers with the
config change:

<a href="https://lists.fedoraproject.org/archives/list/ ... at lists dot fedoraproject.org/thread/7X6B6BGFJ7SYZA243XOVPEJT7KVXRS24/" title="https://lists.fedoraproject.org/archives/list/ ... at lists dot fedoraproject.org/thread/7X6B6BGFJ7SYZA243XOVPEJT7KVXRS24/">https://lists.fedoraproject.org/archives/list/ ... at lists dot fedor...</a>

Re: Can't push to batched an Fedora 30 update?

By Tomasz Torcz at 03/11/2019 - 16:55

On Mon, Mar 11, 2019 at 10:46:47AM -0400, Randy Barlow wrote:
Hmm, rebulding container on config change? Sounds fishy.
Have you tried putting production.ini into ConfigMap?

Re: Can't push to batched an Fedora 30 update?

By Randy Barlow at 03/12/2019 - 11:38

On Mon, 2019-03-11 at 21:55 +0100, Tomasz Torcz wrote:
It is in a configmap:

<a href="https://infrastructure.fedoraproject.org/cgit/ansible.git/tree/roles/bodhi2/base/templates/configmap.yml#n108" title="https://infrastructure.fedoraproject.org/cgit/ansible.git/tree/roles/bodhi2/base/templates/configmap.yml#n108">https://infrastructure.fedoraproject.org/cgit/ansible.git/tree/roles/bod...</a>

The reason I rebuilt the container is that I don't have ACLs to access
OpenShift directly and must interact with it via some Ansible
playbooks, and the only lever I can pull here that I'm aware of builds
a new container.

Re: Can't push to batched an Fedora 30 update?

By Kevin Fenzi at 03/12/2019 - 14:54

On 3/12/19 8:38 AM, Randy Barlow wrote:
We could add acls to allow application owners to do deploys I think.

Can you open a ticket on it and we can evaluate?

kevin

Re: Can't push to batched an Fedora 30 update?

By Alexander Ploumistos at 03/11/2019 - 04:25

On Mon, Mar 11, 2019 at 9:23 AM Richard W.M. Jones < ... at redhat dot com> wrote:
Beta Freeze:
<a href="https://fedoraproject.org/wiki/Milestone_freezes" title="https://fedoraproject.org/wiki/Milestone_freezes">https://fedoraproject.org/wiki/Milestone_freezes</a>