Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 15 results
    • What are the minimum Permissions needed for Trident Admin Users when using a SolidFire Backend?
      https://kb.netapp.com/Cloud/Astra/Trident/What_are_the_minimum_Permissions_needed_for_Trident_Admin_Users_when_using_a_SolidFire_Backend
      The minimum permissions required for the Trident Administrator User for SolidFire Backends are Accounts and Volumes. Account permissions are needed to read/set the CHAP credentials for the user accoun...The minimum permissions required for the Trident Administrator User for SolidFire Backends are Accounts and Volumes. Account permissions are needed to read/set the CHAP credentials for the user account. Example of Permissions for a Trident Admin within the Element UI under Users > Cluster Admins Cluster Admin is needed if you want trident to be able create the account for you if it doesn’t exist. How to update a SolidFire Backend to use a new Tenant account
    • Kubernetes cluster not visible in BlueXP when using cross projects
      https://kb.netapp.com/Cloud/BlueXP/Cloud_Tiering/Kubernetes_cluster_not_visible_in_BlueXP_when_using_cross_projects
      Applies to Google Kubernetes Engine (GKE) cluster in a Host Project for Shared VPC Google Service Project hosts the BlueXP connector and CVO BlueXP Connector has a service account attached to it Issue...Applies to Google Kubernetes Engine (GKE) cluster in a Host Project for Shared VPC Google Service Project hosts the BlueXP connector and CVO BlueXP Connector has a service account attached to it Issue GCP Kubernetes project not listed on GCP Blue XP connector for discovery Import of kubernetes's config yaml file also shows no API calls being run
    • Trident backend creation failed because of dns resolution
      https://kb.netapp.com/Cloud/Astra/Trident/Trident_backend_creation_failed_because_of_dns_resolution
      Request Method: POST Request URL: http://127.0.0.1:8000/trident/v1/backend Request headers: map[Content-Type:[application/json]] Request body: {"aggregate":"aggr_prod","backendName":"prod-backend","da...Request Method: POST Request URL: http://127.0.0.1:8000/trident/v1/backend Request headers: map[Content-Type:[application/json]] Request body: {"aggregate":"aggr_prod","backendName":"prod-backend","dataLIF":"k8sprod-data.example.coml","defaults":{"exportPolicy": "exportprodmi","spaceReserve":"volume"},"limitVolumeSize":"10Gi","managementLIF":"k8sprodmi-mgmt.example.com","password":"....", "storageDriverName":"ontap-nas","storagePrefix":"trident_","username":"vsadmin","version":1} ..............…
    • After ETCD database was restored in OpenShift, the Trident pods are not properly working
      https://kb.netapp.com/Cloud/Astra/Trident/After_ETCD_database_was_restored_in_OpenShift_the_Trident_pods_are_not_properly_working
      Applies to RedHat OpenShift 4.8 NetApp Astra Trident NetApp Ontap 9.X Issue After ETCD database was restored in OpenShift cluster, the Trident pods do not properly connect and are not working as expec...Applies to RedHat OpenShift 4.8 NetApp Astra Trident NetApp Ontap 9.X Issue After ETCD database was restored in OpenShift cluster, the Trident pods do not properly connect and are not working as expected
    • Trident etcd fails to initialize after a saltstack update: "panic: runtime error: makeslice: len out of range"
      https://kb.netapp.com/Cloud/Astra/Trident/Trident_etcd_fails_to_initialize_after_a_saltstack_update__panic__runtime_error__makeslice__len_out_of_range
      Applies to Trident for Kubernetes 19.04 and earlier Issue Recovery after a failure of the Kubernetes cluster nodes, had Trident still unable to initialize due to an error in etcd initialization: panic...Applies to Trident for Kubernetes 19.04 and earlier Issue Recovery after a failure of the Kubernetes cluster nodes, had Trident still unable to initialize due to an error in etcd initialization: panic: runtime error: makeslice: len out of range
    • LDAP authentication no longer working on SolidFire/HCI
      https://kb.netapp.com/on-prem/solidfire/Element_OS_Kbs/LDAP_authentication_no_longer_working_on_SolidFire_HCI
      Applies to All Element versions SolidFire clusters HCI clusters Trident Kubernetes (NKS) Issue no authentication with LDAP on SolidFire/HCI clusters no login on NKS cluster cannot provision new volume...Applies to All Element versions SolidFire clusters HCI clusters Trident Kubernetes (NKS) Issue no authentication with LDAP on SolidFire/HCI clusters no login on NKS cluster cannot provision new volumes with Trident
    • No space left on device when trying to write to a SolidFire storage volume
      https://kb.netapp.com/on-prem/solidfire/Element_OS_Kbs/No_space_left_on_device_when_trying_to_write_to_a_SolidFire_storage_volume
      Applies to NetApp SolidFire Storage Nodes NetApp H Series Storage Nodes When attempting to write to a SolidFire/HCI storage volume via Astra Trident, the following message is presented: buildcontainer...Applies to NetApp SolidFire Storage Nodes NetApp H Series Storage Nodes When attempting to write to a SolidFire/HCI storage volume via Astra Trident, the following message is presented: buildcontainer:Feb-21 14:02 /test/test1/src2/tmp$ touch hello touch: cannot touch 'hello': No space left on device Afterward, you have validated that the storage volume usage capacity is low as shown in the example below: Filesystem Size Used Avail Use% Mounted on
    • How to place trident-operator pod on specific nodes
      https://kb.netapp.com/Cloud/Astra/Trident/How_to_place_trident-operator_pod_on_specific_nodes
      Applies to NetApp Astra Trident Deploying Trident operator manually Description The node where trident-operator pod is placed is undefined by default. This article describes the procedure for placing ...Applies to NetApp Astra Trident Deploying Trident operator manually Description The node where trident-operator pod is placed is undefined by default. This article describes the procedure for placing trident-operator pod on specific nodes in the case of deploying Trident operator manually.
    • How to update a SolidFire Backend to use a new Tenant account
      https://kb.netapp.com/Cloud/Astra/Trident/How_to_update_a_SolidFire_Backend_to_use_a_new_Tenant_account
      Applies to NetApp Trident NetApp SolidFire Description This kb describes how to configure the NetApp SolidFire cluster and the Kubernetes cluster to use NetApp Trident
    • Trident mounts /dev/dm-N instead of /dev/mapper/mpathN
      https://kb.netapp.com/Cloud/Astra/Trident/Trident_mounts__dev_dm-N_instead_of__dev_mapper_mpathN
      Applies to NetApp Astra Trident Ubuntu ONTAP SAN driver iSCSI Multipathing Issue Volumes created via Trident have mount paths /dev/mapper/mpathN and /dev/dm-N coexisting Example: # df -h | grep /dev /...Applies to NetApp Astra Trident Ubuntu ONTAP SAN driver iSCSI Multipathing Issue Volumes created via Trident have mount paths /dev/mapper/mpathN and /dev/dm-N coexisting Example: # df -h | grep /dev /dev/mapper/mpathd 49G 76K 47G 1% /var/lib/kubelet/pods/[ID]/volumes/kubernetes.io~csi/pvc-[ID]/mount /dev/dm-1 30G 20G 8.7G 69% /var/lib/kubelet/pods/[ID]/volumes/kubernetes.io~csi/pvc-[ID]/mount /dev/dm-2 20G 4.2G 15G 23% /var/lib/kubelet/pods/[ID]/volumes/kubernetes.io~csi/pvc-[ID]/mount
    • PV is re-formatted when operating a rolling update for StatefulSet and moving nodes
      https://kb.netapp.com/Cloud/Astra/Trident/PV_is_re-formatted_when_operating_a_rolling_update_for_StatefulSet_and_moving_nodes
      Persistent Volume (PV) having a file system is reformatted when operating a rolling update for StatefulSet and moving nodes time="2020-07-19T03:25:40Z" level=debug msg="<<<< osutils.execCommandWithTim...Persistent Volume (PV) having a file system is reformatted when operating a rolling update for StatefulSet and moving nodes time="2020-07-19T03:25:40Z" level=debug msg="<<<< osutils.execCommandWithTimeout." time="2020-07-19T03:25:40Z" level=debug msg="Could not get FSType for device." time="2020-07-19T03:25:40Z" level=debug msg="Formatting LUN." time="2020-07-19T03:25:40Z" level=debug msg=">>>> osutils.formatVolume" device=/dev/dm-0 fsType=ext4