vsphere integrator creates but never binds volume
Bug #1847809 reported by
Chris Carver
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
CDK Addons |
Triaged
|
Medium
|
Unassigned | ||
Kubernetes Control Plane Charm |
Triaged
|
Medium
|
Unassigned | ||
vSphere Integrator Charm |
Triaged
|
Medium
|
Unassigned |
Bug Description
Juju version: 2.6.9-bionic-amd64
K8s version: 1.16.1
vSphere: 6.7 U3
Using K8s 1.16, the vSphere integrator creates the volumes on the specified datastore but the volumes are never bound, thus leaving the PVC in a "pending" state. Using the "kubectl describe pvc" command does not show any errors.
description: | updated |
Changed in charm-vsphere-integrator: | |
status: | Incomplete → New |
Changed in cdk-addons: | |
importance: | Undecided → Medium |
Changed in charm-kubernetes-master: | |
importance: | Undecided → Medium |
Changed in charm-vsphere-integrator: | |
importance: | Undecided → Medium |
Changed in cdk-addons: | |
status: | New → Triaged |
Changed in charm-kubernetes-master: | |
status: | New → Triaged |
Changed in charm-vsphere-integrator: | |
status: | New → Triaged |
To post a comment you must log in.
Hi, thanks for the bug report.
When reporting a Charmed Kubernetes problem, please run juju-crashdump and include the resulting tarball as an attachment to your bug. To run juju-crashdump:
sudo snap install juju-crashdump --channel edge --classic
juju-crashdump -a debug-layer -a config