Ask Your Question

nitins's profile - activity

2015-07-01 16:19:31 -0600 received badge  Famous Question (source)
2015-03-10 06:47:24 -0600 received badge  Notable Question (source)
2015-03-10 06:47:24 -0600 received badge  Popular Question (source)
2015-01-24 13:37:11 -0600 received badge  Famous Question (source)
2015-01-08 09:56:37 -0600 received badge  Taxonomist
2014-12-10 03:00:41 -0600 received badge  Notable Question (source)
2014-12-09 18:05:11 -0600 commented question Instance cannot ping outside although compute node mgmt is pingable

Not sure how to get SNAT working without OVS as I am using nova-network. any suggesstions??

2014-12-09 18:03:48 -0600 commented question Instance cannot ping outside although compute node mgmt is pingable

actually its because there is no source NAT happening for outgoing ICMP packets from the VM.

doing tcpdump on eth0 of the compute host I see following. The source ip is the private ip of the VM, 10:12:13.359045 IP 10.0.0.2 > 10.160.2.111: ICMP echo request, id 941, seq 26, length 6

2014-12-09 02:38:46 -0600 received badge  Popular Question (source)
2014-12-08 17:40:14 -0600 commented answer auto_assign_floating_ip=True is failing VMs from starting

I have already assigned 14 IPs to my tenant and that is why I can manually assign floating IPs to VMs.

Its the auto part that doesn't work.

2014-12-08 17:36:06 -0600 asked a question Instance cannot ping outside although compute node mgmt is pingable

HI I am using FlatDHCPManager to assign private IPs to VMs. I have a 10.0.0.0/24 private network created for that.

I also have a public floating ip pool and VMs are pingable from outside using floating ip address.

I can also ping from inside the instance, compute node/controller mgmt ip as below, but I cannot ping the gateway ip for this subnet.

I don't know why I cannot access internet from instance when instance is accessible from outside.

[centos@dgdfdd ~]$ ping 192.168.55.214
PING 192.168.55.214 (192.168.55.214) 56(84) bytes of data.
64 bytes from 192.168.55.214: icmp_seq=1 ttl=64 time=0.285 ms
64 bytes from 192.168.55.214: icmp_seq=2 ttl=64 time=0.260 ms
^C
--- 192.168.55.214 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1000ms
rtt min/avg/max/mdev = 0.260/0.272/0.285/0.020 ms
[centos@dgdfdd ~]$ ping 192.168.55.254
PING 192.168.55.254 (192.168.55.254) 56(84) bytes of data.
^C
--- 192.168.55.254 ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 999ms

[centos@dgdfdd ~]$

2014-12-08 16:30:28 -0600 asked a question auto_assign_floating_ip=True is failing VMs from starting

HI,

I have Juno running on Ubuntu 14.04. I am able to start VMs fine on my setup, but after I added the "auto_assign_floating_ip=True" in nova.conf file , The VMs fail to spawn giving an error

line 772, in floating_ip_allocate_address\n raise exception.NoMoreFloatingIps()\n\nNoMoreFloatingIps: Zero floating ips available.\n\n']

But I made sure there are more than enough floating IPs available. Also if I remove this line from the nova.conf file and associate a floating ip after launching a VM , it works fine.

The auto assignment of floating IPs in not working. Any ideas how to make it work or this is bug.

Thanks for the help.

2014-12-08 05:02:10 -0600 received badge  Famous Question (source)
2014-12-05 18:49:30 -0600 commented answer NoMoreFloatingIps: Zero floating ips available

i can assign floating ips manually but when I set it to auto_assign_floating_ip=True

in nova.conf then VM fails to spawn.

2014-12-05 18:47:10 -0600 commented answer NoMoreFloatingIps: Zero floating ips available

I am facing same issue....

My project has enough floating IPs assigned, but I stiil get this error

"NoMoreFloatingIps: Zero floating ips available".

root@wlanst-r610-12:/var/log/nova# nova floating-ip-list 8e88f2ad91534e42b0dd480fa0017559 192.168.55.197 None public eth1 8e88f2ad91534e

2014-11-25 16:37:34 -0600 received badge  Notable Question (source)
2014-11-21 17:56:19 -0600 received badge  Enthusiast
2014-11-20 05:08:27 -0600 received badge  Popular Question (source)
2014-11-18 16:39:01 -0600 asked a question nova-compute fails to start " Connection to libvirt failed: Failed to find group record for gid"

Hi,

I am not sure why I keep getting this error when i start nova-compute on ubuntu 14.04. I am using Juno.

also I observed that there was no nova user created in /etc/passwd file while nova installation.

Please help. I am a newbie on openstack issues.

