[
https://issues.apache.org/jira/browse/CLOUDSTACK-8668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14640389#comment-14640389
]
Kishan Kavala commented on CLOUDSTACK-8668:
-------------------------------------------
VR Config file:
#Apache CloudStack Virtual Router Config File <version>
1.0
</version>
<file>
/var/cache/cloud/monitor_service.json
{"config":"[dhcp]:processname=dnsmasq:servicename=dnsmasq:pidfile=/var/run/dnsmasq/dnsmasq.pid:,[ssh]:processname=sshd:servicename=ssh:pidfile=/var/run/sshd.pid:,[webserver]:processname=apache2:servicename=apache2:pidfile=/var/run/apache2.pid:,","type":"monitorservice"}
</file>
<script>
/opt/cloud/bin/update_config.py monitor_service.json </script>
/var/log/cloud.log:
2015-07-24 09:29:28,997 Loading data bag type monitorservice
2015-07-24 09:29:28,998 Command of type monitorservice received
2015-07-24 09:29:28,999 Writing data bag type monitorservice
2015-07-24 09:29:28,999 Creating data bag type ips
2015-07-24 09:29:28,999 Loading data bag type cmdline
2015-07-24 09:29:29,000 Executing ip addr show dev eth1
2015-07-24 09:29:29,019 Will remove all configured addresses on device eth1
2015-07-24 09:29:29,019 Removing addresses from device eth1
2015-07-24 09:29:29,036 Removed address 169.254.2.130/16 from device eth1
2015-07-24 09:29:29,056 Removed address 169.254.2.130/16 from device eth1
2015-07-24 09:29:29,057 Executing ip addr show dev eth0
2015-07-24 09:29:29,075 Will remove all configured addresses on device eth0
2015-07-24 09:29:29,076 Removing addresses from device eth0
2015-07-24 09:29:29,093 Removed address 10.220.39.131/19 from device eth0
2015-07-24 09:29:29,112 Removed address 10.220.39.131/19 from device eth
> VR does not start in basic zone since ip address are not being configured on
> it
> -------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-8668
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8668
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Network Controller
> Affects Versions: 4.6.0
> Environment: Latest build from ACS master
> Reporter: Sanjeev N
> Priority: Blocker
>
> VR does not start in basic zone since ip address are not being configured on
> it
> Steps to reproduce:
> ================
> 1.Bring up CS in basic zone with xen server cluster
> 2.Try to deploy one guest vm using default cent os template
> Expected Result:
> ==============
> VR should come up as part of vm deployment and vm deployment should be
> successfull
> Actual Result:
> ============
> VR creation failed since the IP addresses not are getting assigned to VR's
> guest and link local interfaces.
> Observations:
> ===========
> 1.During vr boot time, cloud-early-config ran successfully and VR console
> output showed that ping to gateway was successful. However, after VR boot we
> don't see any ip addresses on the VRs guest and link local ip address.
> 2. If we run cloud-early-config manually from VR , ip addresses will be
> assigned and persistent.
> Impact:
> =====
> VM deployments will fail since VR remains in stopped state.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
