subject:"\[Openstack\] Can't ping my VM after associating a floating IP address"

Re: [Openstack] Can't ping my VM after associating a floating IP address

2013-03-20 Thread Sylvain Bauza


Le 20/03/2013 13:24, Mohammed Amine SAYA a écrit :

RuntimeError:
Command: ['sudo', 'quantum-rootwrap', '/etc/quantum/rootwrap.conf', 
'ovs-vsctl', '--', '--may-exist', 'add-port', 'br-ex', 'qg-32dd6c6b-b6', '--', 
'set', 'Interface', 'qg-32dd6c6b-b6', 'type=internal', '--', 'set', 
'Interface', 'qg-32dd6c6b-b6', 
'external-ids:iface-id=32dd6c6b-b6e8-4dff-b0db-3d804805c4e4', '--', 'set', 
'Interface', 'qg-32dd6c6b-b6', 'external-ids:iface-status=active', '--', 'set', 
'Interface', 'qg-32dd6c6b-b6', 'external-ids:attached-mac=fa:16:3e:6f:1b:81']
Exit code: 1
Stdout: ''
Stderr: 'sudo: no tty present and no askpass program specified\n'


The answer is here : 
http://www.lmgtfy.com/?q=sudo%3A+no+tty+present+and+no+askpass+program+specified


Are you trying to start the L3 agent thru ssh ?

-Sylvain


___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Can't ping my VM after associating a floating IP address

2013-03-20 Thread Mohammed Amine SAYA

Hi Sylvain,

Thanks for your answer.

No I am not. I am actually logged in the controller machine. I start the
l3-agent with sudo /etc/init.d/quantum-l3-agent start.

But I took a look at /var/log/quantum/dhcp-agent.log and I got this : (see
last log)
Like l3-agent, it complains about some interfaces that do not exist.

Here is the result of ovs-vsctl show on both the contoller node and the
compute node :

On the controller node which also runs as a network node:
8e316a78-ad43-4a0a-89ae-a6c734ef0b52
Bridge br-tun
Port gre-1
Interface gre-1
type: gre
options: {in_key=flow, out_key=flow,
remote_ip=192.168.0.1}
Port gre-2
Interface gre-2
type: gre
options: {in_key=flow, out_key=flow,
remote_ip=192.168.0.2}
Port patch-int
Interface patch-int
type: patch
options: {peer=patch-tun}
Port gre-4
Interface gre-4
type: gre
options: {in_key=flow, out_key=flow,
remote_ip=192.168.1.2}
Port br-tun
Interface br-tun
type: internal
Bridge br-ex
Port eth1
Interface eth1
Port br-ex
Interface br-ex
type: internal
Bridge br-int
Port patch-tun
Interface patch-tun
type: patch
options: {peer=patch-int}
Port br-int
Interface br-int
type: internal
ovs_version: 1.4.5



On the compute node :
6c9b615e-650b-4e80-8d53-233c90eed49e
Bridge br-int
Port br-int
Interface br-int
type: internal
Port patch-tun
Interface patch-tun
type: patch
options: {peer=patch-int}
Port qvof1e2c3c0-bc
tag: 1
Interface qvof1e2c3c0-bc
Bridge br-tun
Port gre-2
Interface gre-2
type: gre
options: {in_key=flow, out_key=flow,
remote_ip=192.168.0.2}
Port gre-1
Interface gre-1
type: gre
options: {in_key=flow, out_key=flow,
remote_ip=192.168.0.1}
Port patch-int
Interface patch-int
type: patch
options: {peer=patch-tun}
Port gre-3
Interface gre-3
type: gre
options: {in_key=flow, out_key=flow,
remote_ip=192.168.1.1}
Port br-tun
Interface br-tun
type: internal
ovs_version: 1.4.5





 2013-03-20 14:22:47DEBUG [quantum.openstack.common.rpc.amqp] Making
