Red Hat Bugzilla – Bug 1596439
[starter-ca-central-1] node cannot recover when volume-config.yaml corrupted
Last modified: 2018-10-11 03:21:19 EDT
Description of problem: It is not clear when this file was corrupted on the node in question, but once it was, the node was unable to bootstrap itself any longer. When analyzed, the volume-config.yaml file was empty and journal entries for atomic-openshift-node reported the fatal error: Jun 29 00:55:52 ip-172-31-24-47.ca-central-1.compute.internal atomic-openshift-node[7997]: F0629 00:55:52.167998 7997 server.go:218] Local quota setup failed: expected kind "VolumeConfig" and apiVersion "kubelet.config.openshift.io/v1" for volume config file Version-Release number of selected component (if applicable): v3.10.7 Expected result: If an error/interruption of the sync process can leave this file empty, it should not be treated as an error.
The sync pod should keep this file up to date. Is the configmap key also empty?
Origin master PR: https://github.com/openshift/origin/pull/20154
Checked with # oc version oc v3.11.0-0.25.0 kubernetes v1.11.0+d4cacc0 features: Basic-Auth GSSAPI Kerberos SPNEGO Server https://qe-wjiang-master-etcd-1:8443 openshift v3.11.0-0.25.0 kubernetes v1.11.0+d4cacc0 Atomic-openshift-node can start with a empty /etc/origin/node/volume-config.yaml now.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:2652