piosystems's profile - activity

2016-12-09 05:53:56 -0600 received badge  Nice Question (source)
2015-02-01 20:59:20 -0600 received badge  Nice Question (source)
2014-10-11 18:32:40 -0600 received badge  Famous Question (source)
2014-10-11 18:32:40 -0600 received badge  Notable Question (source)
2014-09-23 09:27:50 -0600 received badge  Famous Question (source)
2014-08-19 02:54:06 -0600 received badge  Notable Question (source)
2014-08-17 15:14:29 -0600 received badge  Popular Question (source)
2014-08-16 16:09:08 -0600 commented answer How can I get rid of icehouse instance in deleting task state + error status + running power state

The instance has been successfully marked as deleted. However, the usage summary as shown on the horizon's Overview dashboard, still shows the instance as holding processor and memory. I need another database update to correct this inconsistency.

2014-08-16 16:02:12 -0600 commented answer How can I get rid of icehouse instance in deleting task state + error status + running power state

Unfortunately, this did not work for me.

2014-08-16 01:31:27 -0600 received badge  Popular Question (source)
2014-08-14 18:22:39 -0600 asked a question How can I get rid of icehouse instance in deleting task state + error status + running power state

Hello,

I have an Icehouse instance stuck in deleting task state, error status and running power state.

I have tried all kinds of nova commands to get rid of it (reset and then delete, force-delete, reset to active and then delete). The instance always ends up in the same anomalous state.

What steps should I take to get rid of it from the database/filesystem? I need to free the resources.

2014-08-14 18:19:08 -0600 asked a question Can't get rid of deleting + error + running instance

I have an Icehouse instance stuck in deleting task state, error status and running power state.

I have tried all kinds of nova commands to get rid of it (reset and then delete, force-delete, reset to active and then delete). The instance always ends up in the same anomalous state.

What steps should I take to get rid of it from the database? I need to free the resources.

2014-07-09 02:47:36 -0600 received badge  Enthusiast
2014-07-08 05:18:44 -0600 answered a question Why can't I connect to instance via their floating IPs from outside the compute machine?

The problem was that the default gateway was automatically set to that of the private network and not that of the public. The solution was to run "ip route replace ..." as shown below, in order to automatically change the gateway. I attached that execution to post-up of the public interface card.

#my public interface

auto eth2

iface eth2 inet static

    address x.x.x.66

    netmask 255.255.255.224

    post-up ip route replace default via x.x.x.65 dev eth2 metric 100

That's it!

x.x.x.66 is the ip of the public interface

x.x.x.65 is the public gateway

2014-07-08 05:18:36 -0600 commented answer Why can't I connect to instance via their floating IPs from outside the compute machine?

Thanks for the clue, I finally found the solution as shown in my answer below.

2014-07-07 10:39:47 -0600 commented answer Why can't I connect to instance via their floating IPs from outside the compute machine?

I can access VM through the fixed private ip from other systems. The problem is access the VM using the floating ip.

2014-07-07 10:39:47 -0600 received badge  Commentator
2014-07-07 08:27:40 -0600 received badge  Famous Question (source)
2014-07-07 03:33:20 -0600 received badge  Student (source)
2014-07-06 22:57:09 -0600 received badge  Notable Question (source)
2014-07-05 10:58:38 -0600 commented question Why can't I connect to instance via their floating IPs from outside the compute machine?

Thanks dachary for the concern. In response to your request, I have added more information to my original question above (i.e. Additional info section). eth2 is the public ip interface. eth1 is the private ip interface.

2014-07-05 10:36:38 -0600 received badge  Popular Question (source)
2014-07-04 06:29:18 -0600 commented answer Why can't I connect to instance via their floating IPs?

I have exactly the same problem. Can you explain more clearly what you did?

2014-07-04 05:41:30 -0600 commented question Why can't I connect to instance via their floating IPs from outside the compute machine?

Still stuck with inability to access floating ip. Any help?

2014-07-03 05:16:03 -0600 asked a question Why can't I connect to instance via their floating IPs from outside the compute machine?

I have carefully followed the instruction in the URL http://docs.openstack.org/admin-guide... to configure floating ip for openstack instances. I am using havana version and nova.network.manager.FlatDHCPManager as network manager.

After floating ip allocation to an instance, I am able to reach (ping, ssh) the instance's floating ip from the compute node itself. Unfortunately, I cannot access the instance via floating ip, from another server. When I run tcpdump on my public interface, it is clear that requests (e.g. ping requests) get to the interface. Unfortunately, response only occurs when I ping from the compute server itself.

