Issue #8209: New container/fedora-toolbox builds not getting pushed out to "stable" - releng

releng

#8209 New container/fedora-toolbox builds not getting pushed out to "stable"

Closed: Fixed 5 years ago by rishi. Opened 5 years ago by rishi.

Describe the issue

See:
https://bodhi.fedoraproject.org/updates/FEDORA-CONTAINER-2019-244fc7be89
https://bodhi.fedoraproject.org/updates/FEDORA-CONTAINER-2019-1b4cf28755

Those were submitted for a batched push to "stable" 6 days ago. The web UI also says that they were "submitted for stable by bodhi", not sure why. Did I narrowly miss the batch last Tuesday? Or is something wrong?

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

Before Fedora 28 goes EOL.

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

Once Fedora 29 goes EOL.

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

Those using Fedora 28 & 29 Silverblue systems for development will get a somewhat non-ideal user experience.

bowlofeggs commented 5 years ago

Is bodhi-push being run manually right now? It looks like the job has been commented out on the box:

[bowlofeggs@bodhi-backend01 ~][PROD]$ cat /etc/cron.d/bodhi-automated-pushes 
MAILTO=sysadmin-releng-members@fedoraproject.org
#00 00 * * * apache /usr/local/bin/bodhi-automated-pushes.py

Presumably this was done to avoid pushing Fedora 30 changes during the freeze. I would recommend instead to modify the cron job to push a set of releases (see bodhi-push --help, specifically the --releases flag). This way it can still be automated.

Note also that this change has not been made in Ansible. This means that if anyone runs the playbooks it will be re-enabled and will push Fedora 30, which may be risky.

mizdebsk commented 5 years ago

Note also that this change has not been made in Ansible. This means that if anyone runs the playbooks it will be re-enabled and will push Fedora 30, which may be risky.

I can see this change in ansible.git: https://infrastructure.fedoraproject.org/cgit/ansible.git/commit/?id=a3ec2ce