
The kube-sriov-device-plugin pod will mount HostPath:'/var/lib/kubelet' If a pod mounting with rbd PVC is already running when kube-sriov-device-plugin pod starts up, the kube-sriov-device-plugin pod will refer to the rbd mountpoint which is under HostPath: '/var/lib/kubelet'. Even if the rbd is unmounted from the mountpoint on the host, the pod will keep referring to it in its namespace. So kubelet can't unmap the rbd and will fail to mount the volume when pod with rbd PVC is recreated. The kube-sriov-device-plugin doesn't need to use '/var/lib/kubelet' as mountpath because its internal device socket is actually at /var/lib/kubelet/device-plugins/. Changing the kube-sriov-device-plugin mountpath to a less broad path will preserve the rbd PVC mount point under /var/lib/kubelet/. Test plan PASS Installed AIO-SX create SRIOV interfaces create stateful pod with rbd PVC delete kube-sriov-device-plugin delete stateful pod A new stateful pod will automatically be created check if stateful pod was not stuck confirm if stateful pod could mount the volume PASS Create a SRIOV NetworkAttachmentDefinition Launch a POD using the SRIOV interface check if POD is running and if POD has connectivity. PASS Upgrades testing (partial) - verified controller-1 is upgraded and device plugin/pod working with new location. Closes-Bug: #2007596 Signed-off-by: Fabiano Mercer <fabiano.correamercer@windriver.com> Change-Id: I7ef43a1c0ac4f7f0af1a366c298b4c1029d3e915
stx-ansible-playbooks
StarlingX Bootstrap and Deployment Playbooks
Execution environment
- Unix like OS (recent Linux based distributions, MacOS, Cygwin)
- Python 2.7
Additional Required Packages
The playbooks in this repo have been verified with the following versions of Ansible and StarlingX playbooks dependencies:
- sshpass 1.06
- python2-ptyprocess 0.5
- python2-pexpect 4.6
- python2-netaddr 0.7
ansible
2.7.5
Supported StarlingX Releases
The playbooks in this repo are compatible with the following StarlingX releases:
- 20.01
Executing StarlingX Playbooks
Executing Bootstrap Playbook
Please refer to StarlingX Deployment Guides
, section
Configuration controller-0 of the respective system
configuration for instructions on how to set up and execute the
bootstrap playbook from another host.
References
Description
Languages
Jinja
70.4%
Python
21.3%
Shell
8.2%