+++ This bug was initially created as a clone of Bug #1367032 +++ Description of problem: Before Update: hammer -v -u admin -p changeme smart-variable info --id="100" Id: 100 Name: YJIQOcdDFQ1 Default Value: Type: string Puppet class: ntp Description: Hidden Value?: false Validator: Type: Rule: Override values: Merge overrides: no Merge default value: no Avoid duplicates: no Order: fqdn, hostgroup, os, domain Values: Created at: 2016/08/15 10:36:30 Updated at: 2016/08/15 10:42:18 Updating entity: hammer -v -u admin -p changeme --output=csv smart-variable update --id="100" --new-name="XO4txkfDEUD" --puppet-class="ntp" Message,Id Smart variable [YJIQOcdDFQ1] updated,100 Nothing happened and entity has old name: hammer -v -u admin -p changeme smart-variable info --id="100" Id: 100 Name: YJIQOcdDFQ1 Default Value: Type: string Puppet class: ntp Description: Hidden Value?: false Validator: Type: Rule: Override values: Merge overrides: no Merge default value: no Avoid duplicates: no Order: fqdn, hostgroup, os, domain Values: Created at: 2016/08/15 10:36:30 Updated at: 2016/08/15 10:42:36 Version-Release number of selected component (if applicable): Satellite 6.2.0-6.2.1 SNAP1.2 How reproducible: Always Steps to Reproduce: 1. Create smart variable for any puppet class 2. Try to update it with new value for its name 3. Actual results: Entity is not updated Expected results: Entity updated properly Additional info:
Quickly check on 6.2.7 and functionality works in a wrong way, but that is expected as fix is not there
Upstream bug assigned to sshtein
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/16119 has been resolved.
Created attachment 1311158 [details] Updating smart variable name via hammer Verified. Sat-6.3.0 snap 10
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/RHSA-2018:0336