After Vol Clone Export Policy Doesn't Work

[west widget]

I have a weird issue that only occurs on my production NetApp. If I clone a FlexVol and then create a new export policy for the cloned volume, the host in that new policy can't mount any volumes. The showmount command from the host has the new mount. I can ping the NFS server. Telnet works on port 2049. All of the hosts added to the export have working forward and reverse DNS. I am not sure why creating a new export policy for the cloned volume causes this problem.

I created a new policy because the existing policy for the source volume has hosts that will not need or have access to the new cloned volume. Am I missing something? ONTAP 9.13.1

[uncut osprey]

is the host for the new volume also allowed to access the root volume? i.e. is your namespace root's export policy exporting to that host?

usually you have something like -clientmatch 0.0.0.0/0 -rorule sys -rwrule never in your root volume's export policy

I assume you did specify a -junction-path when cloning the volume, because otherwise you also cannot access it, but that's rather obvious

[west widget]

I have to check, but I realize if I add my host to the export policy I also can't mount, I just receive a "permisisons denied" error.

[west widget]

I tried the cli again and made sure to use -junction-active true -foreground true but when I go mount the volume and use a new policy I create, still no luck.

I clone the volume. Create new export policy. Make sure the volume is using the new policy. Mount volume. Add host to export. That should be pretty staight forward.

Are you saying if I have a host called "A", it has to be in the root volume export policy as well as the new one? If so, I already did that as well. No success.

[west widget]

I have deleted and recreated the volume clone several times and still no luck.