Kubespray: Issue with FlexVolume

Created on 15 Sep 2018  路  7Comments  路  Source: kubernetes-sigs/kubespray

Is this a BUG REPORT or FEATURE REQUEST?: Bug

Environment:

  • Cloud provider or hardware configuration: Local Ubuntu 16.04 Server
  • OS (printf "$(uname -srm)\n$(cat /etc/os-release)\n"):

NAME="Ubuntu"
VERSION="16.04.4 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.4 LTS"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial

  • Version of Ansible (ansible --version):

ansible 2.0.0.2
config file = /etc/ansible/ansible.cfg
configured module search path = Default w/o overrides

Network plugin used:

Calico

We ran the standard ansible install command listed on Git (ansible-playbook -i inventory/mycluster/hosts.ini cluster.yml)

Now we are trying to deploy a FlexVolume plugin using the standard directory structure (/var/lib/kubelet/volume-plugins/) but when trying to use it, we get the following message:

Sep 14 22:47:29 kubegcp1 kubelet[30625]: E0914 22:47:29.886471 30625 desired_state_of_world_populator.go:286] Failed to add volume "jukefs" (specName: "jukefs-volume") for pod "0471a781-b870-11e8-85b4-0a96da0bad82" to desiredStateOfWorld. err=failed to get Plugin from volumeSpec for volume "jukefs-volume" err=no volume plugin matched

Any ideas?

lifecyclrotten

Most helpful comment

@dkozlov , I successfuly used agent.flexVolumeDirPath previously with kubernetes 1.10.4. During upgrade to 1.13.1 I've seen error messages like "err=no volume plugin matched" and kube-controller-manager was configured to use default path instead of custom one.

All 7 comments

+1

It's easier to use default path /usr/libexec/kubernetes/kubelet-plugins/volume/exec/. Otherwise it should be set for kubelet, kube-controller-manager and storage provider (in my case - rook operator and it's agent)

@DXist it is really strange because in https://github.com/kubernetes-sigs/kubespray/releases/tag/v2.7.0 I was managed to provide --set agent.flexVolumeDirPath=/var/lib/kubelet/volume-plugins/ and it was enough.

Now in https://github.com/kubernetes-sigs/kubespray/releases/tag/v2.8.1 it is not working and I need to change kubelet_flexvolumes_plugins_dir: /usr/libexec/kubernetes/kubelet-plugins/volume/exec in https://github.com/kubernetes-sigs/kubespray/blob/master/roles/kubernetes/node/defaults/main.yml

@dkozlov , I successfuly used agent.flexVolumeDirPath previously with kubernetes 1.10.4. During upgrade to 1.13.1 I've seen error messages like "err=no volume plugin matched" and kube-controller-manager was configured to use default path instead of custom one.

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Was this page helpful?
0 / 5 - 0 ratings