Pushing updates SOP

Description

Fedora updates for released releases are typically pushed once a day. This SOP covers the steps involved.

Action

Login to a machine that is configured for sigul client support and has the bodhi client installed. If you have not configured your workstation, you can use:

• For EPEL: relepel01
• For Fedora: releng04

Decide what releases you're going to push.

Don't mix types
Please do not push Fedora and EPEL in the same push. Also, please do not push updates for a branched fedora pre-release at the same time as updates for released Fedora.

Get a list of packages to push

$ bodhi -P --push-release F18 --push-release F19 

Blank list?
If the list is blank, that means the prior push failed, and manual intervention may be required. See 'Common Issues' below.

WAIT!
Do NOT press "Yes" yet. Simply view the list and say 'n'.

List the releases above you wish to push from: F18, F19, F20, EL-5, EL-6.

You can also specify '--push-request=testing' to limit pushes. Valid types are 'testing', 'stable', and 'security'.

The list of updates should be in your home directory named 'Stable-$Branch' or 'Testing-$Branch' for each of the Branches you wished to push.

Sign the packages.

• Sign builds using scripts/sigulsign_unsigned.py from releng git repo

$ sigulsign_unsigned.py -vv --write-all fedora-19 $(cat Stable-F19 Testing-F19)

(Make sure you sign each release with the right key... ie, 'fedora-19' key with F19 packages, or 'epel-5' with EL-5 packages)

Run this process from screen
It is strongly suggested that the above procedure be run from screen. Doing so requires a host configured as sigul client. See the sigul client SOP http://fedoraproject.org/wiki/Create_release_signing_key#Sigul

Repeat gathering updates and signing steps

After gathering the list of updates and signing them, repeat the process until there are no new updates to be signed. You want to do this because as you are signing updates, maintainers are submitting new ones. There is a window while you are signing that a new update will be added and if you just push then, the push will fail with an unsigned package.

Perform the bodhi push

Re-run the earlier bodhi command from step 2 and say 'y' to push.

Verification

1. Tail the bodhi server log to watch progress on releng04 or relepel01.

$ tail -f /var/log/bodhi/server.log

2. Wait for the bodhi masher report (sent to bodhi-adminmember@fp.o) for success/failure or errors in the logs. Alternatively, wait for the update reports to be sent to the EPEL or test lists.

Consider Before Running

Pushes often fall over due to tagging issues or unsigned packages. Be prepared to work through the failures and restart pushes from time to time

$ bodhi -P --resume-push

Common issues / problems with pushes

• When the push fails due to new unsigned packages that were added after you started the process. re-run step 4a or 4b with just the package names that need to be signed, then resume.

• When the push fails due to an old package that has no signature, run: koji write-signed-rpm <gpgkeyid> <n-v-r> and resume.

• When the push fails due to a package moving from testing to stable and leaving an old version of the same package in testing: koji untag-pkg <tag> <n-v-r> to untag the package and resume. You may need to add --force.

• When the push fails due to a package not being tagged with updates-testing when being moved stable: koji tag-pkg dist-<tag>-updates-testing <n-v-r>

• When the push fails and you see in the server.log "Identity shutting down", bodhi has quit for some reason. Do "sudo service httpd restart" and resume the push.

• When signing fails, you may need to ask that the sigul bridge or server be restarted.

• When an update was deleted from bodhi, it may still be in the updates-testing tag. You may need to: koji untag-pkg <tag> <n-v-r> to untag the package and resume. You may need to add --force.

Other issues should be addressed by releng or bodhi developers in #fedora-admin.