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.

Bug 1219891

Summary:	Missing define for TCP_USER_TIMEOUT in netinet/tcp.h
Product:	Red Hat Enterprise Linux 7	Reporter:	John Eckersberg <jeckersb>
Component:	glibc	Assignee:	Carlos O'Donell <codonell>
Status:	CLOSED ERRATA	QA Contact:	Arjun Shankar <ashankar>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	7.2	CC:	ashankar, bperkins, dmaley, fdinitto, fweimer, jeckersb, jkurik, jlayton, mcermak, mnewsome, pbokoc, pfrankli, rohara, trond.myklebust
Target Milestone:	rc	Keywords:	Patch
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glibc-2.17-90.el7	Doc Type:	Bug Fix
Doc Text:	The library header netinet/tcp.h did not contain some of the newer definitions such as TCP_USER_TIMEOUT which were required for user applications to compile correctly. The library headers have been updated and synchronized with Linux kernel definitions for TCP_* constants. Two new structures, tcp_repair_opt, and tcp_cookie_transactions have also been added to the header.	Story Points:	---
Clone Of:
Clones:	1226799 (view as bug list)		Environment:
Last Closed:	2015-11-19 04:18:12 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1198791, 1226799

Description John Eckersberg 2015-05-08 15:25:56 UTC

Description of problem:

netinet/tcp.h is missing the define for TCP_USER_TIMEOUT (along with others).  Looks like davem fixed this upstream in 2.18 here:

https://sourceware.org/git/?p=glibc.git;a=commit;h=e83d72988d89378e7c70a1b7ba0b450a699ea70a

But this hasn't made its way into the RHEL7 glibc.

We're trying to use this features to improve availability for RHEL OpenStack Platform so it would be great to get this fixed quickly if possible.



Version-Release number of selected component (if applicable):

glibc-headers-2.17-78.el7.x86_64

Comment 2 John Eckersberg 2015-05-08 15:29:37 UTC

One more note I forgot, I'd like to get this proposed for 7.1.z once the flags are set.  We got a kernel fix backported for 7.1.z to fix a related issue (bug 1215924) so it would be nice to get an updated glibc build to go with it.

Comment 3 Fabio Massimo Di Nitto 2015-05-11 20:26:33 UTC

Raising severity as this affects a major component in OpenStack and we can't rebuild the package until the headers are fixed.

Comment 23 errata-xmlrpc 2015-11-19 04:18:12 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/RHSA-2015-2199.html