kola/kubeadm: exclude azure platform #174
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tests are currently failing - we exclude them to take some time to properly identify the underlying issue. controller node spams a lot of FlexVolume related error: ```shell May 17 07:54:56.409708 kubelet[2807]: W0517 07:54:56.409706 2807 driver-call.go:149] FlexVolume: driver call failed: executable: /opt/libexec/kubernetes/kubelet-plugins/volume/exec/nodeagent~uds/uds, args: [init], error: fork/exec /opt/libexec/kubernetes/kubelet-plugins/volume/exec/nodeagent~uds/uds: no such file or directory, output: "" May 17 07:54:56.413207 kubelet[2807]: E0517 07:54:56.413152 2807 plugins.go:748] Error dynamically probing plugins: Error creating Flexvolume plugin from directory nodeagent~uds, skipping. Error: unexpected end of JSON input ``` and from the worker node: ```shell May 17 07:57:27.018416 kubelet[1483]: E0517 07:57:27.018373 1483 server.go:204] "Failed to load kubelet config file" err="failed to load Kubelet config file /var/lib/kubelet/config.yaml, error failed to read kubelet config file \"/var/lib/kubelet/config.yaml\", error: open /var/lib/kubelet/config.yaml: no such file or directory" path="/var/lib/kubelet/config.yaml" May 17 07:57:27.020692 systemd[1]: kubelet.service: Main process exited, code=exited, status=1/FAILURE May 17 07:57:27.020869 systemd[1]: kubelet.service: Failed with result 'exit-code'. ``` kubelet does not find its config, which means kubeadm does not properly join the cluster
pothos
approved these changes
May 17, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
tests are currently failing - we exclude them to take some time to
properly identify the underlying issue.
controller node spams a lot of FlexVolume related error:
May 17 07:54:56.409708 kubelet[2807]: W0517 07:54:56.409706 2807 driver-call.go:149] FlexVolume: driver call failed: executable: /opt/libexec/kubernetes/kubelet-plugins/volume/exec/nodeagent~uds/uds, args: [init], error: fork/exec /opt/libexec/kubernetes/kubelet-plugins/volume/exec/nodeagent~uds/uds: no such file or directory, output: "" May 17 07:54:56.413207 kubelet[2807]: E0517 07:54:56.413152 2807 plugins.go:748] Error dynamically probing plugins: Error creating Flexvolume plugin from directory nodeagent~uds, skipping. Error: unexpected end of JSON inputand from the worker node:
kubelet does not find its config, which means kubeadm does not properly
join the cluster
an issue has been opened to track this: flatcar/Flatcar#399