asynchronous call on q-plugin ...
2013-03-20 14:22:47DEBUG [quantum.openstack.common.rpc.amqp] MSG_ID is
1d5a7c943a1845d3837f9bc4d6d72590
2013-03-20 14:22:47DEBUG [amqplib] Closed channel #1
2013-03-20 14:22:47DEBUG [amqplib] using channel_id: 1
2013-03-20 14:22:47DEBUG [amqplib] Channel open
2013-03-20 14:23:17 INFO [quantum.agent.dhcp_agent] Synchronizing state
2013-03-20 14:23:17DEBUG [quantum.openstack.common.rpc.amqp] Making
asynchronous call on q-plugin ...
2013-03-20 14:23:17DEBUG [quantum.openstack.common.rpc.amqp] MSG_ID is
910cccbade364f5cba63eb787db731e3
2013-03-20 14:23:17DEBUG [amqplib] Closed channel #1
2013-03-20 14:23:17DEBUG [amqplib] using channel_id: 1
2013-03-20 14:23:17DEBUG [amqplib] Channel open
2013-03-20 14:23:17DEBUG [quantum.openstack.common.rpc.amqp] Making
asynchronous call on q-plugin ...
2013-03-20 14:23:17DEBUG [quantum.openstack.common.rpc.amqp] MSG_ID is
e26dc4c782954d349462c7b237755b89
2013-03-20 14:23:17DEBUG [amqplib] Closed channel #1
2013-03-20 14:23:17DEBUG [amqplib] using channel_id: 1
2013-03-20 14:23:17DEBUG [amqplib] Channel open
2013-03-20 14:23:17DEBUG [quantum.openstack.common.rpc.amqp] Making
asynchronous call on q-plugin ...
2013-03-20 14:23:17DEBUG [quantum.openstack.common.rpc.amqp] MSG_ID is
185e0f3426d242ea9188582e0d09b2b3
2013-03-20 14:23:17DEBUG [amqplib] Closed channel #1
2013-03-20 14:23:17DEBUG [amqplib] using channel_id: 1
2013-03-20 14:23:17DEBUG [amqplib] Channel open
2013-03-20 14:23:17DEBUG [quantum.agent.linux.utils] Running command:
ip -o link show tap8d6cc6c4-d1
2013-03-20 14:23:17DEBUG [quantum.agent.linux.utils]
Command: ['ip', '-o', 'link', 'show', 'tap8d6cc6c4-d1']
Exit code: 1
Stdout: ''
Stderr: 'Device tap8d6cc6c4-d1 does not exist.\n'
2013-03-20 14:23:17DEBUG [quantum.agent.linux.utils] Running command:
ip -o link show br-int
2013-03-20 14:23:17DEBUG [quantum.agent.linux.utils]
Command: ['ip', '-o', 'link', 'show', 'br-int']
Exit code: 0
Stdout: '5: br-int: BROADCAST,MULTICAST mtu 1500 qdisc noop state DOWN
mode DEFAULT \\link/ether 16:cc:49:e1:d2:4c brd ff:ff:ff:ff:ff:ff\n'
Stderr: ''
2013-03-20 14:23:17DEBUG [quantum.agent.linux.utils] Running command:
ip -o link show

Re: [Openstack] Can't ping my VM after associating a floating IP address

2013-03-20 Thread Sylvain Bauza

You are having the exact same issue, sudo is complaining about being 
executed without a tty.
Could you please take a look at the various links I provided to you and 
check ?


Basically, you can quickly disable requiretty on sudoers and retry, to 
check if that fixes the problem.

Which is your distro ?
Could you please paste /etc/sudoers ?

Also, please use 'sudo service quantum-XXX-agent restart' instead of 
'sudo /etc/init.d/quantum-X-agent restart' directly.


-Sylvain

Le 20/03/2013 14:29, Mohammed Amine SAYA a écrit :

Hi Sylvain,

Thanks for your answer.

No I am not. I am actually logged in the controller machine. I start 
the l3-agent with sudo /etc/init.d/quantum-l3-agent start.


But I took a look at /var/log/quantum/dhcp-agent.log and I got this : 
(see last log)

Like l3-agent, it complains about some interfaces that do not exist.

Here is the result of ovs-vsctl show on both the contoller node and 
the compute node :


On the controller node which also runs as a network node:
8e316a78-ad43-4a0a-89ae-a6c734ef0b52
Bridge br-tun
Port gre-1
Interface gre-1
type: gre
options: {in_key=flow, out_key=flow, 
remote_ip=192.168.0.1}

Port gre-2
Interface gre-2
type: gre
options: {in_key=flow, out_key=flow, 
remote_ip=192.168.0.2}

