StarlingX

  1. Bug #1829931
  2. Comment #3

Comment 3 for bug 1829931

Revision history for this message
Al Bailey (albailey1974) wrote : Re: Standby controller not up in hypervisor list in 15 mins after host-unlock

The 15 minutes are
host-unlock at 2019-05-21 13:37:51
hypervisors up at 2019-05-21 13:51:28

The daemon.log shows that the controller comes out of its reboot at
2019-05-21T13:41:16 systemd 219 running in system mode.

and gets through the puppet manifests etc..

2019-05-21T13:44:15.089 controller-1 sm[93229]: info Starting sm: OK

The first kubernetes activities start at around that time as well.
  "Started Kubernetes transient mount for"
Those continue until 2019-05-21T13:51:14

Note: the nameserver logs come out even later:
2019-05-21T13:55:23.000 controller-1 dnsmasq[275911]: info using nameserver 10.96.0.10#53 for domain cluster.local

It looks like this system took a very long time to fully come up.