Ask Your Question

leethaoqn's profile - activity

2016-12-09 05:53:52 -0500 received badge  Good Answer (source)
2016-10-23 03:44:18 -0500 received badge  Nice Answer (source)
2015-01-08 09:11:14 -0500 received badge  Famous Question (source)
2014-12-24 04:11:17 -0500 received badge  Famous Question (source)
2014-12-01 23:50:00 -0500 received badge  Necromancer (source)
2014-12-01 15:34:37 -0500 received badge  Famous Question (source)
2014-10-22 14:23:22 -0500 received badge  Student (source)
2014-10-16 05:45:57 -0500 received badge  Notable Question (source)
2014-10-01 23:50:48 -0500 commented question No internet access from VM

could you ping from vm to controller or networknode? and post **ip netns**

2014-09-30 05:57:19 -0500 received badge  Notable Question (source)
2014-09-22 17:14:56 -0500 received badge  Famous Question (source)
2014-09-22 09:41:27 -0500 commented answer Can I launch a instance with OVF file in openstack?

thank for your suggestion, but i didn't soft reboot instance in this link

2014-09-22 08:10:42 -0500 commented answer Can I launch a instance with OVF file in openstack?

@antonio : how do you do if the vm has two disk : one disk for root and one disk for data

2014-09-22 04:44:55 -0500 commented answer How to import a VMWare VM with multiple drives?

hi rz2p, when i relaunch my instance, i only see the vda not vdb. I will check file libvirt.xml and the file copy from Driver 2 is lost. How can i fix that?

2014-09-21 21:57:26 -0500 received badge  Popular Question (source)
2014-09-18 23:02:05 -0500 asked a question move instance openstack to vmware

Dear all,
I have the instance centos run on openstack. Can openstack support move this instance to vmware and how can do that?
Thank

2014-09-16 06:08:31 -0500 received badge  Popular Question (source)
2014-09-08 03:26:26 -0500 commented answer Instance cannot reach neutron metadate service

here a error log about metadata

 Sep  8 15:18:22 NetworkNode 2014-09-08 15:18:22.121 1402 ERROR neutron.agent.metadata.agent [req-576c3a17-5635-4d29-a8e5-9d12197b827b None] Failed reporting state!#0122014-09-08 15:18:22.121 1402 TRACE neutron.agent.metadata.agent Traceback (most recen
2014-09-08 03:04:58 -0500 commented answer VM instance can't reach external network. NATed packet not return.

yeah here my conf:

net.ipv4.conf.default.rp_filter = 0
net.ipv4.conf.all.rp_filter = 0
net.ipv4.ip_forward = 1
2014-09-08 03:01:52 -0500 commented answer Instance cannot reach neutron metadate service

yeah, i viewed that and my config is the same

2014-09-08 02:20:40 -0500 commented question VM instance can't reach external network. NATed packet not return.

please share me your config about network node

2014-09-08 02:17:34 -0500 asked a question Instance cannot reach neutron metadate service

Hi all, I install ice house with three node : 1 controller , 1 compute and 1 network.
From controller , i can ssh and ping my instance. In instance i can see the route 169.254.0.0 but i can't ping it .
I get this error when i started my vm .

checking http://169.254.169.254/2009-04-04/instance-id
failed 1/20: up 12.49. request failed

Here some information :
- ip netns

