Can't push to batched an Fedora 30 update?

[Richard W.M. Jones]

https://bodhi.fedoraproject.org/updates/FEDORA-2019-fd699ee2ea

"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.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
libguestfs lets you edit virtual machines.  Supports shell scripting,
bindings from many languages.  http://libguestfs.org

[Alexander Ploumistos]

On Mon, Mar 11, 2019 at 9:23 AM Richard W.M. Jones <rjones(a)redhat.com&gt; wrote:
>  https://bodhi.fedoraproject.org/updates/FEDORA-2019-fd699ee2ea
>
>  "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."? 
Beta Freeze:
https://fedoraproject.org/wiki/Milestone_freezes

[Randy Barlow]

On Mon, 2019-03-11 at 08:22 +0000, Richard W.M. Jones wrote:
>  https://bodhi.fedoraproject.org/updates/FEDORA-2019-fd699ee2ea
>  
>  "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 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.

>  I guess this is something to do with "Failed to talk to
> Greenwave."? 
This is a separate issue:

https://pagure.io/greenwave/issue/388

[Randy Barlow]

On Mon, 2019-03-11 at 10:35 -0400, Randy Barlow wrote:
>  On Mon, 2019-03-11 at 08:22 +0000, Richard W.M. Jones wrote:
>  > https://bodhi.fedoraproject.org/updates/FEDORA-2019-fd699ee2ea
>  > 
>  > "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 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. 
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:

https://lists.fedoraproject.org/archives/list/[e-mail]...

[Tomasz Torcz]

On Mon, Mar 11, 2019 at 10:46:47AM -0400, Randy Barlow wrote:
>  On Mon, 2019-03-11 at 10:35 -0400, Randy Barlow wrote:
>  > On Mon, 2019-03-11 at 08:22 +0000, Richard W.M. Jones wrote:
>  > > https://bodhi.fedoraproject.org/updates/FEDORA-2019-fd699ee2ea
>  > > 
>  > > "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 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.
>  
>  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:
>  
>
> https://lists.fedoraproject.org/archives/list/[e-mail]...
  Hmm, rebulding container on config change? Sounds fishy.
Have you tried putting production.ini into ConfigMap?

-- 
Tomasz Torcz               "Never underestimate the bandwidth of a station
xmpp: zdzichubg(a)chrome.pl    wagon filled with backup tapes." -- Jim Gray

[Randy Barlow]

On Mon, 2019-03-11 at 21:55 +0100, Tomasz Torcz wrote:
>    Hmm, rebulding container on config change? Sounds fishy.
>  Have you tried putting production.ini into ConfigMap? 
It is in a configmap:

https://infrastructure.fedoraproject.org/cgit/ansible.git/tree/roles/bodh...

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.

[Kevin Fenzi]

On 3/12/19 8:38 AM, Randy Barlow wrote:
>  On Mon, 2019-03-11 at 21:55 +0100, Tomasz Torcz wrote:
> >   Hmm, rebulding container on config change? Sounds fishy.
> > Have you tried putting production.ini into ConfigMap?
>  
>  It is in a configmap:
>  
>
> https://infrastructure.fedoraproject.org/cgit/ansible.git/tree/roles/bodh...
>  
>  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. 
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

[Randy Barlow]

This should be resolved now. Sorry for the issues!