Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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.

[Sat6.2] LDAP Groups base DN not visible in CLI through command "#hammer auth-source ldap info"

Version-Release number of selected component (if applicable):Satellite 6.2.x

>> Description of problem:

>> How reproducible:
A RHEL 7.2 installation with Satellite 6.2.10 configured to use external LDAP authentication (created using hammer)

In Satellite WebUI Administer >> LDAP authentication >> authentication source >> Account >> Here we can set Groups base DN but if we check this info from "#hammer auth-source ldap info --name "name" then it will not visible."

>> Actual results:

 Group base DN is not visible through command on Satellite: #hammer auth-source ldap info --name "name"

>> Expected results:

 Group base DN should be visible through command on Satellite: #hammer auth-source ldap info --name "name" like it visible in Satellite WebUI Administer >> LDAP authentication >> authentication source >> Account.

Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/20227 has been resolved.

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/RHSA-2018:2927