Closed bowlofeggs closed 7 years ago
Vit further comented:
I'd say there is several issues in here:
1) The server is not returning JSON where it is expected. 2) The error itself is weird:
<p class="lead">"rubygem-httparty-0.14.0-1.fc25" is not one of unpush, testing, revoke, obsolete, stable</p> <p class="lead">Invalid update id</p> <p class="lead">ACL validation mechanism was unable to determine ACLs.</p>
Trying the same withupdate ID "FEDORA-2016-e4fe08f108" fails similarly
3) There should be not tracebacks, no HTML output, but some clear error message appropriate for CLI.
I learned that the order of the arguments used in the bug report is backwards - you have to specify the update id and then the state you wish the update to be moved to. Thus instead of:
$ bodhi updates request revoke rubygem-httparty-0.14.0-1.fc25
it should be:
$ bodhi updates request rubygem-httparty-0.14.0-1.fc25 revoke
The server was sending a 404 since it could not find an update with id "revoke". However, the CLI should have made this clearer for the user when reporting the error so I will see what I can do about fixing the error reporting.
Vít Ondruch reported this issue: