Retagging a koji build as f17-updates-candidate?

[Carlos O'Donell]

Devs,

While pushing out a CVE fix for glibc I received a server error from bodhi.

~~~
[carlos at koi glibc]$ fedpkg build
Building glibc-2.15-59.fc17 for f17-candidate
Created task: 5143544
Task info: http://koji.fedoraproject.org/koji/taskinfo?taskID=5143544
Watching tasks (this may be safely interrupted)...
5143544 build (f17-candidate, /glibc:e3b31b75191f99494a419b5d3bb36934fa6a0a66): open (buildvm-16.phx2.fedoraproject.org)
  5143545 buildSRPMFromSCM (/glibc:e3b31b75191f99494a419b5d3bb36934fa6a0a66): free
  5143545 buildSRPMFromSCM (/glibc:e3b31b75191f99494a419b5d3bb36934fa6a0a66): free -> open (buildvm-26.phx2.fedoraproject.org)
  5143545 buildSRPMFromSCM (/glibc:e3b31b75191f99494a419b5d3bb36934fa6a0a66): open (buildvm-26.phx2.fedoraproject.org) -> closed
  0 free  1 open  1 done  0 failed
  5143566 buildArch (glibc-2.15-59.fc17.src.rpm, i686): open (buildvm-12.phx2.fedoraproject.org)
  5143565 buildArch (glibc-2.15-59.fc17.src.rpm, x86_64): open (buildvm-26.phx2.fedoraproject.org)
  5143565 buildArch (glibc-2.15-59.fc17.src.rpm, x86_64): open (buildvm-26.phx2.fedoraproject.org) -> closed
  0 free  2 open  2 done  0 failed
  5143566 buildArch (glibc-2.15-59.fc17.src.rpm, i686): open (buildvm-12.phx2.fedoraproject.org) -> closed
  0 free  1 open  3 done  0 failed
  5143827 tagBuild (noarch): free
  5143827 tagBuild (noarch): free -> closed
  0 free  1 open  4 done  0 failed
5143544 build (f17-candidate, /glibc:e3b31b75191f99494a419b5d3bb36934fa6a0a66): open (buildvm-16.phx2.fedoraproject.org) -> closed
  0 free  0 open  5 done  0 failed

5143544 build (f17-candidate, /glibc:e3b31b75191f99494a419b5d3bb36934fa6a0a66) completed successfully
[carlos at koi glibc]$ fedpkg update
Creating a new update for  glibc-2.15-59.fc17 
Password for codonell: 
Creating a new update for  glibc-2.15-59.fc17 
ServerError(https://admin.fedoraproject.org/updates/save, 500, Internal Server Error)
Traceback (most recent call last):
  File "/usr/bin/bodhi", line 217, in main
    data = bodhi.save(**update_args)
  File "/usr/lib/python2.7/site-packages/fedora/client/bodhi.py", line 111, in save
    'bugs': bugs,
  File "/usr/lib/python2.7/site-packages/fedora/client/baseclient.py", line 344, in send_request
    auth_params=auth_params, retries=retries)
  File "/usr/lib/python2.7/site-packages/fedora/client/proxyclient.py", line 376, in send_request
    raise ServerError(url, http_status, msg)
ServerError: ServerError(https://admin.fedoraproject.org/updates/save, 500, Internal Server Error)
Could not generate update request: Command 'bodhi --new --release f17 --file bodhi.template glibc-2.15-59.fc17 --username codonell' returned non-zero exit status 255
~~~

For good measure I went into bodhi, deleted the update, and tried to issue it again.

However, now I get:
~~~
[carlos at koi glibc]$ fedpkg update
Creating a new update for  glibc-2.15-59.fc17 
Password for codonell: 
Creating a new update for  glibc-2.15-59.fc17 
glibc-2.15-59.fc17 not tagged as an update candidate
~~~
Which makes sense because it seems that bodhi has removed the f17-updates-candidate tag from the koji build.

I see the following email in my inbox:
~~~
Package: glibc
NVR: glibc-2.15-59.fc17
User: bodhi
Status: complete
Tag Operation: untagged
>From Tag: f17-updates-candidate

glibc-2.15-59.fc17 successfully untagged from f17-updates-candidate by bodhi
~~~

What do I do next?

How do I get the koji build tagged again so I can use it for a bodhi update?

Cheers,
Carlos.