Closed deividfoggi closed 7 months ago
@deividfoggi Thanks for your feedback! We will investigate and update as appropriate.
@deividfoggi
Thank you for your feedback! I'd recommend working closer with our support team via an [Azure support request] (https://docs.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request). Or you can leverage our Q&A forum by posting your issue there so our community, and MVPs can further assist you in troubleshooting this issue or finding potential workarounds. [Teams Q&A forum] (https://docs.microsoft.com/en-us/answers/topics/46488/office-teams-windows-itpro.html) for technical questions about the configuration and administration of Microsoft Teams on Windows. [Microsoft Teams Community forum] (https://answers.microsoft.com/en-us/msteams/forum?sort=LastReplyDate&dir=Desc&tab=All&status=all&mod=&modAge=&advFil=&postedAfter=&postedBefore=&threadType=All&isFilterExpanded=false&page=1) Thank you for your time and patience throughout this issue.
đ¨ Looks like you arrived from the internal review site đ¨ Do not enter Microsoft confidential information here
When statically provisioning a nfs file share, no matter what mount options I use in the pv defintion, the following error happens. The only way to workaound is by removing all mount options from pv:
Is it really supported to pass mount options in the pv manifest?
Document Details
â Do not edit this section. It is required for learn.microsoft.com â GitHub issue linking.