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 1629733

Summary:	[DOCKER] pods are stuck in containercreating with error grpc: the connection is unavailable
Product:	Red Hat Enterprise Linux 7	Reporter:	hgomes
Component:	docker	Assignee:	Daniel Walsh <dwalsh>
Status:	CLOSED DUPLICATE	QA Contact:	atomic-bugs <atomic-bugs>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	7.0	CC:	achvatal, amurdaca, anli, aos-bugs, byount, dapark, dornelas, dyocum, erich, fshaikh, gquites, grajawat, hgomes, jack.ottofaro, jcantril, jhonce, jkaur, jlieskov, jmalde, jokerman, jrosenta, kp, kramdoss, ktadimar, lsm5, maupadhy, mmccomas, mmillson, mpatel, mtaru, nnosenzo, pportant, rbost, rcyriac, rekhan, rkshirsa, rpuccini, schoudha, sgaikwad, takirby, tcarlin, umohnani, uobergfe, vlaad, wjiang, wmeng, yannick.kint
Target Milestone:	rc	Keywords:	Extras, OnlineStarter
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	docker-1.13.1-80.git8633870.el7_5	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1560428
Clones:	1643806 (view as bug list)		Environment:
Last Closed:	2018-11-09 17:41:28 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:	1560428, 1643806
Bug Blocks:	1186913

Comment 2 Mrunal Patel 2018-09-28 17:37:34 UTC

One curious thing that we have noticed is that gnome-shell is running. Is this a server or a desktop?

Comment 5 Urvashi Mohnani 2018-10-02 15:41:21 UTC

Hi Mike would it be possible to get access to the node where this issue is occurring?

Comment 6 Mike Millson 2018-10-02 16:15:09 UTC

Hi Urvashi,

I could ask the support engineer to set up a remote session, and we could ask them to execute commands in their environment, and we could observe the results. What is your availability today for that?

Mike

Comment 7 Urvashi Mohnani 2018-10-02 17:02:43 UTC

Hi Mike, would 4pm EST today work?

Comment 16 Antonio Murdaca 2018-10-05 08:17:20 UTC

We've identified 2 back ports likely to fix the issues here:

https://github.com/containerd/containerd/pull/872/commits/de0e943db45b57fe2d422a6d1ebdffd5005a5296
https://github.com/containerd/containerd/pull/828/commits/6feebe941995c6086e9bfbe5c88834e90c7f43e4

we are back porting these as we speak, we'll have a test build for customer who are willing to test the package.

If it turns out that it's actually fixing the issue, we can go with an hotfix package.

Lokesh, I'll ask you to rebuild docker once we have back ports in place.

Comment 19 Antonio Murdaca 2018-10-08 10:15:05 UTC

We've rebuilding docker with an additional BZ fixed that could help with this whole issue (https://bugzilla.redhat.com/show_bug.cgi?id=1636259)

we've rebuilding the docker package again.

Comment 36 Antonio Murdaca 2018-10-23 14:03:10 UTC

That panic has already been fixed by https://github.com/projectatomic/containerd/commit/8c0b404ff7eaae3cfd47b5517470e736f6d52bd6

docker-1.13.1-75.git8633870.el7_5.x86_64 <- this package is old at this point also, we've rebuilt docker with the fixes in question again.

Comment 43 Derrick Ornelas 2018-10-29 01:12:27 UTC

This is actually a docker bug and affects any version of OpenShift using docker 1.13.1 (OCP 3.9, 3.10, 3.11)