Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionVaratharaja Perumal G
2019-12-08 16:38:34 UTC
Description of problem:
Currently katello agent will be installed and configured as part of provisioning workflow but customer want to configure goferless setup. So we should be able to disable/enable katello agent configuration while provisioning host through Satellite 6.
Version-Release number of selected component (if applicable):
Red Hat Satellite 6.6
How reproducible:
Steps to Reproduce:
1. Provision a host with default template.
2. It will provision the new host with katello-agent.
Actual results:
- Newly provisioned hosts have katello-agent configured.
Expected results:
- Customer should be able to disable the katello-agent during the initial configuration.
Additional info:
Code need change:-
Template: redhat_register
kt_activation_keys should be modified as below to customize the configuration using host parameters.
~~~
redhat_install_agent = true
redhat_install_host_tools = true
redhat_install_host_tracer_tools = false
~~~
~~~
redhat_install_agent = host_param_true?('redhat_install_agent')
redhat_install_host_tools = host_param_true?('redhat_install_host_tools')
redhat_install_host_tracer_tools = host_param_true?('redhat_install_host_tracer_tools')
~~~
This is already possible at least with Satellite 6.8, the parameters are
redhat_install_agent
redhat_install_host_tools
redhat_install_host_tracer_tools
Description of problem: Currently katello agent will be installed and configured as part of provisioning workflow but customer want to configure goferless setup. So we should be able to disable/enable katello agent configuration while provisioning host through Satellite 6. Version-Release number of selected component (if applicable): Red Hat Satellite 6.6 How reproducible: Steps to Reproduce: 1. Provision a host with default template. 2. It will provision the new host with katello-agent. Actual results: - Newly provisioned hosts have katello-agent configured. Expected results: - Customer should be able to disable the katello-agent during the initial configuration. Additional info: Code need change:- Template: redhat_register kt_activation_keys should be modified as below to customize the configuration using host parameters. ~~~ redhat_install_agent = true redhat_install_host_tools = true redhat_install_host_tracer_tools = false ~~~ ~~~ redhat_install_agent = host_param_true?('redhat_install_agent') redhat_install_host_tools = host_param_true?('redhat_install_host_tools') redhat_install_host_tracer_tools = host_param_true?('redhat_install_host_tracer_tools') ~~~