Ask Your Question

pernacentus's profile - activity

2015-01-22 05:03:36 -0500 commented question segfault in nova.compute when deleting instances

No, it occurs on every compute node. Just to add more details, I deployed Openstack on each compute node by using Devstack. Here you can find more log entries related to nova: http://paste.openstack.org/show/160204/

2015-01-20 16:07:52 -0500 commented question segfault in nova.compute when deleting instances

My compute agent is running on a physical server equipped with 2 16-cores AMD processors and 32GB of RAM. More than 20% of RAM was free when this error came out.

2015-01-18 04:38:37 -0500 commented question segfault in nova.compute when deleting instances

I'm still having this issue. Again, is anyone experiencing this problem?

2015-01-18 04:38:26 -0500 received badge  Famous Question (source)
2014-11-25 16:57:57 -0500 received badge  Notable Question (source)
2014-11-25 03:59:52 -0500 answered a question segfault in nova.compute when deleting instances

I'm still having this issue. Again, is anyone experiencing this problem?

2014-11-04 08:51:14 -0500 received badge  Popular Question (source)
2014-10-31 04:31:11 -0500 received badge  Enthusiast
2014-10-29 09:20:17 -0500 asked a question segfault in nova.compute when deleting instances

I'm running Icehouse atop Ubuntu server 12.04. I notice a very strange behaviour when I delete multiple vm instances. In fact, instances are kept in deleting state. By trying to analyze the problem, I found out that nova-compute, because of a segmentation fault error, was not running on the nodes containing the vms I was trying to delete. Here's the error from the log:

Oct 28 15:17:19 localhost kernel: [709293.487884] nova-compute[43959]: segfault at 0 ip 00007fe8d0da8c90 sp 00007fe8c4e55878 error 4 in libc-2.15.so[7fe8d0ca0000+1b5000

Is anyone experiencing this issue? How can i solve it?

Thanks in advance.

2014-09-19 05:41:46 -0500 commented answer How to reset incorrect quota count?

Quota numbers aren't being updated for me too, even if I've set as well the in_use field to 0. I don't believe that is a matter of time, because I have 3 active instances and if I create another instance the in_use value increases only by 1.

2014-08-25 22:35:06 -0500 received badge  Nice Question (source)
2014-03-11 04:45:18 -0500 received badge  Famous Question (source)
2014-03-02 07:42:11 -0500 received badge  Notable Question (source)
2014-02-28 05:43:35 -0500 received badge  Popular Question (source)
2014-02-27 15:39:44 -0500 received badge  Student (source)
2014-02-27 04:28:33 -0500 asked a question DHCP problem: instances cannot obtain a specific IP

I'm currently running Openstack Havana with Neutron on my infrastructure. Since yesterday, any booted instance could correctly obtain an IP address from the DHCP server. Yesterday afternoon I've terminated an instance with IP 10.0.0.110 and now, if I try to boot another instance with the same IP, it fails obtaining the address.

However, if I try to boot any other instance with a different IP, it correctly gets an IP address. I've found that dnsmasq mantains a list of mac/IP pairs in the file /opt/stack/data/neutron/dhcp/d333453f-d5d5-4077-b33a-85ec42359422/host. According to this post this file is modified by neutron-dhcp-agent everytime a port has been created. In my own file there is the following line:

 fa:16:3e:c9:ea:c1,host-10-0-0-110.openstacklocal,10.0.0.110

but this mac address does not correspond to any port in my infrastructure (I've also checked any table in neutron_ml2 database). Every time I try to boot a new instance with IP 10.0.0.110, a new line is appended to the file with the same IP but a different mac address, but the former line prevents the newly booted VM from getting an IP. I've also tried to manually delete the line, but Neutron still continues to write it in the file. Is there anybody that have experienced this issue?