[
https://issues.apache.org/jira/browse/CLOUDSTACK-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13636978#comment-13636978
]
ASF subversion and git services commented on CLOUDSTACK-1004:
-------------------------------------------------------------
Commit b888450ec803d7d61b2c30c3528b305e26ce1fb4 in branch refs/heads/master
from [~jzb]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=b888450 ]
CLOUDSTACK-1004: Adding fqdn info to NFS setup instructions. Why this should be
necessary puzzles me.
> add to install guide: fqdn required when adding secondary storage
> ------------------------------------------------------------------
>
> Key: CLOUDSTACK-1004
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1004
> Project: CloudStack
> Issue Type: Improvement
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Doc
> Reporter: Noa Resare
> Assignee: Radhika Nair
> Priority: Minor
>
> I set up a fresh test install of cloudstack 4.0 now and ran into some
> problems. It turned out that the secondary storage VM could not mount the
> secondary storage via NFS because the NFS URI configured when setting up the
> zone only held the hostname and not hostname plus fully qualified domain
> name.
> This worked fine when testing mounts form the hypervisors (that had a
> properly configured search path) but the secondary storage VM doesn't have
> it's domain configured to match the rest of the machines, so secondary
> storage operation failed.
> The error I got in the logfile was kind of unhelpful when tracking down this,
> so a brief note in the installation instruction would have been nice.
> I propose we change item 11 of section 6.2.2 of the installation instruction,
> replacing "The IP address of the server" with "The IP address or fully
> qualified hostname of the server. Please note that only the hostname will not
> work, as the secondary storage VM will not be able to properly resolve the
> hostname"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