qrouter-a9e27d9b-ecf2-4b94-97ba-f13d723bdc83
qdhcp-d8ea1d4a-cc6f-4264-aff5-de6d8e40e749
  • ip netns exec qrouter-a9e27d9b-ecf2-4b94-97ba-f13d723bdc83 iptables -S -t nat |grep 169

    A neutron-l3-agent-PREROUTING -d 169.254.169.254/32 -p tcp -m tcp --dport 80 -j REDIRECT --to-ports 9697
    Error log in metadata

    Sep 8 15:18:22 NetworkNode 2014-09-08 15:18:22.121 1402 ERROR neutron.agent.metadata.agent [req-576c3a17-5635-4d29-a8e5-9d12197b827b None] Failed reporting state!#0122014-09-08 15:18:22.121 1402 TRACE neutron.agent.metadata.agent Traceback (most recent call last):#0122014-09-08 15:18:22.121 1402 TRACE neutron.agent.metadata.agent File "/usr/lib/python2.7/dist-packages/neutron/agent/metadata/agent.py", line 302, in _report_state#0122014-09-08 15:18:22.121 1402 TRACE neutron.agent.metadata.agent use_call=self.agent_state.get('start_flag'))#0122014-09-08 15:18:22.121 1402 TRACE neutron.agent.metadata.agent File "/usr/lib/python2.7/dist-packages/neutron/agent/rpc.py", line 72, in report_state#0122014-09-08 15:18:22.121 1402 TRACE neutron.agent.metadata.agent return self.call(context, msg, topic=self.topic)#0122014-09-08 15:18:22.121 1402 TRACE neutron.agent.metadata.agent File "/usr/lib/python2.7/dist-packages/neutron/openstack/common/rpc/proxy.py", line 129, in call#0122014-09-08 15:18:22.121 1402 TRACE neutron.agent.metadata.agent exc.info, real_topic, msg.get('method'))#0122014-09-08 15:18:22.121 1402 TRACE neutron.agent.metadata.agent Timeout: Timeout while waiting on RPC response - topic: "q-plugin", RPC method: "report_state" info: "<unknown>"#0122014-09-08 15:18:22.121 1402 TRACE neutron.agent.metadata.agent

2014-09-07 21:17:45 -0500 commented question VM instance can't reach external network. NATed packet not return.

How to fix issues with metadata_agent and metadata_proxy ? I have same problem with you- can' curl 169.254.169.254

2014-09-06 04:42:20 -0500 commented question Cannot ping router tenant gateway by OS Nodes and www by Instance

nothing happen with me, it still

curl: (7) couldn't connect to host
2014-09-06 04:13:47 -0500 commented question Unable to login into Horizon console - Something went wrong

check apache error log

2014-09-04 09:12:29 -0500 received badge  Famous Question (source)
2014-09-04 02:09:04 -0500 received badge  Notable Question (source)
2014-08-29 21:49:21 -0500 commented question Instance cannot ping outside

network node :

Linux NetworkNode 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:51:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

compute node :

Linux compute01 3.13.0-34-generic #60-Ubuntu SMP Wed Aug 13 15:45:27 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
2014-08-28 19:05:11 -0500 received badge  Popular Question (source)
2014-08-28 12:55:06 -0500 commented question Instance cannot ping outside

ip netns list
qrouter-a51fe74a-49a9-4662-8ccf-cc7e8b7a0e33
qdhcp-69e86304-94ae-456f-96d7-ca05441d5301

2014-08-28 12:52:08 -0500 commented question Instance cannot ping outside

ps -ef | grep 1044

root      1043     1  0 00:51 ?        00:00:00 ovsdb-server: monitoring pid 1044 (healthy)<br>
2014-08-28 11:56:34 -0500 commented question Instance cannot ping outside

On controller node and compute :

  netstat -lntp | grep 8775
tcp        0      0 0.0.0.0:8775            0.0.0.0:*               LISTEN      1044/python

On network node is nothing

2014-08-28 10:30:46 -0500 commented question Instance cannot ping outside

ya, how to fix metadata access , service neutron-metadata-agent running ok

2014-08-28 03:17:26 -0500 asked a question Instance cannot ping outside

I follow this tutorial icehouse to install openstack with three node (controller, compute01,networknode)

My demo-net, which is tenant net, is 192.168.1.0/24.
My ext-net, which is external net, is 172.22.22.0/24.


I create two instance and it can ping each other. All of service on network node is running ok.

