[jira] [Commented] (CLOUDSTACK-1094) Ipv6 - hostname/hostname --fqdn does not return the name of the VM. But i am able to reach the Vm using their names.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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 to: ip -o -6 addr ls dev 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
[jira] [Commented] (CLOUDSTACK-1094) Ipv6 - hostname/hostname --fqdn does not return the name of the VM. But i am able to reach the Vm using their names.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13578811#comment-13578811 ] Sheng Yang commented on CLOUDSTACK-1094: In Ubuntu 12.10, /sbin/dhclient-scripts didn't have code to deal with ipv6 received hostname at all. It would only deal with ipv4, which is the same as CentOS 6.2 Probably we would just report bug to Ubuntu/CentOS community for this. Mark the bug as won't fix. 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
[jira] [Commented] (CLOUDSTACK-1094) Ipv6 - hostname/hostname --fqdn does not return the name of the VM. But i am able to reach the Vm using their names.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-1094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13566961#comment-13566961
]
Sheng Yang commented on CLOUDSTACK-1094:
Seems the dhclient already got hostname from dhcp server, but didn't apply it
to the environment. That must be related to how guest os works...
lease6 {
interface eth0;
ia-na f0:00:00:38 {
starts 1359580216;
renew 3600;
rebind 6300;
iaaddr fc00:3:1610::aff:fea5:6a7f {
starts 1359580216;
preferred-life 7200;
max-life 7200;
}
option dhcp6.status-code success Oh hai from dnsmasq;
}
option fqdn.encoded true;
option fqdn.server-update true;
option fqdn.no-client-update false;
option fqdn.fqdn centso62.cs1cloud.internal;
option fqdn.hostname centso62;
option fqdn.domainname .cs1cloud.internal;
option dhcp6.client-id 0:3:0:1:6:a0:f0:0:0:38;
option dhcp6.server-id 0:1:0:1:18:9c:36:60:6:ad:9c:0:0:35;
option dhcp6.name-servers fc00:3:1610::aff:fea5:6a93;
}
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
