Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Hammer cannot associate a provisioning template to an Operating System, unless its cloned. But the Web UI can
Version-Release number of selected component (if applicable):
How reproducible:
100%
Steps to Reproduce:
1. Choose a template such as "Satellite Kickstart Default"
2. Use Hammer to associate it to Operating System ID 1
3.
Actual results:
# hammer template update --id 33 --operatingsystem-ids 1
Could not update the config template:
This template is locked. Please clone it to a new template to customize.
Expected results:
Template is associated with the Operating System
Additional info:
This works fine from the Web UI
Comment 1RHEL Program Management
2014-09-20 14:33:01 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
Seems it is possible from the **os**
# hammer os add-config-template --id 1 --config-template-id 33
# hammer os info --id 1
Id: 1
Full name: RedHat 6.5
Release name:
Family: Redhat
Name: RedHat
Major version: 6
Minor version: 5
Partition tables:
Default templates:
Architectures:
x86_64
Installation media:
Example_Org/Library/Red_Hat_6_Server_Kickstart_x86_64_6_5
Templates:
Satellite Kickstart Default (provision)
Parameters:
This is an older bug which has been reported upstream. We are not going to track this bug downstream. When the upstream issue is resolved, the next build will contain the fix. Thank you.
This already works upstream and also works in Satellite 6.2
Verified with
tfm-rubygem-hammer_cli_foreman-0.5.1.10-1.el7sat.noarch
tfm-rubygem-hammer_cli-0.5.1.13-2.el7sat.noarch