-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Volumes created with ontap-nas may not be mountable right away when load-sharing mirrors are in use #84
Comments
I would be curious to see the entries made to the nDVP log and the internal mgt log of the cluster to check and compare timings. For the nDVP logs check here how to get them. For the cluster logs check here on how to get them. The specific logfile to look at is Once you have access to both logs then (1) create a volume and then (2) check both logs and reply to this issue with the details. In my lab I did the above steps and from the cluster logs the I hope with the logs we can see what is going on. Thanks! |
At the moment of mounting, this was the logging @ nDVP.log:
Ill come back to you with the storage logging. |
@dutchiechris uploaded to NetApp FTP, Scott Stanton will move it if i am correct. |
As we discussed on Slack, this appears to be caused by the use of load-sharing mirrors, which means that new volumes appear in the namespace based on a snapshot schedule. This will only be an issue with the 'ontap-nas' driver. There are multiple potential solutions that would get us closer to the desired behavior: the volume is ready to be mounted as soon as the create operation returns. We'll investigate. Thanks for the report! |
Hi,
As discussed with the team on slack today, the following issue:
tl;dr: Create a post-creation check to verify if a volume exists before starting the container who uses it.
We have a single test filer for running PoCs. We run NetApp ONTAP 9, Docker 1.13 & The latest nDVP plugin. When we perform a "Docker volume create" towards the netapp storage driver, the volume is not directly available on the filer, possibly because of a configured advertisement delay on our configuration.
[root@vm~]# docker volume create -d netapp --name=netappslack2
netappslack2
netapp:latest netappslack2
showmount gives /netappdvp_netappslack2 (everyone)
[root@vm~]# mount .99:/netappdvp_netappslack2 test
mount.nfs: mounting .99:/netappdvp_netappslack2 failed, reason given by server: No such file or directory
Yet, containers expect the volume to be there for writing data. Now, the container starts and exits directly using status 32, saying the "file or directory is not available".
Waiting a few minutes, around 4, we perform the docker run again using the created volume. Then, it works fine and mounts the volume.
[root@VM~]# docker run --rm -it -v netappslack2:/take2 alpine ash
/ #
The text was updated successfully, but these errors were encountered: