[
https://issues.apache.org/jira/browse/CLOUDSTACK-9368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15286834#comment-15286834
]
ASF GitHub Bot commented on CLOUDSTACK-9368:
--------------------------------------------
Github user swill commented on the pull request:
https://github.com/apache/cloudstack/pull/1518#issuecomment-219754000
I am having a hard time testing this because I can't seem to get the
templates to become ready using this PR. My CI ran all night last night and
this morning it was still waiting for the templates to be ready. I just did
another run and I am stuck at the same place.
```
http://localhost:8096/client/api?command=listTemplates&templatefilter=all&response=json
Tue May 17 17:17:16 2016 At least template 'tiny linux kvm' is not Ready
```
I am not seeing any errors in the `jetty.log`, so I am not sure what is
going on here...
> Fix for Support configurable NFS version for Secondary Storage mounts
> ---------------------------------------------------------------------
>
> Key: CLOUDSTACK-9368
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9368
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: VMware
> Affects Versions: 4.9.0
> Reporter: Nicolas Vazquez
> Fix For: 4.9.0
>
>
> This issue address a problem introduced in
> [CLOUDSTACK-9252|https://issues.apache.org/jira/browse/CLOUDSTACK-9252] in
> which NFS version couldn't be changed after hosts resources were configured
> on startup (for hosts using `VmwareResource`), and as host parameters didn't
> include `nfs.version` key, it was set `null`.
> h4. Proposed solution
> In this proposed solution `nfsVersion` would be passed in `NfsTO` through
> `CopyCommand` to `VmwareResource`, who will check if NFS version is still
> configured or not. If not, it will use the one sent in the command and will
> set it to its storage processor and storage handler. After those setups, it
> will proceed executing command.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