As suggested in the URL http://docs.openstack.org/admin-guide... , I have set sysctl -w net.ipv4.conf.eth2.rp_filter=0. This has not solved the problem.

Setting firewall_driver=nova.virt.firewall.NoopFirewallDriver did not solve the problem either.

My situation is similar to that presented in https://ask.openstack.org/en/question... . Unfortunately, the solution was not properly explained in that thread. It only mentioned that the gateway had to be changed. Which gateway is not clear.

What else do I need to check or do in order to be able to reach the instances via floating ip, from external machines?

2014-02-26 10:47:06 -0600 received badge  Notable Question (source)
2014-02-26 10:47:06 -0600 received badge  Famous Question (source)
2014-01-31 10:50:03 -0600 received badge  Popular Question (source)
2014-01-31 09:01:09 -0600 commented question Openstack Installation problem. Why is my cirrOS instance always ending up in error state?

I installed openvswitch-switch (sudo apt-get openvswitch-switch). This cleared the "Executable not found" error. I still have the following libvirtError errors:
CPU feature tsc-deadline not found
CPU feature pcid not found
qemu: could not load PC BIOS 'bios.bin'
My systems are Dell PowerEdge r720. Wondering whether there is any additional setting that I am missing.

2014-01-31 05:32:18 -0600 commented question Openstack Installation problem. Why is my cirrOS instance always ending up in error state?

How do I solve the "Stderr: '/usr/bin/nova-rootwrap: Executable not found: ovs-vsctl (filter match = ovs-vsctl)\n'" problem?

2014-01-31 05:28:45 -0600 commented question Openstack Installation problem. Why is my cirrOS instance always ending up in error state?

Traceback (most recent call last):File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 1037, in _build_instance set_access_ip=set_access_ip)
File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 1410, in _spawn LOG.exception(_('Instance failed to spawn'), instance=instance)
File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 1407, in _spawn block_device_info)
...
File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 3202, in _create_domain_and_network self.plug_vifs(instance, network_info)
...
File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/vif.py", line 805, in plug return self.plug_ovs_hybrid(instance, vif)
File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/vif.py", line 436, in plug_ovs_hybrid instance['uuid'])...
File "/usr/lib/python2.7/dist-packages/nova/openstack/common/processutils.py", line 178, in execute cmd=' '.join(cmd)) ProcessExecutionError: ...

2014-01-31 05:06:05 -0600 commented question Openstack Installation problem. Why is my cirrOS instance always ending up in error state?

There are two log messages that seem to stand out.
1. /var/log/libvirt/libvirtd.log shows:
1927: error : virNetSocketReadWire:1377 : End of file while reading data: Input/output error

2. /var/log/nova/nova-compute.log shows:
2014-01-31 11:44:25.330 8195 ERROR nova.compute.manager [req-ab1b5442-ef4c-42db-ad03-de5fb4fdfdac 580f5ac495f24b5ba244e488aa92d730 4d874d7639c142eab658863028908d60] [instance: 3102049c-a4e4-49a7-9e31-6405556591d4] Error: Unexpected error while running command.
Command: sudo nova-rootwrap /etc/nova/rootwrap.conf ovs-vsctl -- --may-exist add-port br100 qvof7025e0b-24 -- set Interface qvof7025e0b-24 external-ids:iface-id=f7025e0b-2492-4625-a3ef-939a742b93f2 external-ids:iface-status=active external-ids:attached-mac=fa:16:3e:5c:6a:7c external-ids:vm-uuid=3102049c-a4e4-49a7-9e31-6405556591d4 Exit code: 96 Stdout: '' Stderr: '/usr/bin/nova-rootwrap: Executable not found: ovs-vsctl (filter match = ovs-vsctl)\n' ...

2014-01-31 04:53:36 -0600 commented answer Openstack Installation problem. Why is my cirrOS instance always ending up in error state?

processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 45 model name : Intel(R) Xeon(R) CPU E5-2665 0 @ 2.40GHz stepping : 7 microcode : 0x710 cpu MHz : 2400.035 cache size : 20480 KB physical id : 0 siblings : 16 core id : 0 cpu cores : 8 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx lahf_lm ida arat xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid bogomips : 4800.07 clflush size : 64 cache_alignment : 64 address sizes : 46 bits physical, 48 ...


(more)

2014-01-30 10:59:03 -0600 commented question Openstack Installation problem. Why is my cirrOS instance always ending up in error state?

Hi Salvo. I posted my response to your request as an answer because the text was too long for comment. Waiting for your further help. Thanks.