rose hinge
Hey! , a customer is experiencing this issue ( https://kb.netapp.com/Cloud/Astra/Trident/After_upgrading_Trident_to_24_10_empty_export_policies_are_created_with_non_existing_rules )
But the are running version 25.02.1 ? so it seems that solution stating * 25.02 was released with a fix for this issue,* isn't working.
Anyone else seeing this problem ?
fringe gust
Please ask customer open a case with Support for investigation
eternal rain
I am facing the same issue. The export policy is created, however, no rules are created within the export-policy. I am running trident version 25.06.
nitish@wsdcmaster:~$ tridentctl version -n trident +----------------+----------------+ | SERVER VERSION | CLIENT VERSION | +----------------+----------------+ | 25.06.0 | 25.06.0 | +----------------+----------------+
`a300_R3::*> vol show -vserver svm_nfs -volume trident_pvc_b785fd23_2169_46d1_8563_e36cad845819 -fields policy
vserver volume policy
svm_nfs trident_pvc_b785fd23_2169_46d1_8563_e36cad845819 trident_pvc_b785fd23_2169_46d1_8563_e36cad845819
a300_R3::*> export-policy rule show -vserver svm_nfs -policyname trident_pvc_b785fd23_2169_46d1_8563_e36cad845819 -instance
There are no entries matching your query.
`
@rose hinge did you get any solution?
fringe gust
@eternal rain - this should work, you are on latest version. What version of ONTAP? I suggest opening a NetApp case for Trident team, due to there could be several factors. we can look at Trident logs and ASUP, etc... Meantime, Can you repro this on another volume? Was a pod created? What is pod status? is this new deployment, or existing? ie. when did last mount work successfully. Is the CIDR range correct in the Trident backend config for the node IPs in the cluster? Can you try a direct mount to the volume from the same node? a different node? (mount -t nfs <dataLIF.10.xxx.xxx.xxx>:/trident_pvc_b785fd23_2169_46d1_8563_e36cad845819 /data -vvv) what is the output? Have you tried updating the Trident backend or bouncing the trident controller and node pods? (these are too many steps to discuss in detail for this Discord channel).
queen hedge
hi, Trident moved to a "per volume" export policy management.
once a volume is mounted in a pod, you will see an export policy named after the volume uuid, and containing only the IP@ of the worker node(s) mounting this volume.