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 1231886 - kadmind should take the port for incremental propagation from portrelease
Summary: kadmind should take the port for incremental propagation from portrelease
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: krb5
Version: 6.7
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Robbie Harwood
QA Contact: Patrik Kis
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-06-15 14:36 UTC by Patrik Kis
Modified: 2021-12-10 14:38 UTC (History)
8 users (show)

Fixed In Version: krb5-1.10.3-44.el6
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-11 01:01:13 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker FREEIPA-7504 0 None None None 2021-12-10 14:38:19 UTC
Red Hat Product Errata RHBA-2016:0945 0 normal SHIPPED_LIVE krb5 bug fix and enhancement update 2016-05-10 22:55:41 UTC

Description Patrik Kis 2015-06-15 14:36:13 UTC 
Description of problem:
When incremental propagation is configured kadmind can not bind to port 754 on master server because that is reserved by portreserve.
It would be nice if kadmind in its init script could release this port, similarly as it releases the port 749.
Note, that port 754 is released normaly by kpropd, but as kpropd and kadmind can not run in the same time, this would not conflict.

IMHO, the this could be fixed by just adding the following line into /etc/init.d/kadmin:
[ -x /sbin/portrelease ] && /sbin/portrelease krb5_prop &>/dev/null || :

Version-Release number of selected component (if applicable):
krb5-libs-1.10.3-42.el6

How reproducible:
always

Steps to Reproduce:
1. Configure incremental propagation:

# cat /var/kerberos/krb5kdc/kdc.conf 
[kdcdefaults]
 kdc_ports = 88
 kdc_tcp_ports = 88

[realms]
 SAFETY-INSPECTOR.SECTOR7G.NUCLEAR-POWER-PLANT.SPRINGSFIELD.NET = {
  #master_key_type = aes256-cts
  acl_file = /var/kerberos/krb5kdc/kadm5.acl
  dict_file = /usr/share/dict/words
  admin_keytab = /var/kerberos/krb5kdc/kadm5.keytab
  supported_enctypes = aes256-cts:normal aes128-cts:normal des3-hmac-sha1:normal arcfour-hmac:normal des-hmac-sha1:normal des-cbc-md5:normal des-cbc-crc:normal
  iprop_enable = true
  iprop_port = 754
 }

2. Start kadmind

# service portreserve status
portreserve (pid  24500) is running...
# service kadmin start
Starting Kerberos 5 Admin Server: [  OK  ]
#
# tail /var/log/kadmind.log
Jun 15 10:34:02 ibm-p8-kvm-04-guest-01.rhts.eng.bos.redhat.com kadmind[24752](info): setting up network...
Jun 15 10:34:02 ibm-p8-kvm-04-guest-01.rhts.eng.bos.redhat.com kadmind[24752](info): listening on fd 7: udp 0.0.0.0.464 (pktinfo)
kadmind: setsockopt(8,IPV6_V6ONLY,1) worked
kadmind: Invalid argument - Cannot request packet info for udp socket address :: port 464
Jun 15 10:34:02 ibm-p8-kvm-04-guest-01.rhts.eng.bos.redhat.com kadmind[24752](info): skipping unrecognized local address family 17
Jun 15 10:34:02 ibm-p8-kvm-04-guest-01.rhts.eng.bos.redhat.com kadmind[24752](info): skipping unrecognized local address family 17
kadmind: setsockopt(8,IPV6_V6ONLY,1) worked
Jun 15 10:34:02 ibm-p8-kvm-04-guest-01.rhts.eng.bos.redhat.com kadmind[24752](info): listening on fd 8: udp fd16::5054:ff:fe91:2364.464
kadmind: setsockopt(9,IPV6_V6ONLY,1) worked
Jun 15 10:34:02 ibm-p8-kvm-04-guest-01.rhts.eng.bos.redhat.com kadmind[24752](info): listening on fd 9: udp 2620:52:0:1040:5054:ff:fe91:2364.464
kadmind: setsockopt(10,IPV6_V6ONLY,1) worked
Jun 15 10:34:02 ibm-p8-kvm-04-guest-01.rhts.eng.bos.redhat.com kadmind[24752](info): listening on fd 10: udp fe80::5054:ff:fe91:2364%eth0.464
kadmind: setsockopt(11,IPV6_V6ONLY,1) worked
Jun 15 10:34:02 ibm-p8-kvm-04-guest-01.rhts.eng.bos.redhat.com kadmind[24752](info): listening on fd 12: tcp 0.0.0.0.464
Jun 15 10:34:02 ibm-p8-kvm-04-guest-01.rhts.eng.bos.redhat.com kadmind[24752](info): listening on fd 11: tcp ::.464
kadmind: Address already in use - Cannot bind server socket on 0.0.0.0.754

^^^^^^^^^^^^^^^^^^^^^^^^^^^^ NOTE THIS
Comment 5 errata-xmlrpc 2016-05-11 01:01:13 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://rhn.redhat.com/errata/RHBA-2016-0945.html
Note You need to log in before you can comment on or make changes to this bug.