Skip to content
This repository has been archived by the owner on Feb 5, 2020. It is now read-only.

bootstrap apiserver fails to start on Openstack #3047

Open
vgkowski opened this issue Feb 28, 2018 · 0 comments
Open

bootstrap apiserver fails to start on Openstack #3047

vgkowski opened this issue Feb 28, 2018 · 0 comments

Comments

@vgkowski
Copy link

vgkowski commented Feb 28, 2018

What keywords did you search in tectonic-installer issues before filing this one?

openstack apiserver

Is this a BUG REPORT or FEATURE REQUEST?

BUG REPORT

Versions

Tectonic version (release or commit hash):

master

Terraform version (terraform version):

0.11.3

Platform (aws|azure|openstack|metal|vmware):

openstack

What happened?

The bootstrap kube-apiserver fails to start

What you expected to happen?

Should start so the installation can move on

How to reproduce it (as minimally and precisely as possible)?

install tectonic with etcd cluster on dedicated VMs
wait for torcx to get the right vversion of Docker and the master-0 to reboot
docker ps -a gives an exited bootstrap apiserver with errors

Anything else we need to know?

Logs for docker logs bootstrap_static_pod_id

I0228 16:06:44.871005       1 logs.go:41] warning: ignoring ServerName for user-provided CA for backwards compatibility is deprecated
I0228 16:06:48.536169       1 serve.go:89] Serving securely on [::]:6443
I0228 16:06:48.542175       1 available_controller.go:262] Starting AvailableConditionController
I0228 16:06:48.542240       1 cache.go:32] Waiting for caches to sync for AvailableConditionController controller
I0228 16:06:48.542365       1 controller.go:84] Starting OpenAPI AggregationController
I0228 16:06:48.542442       1 crd_finalizer.go:242] Starting CRDFinalizer
I0228 16:06:48.543218       1 apiservice_controller.go:112] Starting APIServiceRegistrationController
I0228 16:06:48.543298       1 cache.go:32] Waiting for caches to sync for APIServiceRegistrationController controller
I0228 16:06:48.543395       1 crdregistration_controller.go:110] Starting crd-autoregister controller
I0228 16:06:48.543482       1 controller_utils.go:1019] Waiting for caches to sync for crd-autoregister controller
I0228 16:06:48.549852       1 customresource_discovery_controller.go:152] Starting DiscoveryController
I0228 16:06:48.549898       1 naming_controller.go:274] Starting NamingConditionController
I0228 16:06:53.538907       1 trace.go:76] Trace[1298498081]: "Create /api/v1/namespaces" (started: 2018-02-28 16:06:49.537506516 +0000 UTC m=+6.592050109) (total time: 4.00136735s):
Trace[1298498081]: [4.00136735s] [4.001067406s] END
E0228 16:07:02.552234       1 client_ca_hook.go:78] Unable to refresh the Webhook configuration: configuration is not ready
E0228 16:07:12.551349       1 client_ca_hook.go:78] Unable to refresh the Webhook configuration: configuration is not ready
E0228 16:07:22.550566       1 client_ca_hook.go:78] Unable to refresh the Webhook configuration: configuration is not ready
E0228 16:07:31.564340       1 client_ca_hook.go:78] Unable to refresh the Webhook configuration: configuration is not ready
F0228 16:07:31.564367       1 hooks.go:188] PostStartHook "ca-registration" failed: unable to initialize client CA configmap: timed out waiting for the condition

Etcd working fine from the master-0

sudo ETCDCTL_API=3 etcdctl --cacert=/opt/tectonic/tls/etcd-client-ca.crt --cert=/opt/tectonic/tls/etcd-client.crt --key=/opt/tectonic/tls/etcd-client.key --endpoints=https://test-etcd-0.k8s.vms.xxx:2379 endpoint health
https://test-etcd-0.k8s.vms.xxx:2379 is healthy: successfully committed proposal: took = 3.066808ms
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants