Bug 1333753 - [RFE] Check provisioning template if locked or not via either API or hammer CLI
Summary: [RFE] Check provisioning template if locked or not via either API or hammer CLI
Keywords:
Status: CLOSED DUPLICATE of bug 1328976
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Hammer
Version: 6.1.8
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: Unspecified
Assignee: Marek Hulan
QA Contact: Katello QA List
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-06 10:16 UTC by Kamudini Gazdikova
Modified: 2019-11-14 07:57 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-11 18:12:24 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Kamudini Gazdikova 2016-05-06 10:16:23 UTC
Description of problem:
Check  provisioning template if locked or not via either API or hammer CLI


Version-Release number of selected component (if applicable):
Red Hat Satellite v.6.1.8


Issue: 

Request to add feature for hammer command line to check whether a provision template is locked or not.

Currently hammer template does not print if the template is locked or not.

 hammer template info --id 99
Id:                99
Name:              Boot disk iPXE - generic host
Type:              Bootdisk
Operating systems: 

Locations:         
    Default Location
Organizations:     
    Default Organization
    tesorg2
    test-org

Comment 1 Marek Hulan 2016-05-06 10:22:21 UTC
It's already possible to see via API but Hammer is missing the output definition for info command.

Comment 2 Marek Hulan 2016-05-06 10:23:01 UTC
Created redmine issue http://projects.theforeman.org/issues/14943 from this bug

Comment 3 Bryan Kearney 2016-05-06 14:19:27 UTC
Moving to POST since upstream bug http://projects.theforeman.org/issues/14943 has been closed

Comment 4 Stephen Benjamin 2016-05-11 18:12:24 UTC
1328976 is already 3-ACK'd

*** This bug has been marked as a duplicate of bug 1328976 ***


Note You need to log in before you can comment on or make changes to this bug.