Actions
Bug #7563
closedHammer cannot associate a locked provisioning template to an Operating System, unless its cloned. But the Web UI can
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1144764
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.
- 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
Updated by Dominic Cleal about 10 years ago
- Category set to Templates
- Assignee deleted (
Bryan Kearney)
Updated by Dominic Cleal about 10 years ago
- Related to Feature #3103: Read only provisioning/config templates for plugins added
Updated by Marek Hulán over 7 years ago
- Status changed from New to Resolved
- Target version set to 1.12.1
I can no longer reproduce, this works just fine
$ hammer template info --id 231 Id: 231 Name: adele Type: provision Locked: yes Operating systems: Organizations: Ares $ hammer template update --operatingsystems 'Centos 7.2.1511' --id 231 Config template updated $ hammer template info --id 231 Id: 231 Name: adele Type: provision Locked: yes Operating systems: CentOS Linux 7.2.1511 Organizations: Ares
I verified the same with organizations. Tested with hammer-cli-foreman 0.9.0 and hammer-cli 0.9.0
Actions