DevHeads.net

Bodhi 4.0.0 deployed, one known issue so far

Greetings!

I have just deployed Bodhi 4.0.0 to production:

<a href="https://bodhi.fedoraproject.org/docs/user/release_notes.html" title="https://bodhi.fedoraproject.org/docs/user/release_notes.html">https://bodhi.fedoraproject.org/docs/user/release_notes.html</a>

One known issue has been found[0] so far: after creating an update,
your browser will be redirected to a URL that does not exist. The
update was created, however, and you should receive an e-mail with the
URL to it (and can also see it on your user page in Bodhi).

Let me know if you find any other problems!

[0] <a href="https://github.com/fedora-infra/bodhi/issues/3248" title="https://github.com/fedora-infra/bodhi/issues/3248">https://github.com/fedora-infra/bodhi/issues/3248</a>

Comments

Re: Bodhi 4.0.0 deployed, one known issue so far

By Orion Poplawski at 05/28/2019 - 22:22

On 5/28/19 11:04 AM, Randy Barlow wrote:
Perhaps this is the source of:

# /etc/cron.hourly/0yum-hourly.cron
Updateinfo file is not valid XML: <open file
'/var/cache/yum/x86_64/7/epel/92f2e15cad66d79ea1ad327e2af7af89d98e4d153d7a3e27ff41946f476af5b4-updateinfo.xml.zck',
mode 'rt' at 0x7fa11cc331e0>

<a href="https://pagure.io/releng/issue/8392" title="https://pagure.io/releng/issue/8392">https://pagure.io/releng/issue/8392</a>

?

Re: Bodhi 4.0.0 deployed, one known issue so far

By Randy Barlow at 05/28/2019 - 22:27

On Tue, 2019-05-28 at 20:22 -0600, Orion Poplawski wrote:
Yeah, that's a possibility since this version of Bodhi introduced
zchunked updateinfo files. Maybe jdieter can shed some light on it for
us in the ticket.

Re: Bodhi 4.0.0 deployed, one known issue so far

By Randy Barlow at 05/29/2019 - 11:39

On Tue, 2019-05-28 at 20:22 -0600, Orion Poplawski wrote:
I am working on a bodhi-4.0.1 release today to address this particular
issue.

Re: Bodhi 4.0.0 deployed, one known issue so far

By Fabio Valentini at 05/29/2019 - 11:51

On Wed, May 29, 2019 at 5:40 PM Randy Barlow
< ... at fedoraproject dot org> wrote:
If you're already working on fixing bugs - searching in the web
interface also seems to be broken.
Entries on an autocompleted result in the "package" section link to a
(usually non-existent) user page.

Fabio

Re: Bodhi 4.0.0 deployed, one known issue so far

By Randy Barlow at 05/29/2019 - 12:51

On Wed, 2019-05-29 at 17:51 +0200, Fabio Valentini wrote:
That's surprising, and sounds like this issue:

<a href="https://github.com/fedora-infra/bodhi/issues/3040" title="https://github.com/fedora-infra/bodhi/issues/3040">https://github.com/fedora-infra/bodhi/issues/3040</a>

However, when I try this myself in Firefox on production it does seem
to work as I expect. For example, if I search "kernel" and then click
or use the keyboard to navigate and hit enter on "kernel", I am taken
to this URL:

<a href="https://bodhi.fedoraproject.org/updates/?packages=kernel" title="https://bodhi.fedoraproject.org/updates/?packages=kernel">https://bodhi.fedoraproject.org/updates/?packages=kernel</a>

Can you describe in more detail what you are doing and seeing?

Re: Bodhi 4.0.0 deployed, one known issue so far

By Fabio Valentini at 05/29/2019 - 13:27

On Wed, May 29, 2019, 18:52 Randy Barlow < ... at fedoraproject dot org>
wrote:

Yep, that's exactly what happened.

However, after deleting the browser cache for the bodhi site and trying
again, it now works as expected. Thanks!

I guess there was some stale JavaScript in the cache that didn't get
reloaded.

Fabio

Re: Bodhi 4.0.0 deployed, one known issue so far

By Fabio Valentini at 05/29/2019 - 14:29

On Wed, May 29, 2019 at 7:27 PM Fabio Valentini < ... at gmail dot com> wrote:
I just noticed one other thing: fedora-easy-karma is now broken,
because the REST API doesn't return the "anonymous" field on comments
anymore, which the tool checks for.

Fabio

Re: Bodhi 4.0.0 deployed, one known issue so far

By Randy Barlow at 05/29/2019 - 14:48

