Bug 1102442
Summary: | [RFE] Allow Reserved systems to be returned from bkr client | ||
---|---|---|---|
Product: | [Retired] Beaker | Reporter: | Nick Coghlan <ncoghlan> |
Component: | general | Assignee: | matt jia <mjia> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | tools-bugs <tools-bugs> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | develop | CC: | aigao, asaha, azelinka, bpeck, dcallagh, jburke, mjia, pstudeni |
Target Milestone: | 20.2 | Keywords: | FutureFeature, Patch |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-07-15 03:37:26 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
Nick Coghlan
2014-05-29 01:10:20 UTC
Can we bump the priority to this? We would like to switch jenkins over to using this new reservesys mode and can't easily do it until we can extend and return early. Thanks Beaker 19.1 sprint planning is next week, it should be possible to take a look at this one. On Gerrit: http://gerrit.beaker-project.org/#/c/4265/ Verify steps: 1. create a job with <reservesys/> in a recipe. 2. Once the job status is "Reserved", use bkr system-release R:<recipe_id> or T:<recipetask_id> or system fqdn to return the system. I would suggest the verification step also include returning the system from the test system itself...since we have return2beaker.sh when using the "reservesys" task. (In reply to Amit Saha from comment #5) > I would suggest the verification step also include returning the system from > the test system itself...since we have return2beaker.sh when using the > "reservesys" task. Yeah, that's a fair point although there is no code change for this script. (In reply to Amit Saha from comment #5) > I would suggest the verification step also include returning the system from > the test system itself...since we have return2beaker.sh when using the > "reservesys" task. This RFE is for beaker-client so it's not expected that you will be able to use this command on the test systems -- unless you first install the client, and configure it with suitable authentication etc. We're not planning to offer any equivalent to return2beaker.sh for <reservesys/>, mainly because the entire point of <reservesys/> is that it doesn't change the state of the system at all. (In reply to Dan Callaghan from comment #7) > (In reply to Amit Saha from comment #5) > > I would suggest the verification step also include returning the system from > > the test system itself...since we have return2beaker.sh when using the > > "reservesys" task. > > This RFE is for beaker-client so it's not expected that you will be able to > use this command on the test systems -- unless you first install the client, > and configure it with suitable authentication etc. Right, but it is a potential use case, especially if someone is looking for a command line equivalent of "Release System" from the Web UI. This was actually included in the 20.2 bug fix release. |