Ask Your Question

kranthi.guttikonda9@gmail.com's profile - activity

2017-10-13 07:33:02 -0500 received badge  Nice Answer (source)
2017-04-12 16:19:30 -0500 commented answer How to customize libvirt.xml for an instance ?

Perfect, nova resize may fail while increasing the memory(RAM) with CPU pinning. Updated /usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py function _get_cpu_numa_config_from_instance with a if condition to match memory.

2017-02-11 04:45:49 -0500 received badge  Teacher (source)
2017-02-11 04:45:49 -0500 received badge  Necromancer (source)
2016-04-21 18:10:22 -0500 answered a question How to debug scripts at Heat's SoftwareConfig resource

Generally scripts and yaml will be fine. Sometimes VM doesn't resolve the controller(heat-cfn) host name which is metadata url. So, either try to resolve that(using script by appending values to /etc/hosts) or change heat_metadata_server_url in /etc/heat/heat.conf and restart heat-api and heat-engine services. Re-deploy the start again.

To debug Login to VM sudo os-collect-config --force --one-time --debug

Above will generate a dump. look for phase configure. Pasting the logs snippet below. Just FYI

[2016-04-21 22:52:56,011] (os-refresh-config) [INFO] Completed phase pre-configure [2016-04-21 22:52:56,012] (os-refresh-config) [INFO] Starting phase configure dib-run-parts Thu Apr 21 22:52:56 UTC 2016 Running /usr/libexec/os-refresh-config/configure.d/20-os-apply-config [2016/04/21 10:52:56 PM] [INFO] writing /var/run/heat-config/heat-config [2016/04/21 10:52:56 PM] [INFO] writing /etc/os-collect-config.conf [2016/04/21 10:52:56 PM] [INFO] success dib-run-parts Thu Apr 21 22:52:56 UTC 2016 20-os-apply-config completed dib-run-parts Thu Apr 21 22:52:56 UTC 2016 Running /usr/libexec/os-refresh-config/configure.d/55-heat-config [2016-04-21 22:52:56,440] (heat-config) [WARNING] Skipping config 02fbc622-7fb8-482d-8bc1-9f64d7a96c33, already deployed [2016-04-21 22:52:56,440] (heat-config) [WARNING] To force-deploy, rm /var/lib/heat-config/deployed/02fbc622-7fb8-482d-8bc1-9f64d7a96c33.json dib-run-parts Thu Apr 21 22:52:56 UTC 2016 55-heat-config completed

Check content present in /var/run/heat-config/heat-config, If it's empty look the metadata in /etc/os-collect-config.conf

This must exactly point where the issue is

2016-04-12 16:39:52 -0500 answered a question instance cant access internet

As per my understanding there is no VxLAN tunnel formed between endpoints (neutron and compute) with ports. Something like below

Port "vxlan-c0a80202" Interface "vxlan-c0a80202" type: vxlan options: {df_default="true", in_key=flow, local_ip="192.168.2.1", out_key=flow, remote_ip="192.168.2.2"} Port "vxlan-c0a80203" Interface "vxlan-c0a80203" type: vxlan options: {df_default="true", in_key=flow, local_ip="192.168.2.1", out_key=flow, remote_ip="192.168.2.3"}

Please double check ml2_conf.ini

2016-04-07 16:34:37 -0500 commented answer Heat Orchestration: Scale-down a specific instance

Never mind, I have made it working by creating another alarm. Earlier I was using "ok_actions" and scaledown_policy

2016-04-07 16:26:34 -0500 answered a question Heat Orchestration: Scale-down a specific instance

I have the same question. Even though the alarm state changes to OK, scaledown policy never delete a VM. Am I missing something here? Can someone help?

2015-11-12 12:05:21 -0500 commented answer Launching Instance failed

Provided link works no more. http://virtual2privatecloud.com/troubleshooting-openstack-nova/ (http://virtual2privatecloud.com/troub...)

I am having the same problem. Below is the error I am seeing from Nova logs

ERROR nova.compute.manager [-] Instance failed network setup after 1 attempt(s)

Can you please help me?