You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Bharat Kumar (JIRA)" <ji...@apache.org> on 2013/05/22 07:43:19 UTC
[jira] [Updated] (CLOUDSTACK-2606) [Multiple_IP_Ranges]Syntax error
in dnsmasq config file
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bharat Kumar updated CLOUDSTACK-2606:
-------------------------------------
Assignee: Bharat Kumar
> [Multiple_IP_Ranges]Syntax error in dnsmasq config file
> -------------------------------------------------------
>
> Key: CLOUDSTACK-2606
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2606
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Management Server
> Affects Versions: 4.2.0
> Environment: Latest build from master branch: CloudStack-non-OSS-MASTER-389-rhel6.3.tar.gz
> Reporter: Sanjeev N
> Assignee: Bharat Kumar
> Priority: Blocker
> Fix For: 4.2.0
>
>
> Syntax error in dnsmasq config file while deploying vm in a new subnet
> Steps to Reproduce:
> =================
> 1.Bring up CS in basic zone with xen61 server.
> 2.Add guest ip range in a different cidr compared to what was given during zone deployment.
> 3.Try to deploy vm using the ip address from new cidr
> Expected Result:
> ==============
> When CS tries to deploy guest vm with the ip from new CIDR an ip alias should be created on domR and dnsmosq conf should be updated with new cidr info and dnsmasq should be reloaded.
> Actual Result:
> ============
> On domR ip alias was created but observed syntax error in dnsmasq.conf file due to which dnsmosq reload failed and vm deployment also failed.
> Observations:
> ===========
> Log snippet from SMlog on xenserver:
> [11043] 2013-05-21 10:58:12.504281 ['bin/bash', '/opt/xensource/bin/createipAlias.sh', '169.254.2.135', '18:10.147.43.132:255.255.255.192-']
> [11043] 2013-05-21 10:58:12.672381 #### VMOPS exit createipAlias ####
> [11069] 2013-05-21 10:58:12.885267 #### VMOPS enter createFileInDomr ####
> [11069] 2013-05-21 10:58:12.885349 ['mktemp']
> [11069] 2013-05-21 10:58:12.893460 pread SUCCESS
> [11069] 2013-05-21 10:58:12.893615 ['scp', '-P', '3922', '-q', '-o', 'StrictHostKeyChecking=no', '-i', '/root/.ssh/id_rsa.cloud', '/tmp/tmp.wFgGq11070', 'root@169.254.2.135:/tmp/169-254-2-135.cfg']
> [11069] 2013-05-21 10:58:13.023282 pread SUCCESS
> [11069] 2013-05-21 10:58:13.023388 ['rm', '/tmp/tmp.wFgGq11070']
> [11069] 2013-05-21 10:58:13.031616 pread SUCCESS
> [11069] 2013-05-21 10:58:13.031712 #### VMOPS exit createFileInDomr ####
> [11076] 2013-05-21 10:58:13.148401 #### VMOPS enter configdnsmasq ####
> [11076] 2013-05-21 10:58:13.148491 ['ssh', '-p', '3922', '-q', '-o', 'StrictHostKeyChecking=no', '-i', '/root/.ssh/id_rsa.cloud', 'root@169.254.2.135', '/root/dnsmasq.sh', '/tmp/169-254-2-135.cfg']
> [11076] 2013-05-21 10:58:13.332322 FAILED in util.pread: (rc 2) stdout: '/tmp/169-254-2-135.cfg
> Restarting DNS forwarder and DHCP server: configuration syntax check failed!
> could not configure dnsmasq
> reverting to the old config
> Restarting DNS forwarder and DHCP server: configuration syntax check failed!
> ', stderr: '+ cp /etc/dnsmasq.conf /etc/dnsmasq.conf.bak
> + echo /tmp/169-254-2-135.cfg
> + cp /tmp/169-254-2-135.cfg /etc/dnsmasq.conf
> + service dnsmasq restart
> + result=1
> + '[' 1 -ne 0 ']'
> + echo 'could not configure dnsmasq'
> + echo 'reverting to the old config'
> + cp /etc/dnsmasq.config.bak /etc/dnsmasq.conf
> cp: cannot stat `/etc/dnsmasq.config.bak': No such file or directory
> + service dnsmasq restart
> + exit 2
> '
> [11076] 2013-05-21 10:58:13.332471 failed to config dnsmasq server
> 2.Ran dnsmasq --test on dnsmasq.conf file and found syntax error
> dhcp-option=6,10.103.128.16,10.103.128.16,*
> Syntax check on dnsmasq.conf failed because of the * at the end of the line and failed to load the config.
--
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