Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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.

Description of problem:
To run ipa-client-install --request-cert successfully in anaconda chroot workaround described in bug 1134497 must be used.

To remove the need for workaround:
a) anaconda installer must not bind-mount the DBus system bus socket into chroot (bug 1271551)
b) ipa needs logic to detect this situation and behave according.
c) DBus daemon needs to move socket outside the bind-mounted file system.

As described in bug 1271551, comment 7  a) is not easy to do in anaconda.
Approach b) is nothing else than hiding the workaround from user inside ipa-installer.

I am strongly opposed to the idea of working around the *deliberately* broken environment of Anaconda chroot, in ipa-client-install, or anywhere else.

Upstream ticket:
https://fedorahosted.org/freeipa/ticket/5694

ipa-client-install man page will be updated.

Man page fixed upstream:

master:
da5885b72a284811bda7ddd36b8716d71ac66bd9 man: Decribe ipa-client-install workaround for broken D-Bus enviroment.

ipa-4-3:
149744675315df54280955a829142f21893aa0de man: Decribe ipa-client-install workaround for broken D-Bus enviroment.

Verified.

IPA client version:
===================
[root@dhcp207-173 ~]# rpm -q ipa-client
ipa-client-4.4.0-11.el7.x86_64
[root@dhcp207-173 ~]# 

Please find the attached file which contains console output for verification steps.

Created attachment 1201728 [details]
console output with verification steps

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://rhn.redhat.com/errata/RHBA-2016-2404.html