Bug 2006231
Summary: | Replace `# {{ ansible_managed }}` with `{{ ansible_managed | comment }}` | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Sergei Petrosian <spetrosi> |
Component: | rhel-system-roles | Assignee: | Sergei Petrosian <spetrosi> |
Status: | CLOSED ERRATA | QA Contact: | David Jež <djez> |
Severity: | unspecified | Docs Contact: | Eliane Ramos Pereira <elpereir> |
Priority: | unspecified | ||
Version: | 8.5 | CC: | agk, djez, gfialova, jharuda, nhosoi, rhel-cs-system-management-subsystem-qe, rmeggins, spetrosi |
Target Milestone: | rc | Keywords: | Triaged |
Target Release: | 8.6 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | rhel-system-roles-1.11.0-1.el8 | Doc Type: | Bug Fix |
Doc Text: |
.RHEL System Roles now handle multi-line `ansible_managed` comments in generated files
Previously, some of the RHEL System Roles were using `# {{ ansible_managed }}` to generate some of the files. As a consequence, if a customer had a custom multi-line `ansible_managed` setting, the files would be generated incorrectly. With this fix, all of the system roles use the equivalent of `{{ ansible_managed | comment }}` when generating files so that the `ansible_managed` string is always properly commented, including multi-line `ansible_managed` values. Consequently, generated files have the correct multi-line `ansible_managed` value.
|
Story Points: | --- |
Clone Of: | 2006230 | Environment: | |
Last Closed: | 2022-05-10 14:12:10 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: |
Description
Sergei Petrosian
2021-09-21 09:27:30 UTC
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 (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-2022:1896 This comment was flagged a spam, view the edit history to see the original text if required. |