Master node scale-up fails if etcd is encrypted

Solution Unverified - Updated -

Issue

  • Scale-up playbook fails when trying to add a new master node to an existing cluster with encrypted etcd.
FAILED - RETRYING: Wait for /apis/metrics.k8s.io/v1beta1 when registered (2 retries left).
FAILED - RETRYING: Wait for /apis/metrics.k8s.io/v1beta1 when registered (1 retries left).
fatal: [xx.xx.xx..xx_node_name]: FAILED! => {"attempts": 60, "changed": true, "cmd": ["oc", "--config=/etc/origin/master/admin.kubeconfig", "get", "--raw", "/apis/metrics.k8s.io/v1beta1"], "delta": "0:00:30.302440", "end": "2020-03-06 11:21:50.414815", "msg": "non-zero return code", "rc": 1, "start": "2020-03-06 11:21:20.112375", "stderr": "Error from server (ServiceUnavailable): the server is currently unable to handle the request", "stderr_lines": ["Error from server (ServiceUnavailable): the server is currently unable to handle the request"], "stdout": "", "stdout_lines": []}

Environment

  • Red Hat OpenShift Container Platform 3.11

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