Description of problem: In 6.3 snap6 UI, I see following two settings: 1. Hostname_facts 2. Hostname_prefix However, in CLI hammer same settings are named as: 1. discovery_hostname 2. discovery_prefix I think all settings names in hammer should be consistent w/ UI Version-Release number of selected component (if applicable): sat6.3 snap6 How reproducible: always Steps to Reproduce: 1. hammer settings list | grep discovery 2. 3. Actual results: mismatch in discovery settings names in UI and hammer Expected results: for consistency, name should be same at both places ( UI and CLI) Additional info:
I would prefer to have the fix in 6.3 only. This may create a usability issue as same settings are named differently at UI and CLI.
Upstream bug assigned to orabin
@Brad, I would like to stick w/ the bz.
After another look, I believe this should be fixed in hammer core.
Upstream bug assigned to apatel
Just setting the devel_triaged flag as we seem to be keeping the BZ and fix is in the works in upstream.
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/20360 has been resolved.
VERIFIED Version tested: Satellite 6.5 snap 7 CLI now provides the FULL NAME column which helps to find settings as per UI name. # hammer settings list | grep 'Hostname prefix' discovery_prefix | Hostname prefix | mac | The default prefix to use for the host name, must start with a letter # hammer settings list | grep 'Hostname facts' discovery_hostname | Hostname facts | discovery_bootif | List of facts to use for the hostname (separated by comma, first wins)
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-2019:1222