kube-proxy in CoreOS minion is not started

Bug #1611138 reported by hongbin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Magnum
Fix Released
Undecided
hongbin

Bug Description

This is caused by https://review.openstack.org/#/c/345969/2/magnum/drivers/k8s_coreos_v1/templates/fragments/enable-kube-proxy-minion-coreos.yaml . The change above made the format incorrectly and removed the necessary path to locate the TLS secrets.

The error:
Error: invalid configuration: [unable to read client-cert /etc/kubernetes/ssl/worker.pem for kubelet due to open /etc/kubernetes/ssl/worker.pem: no such file or directory, unable to read client-key /etc/kubernetes/ssl/worker-key.pem for kubelet due to open /etc/kubernetes/ssl/worker-key.pem: no such file or directory, unable to read certificate-authority /etc/kubernetes/ssl/ca.pem for local due to open /etc/kubernetes/ssl/ca.pem: no such file or directory]
invalid configuration: [unable to read client-cert /etc/kubernetes/ssl/worker.pem for kubelet due to open /etc/kubernetes/ssl/worker.pem: no such file or directory, unable to read client-key /etc/kubernetes/ssl/worker-key.pem for kubelet due to open /etc/kubernetes/ssl/worker-key.pem: no such file or directory, unable to read certificate-authority /etc/kubernetes/ssl/ca.pem for local due to open /etc/kubernetes/ssl/ca.pem: no such file or directory]

hongbin (hongbin034)
description: updated
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to magnum (master)

Fix proposed to branch: master
Review: https://review.openstack.org/352623

Changed in magnum:
assignee: nobody → hongbin (hongbin034)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to magnum (master)

Reviewed: https://review.openstack.org/352623
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=c82703932744eeeee4e13a2cbc4354b360f38c98
Submitter: Jenkins
Branch: master

commit c82703932744eeeee4e13a2cbc4354b360f38c98
Author: Hongbin Lu <email address hidden>
Date: Mon Aug 8 17:39:11 2016 -0500

    Fix an issue on kube-proxy in CoreOS bay

    On the kube-proxy container, mount the volume that contains the kube
    certs. Otherwise, kube-proxy cannot read the TLS certificates.

    Change-Id: I0f42208a1d8c24b66923b8be6bc72ba5c97d6b02
    Closes-Bug: #1611138

Changed in magnum:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/magnum 3.0.0

This issue was fixed in the openstack/magnum 3.0.0 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.