Volume still in mounted=true state after pod has volume unmounted

[storageos]

Volume still in mounted=true state after pod has volume unmounted

[avestuk]

@robinbraemer What Kubernetes version are you running and are you using the CSI driver or the native driver?

[robinbraemer]

I have cluster.csi.enable enabled

I've added k8s version output to the main post

[avestuk]

@robinbraemer Thanks. Could you share your volume definition as well please? I'm a little thrown by the way the volume is being referenced in your pod definition. Typically volumes would be created as a persistentVolumeClaim and referenced that way.

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: pvc-1
  annotations:
    volume.beta.kubernetes.io/storage-class: fast
spec:
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 5Gi
---
apiVersion: v1
kind: Pod
metadata:
  name: d1
spec:
  terminationGracePeriodSeconds: 0
  containers:
    - name: debian
      image: debian:9-slim
      command: ["/bin/sleep"]
      args: [ "3600" ]
      volumeMounts:
        - mountPath: /mnt
          name: v1
  volumes:
    - name: v1
      persistentVolumeClaim:
        claimName: pvc-1

The storageos secret doesn't need to be referenced when using CSI as Kubernetes-StorageOS communication takes place using a socket rather than the StorageOS API.

[robinbraemer]

storageos volume inspect myserver/storageos-volume-test
[
    {
        "id": "e9b35e50-c4ed-437f-0788-bafb00db5c34",
        "inode": 166852,
        "name": "storageos-volume-test",
        "size": 10,
        "pool": "default",
        "fsType": "ext4",
        "description": "",
        "labels": {},
        "namespace": "myserver",
        "nodeSelector": "",
        "master": {
            "id": "3f031683-07eb-4685-aaeb-c1d36cc882ba",
            "inode": 215525,
            "node": "f0421320-47d7-a151-ebcc-772d3b32338a",
            "nodeName": "node-2",
            "health": "healthy",
            "status": "active",
            "createdAt": "2019-06-11T12:11:29.792952171Z"
        },
        "mounted": true,
        "mountDevice": "/var/lib/kubelet/plugins/kubernetes.io~storageos/devices/e9b35e50-c4ed-437f-0788-bafb00db5c34",
        "mountpoint": "/var/lib/kubelet/plugins/kubernetes.io~storageos/mounts/vol.myserver.storageos-volume-test",
        "mountedAt": "2019-06-11T12:11:40.280076862Z",
        "mountedBy": "node-2",
        "replicas": [],
        "health": "healthy",
        "status": "active",
        "statusMessage": "",
        "mkfsDone": true,
        "mkfsDoneAt": "2019-06-11T12:11:40.280077636Z",
        "createdAt": "2019-06-11T12:11:29.773546695Z",
        "createdBy": "storageos"
    }
]

When I'm not referencing the secret in the pod the pod cannot start

FailedMount |
MountVolume.SetUp failed for volume "vol" : API error (Unauthenticated access of secure endpoint, please retry after authentication): Invalid username/password

[avestuk]

Hi @robinbraemer sorry could you share the Kubernetes volume definition?

Also could you show me what StorageOS pods you've got running? The API is only used when the native driver is used. CSI uses a socket for Kubernetes-StorageOS communication so the secret is only required to create a username/password for the StorageOS GUI/CLI.

[robinbraemer]

Sorry, I misunderstood something. Closing