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.

Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Hi Russ,

This looks like it was fixed on new versions of Sat (including 6.1.z), we had 2 people from engineering including me and a person from QE who couldn't reproduce this behavior on another bug. 

Additionally https://bugzilla.redhat.com/show_bug.cgi?id=1284832#c23 and 
https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=12309387
https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=12309413 provide hotfixes for ldap_fluff that provide a much more stable ldap backend. 

Could you please verify this doesn't happen anymore with/without the hotfix package?

I was able to close https://bugzilla.redhat.com/show_bug.cgi?id=1404114 today after a call with a customer, and there were no problems with spaces in the base DN. Given how old this bug is, I highly doubt this is still a problem, so I'll close. I will keep the needinfo in case you want to reopen it if it doesn't work in your scenario.