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 1747457 - realmd.conf documentation incorrect
Summary: realmd.conf documentation incorrect
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: realmd
Version: 8.2
Hardware: All
OS: All
unspecified
low
Target Milestone: rc
: 8.2
Assignee: Sumit Bose
QA Contact: sssd-qe
URL:
Whiteboard: sync-to-jira
Depends On: 1625001
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-30 13:24 UTC by Sumit Bose
Modified: 2023-06-26 15:17 UTC (History)
5 users (show)

Fixed In Version: realmd-0.16.3-17.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1625001
Environment:
Last Closed: 2020-04-28 16:59:49 UTC
Type: Bug
Target Upstream Version:
Embargoed:
sbose: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-26673 0 None None None 2023-06-26 15:13:35 UTC
Red Hat Issue Tracker SSSD-1841 0 None None None 2023-06-26 15:17:06 UTC
Red Hat Product Errata RHBA-2020:1884 0 None None None 2020-04-28 16:59:55 UTC

Comment 2 shridhar 2020-01-27 07:03:33 UTC 
Verified with following info

=====================
In previous version
=====================
4q]# rpm -q realmd
realmd-0.16.3-16.el8.x86_64
[root@ci-vm-10-0-136-39 tmp.XRCaT6e24q]# man realmd.conf |col -b | sed -n '/REALM SPECIFIC SETTING/,/computer-ou/p'
REALM SPECIFIC SETTINGS
       These options should go in an section with the same name as the realm in the /etc/realmd.conf file. For
       example for the domain.example.com domain the section would be called [domain.example.com]. To figure out
       the canonical name for a realm use the realm command:

	   $ realm discover --name DOMAIN.example.com
	   domain.example.com
	   ...

       Only specify the settings you wish to override.

       computer-ou



==================
In fixed version
==================

]# rpm -q realmd
realmd-0.16.3-17.el8.x86_64


[root@ci-vm-10-0-138-120 tmp.7aHPxY8qja]# man realmd.conf|col -b|sed -n '/REALM SPECIFIC SETTINGS/,/computer-ou/p'
REALM SPECIFIC SETTINGS
       These options should go in an section with the same name as the realm in the /etc/realmd.conf file. For
       example for the domain.example.com domain the section would be called [domain.example.com]. To figure out
       the canonical name for a realm use the realm command:

	   $ realm discover --name-only DOMAIN.example.com
	   domain.example.com
	   ...

       Only specify the settings you wish to override.

       computer-ou
[root@ci-vm-10-0-138-120 tmp.7aHPxY8qja]# 

Marking verified.
Comment 4 errata-xmlrpc 2020-04-28 16:59:49 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/RHBA-2020:1884
Note You need to log in before you can comment on or make changes to this bug.