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 1479049 - Ectd3 cluster not starting
Summary: Ectd3 cluster not starting
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: etcd3
Version: 7.3
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: rc
: ---
Assignee: Jan Chaloupka
QA Contact: Martin Jenner
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-07 20:21 UTC by Steven Walter
Modified: 2020-09-10 11:09 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-29 18:09:16 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Steven Walter 2017-08-07 20:21:17 UTC 
Description of problem:
Etcd3 service does not start but provides few logs explaining failure

Version-Release number of selected component (if applicable):
etcd-3.1.7-1.el7.src.rpm
kernel-3.10.0-514.21.1.el7.src.rpm

How reproducible:
Unconfirmed

Actual results:

Aug 02 11:45:06 xdcq-etcd3.example.com etcd[12034]: recognized and used environment variable ETCD_ADVERTISE_CLIENT_URLS=https://xxx.xxx.x.132:2379
Aug 02 11:45:06 xdcq-etcd3.example.com etcd[12034]: recognized and used environment variable ETCD_CA_FILE=/etc/etcd/ca.crt
Aug 02 11:45:06 xdcq-etcd3.example.com etcd[12034]: recognized and used environment variable ETCD_CERT_FILE=/etc/etcd/server.crt
Aug 02 11:45:06 xdcq-etcd3.example.com etcd[12034]: recognized and used environment variable ETCD_ELECTION_TIMEOUT=2500
Aug 02 11:45:06 xdcq-etcd3.example.com etcd[12034]: recognized and used environment variable ETCD_HEARTBEAT_INTERVAL=500
Aug 02 11:45:06 xdcq-etcd3.example.com etcd[12034]: recognized and used environment variable ETCD_INITIAL_ADVERTISE_PEER_URLS=https://xxx.xxx.x.132:2380
Aug 02 11:45:06 xdcq-etcd3.example.com etcd[12034]: recognized and used environment variable ETCD_INITIAL_CLUSTER=xdc-etcd1.example.com=https://xxx.xxx.x.127:2380,xdc-etcd2.example.com=https://xxx.xxx.x.128:2380,xdc-etcd3.example.com=https://xxx.xxx.x.132:2380
Aug 02 11:45:06 xdcq-etcd3.example.com etcd[12034]: recognized and used environment variable ETCD_INITIAL_CLUSTER_STATE=new
Aug 02 11:45:06 xdcq-etcd3.example.com etcd[12034]: recognized and used environment variable ETCD_INITIAL_CLUSTER_TOKEN=etcd-cluster-1
Aug 02 11:45:06 xdcq-etcd3.example.com etcd[12034]: recognized and used environment variable ETCD_KEY_FILE=/etc/etcd/server.key
Aug 02 11:45:06 xdcq-etcd3.example.com systemd[1]: etcd.service: main process exited, code=exited, status=1/FAILURE
Aug 02 11:45:06 xdcq-etcd3.example.com systemd[1]: Failed to start Etcd Server.
Aug 02 11:45:06 xdcq-etcd3.example.com systemd[1]: Unit etcd.service entered failed state.
Aug 02 11:45:06 xdcq-etcd3.example.com systemd[1]: etcd.service failed.
Aug 02 11:45:06 xdcq-etcd3.example.com systemd[1]: etcd.service holdoff time over, scheduling restart.
Aug 02 11:45:06 xdcq-etcd3.example.com systemd[1]: Starting Etcd Server...



Expected results:
Etcd service starts

Additional info:
This is part of a 2 master, 3 etcd openshift install; etcd was installed by OCP 3.5's ansible installer playbooks
Comment 4 Brenton Leanhardt 2017-08-11 14:01:38 UTC 
What log level is etcd set to?  Can you set ETCD_DEBUG=true in /etc/etcd/etcd.conf?
Comment 5 Steven Walter 2017-08-11 21:29:00 UTC 
Set ETCD_DEBUG=true. Uploading logs now
Note You need to log in before you can comment on or make changes to this bug.