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 1199488 - systemd-nspawn service enters failed state after shutting down container from inside
Summary: systemd-nspawn service enters failed state after shutting down container from...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: systemd
Version: 7.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: systemd-maint
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-03-06 13:36 UTC by Karel Volný
Modified: 2015-11-19 15:06 UTC (History)
3 users (show)

Fixed In Version: systemd-219-1.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-19 15:06:22 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:2092 0 normal SHIPPED_LIVE systemd bug fix and enhancement update 2015-11-19 12:13:57 UTC

Description Karel Volný 2015-03-06 13:36:13 UTC 
Description of problem:
If a full system is installed into the container which is run as a service, and then the container shuts down itself, not via stopping the service, it is treated as if the service failed. But simply stopping a machine, no crash or whatever, isn't an error ...

Reading the docs[*] I fail to find/understand if some special action is needed to shut down the container without error.

Note that if the same container is run from the commandline, not as a service, it exits without error and after the last shutdown step "Sending SIGTERM to remaining processes..." systemd-nspawn reports "Container has been shut down."

[*] http://www.freedesktop.org/software/systemd/man/systemd-nspawn.html

Version-Release number of selected component (if applicable):
systemd-208-20.el7.x86_64

How reproducible:
always

Steps to Reproduce:
I'm getting the failure as a part of automated testcase, but the important steps go like this:

1. mkdir -p /var/lib/container/rhel7
2. yum -y --nogpgcheck --installroot /var/lib/container/rhel7 groupinstall minimal
3. ln -s '/usr/lib/systemd/system/systemd-nspawn@.service' '/etc/systemd/system/systemd-nspawn@rhel7'
4. systemctl start systemd-nspawn@rhel7
5. run 'poweroff' in the container
6. systemctl status systemd-nspawn@rhel7

Actual results:
systemd-nspawn - Container rhel7
   Loaded: loaded (/usr/lib/systemd/system/systemd-nspawn@.service; enabled)
   Active: failed (Result: exit-code) since Wed 2015-02-25 20:26:32 CET; 1min 36s ago
     Docs: man:systemd-nspawn(1)
  Process: 20063 ExecStart=/usr/bin/systemd-nspawn -bjD /var/lib/container/%i (code=exited, status=1/FAILURE)
 Main PID: 20063 (code=exited, status=1/FAILURE)

...
Feb 25 20:26:07 (hostname filtered) systemd[1]: Started Container rhel7.
Feb 25 20:26:32 (hostname filtered) systemd-nspawn[20063]: Container failed with error code 1.
Feb 25 20:26:32 (hostname filtered) systemd[1]: systemd-nspawn: main process exited, code=exited, status=1/FAILURE
Feb 25 20:26:32 (hostname filtered) systemd[1]: Unit systemd-nspawn entered failed state.


Expected results:
systemd-nspawn - Container rhel7
   Loaded: loaded (/usr/lib/systemd/system/systemd-nspawn@.service; enabled)
   Active: inactive (dead) since Wed 2015-02-25 20:26:32 CET; 1min 36s ago
     Docs: man:systemd-nspawn(1)
  Process: 20063 ExecStart=/usr/bin/systemd-nspawn -bjD /var/lib/container/%i (code=exited, status=0/SUCCESS)
 Main PID: 20063 (code=exited, status=0/SUCCESS)

...
Feb 25 20:26:07 (hostname filtered) systemd[1]: Started Container rhel7.
Feb 25 20:26:32 (hostname filtered) systemd-nspawn[20063]: Container has been shut down.
Feb 25 20:26:32 (hostname filtered) systemd[1]: systemd-nspawn: main process exited, code=exited, status=0/SUCCESS
Feb 25 20:26:32 (hostname filtered) systemd[1]: Unit systemd-nspawn entered stopped state.
...


Additional info:
Comment 3 Lukáš Nykrýn 2015-05-12 14:41:23 UTC 
works for me after rebase
Comment 5 errata-xmlrpc 2015-11-19 15:06:22 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/RHBA-2015-2092.html
Note You need to log in before you can comment on or make changes to this bug.