Skip to main content
NetApp Knowledge Base

PVC Provisioning Failure Over FC with NetApp Trident: Initiators Missing from FC igroup

  1. Last updated
  2. Save as PDF
Views:
65
Visibility:
Public
Votes:
0
Category:
trident-openshift
Specialty:
SNAPX
Last Updated:

Applies to

  • Astra Trident 24.10, 25.02
  • Red Hat OpenShift 4.18
  • Kubernetes 1.31
  • ONTAP-SAN driver (Fibre Channel protocol)

Issue

Persistent Volume Claims (PVCs) created via NetApp Trident in OpenShift remain in the “Pending” state and VMs fail to start. This affects only certain worker nodes, which cannot detect the mapped FC LUNs.
Relevant log output:

  • Trident logs: 
    igroup-create::Error: Initiator group already exists
lun-map::Success
Could not find FCP SCSI device: no devices present yet
failed to stage volume: no devices present yet
  • Storage audit logs: 
    igroupName: test.n1-test-01.test.test.itm-fcp-xxxx...
Initiators: (empty)
  • Pod events: 
    Warning FailedMapVolume: MapVolume.SetUpDevice failed for volume "pvc-xxxx": rpc error: code=Internal desc=failed to stage volume: no devices present yet

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.