<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: NFS Share for vCD 10.2 what did change? in VMware vCloud Director Discussions</title>
    <link>https://communities.vmware.com/t5/VMware-vCloud-Director/NFS-Share-for-vCD-10-2-what-did-change/m-p/2845027#M12949</link>
    <description>&lt;P&gt;Hi! I don't know, what did change between 9 and 10, but I have 10.2 on my site. NFS is on Linux, volume is root:root, rights is 750 recursively.&lt;/P&gt;&lt;P&gt;Note: after vCloud Director fetches NFS share, rights to volume change to 1003:1002&lt;/P&gt;</description>
    <pubDate>Sun, 02 May 2021 06:49:44 GMT</pubDate>
    <dc:creator>Shin_Coldfire</dc:creator>
    <dc:date>2021-05-02T06:49:44Z</dc:date>
    <item>
      <title>NFS Share for vCD 10.2 what did change?</title>
      <link>https://communities.vmware.com/t5/VMware-vCloud-Director/NFS-Share-for-vCD-10-2-what-did-change/m-p/2842288#M12935</link>
      <description>&lt;P&gt;Hi all,&lt;BR /&gt;&lt;BR /&gt;What is the difference between an NFS Share for 9.x and 10.x?&lt;BR /&gt;&lt;BR /&gt;Because the same file share it works on 9.x implementations, but when I try to use it on 10.x I get:&lt;BR /&gt;&lt;BR /&gt;"Unexpected permissions on file /opt/vmware/vcloud-director/data/transfer/xyz while performing operation: touch xyz. Expected: root root 644. Found: root, root, 600"&lt;BR /&gt;&lt;BR /&gt;Used in a 9.7 and works without any issues.&lt;BR /&gt;&lt;BR /&gt;Here we have some notes about the NFS share in 10.2, but nothing specific for the right way to fix it.&lt;BR /&gt;&lt;A href="https://docs.vmware.com/en/VMware-Cloud-Director/10.2/VMware-Cloud-Director-Install-Configure-Upgrade-Guide/GUID-2DE7961A-59F0-4CC9-B8EA-0A6E90DF50EA.html" target="_blank"&gt;https://docs.vmware.com/en/VMware-Cloud-Director/10.2/VMware-Cloud-Director-Install-Configure-Upgrade-Guide/GUID-2DE7961A-59F0-4CC9-B8EA-0A6E90DF50EA.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;I have changed everything I can remember, but still can't put this share to work for vCD 10.2.&lt;BR /&gt;&lt;BR /&gt;Just for information: share was created in a QNAP as NFS Share.&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;&lt;BR /&gt;NW&lt;/P&gt;</description>
      <pubDate>Fri, 16 Apr 2021 17:23:42 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCloud-Director/NFS-Share-for-vCD-10-2-what-did-change/m-p/2842288#M12935</guid>
      <dc:creator>No_Way</dc:creator>
      <dc:date>2021-04-16T17:23:42Z</dc:date>
    </item>
    <item>
      <title>Re: NFS Share for vCD 10.2 what did change?</title>
      <link>https://communities.vmware.com/t5/VMware-vCloud-Director/NFS-Share-for-vCD-10-2-what-did-change/m-p/2845027#M12949</link>
      <description>&lt;P&gt;Hi! I don't know, what did change between 9 and 10, but I have 10.2 on my site. NFS is on Linux, volume is root:root, rights is 750 recursively.&lt;/P&gt;&lt;P&gt;Note: after vCloud Director fetches NFS share, rights to volume change to 1003:1002&lt;/P&gt;</description>
      <pubDate>Sun, 02 May 2021 06:49:44 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCloud-Director/NFS-Share-for-vCD-10-2-what-did-change/m-p/2845027#M12949</guid>
      <dc:creator>Shin_Coldfire</dc:creator>
      <dc:date>2021-05-02T06:49:44Z</dc:date>
    </item>
    <item>
      <title>Re: NFS Share for vCD 10.2 what did change?</title>
      <link>https://communities.vmware.com/t5/VMware-vCloud-Director/NFS-Share-for-vCD-10-2-what-did-change/m-p/2847482#M12953</link>
      <description>&lt;P&gt;Before 10.2 you set the nfs when deploying the ova. Now you have to set it after deploy into the configuration page.&lt;/P&gt;&lt;P&gt;There is a script called nfsValidate.py that checks nfs permissions and other things. It seems to be that there is a known issue with freenas/truenas.&lt;/P&gt;&lt;P&gt;You can bypass that file or you can try to set your nfs mount point in vcenter as follow:&lt;/P&gt;&lt;P&gt;1. Stop vcloud appliance&lt;/P&gt;&lt;P&gt;2. Go to vcloud appliance &amp;gt; configure &amp;gt; vapp options&amp;nbsp;&lt;/P&gt;&lt;P&gt;and set the property&amp;nbsp;&lt;SPAN&gt;vcloudapp.nfs_mount.VMware_vCloud_Director pointing to your nfs share&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 17 May 2021 13:31:32 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCloud-Director/NFS-Share-for-vCD-10-2-what-did-change/m-p/2847482#M12953</guid>
      <dc:creator>mouyaq</dc:creator>
      <dc:date>2021-05-17T13:31:32Z</dc:date>
    </item>
    <item>
      <title>Re: NFS Share for vCD 10.2 what did change?</title>
      <link>https://communities.vmware.com/t5/VMware-vCloud-Director/NFS-Share-for-vCD-10-2-what-did-change/m-p/2847493#M12954</link>
      <description>&lt;P&gt;Hi mouyaq,&lt;BR /&gt;&lt;BR /&gt;Thanks for your reply.&lt;BR /&gt;&lt;BR /&gt;Yes, it was on the configuration page that I get that issue.&lt;BR /&gt;&lt;BR /&gt;I will try your workaround and update this threat.&lt;BR /&gt;&lt;BR /&gt;PS: I had another test vCD and used a Synology without any issues.&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Mon, 17 May 2021 13:51:17 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCloud-Director/NFS-Share-for-vCD-10-2-what-did-change/m-p/2847493#M12954</guid>
      <dc:creator>No_Way</dc:creator>
      <dc:date>2021-05-17T13:51:17Z</dc:date>
    </item>
    <item>
      <title>Re: NFS Share for vCD 10.2 what did change?</title>
      <link>https://communities.vmware.com/t5/VMware-vCloud-Director/NFS-Share-for-vCD-10-2-what-did-change/m-p/2854999#M13018</link>
      <description>&lt;P&gt;There is a bug / inconsistency&amp;nbsp; in&amp;nbsp;nfsValidate.py&lt;/P&gt;&lt;P&gt;In order to fix it you have to change nfs username in script .&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Here is&amp;nbsp; problematic area:&lt;BR /&gt;&lt;BR /&gt;===========cut============&lt;/P&gt;&lt;P&gt;# verify that chmod'ed file has correct ownership and permissions&lt;BR /&gt;perms_test(TEST_FILE, 'root', 'root', response, '750')&lt;/P&gt;&lt;P&gt;# check that chown works&lt;BR /&gt;chown_test(TEST_FILE, response)&lt;BR /&gt;# verify that chown'ed file has correct ownership&lt;BR /&gt;perms_test(TEST_FILE, 'vcloud', 'vcloud', response) # don't check mode in this test&lt;/P&gt;&lt;P&gt;=======end of cut=============&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As you can see script calling sub "perms_test" with different username twice. So unless if your NFS server do not care about username this part will never pass the test. So I changed script to :&lt;/P&gt;&lt;P&gt;===========cut============&lt;/P&gt;&lt;P&gt;# verify that chmod'ed file has correct ownership and permissions&lt;/P&gt;&lt;P&gt;#perms_test(TEST_FILE, 'root', 'root', response, '750')&lt;/P&gt;&lt;P&gt;perms_test(TEST_FILE, 'vcloud', 'vcloud', response, '750')&lt;/P&gt;&lt;P&gt;# check that chown works&lt;BR /&gt;chown_test(TEST_FILE, response)&lt;BR /&gt;# verify that chown'ed file has correct ownership&lt;BR /&gt;perms_test(TEST_FILE, 'vcloud', 'vcloud', response) # don't check mode in this test&lt;/P&gt;&lt;P&gt;=======end of cut=============&lt;/P&gt;&lt;P&gt;and successfully deployed the nodes.&lt;BR /&gt;&lt;BR /&gt;You will ask why than primary node get deployed ? Answer is very simple , this subroutine never get called from primary node deployment routine.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;So I recommend vMware to test the code better to avoid such confusion.&lt;/P&gt;</description>
      <pubDate>Tue, 29 Jun 2021 12:40:51 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCloud-Director/NFS-Share-for-vCD-10-2-what-did-change/m-p/2854999#M13018</guid>
      <dc:creator>A_Shahoff</dc:creator>
      <dc:date>2021-06-29T12:40:51Z</dc:date>
    </item>
  </channel>
</rss>

