[
https://issues.apache.org/jira/browse/CLOUDSTACK-1094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13578804#comment-13578804
]
Sheng Yang commented on CLOUDSTACK-1094:
----------------------------------------
It's purely guest OS bug.
For CentOS 6.2, I've figured out:
1. Set dhcpname=localhost.localdomain
2. Modify the /etc/sysconfig/network-scripts/ifup-post, search for
set_hostname, change the ip command above from:
ip -o -4 addr ls dev xxxx
to:
ip -o -6 addr ls dev xxxx
Would get centos the correct host name after reboot.
Obviously it's CentOS bug to only fetch the host name based on ipv4 address. I
don't think we can do anything about it.
> Ipv6 - hostname/hostname --fqdn does not return the name of the VM. But i am
> able to reach the Vm using their names.
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-1094
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1094
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: 4.1.0
> Environment: Build from ipv6 branch
> Reporter: Sangeetha Hariharan
> Assignee: Sheng Yang
> Fix For: 4.1.0
>
>
> Ipv6 - hostname/hostname --fqdn does not return the name of the VM. But i am
> able to reach the Vm using their names.
> Steps to reproduce the problem:
> Set up - Advanced Zone.
> Create a shared network using Ipv6 parameters.
> Deploy 2 Vms in this network.
> From within one VM, try to use hostname / hostname --fqdn command.
> hostname returned in this case does not reflect the name with which he Vm was
> deployed.
> But from another Vm in the same network , I am able to access this Vm using
> its name.
--
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
