Bug 1264716

Summary:	Port bkr group-modify to use new HTTP APIs
Product:	[Retired] Beaker	Reporter:	matt jia <mjia>
Component:	command line	Assignee:	matt jia <mjia>
Status:	CLOSED CURRENTRELEASE	QA Contact:	tools-bugs <tools-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	develop	CC:	dcallagh, dowang, mjia, rjoost
Target Milestone:	23.0	Keywords:	Patch
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-07-07 23:12:11 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description matt jia 2015-09-21 01:24:27 UTC

Bug 1251356 has introduced several new HTTP APIs for the group page. bkr group-modify now can be ported to use those APIs to take place of the old XMLRPC methods.

Comment 1 matt jia 2015-09-21 01:24:49 UTC

On Gerrit:

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

Comment 2 Dan Callaghan 2015-09-29 05:12:08 UTC

I was thinking we should actually roll this out of 22.0 and put it in for 23.0 instead. The reason is that users generally upgrade their bkr client shortly after we publish it to the repos, but the Beaker server is often upgraded days or weeks later. So it's quite common to be running a newer client than the server.

We have bug 1029287 which is about giving a better error message in case the server is too old to support an API which the client is trying to use. And we should implement that. But even if we do, people will still be forced to downgrade their client if they want it to actually work with the older server.

So at the same time, we are probably better off not using newly introduced APIs in the client until at least one release after they are added to the server, to decrease the likelihood of breakage because the server is too old for the client.

Comment 3 Dan Callaghan 2016-04-05 11:10:29 UTC

This bug fix is included in beaker-client-23.0-0.git.138.34eb2fc which is currently available for download here:

https://beaker-project.org/nightlies/develop/

Comment 5 Dan Callaghan 2016-07-07 23:12:11 UTC

Beaker 23.0 has been released.