update for bodhi 2.0
ClosedPublic

Authored by kparal on Aug 18 2015, 3:16 PM.

Details

Summary

This is upgradepath changes. It will also need accompanying libtaskotron changes.

Test Plan

I ran it manually against staging Bodhi 2.0, it seemed to work (a lot of updates were not found, because its data set is different I guess).

Diff Detail

Repository
rUPGR task-upgradepath
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.
kparal retitled this revision from to update for bodhi 2.0.Aug 18 2015, 3:16 PM
kparal updated this object.
kparal edited the test plan for this revision. (Show Details)
kparal added reviewers: tflink, jskladan, lbrabec.
tflink added a subscriber: lmacken.Aug 18 2015, 3:31 PM

Questions about the bodhi-related changes to libtaskotron - I thought we didn't need to worry about whether or not an update had an updateid/alias anymore

upgradepath.py
90–91

Is this needed anymore? I thought that bodhi12 was assigning an updateid (or alias?) to updates on creation instead of at push time. can we just ignore the title?

567

same question as above - do we need to have the title as a backup anymore?

kparal added inline comments.Aug 18 2015, 5:13 PM
upgradepath.py
90–91

It seems that updateid was renamed to alias, at least I haven't seen updateid anywhere.

If Luke confirms that alias exists for all update objects, then yes, we can get rid of falling back to title.

kparal planned changes to this revision.Aug 18 2015, 6:54 PM
kparal added inline comments.
upgradepath.py
90–91

Confirmed by Luke. I'll amend the patch.

kparal updated this revision to Diff 1331.Aug 18 2015, 7:38 PM
  • use Bodhi update aliases
kparal marked 4 inline comments as done.Aug 18 2015, 7:40 PM
tflink accepted this revision.Aug 18 2015, 8:29 PM
This revision is now accepted and ready to land.Aug 18 2015, 8:29 PM
This revision was automatically updated to reflect the committed changes.