From Fedora Project Wiki

(update to be a bit cleaner)
(more info)
Line 1: Line 1:
 
== Description ==
 
== Description ==
 
Fedora updates are typically pushed once a day. This SOP covers the steps involved.
 
Fedora updates are typically pushed once a day. This SOP covers the steps involved.
 +
 +
=== Coordinate ===
 +
 +
Releng has a rotation of who pushes updates when. Please coordinate and only push updates when you are expected to or have notified other releng folks you are doing so. See: https://apps.fedoraproject.org/calendar/release-engineering/ for the list or on irc you can run '.pushduty' in any channel with zodbot to see who is on duty this week.
  
 
=== Login to machine to sign updates ===
 
=== Login to machine to sign updates ===
  
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: bodhi-backend01.phx2.fedoraproject.org
+
Login to a machine that is configured for sigul client support and has the bodhi client installed. Currently, this machine  is: bodhi-backend01.phx2.fedoraproject.org
  
 
=== Decide what releases you're going to push. ===
 
=== Decide what releases you're going to push. ===
Line 11: Line 15:
  
 
* If there is no Freeze ongoing you can push all Fedora and EPEL releases at the same time if you wish.  
 
* If there is no Freeze ongoing you can push all Fedora and EPEL releases at the same time if you wish.  
 +
 +
* From time to time there may be urgent requests in some branches, you can only push those if requested. Note however that bodhi2 will automatically push branches with security updates before others.
  
 
=== Get a list of packages to push ===
 
=== Get a list of packages to push ===
Line 19: Line 25:
 
<enter your password+2factorauth, then your fas password>
 
<enter your password+2factorauth, then your fas password>
 
</pre>
 
</pre>
{{admon/warning|Blank list?| If the list is blank, that means the prior push failed, and manual intervention may be required. See 'Common Issues' below.}}
+
 
{{admon/warning|WAIT!| Do NOT press "Yes" yet. Simply view the list and say 'n'.}}
+
You can say 'n' to the push at this point if you wish to sign packages (see below). Or you can keep this request open in a window while you sign the packages, then come back and say y.  
  
 
List the releases above you wish to push from: 23 22 21 5 6 7, etc
 
List the releases above you wish to push from: 23 22 21 5 6 7, etc
  
You can also specify '--push-request=testing' to limit pushes. Valid types are 'testing' or 'stable'.
+
You can also specify '--request=testing' to limit pushes. Valid types are 'testing' or 'stable'.
  
 
The list of updates should be in the cache directory named 'Stable-$Branch' or 'Testing-$Branch' for each of the Branches you wished to push.
 
The list of updates should be in the cache directory named 'Stable-$Branch' or 'Testing-$Branch' for each of the Branches you wished to push.
 +
 +
During freezes you will need to do two steps: (If say, fedora 23 branched was frozen):
 +
 +
<pre>
 +
$ cd /var/cache/sigul
 +
$ sudo -u masher bodhi-push --releases 23 --request=testing --username <username>
 +
</pre>
 +
 +
Then
 +
 +
<pre>
 +
$ cd /var/cache/sigul
 +
$ sudo -u masher bodhi-push --releases '22 21 5 6 7' --username <username>
 +
</pre>
  
 
=== Sign the packages. ===  
 
=== Sign the packages. ===  

Revision as of 17:01, 23 August 2015

Description

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

Coordinate

Releng has a rotation of who pushes updates when. Please coordinate and only push updates when you are expected to or have notified other releng folks you are doing so. See: https://apps.fedoraproject.org/calendar/release-engineering/ for the list or on irc you can run '.pushduty' in any channel with zodbot to see who is on duty this week.

Login to machine to sign updates

Login to a machine that is configured for sigul client support and has the bodhi client installed. Currently, this machine is: bodhi-backend01.phx2.fedoraproject.org

Decide what releases you're going to push.

  • If there is a Freeze ongoing, you SHOULD NOT push all stable requests for a branched release, only specific blocker or freeze exception requests that QA will request in a releng ticket.
  • If there is no Freeze ongoing you can push all Fedora and EPEL releases at the same time if you wish.
  • From time to time there may be urgent requests in some branches, you can only push those if requested. Note however that bodhi2 will automatically push branches with security updates before others.

Get a list of packages to push

$ cd /var/cache/sigul
$ sudo -u masher bodhi-push --releases '23 22 21 5 6 7' --username <yourusername>
<enter your password+2factorauth, then your fas password>

You can say 'n' to the push at this point if you wish to sign packages (see below). Or you can keep this request open in a window while you sign the packages, then come back and say y.

List the releases above you wish to push from: 23 22 21 5 6 7, etc

You can also specify '--request=testing' to limit pushes. Valid types are 'testing' or 'stable'.

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

During freezes you will need to do two steps: (If say, fedora 23 branched was frozen):

$ cd /var/cache/sigul
$ sudo -u masher bodhi-push --releases 23 --request=testing --username <username>

Then

$ cd /var/cache/sigul
$ sudo -u masher bodhi-push --releases '22 21 5 6 7' --username <username>

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)

Here is another example, inside a loop:

for i in 20 19 18 ; do NSS_HASH_ALG_SUPPORT=+md5 sigulsign_unsigned.py fedora-$i -v --write-all $(cat {Stable,Testing}-F${i}) ; done
  • You may need to add 'NSS_HASH_ALG_SUPPORT=+MD5' before sigulsign_unsigned (or add it to your ~/.bashrc).

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. Monitor the sysemd journal

$ journalctl -u fedmsg-hub -l -f

2. Watch for fedmsgs through the process. It will indicate what releases it's working on, etc.

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

$ sudo -u masher bodhi-push --resume

Bodhi will ask you which push(es) you want to resume.

Consider testing if the mash lock file exists. May indicate a previous push has not completed, or somehow failed:

$ ls /mnt/koji/mash/updates/MASHING-*

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