Dieser Inhalt ist in der von Ihnen ausgewählten Sprache nicht verfügbar.
Chapter 3. Bug fixes
This part describes bugs fixed in Red Hat Satellite 6.15 that have a significant impact on users.
Concurrency level setting
Previously, the Concurrency level setting used in remote execution job scheduling did not always function properly. This could lead to the jobs being frozen until the service restart. With this release, this issue is now fixed and the Concurrency level setting works as intended.
Jira:SAT-19794
Updating host facts now does not trigger the host_updated event
Previously, updating host facts would trigger the host_updated event multiple times. This caused the subscribed webhooks to fire more than once on a single update of the host facts. With this release, updating the host facts does not trigger the host_updated event. If you want to be notified when host facts are updated, subscribe your webhooks to the new host_facts_updated event. This new event triggers the webhook only once with each update of the host facts. The host_updated event is still triggered if a user manually updates a host.
Jira:SAT-20746
You can now access full details from webhook when removing a host
Previously, only basic information about the host was available to the webhook template when you deleted a host. With this release, when you delete a host, the webhook template can access the full host details.
Jira:SAT-20745
Registration exit code reflects registration failure
Previously, the registration command returned the 0 exit code even when host registration failed. With this release, the registration command returns 0 only when it succeeds and non-zero codes otherwise.
Non-admin users can override Ansible variables
Previously, Satellite users other than the System Administrator could not override Ansible variables even when they were assigned the Ansible Roles Manager user role. With this release, permissions have been corrected and non-admin users can override Ansible variables.
Generate host registration commands by using 0 as unlimited for JWT expiration
Previously, it was not clear what value Hammer and API accept for generation of the host registration command with an unlimited authorization token. The accepted values are as follows:
- 0 means unlimited
- A value between 0 and 999999 is expiration in hours, 4 hours by default
- Other values are not accepted.
With this release, the unlimited value has been clarified in the Hammer help and API reference.
