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.
I put exit 1 in the entry script for etcd container. and built locally and then tested without Type=notify in the service file, and I see that the systemctl status logs the start error correctly.
systemctl status etcd.service
● etcd.service - Etcd Server
Loaded: loaded (/etc/systemd/system/etcd.service; enabled; vendor preset: disabled)
Active: failed (Result: start-limit) since Thu 2016-09-15 12:39:31 EDT; 6s ago
Process: 16412 ExecStop=/bin/runc kill etcd (code=exited, status=1/FAILURE)
Process: 16393 ExecStart=/bin/runc start etcd (code=exited, status=1/FAILURE)
Main PID: 16393 (code=exited, status=1/FAILURE)
Sep 15 12:39:31 rhel73 systemd[1]: Unit etcd.service entered failed state.
Sep 15 12:39:31 rhel73 systemd[1]: etcd.service failed.
Sep 15 12:39:31 rhel73 systemd[1]: etcd.service holdoff time over, scheduling restart.
Sep 15 12:39:31 rhel73 systemd[1]: start request repeated too quickly for etcd.service
Sep 15 12:39:31 rhel73 systemd[1]: Failed to start Etcd Server.
Sep 15 12:39:31 rhel73 systemd[1]: Unit etcd.service entered failed state.
Sep 15 12:39:31 rhel73 systemd[1]: etcd.service failed.
So I dont think there is an issue here.
CAI,
Also as per systemd docuementation, Type=notify is useful when "the daemon sends a notification message via sd_notify(3) or an equivalent call when it has finished starting up".
I am not sure runc or etcd does that.
CAI,
I think I see the difference when using Type=notify.
#systemctl start etcd.service
Job for etcd.service failed because the control process exited with error code. See "systemctl status etcd.service" and "journalctl -xe" for details.
I think this failure is not available without Type=notify.
I will fix it next built today.