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 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:
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