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 1063905 - Move ipa-otpd socket directory
Summary: Move ipa-otpd socket directory
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: krb5
Version: 7.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Nalin Dahyabhai
QA Contact: Patrik Kis
URL:
Whiteboard:
Depends On: 1063850
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-11 15:44 UTC by Martin Kosek
Modified: 2014-06-18 01:08 UTC (History)
4 users (show)

Fixed In Version: krb5-1.11.3-46.el7
Doc Type: Bug Fix
Doc Text:
Clone Of: 1063850
Environment:
Last Closed: 2014-06-13 09:24:19 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Martin Kosek 2014-02-11 15:44:59 UTC
+++ This bug was initially created as a clone of Bug #1063850 +++

This bug is created as a clone of upstream ticket:
https://fedorahosted.org/freeipa/ticket/4167

Upstream has changed the default OTP socket search directory:
https://github.com/krb5/krb5/pull/45

This code will be available in 1.13 by default. We will probably update this change in krb5 1.12 (and maybe 1.11). FreeIPA will need to respect this default. And any update in krb5 which makes this change needs to be synchronized with FreeIPA.

Comment 1 Martin Kosek 2014-02-11 15:45:45 UTC
This Bugzilla is to track the krb5 change in 7.0.

Comment 2 Martin Kosek 2014-02-11 16:52:38 UTC
As discussed in a triage meeting, this Bugzilla shall be tested as sanity only. It is a forward looking precaution, to avoid this backwards incompatible change after 7.0.

Comment 3 Nalin Dahyabhai 2014-02-11 18:12:45 UTC
Testing note:  this change also requires that we create and own /var/run/krb5kdc, and because /run is created fresh at boot-time we've added configuration to trigger its creation on reboot.  Please also verify that a) the directory exists after we install the new krb5-server package fresh and b) that it is there again when the system is booted, whether or not the krb5kdc service is started.

Comment 5 Patrik Kis 2014-02-13 16:02:55 UTC
(In reply to Nalin Dahyabhai from comment #3)
> Testing note:  this change also requires that we create and own
> /var/run/krb5kdc, and because /run is created fresh at boot-time we've added
> configuration to trigger its creation on reboot.  Please also verify that a)
> the directory exists after we install the new krb5-server package fresh and
> b) that it is there again when the system is booted, whether or not the
> krb5kdc service is started.

Apart if this I can also verify that the KDC connects to a test unix socket (created by socat) on the new location and if the socket name can be configured. Of course I won't be able to check the sanity of of the communication over the socket, but that will be checked later by IPA when the time comes.
I think it will be sufficient test for now. Should you have other ideas, please let me know.

Comment 7 Ludek Smid 2014-06-13 09:24:19 UTC
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.


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