Re: [Openstack] quantum-plugin-openvswitch-agent error
Arindam, Do you have sudo configured properly? Something like the following? Defaults:quantum !requiretty quantum ALL = (root) NOPASSWD: /usr/bin/quantum-rootwrap Jay S. Bryant Linux Developer - OpenStack Enterprise Edition Department 7YLA, Building 015-2, Office E125, Rochester, MN Telephone: (507) 253-4270, FAX (507) 253-6410 TIE Line: 553-4270 E-Mail: jsbry...@us.ibm.com All the world's a stage and most of us are desperately unrehearsed. -- Sean O'Casey From: Arindam Choudhury To: openstack , Date: 04/29/2013 02:38 PM Subject:[Openstack] quantum-plugin-openvswitch-agent error Sent by:"Openstack" Hi, I am getting the following error. Any help will be highly appreciated. head /var/log/quantum/ovs-agent.log 2013-04-29 16:59:15ERROR [quantum.agent.linux.ovs_lib] Unable to execute ['ovs-vsctl', '--timeout=2', '--', '--if-exists', 'del-port', 'br-int', 'patch-tun']. Exception: Command: ['sudo', 'ovs-vsctl', '--timeout=2', '--', '--if-exists', 'del-port', 'br-int', 'patch-tun'] Exit code: 1 Stdout: '' Stderr: 'sudo: sin tty presente y no hay programa askpass especificado\n' 2013-04-29 16:59:15ERROR [quantum.agent.linux.ovs_lib] Unable to execute ['ovs-ofctl', 'del-flows', 'br-int']. Exception: Command: ['sudo', 'ovs-ofctl', 'del-flows', 'br-int'] Exit code: 1 Stdout: '' Stderr: 'sudo: sin tty presente y no hay programa askpass especificado\n' ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp <>___ 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] Quantum CLI errors on Grizzly
Ashutosh, Have you verified that the necessary Quantum processes are running? If not, ensure that quantum-dhcp-agent, quantum-l3-agent, quantum-openvswitch-agent and most importantly quantum are running. If those processes are running can you share the output from /var/log/quantum/server.log . It should contain a hint as to why the server is not ready for connections. Also, please be aware, the first time you start quantum it can take quite some time to be ready for CLI connections depending on the speed of the database you are using. Jay S. Bryant Linux Developer - OpenStack Enterprise Edition Department 7YLA, Building 015-2, Office E125, Rochester, MN Telephone: (507) 253-4270, FAX (507) 253-6410 TIE Line: 553-4270 E-Mail: jsbry...@us.ibm.com All the world's a stage and most of us are desperately unrehearsed. -- Sean O'Casey From: Ashutosh Narayan To: OpenStack , Date: 04/29/2013 05:08 AM Subject:[Openstack] Quantum CLI errors on Grizzly Sent by:"Openstack" Hi folks, I have installed Grizzly on CentOS 6.3 and was setting up Quantum by following the instructions given in the below link : https://fedoraproject.org/wiki/Packstack_to_Quantum In step 13 when I start using Quantum CLI to create a private network using the command - quantum net-create private I get [ Error 111 ] Connection refused as an error. I have installed OpenvSwitch from the source Even in the dashboard it's not allowing me to create Routers. Same Error 111 is seen there too. Any suggestions ? Thank you, -- Ashutosh Narayan http://ashutoshn.wordpress.com/ ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp <>___ 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] nova-network no ip for vm
Arindam, You need to make sure that nova-network is not started and that quantum is started on your control node. Also ensure that your /etc/nova/nova.conf is configured to use quantum and a plugin. For my setup I have: network_api_class = nova.network.quantumv2.api.API quantum_admin_username = quantum_admin_password = quantum_admin_auth_url = http://localhost:5000/v2.0/ quantum_auth_strategy = keystone quantum_admin_tenant_name = service quantum_url = http://localhost:9696/ libvirt_vif_driver = nova.virt.libvirt.vif.LibvirtOpenVswitchVirtualPortDriver linuxnet_interface_driver = nova.network.linux_net.LinuxOVSInterfaceDriver linuxnet_ovs_integration_bridge = br-int quantum_ovs_bridge = br-int In the default section of my nova.conf. Obviously those will vary depending on your hypervisor and which plugin you are using. Jay S. Bryant Linux Developer - OpenStack Enterprise Edition Department 7YLA, Building 015-2, Office E125, Rochester, MN Telephone: (507) 253-4270, FAX (507) 253-6410 TIE Line: 553-4270 E-Mail: jsbry...@us.ibm.com All the world's a stage and most of us are desperately unrehearsed. -- Sean O'Casey From: Arindam Choudhury To: Jay S Bryant/Rochester/IBM@IBMUS, openstack , Date: 04/25/2013 11:42 AM Subject:RE: [Openstack] nova-network no ip for vm Hi, Actually the problem was solved by installing nbd module. Now I have one weird problem. I have mistakenly installed nova-network in compute node and it had became the default one. Can you tell be how to fix it? To: arin...@live.com Subject: Re: [Openstack] nova-network no ip for vm From: jsbry...@us.ibm.com Date: Thu, 25 Apr 2013 11:32:18 -0500 Arindam, I realized last night that the iptables command I sent didn't have the right network interface specification for your environment. It should have been: iptables -I INPUT -i -p udp --dport 67:68 --sport 67:68 -j ACCEPT . It looks like that might be vnet0? Sorry, I don't use iptables much and just stumbled upon the fix for our environment out of luck. :-) Jay S. Bryant Linux Developer - OpenStack Enterprise Edition Department 7YLA, Building 015-2, Office E125, Rochester, MN Telephone: (507) 253-4270, FAX (507) 253-6410 TIE Line: 553-4270 E-Mail: jsbry...@us.ibm.com All the world's a stage and most of us are desperately unrehearsed. -- Sean O'Casey From:Arindam Choudhury To:Staicu Gabriel , openstack , Date:04/25/2013 04:19 AM Subject:Re: [Openstack] nova-network no ip for vm Sent by:"Openstack" Hi, Thanks for your reply. Here is the logs from /var/log/messages: Apr 25 11:14:40 aopcso1 kernel: [589256.953753] device vnet0 entered promiscuous mode Apr 25 11:14:40 aopcso1 kernel: [589257.014414] br100: port 2(vnet0) entering forwarding state Apr 25 11:14:40 aopcso1 kernel: [589257.014430] br100: port 2(vnet0) entering forwarding state Apr 25 11:14:55 aopcso1 kernel: [589272.014705] br100: port 2(vnet0) entering forwarding state and the logs from /var/log/syslog: Apr 25 11:14:07 aopcso1 dnsmasq[12485]: direcciónes /etc/hosts - 23 leídas Apr 25 11:14:07 aopcso1 dnsmasq-dhcp[12485]: read /var/lib/nova/networks/nova-br100.conf Apr 25 11:14:39 aopcso1 NetworkManager[3980]:SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/vnet0, iface: vnet0) Apr 25 11:14:39 aopcso1 NetworkManager[3980]:SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/vnet0, iface: vnet0): no ifupdown configuration found. Apr 25 11:14:39 aopcso1 NetworkManager[3980]: /sys/devices/virtual/net/vnet0: couldn't determine device driver; ignoring... Apr 25 11:14:40 aopcso1 kernel: [589256.953753] device vnet0 entered promiscuous mode Apr 25 11:14:40 aopcso1 kernel: [589257.014414] br100: port 2(vnet0) entering forwarding state Apr 25 11:14:40 aopcso1 kernel: [589257.014430] br100: port 2(vnet0) entering forwarding state Apr 25 11:14:44 aopcso1 ntpd[4796]: Listen normally on 67 vnet0 fe80::fc16:3eff:fe8a:f597 UDP 123 Apr 25 11:14:44 aopcso1 ntpd[4796]: peers refreshed Apr 25 11:14:50 aopcso1 kernel: [589267.164541] vnet0: no IPv6 routers present Apr 25 11:14:55 aopcso1 kernel: [589272.014705] br100: port 2(vnet0) entering forwarding state Date: Thu, 25 Apr 2013 01:53:02 -0700 From: gabriel_sta...@yahoo.com Subject: Re: [Openstack] nova-network no ip for vm To: arin...@live.com; openstack@lists.launchpad.net Hi, A place to look for eventually error messages is also /var/log/messages. Look for dnsmasq related message and post them here. Regards, Gabriel From: Arin
Re: [Openstack] problem with metadata and ping
Can you provided the output of 'ifconfig' on the hosting node? Also 'ps aux | grep dnsmasq' . Jay S. Bryant Linux Developer - OpenStack Enterprise Edition Department 7YLA, Building 015-2, Office E125, Rochester, MN Telephone: (507) 253-4270, FAX (507) 253-6410 TIE Line: 553-4270 E-Mail: jsbry...@us.ibm.com All the world's a stage and most of us are desperately unrehearsed. -- Sean O'Casey From: Arindam Choudhury To: Jay S Bryant/Rochester/IBM@IBMUS, openstack , Date: 04/24/2013 11:16 AM Subject:RE: [Openstack] problem with metadata and ping Hi, So I added that rule: iptables -I INPUT -i tap+ -p udp --dport 67:68 --sport 67:68 -j ACCEPT but still the same problem. There is another thing: # nova-manage service list Binary Host Zone Status State Updated_At nova-network aopcach internal enabled :-) 2013-04-24 16:07:37 nova-certaopcach internal enabled :-) 2013-04-24 16:07:36 nova-conductor aopcach internal enabled :-) 2013-04-24 16:07:36 nova-consoleauth aopcach internal enabled :-) 2013-04-24 16:07:36 nova-scheduler aopcach internal enabled :-) 2013-04-24 16:07:36 nova-network aopcso1 internal enabled :-) 2013-04-24 16:07:36 nova-compute aopcso1 nova enabled:-) 2013-04-24 16:07:37 shows all the host and services. But in dashboard it only shows the services running in aopcach. screenshot: http://imgur.com/ED9nbxU To: arin...@live.com CC: openstack@lists.launchpad.net Subject: RE: [Openstack] problem with metadata and ping From: jsbry...@us.ibm.com Date: Wed, 24 Apr 2013 10:55:12 -0500 Arindam, Ooops, I had a typo. The command should have been: iptables -I input -i tap+ -p udp -dport 67:68 --sport 67:68 -j ACCEPT You need the iptables configuration on the system where dnsmasq is running. It shouldn't be necessary in the compute nodes that are being booted. Jay S. Bryant Linux Developer - OpenStack Enterprise Edition Department 7YLA, Building 015-2, Office E125, Rochester, MN Telephone: (507) 253-4270, FAX (507) 253-6410 TIE Line: 553-4270 E-Mail: jsbry...@us.ibm.com All the world's a stage and most of us are desperately unrehearsed. -- Sean O'Casey From: Arindam Choudhury To:Jay S Bryant/Rochester/IBM@IBMUS, openstack , Date:04/24/2013 10:47 AM Subject:RE: [Openstack] problem with metadata and ping Hi, Thanks for your reply. The dnsmasq is running properly. when I tried to run iptables -I input -i tap+ -p udp 67:68 --sport 67:68 -j ACCEPT it says, # iptables -I input -i tap+ -p udp 67:68 --sport 67:68 -j ACCEPT Bad argument `67:68' Do I have to do this iptables configuration in controller or in compute nodes also. To: arin...@live.com Subject: Re: [Openstack] problem with metadata and ping From: jsbry...@us.ibm.com Date: Wed, 24 Apr 2013 10:17:41 -0500 Arindam, I saw a similar problem with quantum. If you have iptables running on the hosting system you may need to update the rules to allow the DHCP Discover packet through: iptables -I input -i tap+ -p udp 67:68 --sport 67:68 -j ACCEPT Also ensure that dnsmasq is running properly. Jay S. Bryant Linux Developer - OpenStack Enterprise Edition Department 7YLA, Building 015-2, Office E125, Rochester, MN Telephone: (507) 253-4270, FAX (507) 253-6410 TIE Line: 553-4270 E-Mail: jsbry...@us.ibm.com All the world's a stage and most of us are desperately unrehearsed. -- Sean O'Casey From:Arindam Choudhury To:openstack , Date:04/24/2013 10:12 AM Subject:Re: [Openstack] problem with metadata and ping Sent by:"Openstack" hi, I was misled by this: [(keystone_user)]$ nova list +--+++---+ | ID | Name | Status | Networks | +--+++---+ | 122ceb44-0b2d-442f-bb4b-c5a8cdbcb757 | cirros | ACTIVE | private=192.168.100.2 | +--+++---+ This is a nova-network problem. From
Re: [Openstack] problem with metadata and ping
Arindam, Ooops, I had a typo. The command should have been: iptables -I input -i tap+ -p udp -dport 67:68 --sport 67:68 -j ACCEPT You need the iptables configuration on the system where dnsmasq is running. It shouldn't be necessary in the compute nodes that are being booted. Jay S. Bryant Linux Developer - OpenStack Enterprise Edition Department 7YLA, Building 015-2, Office E125, Rochester, MN Telephone: (507) 253-4270, FAX (507) 253-6410 TIE Line: 553-4270 E-Mail: jsbry...@us.ibm.com All the world's a stage and most of us are desperately unrehearsed. -- Sean O'Casey From: Arindam Choudhury To: Jay S Bryant/Rochester/IBM@IBMUS, openstack , Date: 04/24/2013 10:47 AM Subject:RE: [Openstack] problem with metadata and ping Hi, Thanks for your reply. The dnsmasq is running properly. when I tried to run iptables -I input -i tap+ -p udp 67:68 --sport 67:68 -j ACCEPT it says, # iptables -I input -i tap+ -p udp 67:68 --sport 67:68 -j ACCEPT Bad argument `67:68' Do I have to do this iptables configuration in controller or in compute nodes also. To: arin...@live.com Subject: Re: [Openstack] problem with metadata and ping From: jsbry...@us.ibm.com Date: Wed, 24 Apr 2013 10:17:41 -0500 Arindam, I saw a similar problem with quantum. If you have iptables running on the hosting system you may need to update the rules to allow the DHCP Discover packet through: iptables -I input -i tap+ -p udp 67:68 --sport 67:68 -j ACCEPT Also ensure that dnsmasq is running properly. Jay S. Bryant Linux Developer - OpenStack Enterprise Edition Department 7YLA, Building 015-2, Office E125, Rochester, MN Telephone: (507) 253-4270, FAX (507) 253-6410 TIE Line: 553-4270 E-Mail: jsbry...@us.ibm.com All the world's a stage and most of us are desperately unrehearsed. -- Sean O'Casey From:Arindam Choudhury To:openstack , Date:04/24/2013 10:12 AM Subject:Re: [Openstack] problem with metadata and ping Sent by:"Openstack" hi, I was misled by this: [(keystone_user)]$ nova list +--+++---+ | ID | Name | Status | Networks | +--+++---+ | 122ceb44-0b2d-442f-bb4b-c5a8cdbcb757 | cirros | ACTIVE | private=192.168.100.2 | +--+++---+ This is a nova-network problem. From: arin...@live.com To: openstack@lists.launchpad.net Date: Wed, 24 Apr 2013 16:12:47 +0200 Subject: [Openstack] problem with metadata and ping Hi, I having problem with metadata service. I am using nova-network. The console log says: Starting network... udhcpc (v1.18.5) started Sending discover... Sending discover... Sending discover... No lease, failing WARN: /etc/rc3.d/S40network failed cloudsetup: checking http://169.254.169.254/20090404/metadata/instanceid wget: can't connect to remote host (169.254.169.254): Network is unreachable cloudsetup: failed 1/30: up 10.06. request failed. the whole console log is here: https://gist.github.com/arindamchoudhury/5452385 my nova.conf is here: https://gist.github.com/arindamchoudhury/5452410 [(keystone_user)]$ nova network-list ++-+--+ | ID | Label | Cidr | ++-+--+ | 1 | private | 192.168.100.0/24 | ++-+--+ [(keystone_user)]$ nova secgroup-list +-+-+ | Name| Description | +-+-+ | default | default | +-+-+ [(keystone_user)]$ nova secgroup-list-rules default +-+---+-+---+--+ | IP Protocol | From Port | To Port | IP Range | Source Group | +-+---+-+---+--+ | icmp| -1| -1 | 0.0.0.0/0 | | | tcp | 22| 22 | 0.0.0.0/0 | | +-+---+-+---+--+ ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More
