#10832 I can't push FEDORA-2022-0feca8b2c9 to stable
Closed: Fixed 2 years ago by humaton. Opened 2 years ago by plautrba.

all gating test are waived, openqa issue is resolved, but it's still Testing and there's no Push to stable button

  • When do you need this? (YYYY/MM/DD)

2022/06/10

  • When is this no longer needed or useful? (YYYY/MM/DD)

  • If we cannot complete your request, what is the impact?

Fedora will not get latest SELinux Userspace release


This not being in stable now clashes with the Python 3.11 rebuilds. We need this in stable, could you please help?

Metadata Update from @phsmoura:
- Issue tagged with: medium-gain, medium-trouble, ops

2 years ago

I've tagged the builds from that update to f37-python. Thus, hopefully, this is now only blocking merging of the side tag (and that will not happen today).

I tried a number of things to get that update to stable, but nothing seemed to work. ;(

Perhaps @mattia has some idea?

When I edit it I can see bodhi saying it has 0 bugs to update... but thats it in the bodhi logs. It's like it just is ignoring it because it's requested stable and it didn't do it?

If it helped I could rebuild SELinux userpasce in a new sidetag.

@plautrba it would only help if you bump the release. Otherwise, bodhi will fail to create updates for existing NVR.

I have no idea why it was stuck, but after revoking the current stable request the update got processed right at the next approve_testing run.
It is now in stable.

I think the upstream cause was due to an erroneous workflow not considered by Bodhi:
https://github.com/fedora-infra/bodhi/issues/4566

Thanks, @mattia
The update is pushed and there is an upstream tracking issue. Closing.

Metadata Update from @humaton:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

2 years ago

Login to comment on this ticket.

Metadata
Boards 1
Ops Status: Backlog