• rhel-system-roles-1.23.0-2.13.el9
    • None
    • rhel-sst-system-roles
    • 24
    • 26
    • 3
    • QE ack, Dev ack
    • False
    • Hide

      None

      Show
      None
    • Yes
    • Red Hat Enterprise Linux
    • None
    • Feature
    • Hide
      .New `rhc_insights.ansible_host` option in the `rhc` role to set Ansible hostnames

      You can now configure or update the Ansible hostname for the systems registered to Red Hat Insights by using the new `rhc_insights.ansible_host` parameter. When set, the parameter changes the `ansible_host` configuration in the `/etc/insights-client/insights-client.conf` file to your selected Ansible hostname. If your system is already connected with Red Hat Insights, this parameter will update the existing Ansible hostname.
      Show
      .New `rhc_insights.ansible_host` option in the `rhc` role to set Ansible hostnames You can now configure or update the Ansible hostname for the systems registered to Red Hat Insights by using the new `rhc_insights.ansible_host` parameter. When set, the parameter changes the `ansible_host` configuration in the `/etc/insights-client/insights-client.conf` file to your selected Ansible hostname. If your system is already connected with Red Hat Insights, this parameter will update the existing Ansible hostname.
    • Done
    • None

      Goal

      • As an administrator, I want to configure the hostname for systems used in Ansible playbooks

      Acceptance Criteria

      • If not set, the role does not change the configuration of the ansible_host configuration in /etc/insights-client/insights-client.conf
      • When set, the role changes the ansible_host configuration in /etc/insights-client/insights-client.conf
        • if a system needs to be connected to Insights, the specified ansible_host will be used
        • if a system is already connected to Insights, the specified ansible_host will replace the existing one

            [RHEL-16974] rhc: new rhc_insights.ansible_host parameter

            Errata Tool added a comment -

            Since the problem described in this issue should be resolved in a recent advisory, it has been closed.

            For information on the advisory (rhel-system-roles bug fix and enhancement update), 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/RHBA-2024:2227

            Errata Tool added a comment - Since the problem described in this issue should be resolved in a recent advisory, it has been closed. For information on the advisory (rhel-system-roles bug fix and enhancement update), 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/RHBA-2024:2227

            Jan Stavel added a comment -

            Hello, I have verified linux-system-roles from master branch.

            I've run a simple playbook to use rhc role to register  a system to insights service.

            I've set display_name and ansible_host variable too.

            Both variables appeared in console.redhat.com inventory.

            The playbook was inspired by tests/tests_insights_display_name.yml. I took just a part for registering and checking config file to verify the properties are set even in the config file.

            Jan Stavel added a comment - Hello, I have verified linux-system-roles from master branch. I've run a simple playbook to use rhc role to register  a system to insights service. I've set display_name and ansible_host variable too. Both variables appeared in console.redhat.com inventory. The playbook was inspired by tests/tests_insights_display_name.yml. I took just a part for registering and checking config file to verify the properties are set even in the config file.

            gitlab-bot added a comment -

            Richard Megginson mentioned this issue in a merge request of Red Hat / centos-stream / rpms / rhel-system-roles on branch c9s-1.23.0-2.13:

            system roles release 1.23.0-2.13

            gitlab-bot added a comment - Richard Megginson mentioned this issue in a merge request of Red Hat / centos-stream / rpms / rhel-system-roles on branch c9s-1.23.0-2.13 : system roles release 1.23.0-2.13

            gitlab-bot added a comment -

            Richard Megginson mentioned this issue in a merge request of Red Hat / centos-stream / rpms / rhel-system-roles on branch c9s-2:

            system roles update 1.23.0-2.9

            gitlab-bot added a comment - Richard Megginson mentioned this issue in a merge request of Red Hat / centos-stream / rpms / rhel-system-roles on branch c9s-2 : system roles update 1.23.0-2.9

            gitlab-bot added a comment -

            Richard Megginson mentioned this issue in a merge request of Red Hat / centos-stream / rpms / rhel-system-roles on branch c9s-20240126:

            system roles update 1.23.0-2.9

            gitlab-bot added a comment - Richard Megginson mentioned this issue in a merge request of Red Hat / centos-stream / rpms / rhel-system-roles on branch c9s-20240126 : system roles update 1.23.0-2.9

            sync bot added a comment -

            An attempt was made to sync this Jira Issue to quality engineering's test management system as a product requirement work item to be verified by Quality Engineering.

            The user defined as the QA Contact, 'rhel-cs-system-management-subsystem-qe', does not exist in the target test management system project, 'RHEL BaseOS'. For more information: QA Contact

            This allows Quality Engineering to provide traceability to the testing assets that cover verification of the new functionality. It allows stakeholders visibility into the test approach, test coverage and execution results. For more information about this sync utility please see: Product Requirements Synchronization Jira to Polarion.

            sync bot added a comment - An attempt was made to sync this Jira Issue to quality engineering's test management system as a product requirement work item to be verified by Quality Engineering. The user defined as the QA Contact, 'rhel-cs-system-management-subsystem-qe', does not exist in the target test management system project, 'RHEL BaseOS'. For more information: QA Contact This allows Quality Engineering to provide traceability to the testing assets that cover verification of the new functionality. It allows stakeholders visibility into the test approach, test coverage and execution results. For more information about this sync utility please see: Product Requirements Synchronization Jira to Polarion .

            djez@redhat.com you granted QE ack to the 8.10 clone https://issues.redhat.com/browse/RHEL-16975 - can you please grant QE ack to this issue?

            Richard Megginson added a comment - djez@redhat.com you granted QE ack to the 8.10 clone https://issues.redhat.com/browse/RHEL-16975 - can you please grant QE ack to this issue?

            sync bot added a comment -

            An attempt was made to sync this Jira Issue to quality engineering's test management system as a product requirement work item to be verified by Quality Engineering.

            The user defined as the QA Contact, 'rhel-cs-system-management-subsystem-qe', does not exist in the target test management system project, 'RHEL BaseOS'. For more information: QA Contact

            This allows Quality Engineering to provide traceability to the testing assets that cover verification of the new functionality. It allows stakeholders visibility into the test approach, test coverage and execution results. For more information about this sync utility please see: Product Requirements Synchronization Jira to Polarion.

            sync bot added a comment - An attempt was made to sync this Jira Issue to quality engineering's test management system as a product requirement work item to be verified by Quality Engineering. The user defined as the QA Contact, 'rhel-cs-system-management-subsystem-qe', does not exist in the target test management system project, 'RHEL BaseOS'. For more information: QA Contact This allows Quality Engineering to provide traceability to the testing assets that cover verification of the new functionality. It allows stakeholders visibility into the test approach, test coverage and execution results. For more information about this sync utility please see: Product Requirements Synchronization Jira to Polarion .

            djez@redhat.com rhn-support-jharuda - ptoscano@redhat.com who else should be assigned from rhc QE? requesting qa_ack and Preliminary Testing - the role has tests_insights_ansible_host.yml for this feature

            A yum repository for the scratch build of rhel-system-roles-1.23.0-2.7.1.el9 (task 58223670) is available at:

            https://brew-task-repos.engineering.redhat.com/repos/scratch/rmeggins/rhel-system-roles/1.23.0/2.7.1.el9/

            You can install the rpms locally by putting this .repo file in your /etc/yum.repos.d/ directory:

            https://brew-task-repos.engineering.redhat.com/repos/scratch/rmeggins/rhel-system-roles/1.23.0/2.7.1.el9/rhel-system-roles-1.23.0-2.7.1.el9-scratch.repo

            It is necessary to have internal Red Hat CA certificates installed on the system, if
            you want to use yum repository. You can install required certificates from:

            The full list of repos is:
            https://brew-task-repos.engineering.redhat.com/repos/scratch/rmeggins/rhel-system-roles/1.23.0/2.7.1.el9/noarch/

            Richard Megginson added a comment - djez@redhat.com rhn-support-jharuda - ptoscano@redhat.com who else should be assigned from rhc QE? requesting qa_ack and Preliminary Testing - the role has tests_insights_ansible_host.yml for this feature A yum repository for the scratch build of rhel-system-roles-1.23.0-2.7.1.el9 (task 58223670) is available at: https://brew-task-repos.engineering.redhat.com/repos/scratch/rmeggins/rhel-system-roles/1.23.0/2.7.1.el9/ You can install the rpms locally by putting this .repo file in your /etc/yum.repos.d/ directory: https://brew-task-repos.engineering.redhat.com/repos/scratch/rmeggins/rhel-system-roles/1.23.0/2.7.1.el9/rhel-system-roles-1.23.0-2.7.1.el9-scratch.repo It is necessary to have internal Red Hat CA certificates installed on the system, if you want to use yum repository. You can install required certificates from: http://hdn.corp.redhat.com/rhel7-csb-stage/repoview/redhat-internal-cert-install.html (rpm) https://certs.corp.redhat.com/ (cert files) The full list of repos is: https://brew-task-repos.engineering.redhat.com/repos/scratch/rmeggins/rhel-system-roles/1.23.0/2.7.1.el9/noarch/

              rmeggins@redhat.com Richard Megginson
              ptoscano@redhat.com Pino Toscano
              Jason Jerome Jason Jerome
              Jakub Haruda Jakub Haruda
              Sagar Dubewar Sagar Dubewar
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: