Why flanneld fails to start in Red Hat Enterprise Atomic Host 7.2 ?

Solution Unverified - Updated -

Issue

  • Why flanneld fails to start in Red Hat Enterprise Atomic Host 7.2 ?
Job for flanneld.service failed because a timeout was exceeded. See "systemctl status flanneld.service" and "journalctl -xe" for details.
-bash-4.2# systemctl status flanneld
● flanneld.service - Flanneld overlay address etcd agent
   Loaded: loaded (/usr/lib/systemd/system/flanneld.service; enabled; vendor preset: disabled)
   Active: activating (start) since Mon 2016-03-21 09:33:40 MST; 15s ago
 Main PID: 2675 (flanneld)
   CGroup: /system.slice/flanneld.service
           └─2675 /usr/bin/flanneld -etcd-endpoints=http://redhat.com:2379 -etcd-prefix=/atomic.io/network

Mar 21 09:33:46 redhat.com flanneld[2675]: E0321 09:33:46.154445 02675 network.go:53] Failed to retrieve network config: client: etcd cluster is unavailable or misconfigured

Environment

  • Red Hat Enterprise Atomic Host 7.2
  • Flanneld

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.