Bug 1814441 - Kubelet throws "unable to read existing bootstrap client config" Error
Summary: Kubelet throws "unable to read existing bootstrap client config" Error
Keywords:
Status: CLOSED DUPLICATE of bug 1814433
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Windows Containers
Version: 4.5
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: 4.6.0
Assignee: vhire@redhat.com
QA Contact: gaoshang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-03-17 21:21 UTC by vhire@redhat.com
Modified: 2020-06-29 19:35 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-06-29 19:35:58 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description vhire@redhat.com 2020-03-17 21:21:43 UTC
Description of problem:
After bootstrapping the kubelet, the kubelet logs show errors

Version-Release number of selected component (if applicable):


How reproducible:
When Windows node is bootstrapped using WSU

Steps to Reproduce:
1. Create Windows Node
2.Run WSU
3.Open C:\k\kubelet.log

Actual results:
E0317 16:12:14.848142    4352 bootstrap.go:240] unable to read existing bootstrap client config: invalid configuration: [unable to read client-cert c:\var\lib\kubelet\pki\kubelet-client-current.pem for default-auth due to open c:\var\lib\kubelet\pki\kubelet-client-current.pem: The system cannot find the path specified., unable to read client-key c:\var\lib\kubelet\pki\kubelet-client-current.pem for default-auth due to open c:\var\lib\kubelet\pki\kubelet-client-current.pem: The system cannot find the path specified.]


Expected results:
No errors


Additional info:

Comment 1 Aravindh Puthiyaparambil 2020-05-18 15:29:12 UTC
This will be addressed by https://issues.redhat.com/browse/WINC-134

Comment 2 Aravindh Puthiyaparambil 2020-06-29 19:35:58 UTC

*** This bug has been marked as a duplicate of bug 1814433 ***


Note You need to log in before you can comment on or make changes to this bug.