2014-11-18 14:32:12.578 21438 AUDIT nova.service [-] Starting compute node (version 2014.2) 2014-11-18 14:32:12.578 21438 DEBUG nova.virt.libvirt.driver [-] Connecting to libvirt: qemu:///system _get_new_connection /usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py:724 2014-11-18 14:32:12.589 21438 ERROR nova.virt.libvirt.driver [-] Connection to libvirt failed: Failed to find group record for gid '151' 2014-11-18 14:32:12.589 21438 TRACE nova.virt.libvirt.driver Traceback (most recent call last): 2014-11-18 14:32:12.589 21438 TRACE nova.virt.libvirt.driver File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 839, in _connect 2014-11-18 14:32:12.589 21438 TRACE nova.virt.libvirt.driver libvirt.openAuth, uri, auth, flags) 2014-11-18 14:32:12.589 21438 TRACE nova.virt.libvirt.driver File "/usr/lib/python2.7/dist-packages/eventlet/tpool.py", line 139, in proxy_call 2014-11-18 14:32:12.589 21438 TRACE nova.virt.libvirt.driver rv = execute(f,args,kwargs) 2014-11-18 14:32:12.589 21438 TRACE nova.virt.libvirt.driver File "/usr/lib/python2.7/dist-packages/eventlet/tpool.py", line 77, in tworker 2014-11-18 14:32:12.589 21438 TRACE nova.virt.libvirt.driver rv = meth(args,kwargs) 2014-11-18 14:32:12.589 21438 TRACE nova.virt.libvirt.driver File "/usr/lib/python2.7/dist-packages/libvirt.py", line 105, in openAuth 2014-11-18 14:32:12.589 21438 TRACE nova.virt.libvirt.driver if ret is None:raise libvirtError('virConnectOpenAuth() failed') 2014-11-18 14:32:12.589 21438 TRACE nova.virt.libvirt.driver libvirtError: Failed to find group record for gid '151' 2014-11-18 14:32:12.589 21438 TRACE nova.virt.libvirt.driver 2014-11-18 14:32:12.616 21438 WARNING nova.virt.libvirt.driver [-] Cannot update service status on host: cdbu04,since it is not registered. 2014-11-18 14:32:12.617 21438 ERROR nova.openstack.common.threadgroup [-] Connection to the hypervisor is broken on host: cdbu04 2014-11-18 14:32:12.617 21438 TRACE nova.openstack.common.threadgroup Traceback (most recent call last): 2014-11-18 14:32:12.617 21438 TRACE nova.openstack.common.threadgroup File "/usr/lib/python2.7/dist-packages/nova/openstack/common/threadgroup.py", line 125, in wait 2014-11-18 14:32:12.617 21438 TRACE nova.openstack.common.threadgroup x.wait() 2014-11-18 14:32:12.617 21438 TRACE nova.openstack.common.threadgroup File "/usr/lib/python2.7/dist-packages/nova/openstack/common/threadgroup.py", line 47, in wait 2014-11-18 14:32:12.617 21438 TRACE nova.openstack.common.threadgroup return self.thread.wait() 2014-11-18 14:32:12.617 21438 TRACE nova.openstack.common.threadgroup File "/usr/lib/python2.7/dist-packages/eventlet/greenthread.py", line 168, in wait 2014-11-18 14:32:12.617 21438 TRACE nova.openstack.common.threadgroup return ... (more)

2014-11-12 02:23:37 -0600 received badge  Popular Question (source)
2014-11-12 02:23:37 -0600 received badge  Famous Question (source)
2014-11-12 02:23:37 -0600 received badge  Notable Question (source)
2014-11-04 16:55:45 -0600 asked a question update to dnsmasq doesn't solve bug 977555

HI ,

I installed Havana on Centos 6.4. The deployment went smooth . but the VM cannot be started.

I think I am hitting 977555 which requires update of dnsmasq. yum update tell me that I already have the latest version. What version do I need if not the one below?

also pasting relevant logs from compute node.

[root@cdbu02 ~]# yum install dnsmasq-2.48-14.el6.x86_64 Loaded plugins: fastestmirror Setting up Install Process Loading mirror speeds from cached hostfile * base: http://mirrors.syringanetworks.net * centosplus: http://mirrors.sonic.net * contrib: http://centos.mirrors.hoobly.com * epel: http://linux.mirrors.es.net * epel-debuginfo: http://linux.mirrors.es.net * epel-source: http://linux.mirrors.es.net * extras: http://centos.mirrors.hoobly.com * updates: http://mirrors.syringanetworks.net Package dnsmasq-2.48-14.el6.x86_64 already installed and latest version Nothing to do


2014-11-03 17:49:59.263 16091 TRACE nova.openstack.common.rpc.amqp Command: sudo nova-rootwrap /etc/nova/rootwrap.conf env CONFIG_FILE=["/usr/share/nova/nova-dist.conf", "/etc/nova/nova.conf"] NETWORK_ID=4 dnsmasq --strict-order --bind-interfaces --conf-file= --pid-file=/var/lib/nova/networks/nova-br100.pid --listen-address=172.78.0.1 --except-interface=lo --dhcp-range=set:vmnet,172.78.0.2,static,255.255.255.0,120s --dhcp-lease-max=256 --dhcp-hostsfile=/var/lib/nova/networks/nova-br100.conf --dhcp-script=/usr/bin/nova-dhcpbridge --leasefile-ro --domain=novalocal --no-hosts --addn-hosts=/var/lib/nova/networks/nova-br100.hosts 2014-11-03 17:49:59.263 16091 TRACE nova.openstack.common.rpc.amqp Exit code: 2 2014-11-03 17:49:59.263 16091 TRACE nova.openstack.common.rpc.amqp Stdout: u'' 2014-11-03 17:49:59.263 16091 TRACE nova.openstack.common.rpc.amqp Stderr: u'\ndnsmasq: failed to set SO_REUSE{ADDR|PORT} on DHCP socket: Protocol not available\n'