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.
Description of problem:
Running a container image is managed by Atomic then stop it, and restart docker-latest service, the stopped container is started again.
Version-Release number of selected component (if applicable):
# rpm -q docker-latest atomic
docker-latest-1.10.3-12.el7.x86_64
atomic-1.9-4.gitff44c6a.el7.x86_64
How reproducible:
always
Steps to Reproduce:
1. atomic install registry.access.redhat.com/rhel7/rsyslog:latest
2. atomic run registry.access.redhat.com/rhel7/rsyslog:latest
3. docker-latest ps
4. docker-latest stop <container_id>
Actual results:
# docker-latest ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
aff96890b1ce registry.access.redhat.com/rhel7/rsyslog:latest "/bin/rsyslog.sh" 6 seconds ago Up 5 seconds rsyslog
# docker-latest stop aff96890b1ce
aff96890b1ce
# docker-latest ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
# docker-latest ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
aff96890b1ce registry.access.redhat.com/rhel7/rsyslog:latest "/bin/rsyslog.sh" About a minute ago Exited (0) 13 seconds ago rsyslog
# systemctl restart docker-latest
# docker-latest ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
aff96890b1ce registry.access.redhat.com/rhel7/rsyslog:latest "/bin/rsyslog.sh" About a minute ago Up 2 seconds rsyslog
Expected results:
Additional info:
I have a running rsyslog container before upgrading docker-latest RPM packages, I found the running rsyslog container is still running after upgrading docker-latest, it should be an expected result, in order to get a clear test environment, I stopped rsyslog container and deleted it from my RHEL7 system, and also delete all of inactive containers, and then I ran steps in above section Steps to Reproduce.
If the container is set to autostart then restarting the daemon would start the container. I don't see this as a bug.
Reopen if you don't agree or I am mistaken.