RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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.
Bug 1616018 - documentation updates of rhel-system-roles
Summary: documentation updates of rhel-system-roles
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: rhel-system-roles
Version: 7.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Pavel Cahyna
QA Contact: David Jež
URL:
Whiteboard:
Depends On:
Blocks: 1664757
TreeView+ depends on / blocked
 
Reported: 2018-08-14 18:06 UTC by Pavel Cahyna
Modified: 2019-01-12 11:36 UTC (History)
5 users (show)

Fixed In Version: rhel-system-roles-1.0-3.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-08-21 09:32:58 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github linux-system-roles kdump pull 16 0 None None None 2018-08-16 06:44:02 UTC
Github linux-system-roles network pull 80 0 None None None 2018-08-15 14:58:57 UTC
Github linux-system-roles postfix pull 5 0 None None None 2018-08-16 06:47:30 UTC
Github linux-system-roles selinux pull 30 0 None None None 2018-08-16 06:46:40 UTC
Github linux-system-roles timesync pull 18 0 None None None 2018-08-16 06:45:50 UTC
Github linux-system-roles timesync pull 19 0 None None None 2018-08-16 06:42:03 UTC
Red Hat Bugzilla 1602901 0 unspecified CLOSED selinux: define the behavior when selinux_state not given 2021-02-22 00:41:40 UTC
Red Hat Product Errata RHEA-2018:2531 0 None None None 2018-08-21 09:33:07 UTC

Internal Links: 1602901

Description Pavel Cahyna 2018-08-14 18:06:50 UTC
After the recent changes in role syntax and semantics (bz1479381 and bugs it depends on), the new behavior should be better documented. This applies in particular to the selinux role, whose README is rather brief.

Comment 2 Pavel Cahyna 2018-08-15 14:36:17 UTC
Also the timesync_ntp_provider_os_default variable seems to be undocumented.

Comment 3 Pavel Cahyna 2018-08-15 14:58:57 UTC
There should be prominent warnings in roles that blow away non-Ansible managed settings. This seems to be the case at least for timesync and kdump (which overwrites /etc/kdump.conf and /etc/sysconfig/kdump). See https://github.com/linux-system-roles/network/pull/80 for an example of adding a warning for the network role.

Comment 5 Pavel Cahyna 2018-08-16 12:47:40 UTC
(In reply to Pavel Cahyna from comment #2)
> Also the timesync_ntp_provider_os_default variable seems to be undocumented.

I am postponing this to a later update.

Comment 8 errata-xmlrpc 2018-08-21 09:32:58 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, 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/RHEA-2018:2531


Note You need to log in before you can comment on or make changes to this bug.