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.
Bug 1667428 - Unable to change settings when hammer defaults are defined
Summary: Unable to change settings when hammer defaults are defined
Keywords:
Status: CLOSED DUPLICATE of bug 1649011
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Hammer
Version: 6.4
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Sachin Ghai
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-01-18 13:11 UTC by Steffen Froemer
Modified: 2019-01-21 21:52 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-21 21:52:19 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Steffen Froemer 2019-01-18 13:11:49 UTC
Description of problem:
Trying to change satellite settings using hammer, when a default parameter is defined, failing with error

Association not found for organization

Version-Release number of selected component (if applicable):
tfm-rubygem-hammer_cli-0.13.1.1-1.el7sat.noarch

How reproducible:
alwyas

Steps to Reproduce:
1. hammer defaults add --param-name organization --param-value "DEFAULT_ORGANIZATION"                                                                                                                                                   
2. hammer settings set --name 'append_domain_name_for_hosts' --value 'true'
3.


Actual results:
Could not update the setting:
  Association not found for organization


Expected results:
the settings should be changed

Additional info:

[root@sat6-1 ~]# hammer defaults add --param-name organization --param-value "CRAZY LAB"                                                                                                                                                   
Added organization default-option with value CRAZY LAB.

[root@sat6-1 ~]# hammer defaults list
-------------|----------
PARAMETER    | VALUE
-------------|----------
organization | CRAZY LAB
-------------|----------

[root@sat6-1 ~]# hammer settings set --name 'append_domain_name_for_hosts' --value 'true'
Could not update the setting:
  Association not found for organization

[root@sat6-1 ~]# hammer defaults delete --param-name organization
organization was deleted successfully.

[root@sat6-1 ~]# hammer defaults list
----------|------
PARAMETER | VALUE
----------|------

[root@sat6-1 ~]# hammer settings set --name 'append_domain_name_for_hosts' --value 'true'
Setting [append_domain_name_for_hosts] updated to [true].
[root@sat6-1 ~]#


Also listing settings is not possible, when defaults are set

[root@sat6-1 ~]# hammer settings list
Association not found for organization

Comment 3 Brad Buckingham 2019-01-21 21:52:19 UTC
Thanks for the bugzilla.  This appears to be a duplicate of bug 1649011; therefore, closing this one.

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


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