You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Abhinandan Prateek (JIRA)" <ji...@apache.org> on 2013/08/17 05:18:47 UTC
[jira] [Reopened] (CLOUDSTACK-4132) current dnsmasq config does not
allow guest virtual machines(clients) to update its hostnames with a DNS
server
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Abhinandan Prateek reopened CLOUDSTACK-4132:
--------------------------------------------
ERROR [utils.ssh.SshHelper] (DirectAgent-149:10.223.73.2) SSH execution of command /root/edithosts.sh -m 06:90:3a:00:00:11 -4 10.223.73.55 -h blank3 -d 10.223.73.1 -n 10.223.73.53 has an error status code in return. result output:
ERROR [vmware.resource.VmwareResource] (DirectAgent-149:10.223.73.2) dhcp_entry command on domR 10.223.73.53 failed, message:
INFO [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-14:job-14 = [ 64c3f28d-afd9-41a6-98fc-9b5e2acc6f27 ]) Unable to contact resource.
com.cloud.exception.ResourceUnavailableException: Resource [Pod:1] is unreachable: Unable to apply dhcp entry on router
I tried to run this command by ssh to the VR:
/bin/bash -x /root/edithosts.sh -m 06:44:32:00:00:0e -4 10.223.73.52 -h blank -d 10.223.73.1 -n 10.223.73.53
It gave me "timed out waiting for dnsmasq to start".
Manually start dnsmasq on VR gave me error " bad option at line 634 of /etc/dnsmasq.conf", that line is "dhcp-client-update".
> current dnsmasq config does not allow guest virtual machines(clients) to update its hostnames with a DNS server
> ----------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-4132
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4132
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Virtual Router
> Affects Versions: 4.2.0
> Reporter: Ram Ganesh
> Assignee: Bharat Kumar
> Priority: Critical
> Fix For: 4.2.0
>
>
> Current dnsmasq.conf does not have "dhcp-client-update" flag enabled thereby preventing say Windows clients to update AD servers with its hostname. We should enhance the config file to support this. More information about this parameter can be found here - http://www.thekelleys.org.uk/dnsmasq/docs/dnsmasq-man.html
--
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