Start a Conversation

Unsolved

I

2 Posts

831

December 23rd, 2020 20:00

Vxflex CSI Issue: after CSI driver installation, CSI controller and CSI node stopped

Hi experts,

we have suffered a problem when tried to deploy CSI driver in customer's K8S environment.

After CSI driver installation, CSI controller and CSI node not started,  status is "stopped".  We don't know the failure reason yet. Hope you can help.

 

CSI Status was showing as below:

Status:

  Controller Status:

    Stopped:

      vxflexos-controller

  Driver Hash:  277878806

  Last Update:

    Condition:  Succeeded

    Time:       2020-12-22T04:48:04Z

  Node Status:

    Stopped:

      vxflexos-node

  State:  Succeeded

Events:  

 

Below are the details of CSI Status  :

 

# kubectl -n vxflexos describe csivxflexoses.storage.dell.com

Name:         vxflexos

Namespace:    vxflexos

Labels:      

Annotations:  storage.dell.com/CSIDriverConfigVersion: v3

              storage.dell.com/attacher.Image: k8s.gcr.io/sig-storage/csi-attacher:v3.0.0

              storage.dell.com/attacher.Image.IsDefault: true

              storage.dell.com/provisioner.Image: k8s.gcr.io/sig-storage/csi-provisioner:v2.0.2

              storage.dell.com/provisioner.Image.IsDefault: true

              storage.dell.com/registrar.Image: k8s.gcr.io/sig-storage/csi-node-driver-registrar:v2.0.1

              storage.dell.com/registrar.Image.IsDefault: true

              storage.dell.com/resizer.Image: quay.io/k8scsi/csi-resizer:v1.0.0

              storage.dell.com/resizer.Image.IsDefault: true

              storage.dell.com/snapshotter.Image: k8s.gcr.io/sig-storage/csi-snapshotter:v3.0.2

              storage.dell.com/snapshotter.Image.IsDefault: true

API Version:  storage.dell.com/v1

Kind:         CSIVXFlexOS

Metadata:

  Creation Timestamp:  2020-12-22T04:48:03Z

  Generation:          3

  Managed Fields:

    API Version:  storage.dell.com/v1

    Fields Type:  FieldsV1

    fieldsV1:

      f:spec:

        .:

        f:driver:

          .:

          f:common:

            .:

            f:envs:

            f:image:

            f:imagePullPolicy:

          f:configVersion:

          f:initContainers:

          f:replicas:

          f:snapshotClass:

    Manager:      kubectl

    Operation:    Update

    Time:         2020-12-22T04:48:03Z

    API Version:  storage.dell.com/v1

    Fields Type:  FieldsV1

    fieldsV1:

      f:metadata:

        f:annotations:

          .:

          f:storage.dell.com/CSIDriverConfigVersion:

          f:storage.dell.com/attacher.Image:

          f:storage.dell.com/attacher.Image.IsDefault:

          f:storage.dell.com/provisioner.Image:

          f:storage.dell.com/provisioner.Image.IsDefault:

          f:storage.dell.com/registrar.Image:

          f:storage.dell.com/regist

2 Intern

 • 

167 Posts

December 28th, 2020 02:00

Hi @iCece ,

Unfortunately we will need more logs. Please contact me in PM so we can exchange emails.

Rgds.

2 Posts

December 30th, 2020 17:00

Hi @Flo_csI ,

Thanks for your reply.

We have fixed this problem, due to the security policy set by customers in K8S node, the CSI node not work. After changed the policy, it works now.

However the installation guide did not clearly specify the required authorizations, so it takes some time to do the trouble shooting.

No Events found!

Top