From controller, i can ssh to instance , ping floating ip of instance is ok .
From qrrouter and qdhcp , i can ping the instance and the outside network.
My problem is the instance cannot ping the controller and the outside network . In the console log of instance, it can't connect metadate service.

checking http://169.254.169.254/2009-04-04/instance-id
failed 1/20: up 15.87. request failed
failed 2/20: up 29.21. request failed
failed 3/20: up 41.43. request failed

Here is ovs-vsctl show on network node:

17e35285-e6f5-4b4d-98d5-889b6fd39830
    Bridge br-tun
        Port patch-int
            Interface patch-int
                type: patch
                options: {peer=patch-tun}
        Port br-tun
            Interface br-tun
                type: internal
        Port "gre-c0a80ab5"
            Interface "gre-c0a80ab5"
                type: gre
                options: {in_key=flow, local_ip="192.168.10.184", out_key=flow, remote_ip="192.168.10.181"}
        Port "gre-c0a80ab6"
            Interface "gre-c0a80ab6"
                type: gre
                options: {in_key=flow, local_ip="192.168.10.184", out_key=flow, remote_ip="192.168.10.182"}
    Bridge br-ex
        Port "eth0"
            Interface "eth0"
        Port "qg-0fdb50b1-6b"
            Interface "qg-0fdb50b1-6b"
                type: internal
        Port br-ex
            Interface br-ex
                type: internal
    Bridge br-int
        Port patch-tun
            Interface patch-tun
                type: patch
                options: {peer=patch-int}
        Port "qr-3ece34d9-2f"
            tag: 1
            Interface "qr-3ece34d9-2f"
                type: internal
        Port br-int
            Interface br-int
                type: internal
        Port "tap10785084-ff"
            tag: 1
            Interface "tap10785084-ff"
                type: internal
    ovs_version: "2.0.1"

Here ovs-vsctl on compute node :

f770b074-9fa6-40a0-965b-db0ae5a53475
    Bridge br-tun
        Port br-tun
            Interface br-tun
                type: internal
        Port patch-int
            Interface patch-int
                type: patch
                options: {peer=patch-tun}
        Port "gre-c0a80ab6"
            Interface "gre-c0a80ab6"
                type: gre
                options: {in_key=flow, local_ip="192.168.10.181", out_key=flow, remote_ip="192.168.10.182"}
        Port "gre-c0a80ab8"
            Interface "gre-c0a80ab8"
                type: gre
                options: {in_key=flow, local_ip="192.168.10.181", out_key=flow, remote_ip="192.168.10.184"}
    Bridge br-int
        fail_mode: secure
        Port patch-tun
            Interface patch-tun
                type: patch
                options: {peer=patch-int}
        Port br-int
            Interface br-int
                type: internal
        Port "qvo0d1afd48-10"
            tag: 1
            Interface "qvo0d1afd48-10"
        Port "gw-3b2efe4e-85"
            tag: 4095
            Interface "gw-3b2efe4e-85"
                type: internal
        Port "qvof140c766-70"
            tag: 1
            Interface "qvof140c766-70"
    ovs_version: "2.0.1"
2014-08-28 02:00:25 -0500 commented answer following guide to configure neutron, but cannot ping gateway of demo-net.

did you install dnsmasq in the network node?

2014-08-27 21:16:25 -0500 commented answer following guide to configure neutron, but cannot ping gateway of demo-net.

netstat -antp | grep 8775
on compute note

tcp        0      0 0.0.0.0:8775            0.0.0.0:*               LISTEN      1850/python

On controller node is same, on network node in nothing

2014-08-27 04:22:37 -0500 commented answer following guide to configure neutron, but cannot ping gateway of demo-net.

dear dbaxps, i have same problem with hugesu but from controller i can ssh into the instance. As the link your post, i didn't see the route 169.254.0.0 on the routing table and my instance . Please help me
checking http://169.254.169.254/2009-04-04/instance-id faile