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:
If you run a lot of systemd-run --scope /bin/true processes, you can see some scopes still in "running" state in systemctl -t scope.

Version-Release number of selected component (if applicable):
systemd-219-19.el7_2.2


Steps to Reproduce:
1. The easiest way is to run /CoreOS/systemd/Regression/scope-unit-stress-test

Actual results:
There are still scopes running even after /bin/true quits.

Expected results:
No scopes running.

Additional info:

I split test to 2 phases. One is spawning systemd-run from external script file (which contains for cycle) and another one is spawning it from inline for cycle.

It looks the same but this bug only is present in the "inline" phase, which is really weird. I will try to investigate this more.

I am not able to reproduce this anymore with the newest systemd.

Closing for now.