Port patch-int
Interface patch-int
type: patch
options: {peer=patch-tun}
Port gre-4
Interface gre-4
type: gre
options: {in_key=flow, out_key=flow, 
remote_ip=192.168.1.2}

Port br-tun
Interface br-tun
type: internal
Bridge br-ex
Port eth1
Interface eth1
Port br-ex
Interface br-ex
type: internal
Bridge br-int
Port patch-tun
Interface patch-tun
type: patch
options: {peer=patch-int}
Port br-int
Interface br-int
type: internal
ovs_version: 1.4.5



On the compute node :
6c9b615e-650b-4e80-8d53-233c90eed49e
Bridge br-int
Port br-int
Interface br-int
type: internal
Port patch-tun
Interface patch-tun
type: patch
options: {peer=patch-int}
Port qvof1e2c3c0-bc
tag: 1
Interface qvof1e2c3c0-bc
Bridge br-tun
Port gre-2
Interface gre-2
type: gre
options: {in_key=flow, out_key=flow, 
remote_ip=192.168.0.2}

Port gre-1
Interface gre-1
type: gre
options: {in_key=flow, out_key=flow, 
remote_ip=192.168.0.1}

Port patch-int
Interface patch-int
type: patch
options: {peer=patch-tun}
Port gre-3
Interface gre-3
type: gre
options: {in_key=flow, out_key=flow, 
remote_ip=192.168.1.1}

Port br-tun
Interface br-tun
type: internal
ovs_version: 1.4.5




 2013-03-20 14:22:47DEBUG [quantum.openstack.common.rpc.amqp] 
Making asynchronous call on q-plugin ...
2013-03-20 14:22:47DEBUG [quantum.openstack.common.rpc.amqp] 
MSG_ID is 1d5a7c943a1845d3837f9bc4d6d72590

2013-03-20 14:22:47DEBUG [amqplib] Closed channel #1
2013-03-20 14:22:47DEBUG [amqplib] using channel_id: 1
2013-03-20 14:22:47DEBUG [amqplib] Channel open
2013-03-20 14:23:17 INFO [quantum.agent.dhcp_agent] Synchronizing 
state
2013-03-20 14:23:17DEBUG [quantum.openstack.common.rpc.amqp] 
Making asynchronous call on q-plugin ...
2013-03-20 14:23:17DEBUG [quantum.openstack.common.rpc.amqp] 
MSG_ID is 910cccbade364f5cba63eb787db731e3

2013-03-20 14:23:17DEBUG [amqplib] Closed channel #1
2013-03-20 14:23:17DEBUG [amqplib] using channel_id: 1
2013-03-20 14:23:17DEBUG [amqplib] Channel open
2013-03-20 14:23:17DEBUG [quantum.openstack.common.rpc.amqp] 
Making asynchronous call on q-plugin ...
2013-03-20 14:23:17DEBUG [quantum.openstack.common.rpc.amqp] 
MSG_ID is e26dc4c782954d349462c7b237755b89

2013-03-20 14:23:17DEBUG [amqplib] Closed channel #1
2013-03-20 14:23:17DEBUG [amqplib] using channel_id: 1
2013-03-20 14:23:17DEBUG [amqplib] Channel open
2013-03-20 14:23:17DEBUG [quantum.openstack.common.rpc.amqp] 
Making asynchronous call on q-plugin ...
2013-03-20 14:23:17DEBUG [quantum.openstack.common.rpc.amqp] 
MSG_ID is 185e0f3426d242ea9188582e0d09b2b3

2013-03-20 14:23:17DEBUG [amqplib] Closed channel #1
2013-03-20 14:23:17DEBUG [amqplib] using channel_id: 1
2013-03-20 14:23:17DEBUG [amqplib] Channel open
2013-03-20 14:23:17DEBUG [quantum.agent.linux.utils] Running 
command: ip -o link show tap8d6cc6c4-d1

2013-03-20 14:23:17DEBUG [quantum.agent.linux.utils]
Command: ['ip', '-o', 'link', 'show',

Re: [Openstack] Can't ping my VM after associating a floating IP address

Re: [Openstack] Can't ping my VM after associating a floating IP address

Re: [Openstack] Can't ping my VM after associating a floating IP address

3 matches

Site Navigation

Mail list logo

Footer information