service etcd fails to start while installing etcd package

[bugproxy]

Problem Description
-----------------------------------
service etcd start fails to start while installation and subsequent service starts on Ubuntu 17.10.

root@ltc-test-ci2:~# apt install etcd
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
  etcd
0 upgraded, 1 newly installed, 0 to remove and 1 not upgraded.
Need to get 0 B/13.4 MB of archives.
After this operation, 87.0 MB of additional disk space will be used.
Selecting previously unselected package etcd.
(Reading database ... 140691 files and directories currently installed.)
Preparing to unpack .../etcd_3.1.0-1_ppc64el.deb ...
Unpacking etcd (3.1.0-1) ...
Processing triggers for ureadahead (0.100.0-19) ...
Processing triggers for systemd (233-6ubuntu3) ...
Processing triggers for man-db (2.7.6.1-2) ...
Setting up etcd (3.1.0-1) ...
Adding system user `etcd' (UID 115) ...
Adding new group `etcd' (GID 121) ...
Adding new user `etcd' (UID 115) with group `etcd' ...
Creating home directory `/var/lib/etcd/' ...
Created symlink /etc/systemd/system/etcd2.service -> /lib/systemd/system/etcd.service.
Created symlink /etc/systemd/system/multi-user.target.wants/etcd.service -> /lib/systemd/system/etcd.service.
Job for etcd.service failed because the service did not take the steps required by its unit configuration.
See "systemctl status etcd.service" and "journalctl -xe" for details.
invoke-rc.d: initscript etcd, action "start" failed.
* etcd.service - etcd - highly-available key value store
   Loaded: loaded (/lib/systemd/system/etcd.service; enabled; vendor preset: enabled)
   Active: activating (auto-restart) (Result: protocol) since Tue 2017-06-27 01:22:38 EDT; 7ms ago
     Docs: https://github.com/coreos/etcd
           man:etcd
  Process: 41075 ExecStart=/usr/bin/etcd $DAEMON_ARGS (code=exited, status=1/FAILURE)
 Main PID: 41075 (code=exited, status=1/FAILURE)

Jun 27 01:22:38 ltc-test-ci2 systemd[1]: Failed to start etcd - highly-available key value store.
Jun 27 01:22:38 ltc-test-ci2 systemd[1]: etcd.service: Unit entered failed state.
Jun 27 01:22:38 ltc-test-ci2 systemd[1]: etcd.service: Failed with result 'protocol'.
dpkg: error processing package etcd (--configure):
 subprocess installed post-installation script returned error exit status 1
Processing triggers for ureadahead (0.100.0-19) ...
Processing triggers for systemd (233-6ubuntu3) ...
Errors were encountered while processing:
 etcd
E: Sub-process /usr/bin/dpkg returned an error code (1)

Environment
------------------
Kernel Build: 4.10.0-22-generic
System Name : ltc-ci2
Model : 8247-22L
Platform : PowerNV ( P8 )

Uname output
-------------------
# uname -a
Linux ltc-test-ci2 4.10.0-22-generic #24-Ubuntu SMP Mon May 22 17:42:33 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

Steps to reproduce:
---------------------------
1. apt install etcd

etcd version: 3.1.0-1

== Comment: #1 - Harish Sriram <email address hidden> - 2017-06-27 00:49:28 ==
root@ltc-test-ci2:~/harish/etcd/etcd-3.1.0# systemctl status etcd.service
* etcd.service - etcd - highly-available key value store
   Loaded: loaded (/lib/systemd/system/etcd.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Tue 2017-06-27 01:47:48 EDT; 3s ago
     Docs: https://github.com/coreos/etcd
           man:etcd
  Process: 43898 ExecStart=/usr/bin/etcd $DAEMON_ARGS (code=exited, status=1/FAILURE)
 Main PID: 43898 (code=exited, status=1/FAILURE)

Jun 27 01:47:48 ltc-test-ci2 systemd[1]: Starting etcd - highly-available key value store...
Jun 27 01:47:48 ltc-test-ci2 etcd[43898]: etcd on unsupported platform without ETCD_UNSUPPORTED_ARCH=ppc64le set.
Jun 27 01:47:48 ltc-test-ci2 systemd[1]: etcd.service: Main process exited, code=exited, status=1/FAILURE
Jun 27 01:47:48 ltc-test-ci2 systemd[1]: Failed to start etcd - highly-available key value store.
Jun 27 01:47:48 ltc-test-ci2 systemd[1]: etcd.service: Unit entered failed state.
Jun 27 01:47:48 ltc-test-ci2 systemd[1]: etcd.service: Failed with result 'exit-code'.
root@ltc-test-ci2:~/harish/etcd/etcd-3.1.0# systemctl restart etcd.service
Job for etcd.service failed because the service did not take the steps required by its unit configuration.
See "systemctl status etcd.service" and "journalctl -xe" for details.
root@ltc-test-ci2:~/harish/etcd/etcd-3.1.0# systemctl status etcd.service
* etcd.service - etcd - highly-available key value store
   Loaded: loaded (/lib/systemd/system/etcd.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Tue 2017-06-27 01:48:13 EDT; 8s ago
     Docs: https://github.com/coreos/etcd
           man:etcd
  Process: 43942 ExecStart=/usr/bin/etcd $DAEMON_ARGS (code=exited, status=1/FAILURE)
 Main PID: 43942 (code=exited, status=1/FAILURE)

Jun 27 01:48:13 ltc-test-ci2 systemd[1]: Starting etcd - highly-available key value store...
Jun 27 01:48:13 ltc-test-ci2 etcd[43942]: etcd on unsupported platform without ETCD_UNSUPPORTED_ARCH=ppc64le set.
Jun 27 01:48:13 ltc-test-ci2 systemd[1]: etcd.service: Main process exited, code=exited, status=1/FAILURE
Jun 27 01:48:13 ltc-test-ci2 systemd[1]: Failed to start etcd - highly-available key value store.
Jun 27 01:48:13 ltc-test-ci2 systemd[1]: etcd.service: Unit entered failed state.
Jun 27 01:48:13 ltc-test-ci2 systemd[1]: etcd.service: Failed with result 'exit-code'.

root@ltc-test-ci2:~/harish/etcd/etcd-3.1.0# echo $ETCD_UNSUPPORTED_ARCH
ppc64le

[bugproxy (bugproxy)]

Default Comment by Bridge

[bugproxy (bugproxy)]

Default Comment by Bridge

[Frank Heimes (fheimes)]

The package etcd is part of the universe section of the Ubuntu archive. Universe packages are maintained by the community, and the maintainers do not necessarily work for Canonical, therefore these packages are not always supported directly by Canonical.
The existing process to update packages in the Universe archive with patches, is as follows:
1) Upstream: Upstream your fix to the appropriate upstream project.
2) Debian: once your patch is ack’ed and accepted upstream, you need to request a merge of this patch to the package in Debian stable. https://www.debian.org/Bugs/Reporting use this link to report your issue and submit a fix.
3) Ubuntu: Once it is merged into Debian stable, request a merge of this package with Ubuntu. https://wiki.ubuntu.com/Debian/Bugs will provide you an overview on how to handle bugs that are reported to Debian and subsequently to Ubuntu.
  - The merge request lands by default in Ubuntu's current development release (today ‘Artful’).
  - If required an SRU may follow to get the changes into already released Ubuntu versions (like ‘Xenial’ or ‘Zesty’).
Work with the respective upstream maintainers (Debian and Ubuntu) is required during this process. For critical issues we can advise you as you go through this process and help push the patches through by chasing the appropriate project contributors.