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 1772365 - Container process reported running but not actually running
Summary: Container process reported running but not actually running
Keywords:
Status: CLOSED DUPLICATE of bug 1693559
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: docker
Version: 7.6
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Daniel Walsh
QA Contact: atomic-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks: 1186913
TreeView+ depends on / blocked
 
Reported: 2019-11-14 09:15 UTC by Takayoshi Kimura
Modified: 2023-03-24 16:02 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-20 21:29:45 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Takayoshi Kimura 2019-11-14 09:15:45 UTC
Description of problem:

A container process got exit but the container keeps Running status, no process restart happened. Some other container process got defunct status.

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

docker-1.13.1-96.gitb2f74b2.el7.x86_64

How reproducible:

2 times, on different hosts

Steps to Reproduce:
1. Unknown
2.
3.

Actual results:


Expected results:


Additional info:

Comment 8 Daniel Walsh 2019-11-19 13:02:59 UTC
We are no longer updating versions of Docker.  RHEL7 has entered a phase were we only fix Security issues (CVEs).  In RHEL8 we have moved away from Docker to Podman, Buildah, Skopeo.

Is the customer willing to try these tools?

Comment 10 Takayoshi Kimura 2019-11-20 00:18:22 UTC
The customer is using OpenShift 3.x so it must be RHEL7.

Comment 11 Robb Manes 2019-11-20 21:29:45 UTC
I have debugged this in the support case and determined it is almost certainly a duplicate of bz1693559, a bug in systemd dbus message handling, where Docker can hang due to containers not properly shutting down.

*** This bug has been marked as a duplicate of bug 1693559 ***


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