Data lifs were not defined in the Trident backend configuration, so they are detected automatically by Trident Defined new IP addresses for lifs in an ontap SVM New pods can properly mount PVCs using ...Data lifs were not defined in the Trident backend configuration, so they are detected automatically by Trident Defined new IP addresses for lifs in an ontap SVM New pods can properly mount PVCs using the new lifs Pods created before the changes, can't access the new lifs defined in the SVM and having mount issues with the following error: Unable to attach or mount volumes: unmounted volumes=[<nameofPVC>], unattached volumes=[], failed to process volumes=[]: timed out waiting for the condition
NetApp Astra Trident RedHat Openshift cluster (OCP) After installing Trident in a kubernetes cluster, the Trident pods do not reach running status and getting issues to be assigned to kubernetes nodes...NetApp Astra Trident RedHat Openshift cluster (OCP) After installing Trident in a kubernetes cluster, the Trident pods do not reach running status and getting issues to be assigned to kubernetes nodes: Warning FailedScheduling xmys (x155 over 13h) default-scheduler 0/9 nodes are available: 1 node(s) didn't match Pod's node affinity/selector. preemption: 0/9 nodes are available: 1 Preemption is not helpful for scheduling, 8 node(s) didn't match Pod's node affinity/selector
