Bug 812831

user name problem is connected with bug:
https://bugzilla.redhat.com/show_bug.cgi?id=809076
We tried more possibilities of usernames:

baseos-qe
daemons-test-review
daemons-test-review

   regards
   Honza

Reason why we need access web interface with that user is, that we need to do some ACK/NACK for recipesets. And there is needed to be logged is under mentioned user

so solutins are two:
 first is to implement bug in previous comment and allow users what are CCed also ACK/NACK, cancel jobs

 second is implement "bkr recipe-ack/recipe-nack" as command line tool where the user is allowed.
Doinf Cancel is allowed from command line, only ack/nack is not implemented

for me the best is to implement both functions

   Regards
   Honza

We can add the command line options to ack/nack.

Hi,
okay. it will be enought at least for now.

Command line tool should also know how to change retention tag for job, it is also important for us.

   Thanks
   Honza

Sorry, I didn't read this carefully. I have only implemented the ack/nak via cmd line, not the retention tag. I've created a new BZ for the retention tag functionality,  821287.

Thanks for the fix but I can't test it as there are no distros available on the stage server. Every job I try to schedule ends with "Failed to import job because of: u'No distro tree matches Recipe:..."

(In reply to comment #7)
> Thanks for the fix but I can't test it as there are no distros available on the
> stage server. Every job I try to schedule ends with "Failed to import job
> because of: u'No distro tree matches Recipe:..."

Sorry about that..  We are aware of the problem and should have it resolved some time Today.

I've updated to the newest beaker-client from beaker-stage repo:
beaker-client-0.8.2-8.el6eso.noarch

But it doesn't seem to support the recipeset nacking:
$ bkr help |grep -i nack
$

http://gerrit.beaker-project.org/#/c/1123/

I've tested the job-modify action and, except the already known issue with re-modifying response, it works well. 

Few minor issues I've noticed:

 * non-zero exit code for errors

 * job-modify should give better error message when called with unsupported parameter:
$ bkr job-modify -r wqeq J:16365
<Fault 1: "<class 'sqlalchemy.orm.exc.NoResultFound'>:No row was found for one()">
No jobs modified

 * I can pre-ack/nak a job/recipeSet before it's finished. Not sure if it's a feature or bug. But WebUI doesn't allow this.

>  * non-zero exit code for errors
I mean, *should be* non-zero, currently it isn't.

(In reply to comment #17)
> I've tested the job-modify action and, except the already known issue with
> re-modifying response, it works well. 
> 
> Few minor issues I've noticed:
> 
>  * non-zero exit code for errors
> 
>  * job-modify should give better error message when called with unsupported
> parameter:
> $ bkr job-modify -r wqeq J:16365
> <Fault 1: "<class 'sqlalchemy.orm.exc.NoResultFound'>:No row was found for
> one()">
> No jobs modified
> 

These have now been updated on stage.

>  * I can pre-ack/nak a job/recipeSet before it's finished. Not sure if it's
> a feature or bug. But WebUI doesn't allow this.

This should be perfectly harmless, but you're right, it is inconsistent with the WebUI.

Beaker 0.9.0 has been released.