Bug 1544498

Summary: Bootdisk provision method does not appear
Product: Red Hat Satellite Reporter: Lukas Zapletal <lzap>
Component: HammerAssignee: Tomas Strachota <tstrachota>
Status: CLOSED ERRATA QA Contact: Harshad More <hmore>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.3.0CC: akarsale, dhlavacd, fgarciad, gapatil, hmore, kgaikwad, mhulan, pcreech, rabajaj, rankumar, rvdwees, tstrachota
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
URL: http://projects.theforeman.org/issues/22552
Whiteboard:
Fixed In Version: tfm-rubygem-hammer_cli_foreman-0.11.0.6-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1572291 (view as bug list) Environment:
Last Closed: 2018-06-19 20:17:00 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 Lukas Zapletal 2018-02-12 16:27:11 UTC 
When Foreman is started with Bootdisk plugin which registers new provision method called "bootdisk" it does not show up in hammer host create --help command:

--provision-method METHOD                 Possible value(s): 'build', 'image'

The method string is properly registered in engine registry, but from here my hammer expertise ends, so filing an issue for that.

Versions:

6.3 beta and all 6.3 snaps.
Comment 2 Satellite Program 2018-02-12 19:10:26 UTC 
Upstream bug assigned to tstrachota
Comment 3 Satellite Program 2018-02-12 19:10:30 UTC 
Upstream bug assigned to tstrachota
Comment 4 Satellite Program 2018-02-13 17:10:29 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/22552 has been resolved.
Comment 8 Lukas Zapletal 2018-05-29 06:19:44 UTC 
*** Bug 1582468 has been marked as a duplicate of this bug. ***
Comment 11 errata-xmlrpc 2018-06-19 20:17:00 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:1950