Bug 2177730
| Summary: | [RFE] Ability to select Puppet configuration via UIs in integrated setups | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Zuzana Lena Ansorgova <zuansorg> | ||||
| Component: | Puppet | Assignee: | satellite6-bugs <satellite6-bugs> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | Satellite QE Team <sat-qe-bz-list> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | Unspecified | CC: | ahumbe, gtalreja, jwfrey, lstejska | ||||
| Target Milestone: | Unspecified | Keywords: | FutureFeature | ||||
| Target Release: | Unused | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Enhancement | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2024-05-13 10:04:06 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team. Thank you. Thank you for your interest in Red Hat Satellite. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this feel free to contact your Red Hat Account Team. Thank you. |
Created attachment 1950247 [details] Provisioning form with highlighted Puppet configuration fields Description of problem: During host Registration, Puppet integration between the host and Satellite can be configured using host parameters (puppet_server, puppet_ca_server, puppet_environment). This configures the Puppet agent on the host, but it doesn't configure the Puppet integration in Satellite. For example, Satellite does not know to which Puppet environment the host belongs. The user has to take additional steps to assign the environment after the host is registered before they can start assigning Puppet classes. It would be more user-friendly if Puppet was configured during Registration the same way as during the Provisioning process. The user should be able to select Puppet CA Capsules and the Puppet environment from a dropdown menu in the Registration form or using variables in CLI or API. This should configure both the Puppet agent on the host and the integration in Satellite. At the same time, these values can be inherited from a host group. The host parameters are meant to configure the Puppet agent for non-integrated setups. Version-Release number of selected component (if applicable): N/A How reproducible: always Steps to Reproduce: 1. Configure host parameters puppet_server and puppet_ca_server using the hostname of Puppet and Puppet CA Capsule as values, and puppet_environment 2. Register a host Actual results: Puppet agent is configured, but Satellite is not aware of the Puppet configuration on the host Expected results: Satellite should be aware of the Puppet configuration on the host, especially the Puppet environment, after Registration without the user having to take additional steps Additional info: Screenshot of the Provisioning form ("Create Host") attached for illustration. Let's add a similar set of fields to the "Register Host" form and corresponding variables to CLI and API. This is mainly about improving the UX workflow.