Re: [Openstack] Cinder error
Hi Guilherme,
The RabbitMQ has virtual host for many applications. Default, the Rabbit
created a default virtualhost with /.
You can see this with the command:
root@controller:~# rabbitmqctl list_permissions
Listing permissions in vhost "/" ...
guest.*.*.*
...done.
Regards,
Marcelo Dieder
On 09/23/2013 04:57 PM, Guilherme Russi wrote:
I guess I've got something:
2013-09-23 16:52:17 INFO [cinder.openstack.common.rpc.common]
Connected to AMQP server on localhost:5672
I've found this page
https://ask.openstack.org/en/question/4581/cinder-unable-to-connect-to-rabbitmq/ and zipmaster07
answered "rabbit_virtual_host = /nova
I commented out the "rabbit_virtual_host", restarted all cinder
services and I can see a successful connection to AMQP now."
And I did that, now it's connected, but what is this
rabbit_virtual_host? What does it do?
I'll test my volumes now.
Regards.
2013/9/23 Guilherme Russi <mailto:luisguilherme...@gmail.com>>
I've looked at the quantum/server.log and nova-scheduler.log and
they show:
2013-09-23 16:25:27 INFO [quantum.openstack.common.rpc.common]
Reconnecting to AMQP server on localhost:5672
2013-09-23 16:25:27 INFO [quantum.openstack.common.rpc.common]
Connected to AMQP server on localhost:5672
2013-09-23 16:24:01.830 5971 INFO nova.openstack.common.rpc.common
[-] Reconnecting to AMQP server on 127.0.0.1:5672
<http://127.0.0.1:5672>
2013-09-23 16:24:01.879 5971 INFO nova.openstack.common.rpc.common
[-] Connected to AMQP server on 127.0.0.1:5672 <http://127.0.0.1:5672>
But at the cinder-volume.log:
INFO [cinder.openstack.common.rpc.common] Reconnecting to AMQP
server on localhost:5672
2013-09-23 16:46:04ERROR [cinder.openstack.common.rpc.common]
AMQP server on localhost:5672 is unreachable: Socket closed.
Trying again in 30 seconds.
I was typing when you sent your answer, here is it:
rabbitmq-server status
Status of node rabbit@hemera ...
[{pid,17266},
{running_applications,[{rabbit,"RabbitMQ","2.7.1"},
{os_mon,"CPO CXC 138 46","2.2.7"},
{sasl,"SASL CXC 138 11","2.1.10"},
{mnesia,"MNESIA CXC 138 12","4.5"},
{stdlib,"ERTS CXC 138 10","1.17.5"},
{kernel,"ERTS CXC 138 10","2.14.5"}]},
{os,{unix,linux}},
{erlang_version,"Erlang R14B04 (erts-5.8.5) [source] [64-bit]
[smp:4:4] [rq:4] [async-threads:30] [kernel-poll:true]\n"},
{memory,[{total,30926120},
{processes,14354392},
{processes_used,14343184},
{system,16571728},
{atom,1124441},
{atom_used,1120343},
{binary,268176},
{code,11134417},
{ets,2037120}]},
{vm_memory_high_watermark,0.4},
{vm_memory_limit,3299385344 }]
...done.
Yes, I've restarted the rabbitmq-server, but as you can see at the
logs, quantum and nova are connected.
Ideas??
Regards.
2013/9/23 Marcelo Dieder mailto:marcelodie...@gmail.com>>
What's the status of your rabbitmq?
# rabbitmqctl status
And do you tried restart the rabbitmq?
Regards,
Marcelo Dieder
On 09/23/2013 03:31 PM, Guilherme Russi wrote:
Yes, it is at the same place
cat /etc/cinder/cinder.conf
[DEFAULT]
rootwrap_config=/etc/cinder/rootwrap.conf
sql_connection = mysql://cinder:password@localhost/cinder
api_paste_confg = /etc/cinder/api-paste.ini
iscsi_helper=ietadm
#iscsi_helper = tgtadm
volume_name_template = volume-%s
volume_group = cinder-volumes
verbose = True
auth_strategy = keystone
iscsi_ip_address=localhost
rabbit_host = localhost
rabbit_port = 5672
rabbit_userid = rabbit
rabbit_password = password
rabbit_virtual_host = /nova
state_path = /var/lib/cinder
lock_path = /var/lock/cinder
volumes_dir = /var/lib/cinder/volumes
Another idea?
Regards.
2013/9/23 Gangur, Hrushikesh (HP Converged Cloud - R&D -
Sunnyvale) mailto:hrushikesh.gan...@hp.com>>
Ensure that cinder configuration files have correct IP of
rabbimq host.
*From:*Guilherme Russi [mailto:luisguilherme...@gmail.com
<mailto:luisguilherme...@gmail.com>]
*Sent:* Monday, September 23, 2013 10:53 AM
*To:* openstack
*Subject:* [Openstack] Cinder error
Hello guys, I'm reinstalling my OpenStack Grizzly and I&#x
Re: [Openstack] Cinder error
What's the status of your rabbitmq? # rabbitmqctl status And do you tried restart the rabbitmq? Regards, Marcelo Dieder On 09/23/2013 03:31 PM, Guilherme Russi wrote: Yes, it is at the same place cat /etc/cinder/cinder.conf [DEFAULT] rootwrap_config=/etc/cinder/rootwrap.conf sql_connection = mysql://cinder:password@localhost/cinder api_paste_confg = /etc/cinder/api-paste.ini iscsi_helper=ietadm #iscsi_helper = tgtadm volume_name_template = volume-%s volume_group = cinder-volumes verbose = True auth_strategy = keystone iscsi_ip_address=localhost rabbit_host = localhost rabbit_port = 5672 rabbit_userid = rabbit rabbit_password = password rabbit_virtual_host = /nova state_path = /var/lib/cinder lock_path = /var/lock/cinder volumes_dir = /var/lib/cinder/volumes Another idea? Regards. 2013/9/23 Gangur, Hrushikesh (HP Converged Cloud - R&D - Sunnyvale) mailto:hrushikesh.gan...@hp.com>> Ensure that cinder configuration files have correct IP of rabbimq host. *From:*Guilherme Russi [mailto:luisguilherme...@gmail.com <mailto:luisguilherme...@gmail.com>] *Sent:* Monday, September 23, 2013 10:53 AM *To:* openstack *Subject:* [Openstack] Cinder error Hello guys, I'm reinstalling my OpenStack Grizzly and I'm getting problem with my cinder, I'm getting "*Error: *Unable to retrieve volume list." I was looking at the cinder log and I only found this error: ERROR [cinder.openstack.common.rpc.common] AMQP server on 192.168.3.1:5672 <http://192.168.3.1:5672> is unreachable: Socket closed. Trying again in 30 seconds. I have a partition created: pvdisplay --- Physical volume --- PV Name /dev/sda7 VG Name cinder-volumes PV Size 279,59 GiB / not usable 1,00 MiB Allocatable yes PE Size 4,00 MiB Total PE 71574 Free PE 66454 Allocated PE 5120 PV UUID KHITxF-uagF-xADc-F8fu-na8t-1OXT-rDFbQ6 root@hemera:/home/hemera# vgdisplay --- Volume group --- VG Name cinder-volumes System ID Format lvm2 Metadata Areas1 Metadata Sequence No 6 VG Access read/write VG Status resizable MAX LV0 Cur LV2 Open LV 0 Max PV0 Cur PV1 Act PV1 VG Size 279,59 GiB PE Size 4,00 MiB Total PE 71574 Alloc PE / Size 5120 / 20,00 GiB Free PE / Size 66454 / 259,59 GiB VG UUID mhN3uV-n80a-zjeb-uR35-0IPb-BFmo-G2Qehu I don't know how to fix this error, any help? Thank you all and regards. Guilherme. ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] Pesquisa Openstack Brasil
Sorry. I sent to thist list, but it was for the local list. Please disregard this email. Em 19 de setembro de 2013 09:41, Marcelo Dieder escreveu: > Pessoal, > > Encaminho abaixo o link para a pesquisa do Openstack aqui no Brasil. A > pesquisa foi baseada em partes no "Openstack Survey" que é realizado pela > Fundação. Ainda assim, se alguém do grupo quiser sugerir alguma outra questão, > ou mesmo administrar o formulário por favor fique a vontade. > > A pesquisa será utilizada para apresentarmos o uso do Openstack aqui no > Brasil no próximo Summit em Hong Kong e será muito válido para termos uma > evolução do Openstack por aqui. Penso que é importante a participação de > todos que tenham o mínimo de envolvimento com o projeto. A pesquisa não > levará mais do que 3 minutos, e não há a obrigatoriedade de se > identificar ou mesmo identificar a sua corporação, ainda que seja > necessário colocar algum nome. > > Ela ficará aberta a partir de hoje até o dia 30/09 e será disponibilizadapara > todos verem > os resultados. > > > https://docs.google.com/forms/d/1npNipUeK0Zkru5RvIu25VUcHjmUuvOFugGFWGmuO82M/viewform > > > -- > Att. > Marcelo Dieder > -- Att. Marcelo Dieder ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
[Openstack] Pesquisa Openstack Brasil
Pessoal, Encaminho abaixo o link para a pesquisa do Openstack aqui no Brasil. A pesquisa foi baseada em partes no "Openstack Survey" que é realizado pela Fundação. Ainda assim, se alguém do grupo quiser sugerir alguma outra questão, ou mesmo administrar o formulário por favor fique a vontade. A pesquisa será utilizada para apresentarmos o uso do Openstack aqui no Brasil no próximo Summit em Hong Kong e será muito válido para termos uma evolução do Openstack por aqui. Penso que é importante a participação de todos que tenham o mínimo de envolvimento com o projeto. A pesquisa não levará mais do que 3 minutos, e não há a obrigatoriedade de se identificar ou mesmo identificar a sua corporação, ainda que seja necessário colocar algum nome. Ela ficará aberta a partir de hoje até o dia 30/09 e será disponibilizadapara todos verem os resultados. https://docs.google.com/forms/d/1npNipUeK0Zkru5RvIu25VUcHjmUuvOFugGFWGmuO82M/viewform -- Att. Marcelo Dieder ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
[Openstack] Cannot create instances on Xenserver 6.2
nAPI.py", line 209, in _parse_result\nraise Failure(result[\'ErrorDescription\'])\n', 'Failure: [\'XENAPI_PLUGIN_FAILURE\', \'download_vhd\', \'TypeError\', "download_vhd() got an unexpected keyword argument \'auth_token\'"]\n'] Below more details about the images and computes: root@xenCompute001:~# glance image-list +--+-+-+--+-++ | ID | Name| Disk Format | Container Format | Size| Status | +--+-+-+--+-++ | 835567db-432b-45bb-ad96-3c45a8e4c9a5 | Cirros-0.3.0-x86_64_vhd | vhd | ovf | 9220007 | active | | 95dbc980-a9e5-4413-ba70-8e7200f78c8d | cirros-0.3.0_64 | qcow2 | bare | 9761280 | active | +--+-+-+--+-++ root@xenCompute001:~# glance image-show 835567db-432b-45bb-ad96-3c45a8e4c9a5 +--+--+ | Property | Value| +--+--+ | checksum | 56dcf159bbf8373886112c5d07d23901 | | container_format | ovf | | created_at | 2013-09-13T19:57:49 | | deleted | False| | disk_format | vhd | | id | 835567db-432b-45bb-ad96-3c45a8e4c9a5 | | is_public| True | | min_disk | 0| | min_ram | 0| | name | Cirros-0.3.0-x86_64_vhd | | owner| 45b5536f182f486da4ac0fa35a031f06 | | protected| False| | size | 9220007 | | status | active | | updated_at | 2013-09-13T19:57:49 | +--+--+ root@xen1:~# nova-manage service list Binary Host Zone Status State Updated_At nova-consoleauth controller internal enabled:-) 2013-09-17 05:59:47 nova-certcontroller internal enabled:-) 2013-09-17 05:59:47 nova-scheduler controller internal enabled:-) 2013-09-17 05:59:47 nova-conductor controller internal enabled:-) 2013-09-17 05:59:47 nova-compute c01 nova enabled:-) 2013-09-17 05:59:52 nova-compute xenCompute001nova enabled :-) 2013-09-17 05:59:52 Does anyone know this problem? -- Att. Marcelo Dieder ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] Translation Push - get the dashboard in your language by Sep 24
Hello Tom, Translating to Brazilian Portuguese Marcelo Dieder On 09/12/2013 05:16 AM, Tom Fifield wrote: Do you write Spanish, Italian, Russian, German or Dutch? How about Portuguese? Indonesian? Arabic? Hindi? Actually, if you can write in any language other than English, you have the ability to help get the OpenStack Dashboard into your language. Find your language on: https://www.transifex.com/projects/p/horizon/ and join the team. It's actually a lot of fun, all done through an easy web interface. If we can get 100% completion in your language by September 24th, your text will be included in the next release of OpenStack for thousands around the world to see. So, why not get your friends together and make it happen? :) Thanks, from your friendly Internationalisation Team https://wiki.openstack.org/wiki/I18nTeam ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] Quantum/Grizzy - Instance doesn't get IP
The python-quantumclient also has different versions at the two guides. Marcelo Dieder On 09/06/2013 11:26 AM, Marcelo Dieder wrote: Hi Nicolae, Apparently I have not located the problem, but I followed the tutorial and now the quantum agent-list command worked. I made a comparison with the packages and guide http://docs.openstack.org/grizzly/basic-install/apt/content/basic-install_controller.html The difference between the two seems to be in openvswitch packages and kernel version. Guide in DOCS OpenStack seems the packages are incompatible and commands such as quantum-agent that doesn't exist. Guide: https://github.com/mseknibilel/OpenStack-Grizzly-Install-Guide/blob/OVS_MultiNode/OpenStack_Grizzly_Install_Guide.rst Packages: quantum-plugin-openvswitch:amd64 (2013.1.2-0ubuntu1~cloud0, automatic) quantum-l3-agent:amd64 (2013.1.2-0ubuntu1~cloud0) quantum-dhcp-agent:amd64 (2013.1.2-0ubuntu1~cloud0) quantum-plugin-openvswitch-agent:amd64 (2013.1.2-0ubuntu1~cloud0) python-quantumclient:amd64 (2.2.0-0ubuntu1~cloud0, automatic) python-quantum:amd64 (2013.1.2-0ubuntu1~cloud0, automatic) quantum-metadata-agent:amd64 (2013.1.2-0ubuntu1~cloud0) quantum-common:amd64 (2013.1.2-0ubuntu1~cloud0, automatic) openvswitch-switch:amd64 (1.4.0-1ubuntu1.5) openvswitch-common:amd64 (1.4.0-1ubuntu1.5, automatic) openvswitch-datapath-dkms:amd64 (1.4.0-1ubuntu1.5) root@network:~# lsb_release -a No LSB modules are available. Distributor ID:Ubuntu Description:Ubuntu 12.04.3 LTS Release:12.04 Codename:precise root@network:~# uname -r 3.5.0-39-generic APT Sources deb http://ubuntu-cloud.archive.canonical.com/ubuntu precise-updates/grizzly main Guide: http://docs.openstack.org/grizzly/basic-install/apt/content/basic-install_controller.html quantum-plugin-openvswitch:amd64 (2013.1.2-0ubuntu1~cloud0, automatic) quantum-l3-agent:amd64 (2013.1.2-0ubuntu1~cloud0) quantum-dhcp-agent:amd64 (2013.1.2-0ubuntu1~cloud0) quantum-plugin-openvswitch-agent:amd64 (2013.1.2-0ubuntu1~cloud0) python-quantumclient:amd64 (3.0.a1-1, automatic) python-quantum:amd64 (2013.1.2-0ubuntu1~cloud0, automatic) quantum-metadata-agent:amd64 (2013.1.2-0ubuntu1~cloud0, automatic) quantum-common:amd64 (2013.1.2-0ubuntu1~cloud0, automatic) openvswitch-switch:amd64 (1.4.2+git20120612-9.1~deb7u1) openvswitch-common:amd64 (1.4.2+git20120612-9.1~deb7u1, automatic) openvswitch-datapath-dkms:amd64 (1.4.2+git20120612-9.1~deb7u1) root@network:~# lsb_release -a No LSB modules are available. Distributor ID:Ubuntu Description:Ubuntu 12.04.3 LTS Release:12.04 Codename:precise root@network:~# uname -r 3.2.0-52-generic APT Sources deb http://ubuntu-cloud.archive.canonical.com/ubuntu precise-updates/grizzly main deb http://archive.gplhost.com/debian grizzly main deb http://archive.gplhost.com/debian grizzly-backports main After I set everything up again with guide mseknibilel, the quantum agent-list works, and the instance can finally get the IP. An important issue to be checked is whether the network interfaces of the bridges are in promiscuous mode on the hypervisor. In my case I use XenServer 6.2, I had to enable promisc mode interfaces VIF and PIF. Do you have any logs with errors? Thanks for all. Marcelo Dieder On 09/06/2013 07:20 AM, Nicolae Paladi wrote: Hi Marcelo, I have the same issue (I'm on CentOS 6.4 though); have you found a solution? There was a similar thread earler: http://openstack.redhat.com/forum/discussion/230/warning-quantum-db-agentschedulers_db-fail-scheduling-network/p1 Make sure that all agents are up in 'quantum agent-list' Also, in your quantum/server.log, do you get something like: WARNING [quantum.api.extensions] Extension routed-service-insertion not supported by any of loaded plugins I am trying to understand if this is a related problem or something that can be ignored atm; I can say that after some fiddling with the quantum dhcp agents my instances were getting an IP address and I could reach them yesterday, but apparently that wasn't very stable and today I'm back with the same issue. cheers, /Nicolae On 5 September 2013 03:42, happy idea <mailto:guolongcang.w...@gmail.com>> wrote: Are you sure you had follow this page'guide ? http://docs.openstack.org/grizzly/basic-install/apt/content/basic-install_network.html 2013/9/5 Marcelo Dieder mailto:marcelodie...@gmail.com>> Hi, yes, I have dnsmasq installed on Network Node. root@network:~# apt-get install dnsmasq Reading package lists... Done Building dependency tree Reading state information... Done dnsmasq is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. root@network:~# ps aux | grep -i dnsmasq dnsmasq 3807 0.0 0.1 28820 980 ? S15:29 0:00 /usr/sbin/dnsmasq -x /var/run/dnsmasq/dnsmasq.pid -u dnsmasq
Re: [Openstack] Quantum/Grizzy - Instance doesn't get IP
Hi Nicolae, Apparently I have not located the problem, but I followed the tutorial and now the quantum agent-list command worked. I made a comparison with the packages and guide http://docs.openstack.org/grizzly/basic-install/apt/content/basic-install_controller.html The difference between the two seems to be in openvswitch packages and kernel version. Guide in DOCS OpenStack seems the packages are incompatible and commands such as quantum-agent that doesn't exist. Guide: https://github.com/mseknibilel/OpenStack-Grizzly-Install-Guide/blob/OVS_MultiNode/OpenStack_Grizzly_Install_Guide.rst Packages: quantum-plugin-openvswitch:amd64 (2013.1.2-0ubuntu1~cloud0, automatic) quantum-l3-agent:amd64 (2013.1.2-0ubuntu1~cloud0) quantum-dhcp-agent:amd64 (2013.1.2-0ubuntu1~cloud0) quantum-plugin-openvswitch-agent:amd64 (2013.1.2-0ubuntu1~cloud0) python-quantumclient:amd64 (2.2.0-0ubuntu1~cloud0, automatic) python-quantum:amd64 (2013.1.2-0ubuntu1~cloud0, automatic) quantum-metadata-agent:amd64 (2013.1.2-0ubuntu1~cloud0) quantum-common:amd64 (2013.1.2-0ubuntu1~cloud0, automatic) openvswitch-switch:amd64 (1.4.0-1ubuntu1.5) openvswitch-common:amd64 (1.4.0-1ubuntu1.5, automatic) openvswitch-datapath-dkms:amd64 (1.4.0-1ubuntu1.5) root@network:~# lsb_release -a No LSB modules are available. Distributor ID:Ubuntu Description:Ubuntu 12.04.3 LTS Release:12.04 Codename:precise root@network:~# uname -r 3.5.0-39-generic APT Sources deb http://ubuntu-cloud.archive.canonical.com/ubuntu precise-updates/grizzly main Guide: http://docs.openstack.org/grizzly/basic-install/apt/content/basic-install_controller.html quantum-plugin-openvswitch:amd64 (2013.1.2-0ubuntu1~cloud0, automatic) quantum-l3-agent:amd64 (2013.1.2-0ubuntu1~cloud0) quantum-dhcp-agent:amd64 (2013.1.2-0ubuntu1~cloud0) quantum-plugin-openvswitch-agent:amd64 (2013.1.2-0ubuntu1~cloud0) python-quantumclient:amd64 (3.0.a1-1, automatic) python-quantum:amd64 (2013.1.2-0ubuntu1~cloud0, automatic) quantum-metadata-agent:amd64 (2013.1.2-0ubuntu1~cloud0, automatic) quantum-common:amd64 (2013.1.2-0ubuntu1~cloud0, automatic) openvswitch-switch:amd64 (1.4.2+git20120612-9.1~deb7u1) openvswitch-common:amd64 (1.4.2+git20120612-9.1~deb7u1, automatic) openvswitch-datapath-dkms:amd64 (1.4.2+git20120612-9.1~deb7u1) root@network:~# lsb_release -a No LSB modules are available. Distributor ID:Ubuntu Description:Ubuntu 12.04.3 LTS Release:12.04 Codename:precise root@network:~# uname -r 3.2.0-52-generic APT Sources deb http://ubuntu-cloud.archive.canonical.com/ubuntu precise-updates/grizzly main deb http://archive.gplhost.com/debian grizzly main deb http://archive.gplhost.com/debian grizzly-backports main After I set everything up again with guide mseknibilel, the quantum agent-list works, and the instance can finally get the IP. An important issue to be checked is whether the network interfaces of the bridges are in promiscuous mode on the hypervisor. In my case I use XenServer 6.2, I had to enable promisc mode interfaces VIF and PIF. Do you have any logs with errors? Thanks for all. Marcelo Dieder On 09/06/2013 07:20 AM, Nicolae Paladi wrote: Hi Marcelo, I have the same issue (I'm on CentOS 6.4 though); have you found a solution? There was a similar thread earler: http://openstack.redhat.com/forum/discussion/230/warning-quantum-db-agentschedulers_db-fail-scheduling-network/p1 Make sure that all agents are up in 'quantum agent-list' Also, in your quantum/server.log, do you get something like: WARNING [quantum.api.extensions] Extension routed-service-insertion not supported by any of loaded plugins I am trying to understand if this is a related problem or something that can be ignored atm; I can say that after some fiddling with the quantum dhcp agents my instances were getting an IP address and I could reach them yesterday, but apparently that wasn't very stable and today I'm back with the same issue. cheers, /Nicolae On 5 September 2013 03:42, happy idea <mailto:guolongcang.w...@gmail.com>> wrote: Are you sure you had follow this page'guide ? http://docs.openstack.org/grizzly/basic-install/apt/content/basic-install_network.html 2013/9/5 Marcelo Dieder mailto:marcelodie...@gmail.com>> Hi, yes, I have dnsmasq installed on Network Node. root@network:~# apt-get install dnsmasq Reading package lists... Done Building dependency tree Reading state information... Done dnsmasq is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. root@network:~# ps aux | grep -i dnsmasq dnsmasq 3807 0.0 0.1 28820 980 ? S15:29 0:00 /usr/sbin/dnsmasq -x /var/run/dnsmasq/dnsmasq.pid -u dnsmasq -r /var/run/dnsmasq/resolv.conf -7 /etc/dnsmasq.d,.dpkg-dist,.dpkg-old,.dpkg-new nobody 26040 0.0 0.2 28820 1
Re: [Openstack] Quantum/Grizzy - Instance doesn't get IP
Hi, yes, I have dnsmasq installed on Network Node.
root@network:~# apt-get install dnsmasq
Reading package lists... Done
Building dependency tree
Reading state information... Done
dnsmasq is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@network:~# ps aux | grep -i dnsmasq
dnsmasq 3807 0.0 0.1 28820 980 ?S15:29 0:00
/usr/sbin/dnsmasq -x /var/run/dnsmasq/dnsmasq.pid -u dnsmasq -r
/var/run/dnsmasq/resolv.conf -7
/etc/dnsmasq.d,.dpkg-dist,.dpkg-old,.dpkg-new
nobody 26040 0.0 0.2 28820 1004 ?S15:45 0:00 dnsmasq
--no-hosts --no-resolv --strict-order --bind-interfaces
--interface=tap91e05e25-7f --except-interface=lo
--pid-file=/var/lib/quantum/dhcp/a8f7c937-e8d0-4952-bff6-7d364335df22/pid --dhcp-hostsfile=/var/lib/quantum/dhcp/a8f7c937-e8d0-4952-bff6-7d364335df22/host
--dhcp-optsfile=/var/lib/quantum/dhcp/a8f7c937-e8d0-4952-bff6-7d364335df22/opts
--dhcp-script=/usr/bin/quantum-dhcp-agent-dnsmasq-lease-update
--leasefile-ro --dhcp-range=set:tag0,10.5.5.0,static,120s --conf-file=
--domain=openstacklocal
root 26041 0.0 0.0 28792 244 ?S15:45 0:00 dnsmasq
--no-hosts --no-resolv --strict-order --bind-interfaces
--interface=tap91e05e25-7f --except-interface=lo
--pid-file=/var/lib/quantum/dhcp/a8f7c937-e8d0-4952-bff6-7d364335df22/pid --dhcp-hostsfile=/var/lib/quantum/dhcp/a8f7c937-e8d0-4952-bff6-7d364335df22/host
--dhcp-optsfile=/var/lib/quantum/dhcp/a8f7c937-e8d0-4952-bff6-7d364335df22/opts
--dhcp-script=/usr/bin/quantum-dhcp-agent-dnsmasq-lease-update
--leasefile-ro --dhcp-range=set:tag0,10.5.5.0,static,120s --conf-file=
--domain=openstacklocal
I restarted the service dnsmasq, but occured the same problem when I
started a new instance.
2013-09-04 15:39:44 WARNING [quantum.db.agentschedulers_db] Fail
scheduling network {'status': u'ACTIVE', 'subnets':
[u'80b21701-4b05-4585-985a-60905ff42531'], 'name': u'public',
'provider:physical_network': None, 'admin_state_up': True, 'tenant_id':
u'27d2b93f11ac4e91a3edb26edb28fb6b', 'provider:network_type': u'gre',
'router:external': True, 'shared': False, 'id':
u'b3e465b7-b5a2-45d5-8b24-aa8bea0ab0a0', 'provider:segmentation_id': 2L}
2013-09-04 15:47:00 WARNING [quantum.db.agentschedulers_db] Fail
scheduling network {'status': u'ACTIVE', 'subnets':
[u'80b21701-4b05-4585-985a-60905ff42531'], 'name': u'public',
'provider:physical_network': None, 'admin_state_up': True, 'tenant_id':
u'27d2b93f11ac4e91a3edb26edb28fb6b', 'provider:network_type': u'gre',
'router:external': True, 'shared': False, 'id':
u'b3e465b7-b5a2-45d5-8b24-aa8bea0ab0a0', 'provider:segmentation_id': 2L}
Thanks.
Marcelo Dieder
On 09/04/2013 11:15 AM, Hathaway.Jon wrote:
Do you have dnsmasq installed? I found that it isnt installed as a
dependency. Without it i never received dhcp either.
Sent from my iPhone
On Sep 3, 2013, at 10:31 PM, "happy idea" <mailto:guolongcang.w...@gmail.com>> wrote:
you didn't install the dhcp agent, please refer to this guide
https://github.com/mseknibilel/OpenStack-Grizzly-Install-Guide/blob/OVS_MultiNode/OpenStack_Grizzly_Install_Guide.rst
2013/9/4 Marcelo Dieder <mailto:marcelodie...@gmail.com>>
Hi All!
I have a ambient with 3 hosts (Network, Controller and Node1
(Qemu)). I created an ambient based this tutorial
(http://docs.openstack.org/grizzly/basic-install/apt/content/basic-install_controller.html).
My problem is when I create a instance. The instance Instance
doesn't get IP address.
checkinghttp://169.254.169.254/20090404/instanceid
failed 1/20: up 187.68. request failed
failed 2/20: up 190.06. request failed
failed 3/20: up 192.24. request failed
failed 4/20: up 194.43. request failed
failed 5/20: up 196.61. request failed
failed 6/20: up 198.82. request failed
failed 7/20: up 201.03. request failed
failed 8/20: up 203.22. request failed
failed 9/20: up 205.42. request failed
failed 10/20: up 207.64. request failed
failed 11/20: up 209.87. request failed
failed 12/20: up 212.08. request failed
failed 13/20: up 214.29. request failed
failed 14/20: up 216.49. request failed
failed 15/20: up 218.70. request failed
failed 16/20: up 220.91. request failed
failed 17/20: up 223.13. request failed
failed 18/20: up 225.38. request failed
failed 19/20: up 227.62. request failed
failed 20/20: up 229.87. request failed
failed to read iid from metadata. tried 20
no results found for mode=net. up 232.10
Re: [Openstack] Quantum/Grizzly - Instance doesn't get IP
---+
| id | name|
external_gateway_info |
+--+-++
| 3a703f92-e1d5-4f06-8970-8ae899d40a99 | demo-router | {"network_id":
"b3e465b7-b5a2-45d5-8b24-aa8bea0ab0a0"} |
+--+-++
(quantum) subnet-list
+--+-+--++
| id | name|
cidr | allocation_pools |
+--+-+--++
| 80b21701-4b05-4585-985a-60905ff42531 | public-subnet |
xxx.xxx.xxx.0/24 | {"start": "xxx.xxx.xxx.165", "end": "xxx.xxx.xxx.170"} |
| fd7f324c-25ec-4134-ab97-e827fcf12824 | demo-net-subnet |
10.5.5.0/24 | {"start": "10.5.5.2", "end": "10.5.5.254"} |
+--+-+--++
(quantum)
Any more suggestions?
Thanks!
Marcelo Dieder
On 09/04/2013 02:13 AM, happy idea wrote:
you didn't install the dhcp agent, please refer to this guide
https://github.com/mseknibilel/OpenStack-Grizzly-Install-Guide/blob/OVS_MultiNode/OpenStack_Grizzly_Install_Guide.rst
2013/9/4 Marcelo Dieder <mailto:marcelodie...@gmail.com>>
Hi All!
I have a ambient with 3 hosts (Network, Controller and Node1
(Qemu)). I created an ambient based this tutorial
(http://docs.openstack.org/grizzly/basic-install/apt/content/basic-install_controller.html).
My problem is when I create a instance. The instance Instance
doesn't get IP address.
checkinghttp://169.254.169.254/20090404/instanceid
failed 1/20: up 187.68. request failed
failed 2/20: up 190.06. request failed
failed 3/20: up 192.24. request failed
failed 4/20: up 194.43. request failed
failed 5/20: up 196.61. request failed
failed 6/20: up 198.82. request failed
failed 7/20: up 201.03. request failed
failed 8/20: up 203.22. request failed
failed 9/20: up 205.42. request failed
failed 10/20: up 207.64. request failed
failed 11/20: up 209.87. request failed
failed 12/20: up 212.08. request failed
failed 13/20: up 214.29. request failed
failed 14/20: up 216.49. request failed
failed 15/20: up 218.70. request failed
failed 16/20: up 220.91. request failed
failed 17/20: up 223.13. request failed
failed 18/20: up 225.38. request failed
failed 19/20: up 227.62. request failed
failed 20/20: up 229.87. request failed
failed to read iid from metadata. tried 20
no results found for mode=net. up 232.10. searched: nocloud configdrive ec2
failed to get instanceid of datasource
Starting dropbear sshd: generating rsa key... generating dsa key... OK
=== network info ===
ifinfo: lo,up,127.0.0.1,8,::1
ifinfo: eth0,up,,8,fe80::f816:3eff:fef3:2a6d
=== datasource: None None ===
At the controller I received the warning:
2013-09-04 00:40:44 WARNING
[quantum.scheduler.dhcp_agent_scheduler] No active DHCP agents
2013-09-04 00:40:44 WARNING [quantum.db.agentschedulers_db] Fail
scheduling network {'status': u'ACTIVE', 'subnets':
[u'80b21701-4b05-4585-985a-60905ff42531'], 'name': u'public',
'provider:physical_network': None, 'admin_state_up': True,
'tenant_id': u'27d2b93f11ac4e91a3edb26edb28fb6b',
'provider:network_type': u'gre', 'router:external': True,
'shared': False, 'id': u'b3e465b7-b5a2-45d5-8b24-aa8bea0ab0a0',
'provider:segmentation_id': 2L}
And when I executed:
root@cloud:~# quantum agent-list
Unknown command ['agent-list']
Other commands:
root@cloud:~# nova-manage service list
Binary Host Zone Status State Updated_At
nova-certcloud internal enabled:-)
2013-09-04 03:59:12
nova-consoleauth cloud internal enabled:-)
2013-09-04 03:59:12
nova-scheduler cloud internal enabled:-)
2013-09-04 03:59:12
nova-conductor cloud internal enabled:-)
2013-09-04 03:59:12
nova-compute c01 nova enabled:-) 2013-09-04
03:59:04
root@c01:~# nova list
+--+-+++
| ID | Name
[Openstack] Quantum/Grizzy - Instance doesn't get IP
Hi All!
I have a ambient with 3 hosts (Network, Controller and Node1 (Qemu)). I
created an ambient based this tutorial
(http://docs.openstack.org/grizzly/basic-install/apt/content/basic-install_controller.html).
My problem is when I create a instance. The instance Instance doesn't
get IP address.
checking http://169.254.169.254/20090404/instanceid
failed 1/20: up 187.68. request failed
failed 2/20: up 190.06. request failed
failed 3/20: up 192.24. request failed
failed 4/20: up 194.43. request failed
failed 5/20: up 196.61. request failed
failed 6/20: up 198.82. request failed
failed 7/20: up 201.03. request failed
failed 8/20: up 203.22. request failed
failed 9/20: up 205.42. request failed
failed 10/20: up 207.64. request failed
failed 11/20: up 209.87. request failed
failed 12/20: up 212.08. request failed
failed 13/20: up 214.29. request failed
failed 14/20: up 216.49. request failed
failed 15/20: up 218.70. request failed
failed 16/20: up 220.91. request failed
failed 17/20: up 223.13. request failed
failed 18/20: up 225.38. request failed
failed 19/20: up 227.62. request failed
failed 20/20: up 229.87. request failed
failed to read iid from metadata. tried 20
no results found for mode=net. up 232.10. searched: nocloud configdrive ec2
failed to get instanceid of datasource
Starting dropbear sshd: generating rsa key... generating dsa key... OK
=== network info ===
ifinfo: lo,up,127.0.0.1,8,::1
ifinfo: eth0,up,,8,fe80::f816:3eff:fef3:2a6d
=== datasource: None None ===
At the controller I received the warning:
2013-09-04 00:40:44 WARNING [quantum.scheduler.dhcp_agent_scheduler] No
active DHCP agents
2013-09-04 00:40:44 WARNING [quantum.db.agentschedulers_db] Fail
scheduling network {'status': u'ACTIVE', 'subnets':
[u'80b21701-4b05-4585-985a-60905ff42531'], 'name': u'public',
'provider:physical_network': None, 'admin_state_up': True, 'tenant_id':
u'27d2b93f11ac4e91a3edb26edb28fb6b', 'provider:network_type': u'gre',
'router:external': True, 'shared': False, 'id':
u'b3e465b7-b5a2-45d5-8b24-aa8bea0ab0a0', 'provider:segmentation_id': 2L}
And when I executed:
root@cloud:~# quantum agent-list
Unknown command ['agent-list']
Other commands:
root@cloud:~# nova-manage service list
Binary Host Zone Status State Updated_At
nova-certcloud internal enabled:-) 2013-09-04 03:59:12
nova-consoleauth cloud internal enabled:-) 2013-09-04 03:59:12
nova-scheduler cloud internal enabled:-) 2013-09-04 03:59:12
nova-conductor cloud internal enabled:-) 2013-09-04 03:59:12
nova-compute c01 nova enabled:-) 2013-09-04 03:59:04
root@c01:~# nova list
+--+-+++
| ID | Name| Status |
Networks |
+--+-++--------+
| 2c704622-1b5f-4651-9553-51aabee9090c | test29 | ACTIVE |
public=xxx.xxx.xxx.xxx |
I searched but I couldn't find any resolution. Anybody has this problem?
Cheers.
Marcelo Dieder
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