On Wed, 2019-05-29 at 20:29 +0200, Fabio Valentini wrote:
See <a href="https://pagure.io/fesco/issue/2137" title="https://pagure.io/fesco/issue/2137">https://pagure.io/fesco/issue/2137</a>

Re: Bodhi 4.0.0 deployed, one known issue so far

By Dan =?utf-8?B?x... at 05/28/2019 - 17:41

Hi,

I just tried to submit an update via `fedpkg update` but got a failure
via the cli:
$ fedpkg update
Could not execute update: Could not generate update request: 'anonymous'
A copy of the filled in template is saved as bodhi.template.last

Nevertheless the update got submitted and is available on Bodhi (it's
this one:
<a href="https://bodhi.fedoraproject.org/updates/FEDORA-2019-16433c312e" title="https://bodhi.fedoraproject.org/updates/FEDORA-2019-16433c312e">https://bodhi.fedoraproject.org/updates/FEDORA-2019-16433c312e</a>).

Cheers,

Dan

Randy Barlow < ... at fedoraproject dot org> writes:

Re: Bodhi 4.0.0 deployed, one known issue so far

By Randy Barlow at 05/29/2019 - 11:38

On Tue, 2019-05-28 at 17:41 -0400, Dan Čermák wrote:
Hi Dan!

I presume you are using a Bodhi 2 or 3 client there? This is a known
compatibility issue between the Bodhi 3 client and the Bodhi 4 server:

<a href="https://bugzilla.redhat.com/show_bug.cgi?id=1714950" title="https://bugzilla.redhat.com/show_bug.cgi?id=1714950">https://bugzilla.redhat.com/show_bug.cgi?id=1714950</a>

There's a FESCo ticket where we are discussing what to do about it. I'm
kind of undecided between putting Bodhi 4 into Fedora 29+ (and maybe
even EPEL 7, which may be tricky due to dependencies) and making a
Bodhi 3.15 that can talk to Bodhi 4 server (downside is that this will
require more effort on my part, and I have a lot on my plate ☹). Feel
free to voice your opinions on the FESCo ticket!

Re: Bodhi 4.0.0 deployed, one known issue so far

By Josh Boyer at 05/29/2019 - 11:58

On Wed, May 29, 2019 at 11:39 AM Randy Barlow
< ... at fedoraproject dot org> wrote:
Could you make a container image based on F30 that can be run on
F29/EPEL 7/8? That offers users a way to use the new tool on the OS
of their choice and avoids you having to write new code or bring back
a bunch of dependencies to the Fedora release itself.

josh

Re: Bodhi 4.0.0 deployed, one known issue so far

By Randy Barlow at 05/29/2019 - 12:47

On Wed, 2019-05-29 at 11:58 -0400, Josh Boyer wrote:
Yeah anyone could easily do this (just a FROM line [note: it's in
Rawhide, not F30] and a RUN dnf install line), but there are also
dependencies on bodhi-client in EPEL 7 and F29/30 so it wouldn't fully
address the issue. Any end user who wants to work around it could do
this though, and I have also provided a Copr[0] that has the new Bodhi
client that you can use too.

I also considered modularity, but there's currently a stay on adding
new packages to the default stream since RPMs can't currently depend on
modules (and things do depend on Bodhi).

Miro and I have proposed on the FESCo ticket to create a bodhi3-client
package and upgrade F29/30 to Bodhi 4.

[0] <a href="https://copr.fedorainfracloud.org/coprs/bowlofeggs/bodhi" title="https://copr.fedorainfracloud.org/coprs/bowlofeggs/bodhi">https://copr.fedorainfracloud.org/coprs/bowlofeggs/bodhi</a>

Re: Bodhi 4.0.0 deployed, one known issue so far

By Bob Mauchin at 05/30/2019 - 10:13

On Wednesday, 29 May 2019 18:47:51 CEST Randy Barlow wrote:
I've installed Bodhi 4 from Rawhide but fedpkg doesn't seem to be compatible
with it yet:

Could not execute update: This system has bodhi v4, which is unsupported.

Re: Bodhi 4.0.0 deployed, one known issue so far

By Randy Barlow at 05/30/2019 - 11:37

On Thu, 2019-05-30 at 16:13 +0200, Robert-André Mauchin wrote:
<a href="https://pagure.io/fedpkg/issue/330" title="https://pagure.io/fedpkg/issue/330">https://pagure.io/fedpkg/issue/330</a>

Re: Bodhi 4.0.0 deployed, one known issue so far

By Petr Pisar at 05/29/2019 - 11:01

On 2019-05-28, Dan Čermák <dan.cermak@cgc-instruments.com> wrote:
-- Petr