Hello Lluis Dev,
I'm calling Dev's attention to this problem.
Look forward to hear back whenever possible.
Cheers,
Joao
-----Original Message-----
From: Lluís Gifre [mailto:[email protected]]
Sent: 10 April 2015 17:03
To: Joao Prino; Adrian Smith
Cc: contrailuser
Subject: Re: [Users] Error creating volumes with cinder
Hi Joao,
Yes, I have already done this correciton but the problem "No backend provided"
and "No valid host was found" while the cinder-scheduler is creating the volume
is still happening.
Thanks,
Lluis
El 10/04/15 a les 17:54, Joao Prino ha escrit:
> Hi Lluis,
>
> I had this exact same problem where was able to solve it by adding the
> "rabbit_host = <ip>" under '/etc/cinder/cinder.conf', editing
> '/etc/rabbitmq/rabbitmq.config' to match my cluster setup's fqdn (wrongly
> populated) and changed the existing "rabbit_host = <ip>" from
> '/etc/nova/nova.conf as it had the wrong IP assigned to it.
> This problem was due to having two NICs where RabbitMQ was given my
> NIC1 address settings and it should have had my NIC2's address according to
> the testbed file..
>
> Hope it helps!
>
> Joao
>
>
> -----Original Message-----
> From: Users [mailto:[email protected]] On Behalf Of
> Lluís Gifre
> Sent: 10 April 2015 15:19
> To: Adrian Smith
> Cc: contrailuser
> Subject: Re: [Users] Error creating volumes with cinder
>
> Hi Adrian,
>
> Thanks for your quick answer.
> I checked the log you mentioned but I hadn't found any interesting thing.
>
> Do you have any other idea?
>
> Thanks,
> Lluis
>
> El 10/04/15 a les 13:14, Adrian Smith ha escrit:
>> Hi Lluis,
>>
>> Take a look in the cinder scheduler log,
>> /var/log/cinder/scheduler.log. It should have a more meaningful error.
>>
>> Adrian
>>
>> On 10 April 2015 at 11:48, Lluís Gifre <[email protected]> wrote:
>>> Dear all,
>>>
>>> I'm deploying a opencontrail 2.10 + openstack icehouse testbed in
>>> Ubuntu 14.04.
>>> I tried it in many ways (with physical and virtual machines, single
>>> and multi-box testbeds).
>>>
>>> Right now I'm trying with a single virtual machine with LVM and the
>>> cinder-volumes volume group created.
>>>
>>> The deploy completes successfully.
>>>
>>> However, just after completing the set-up, I realized that in
>>> cinder-schedule.log the next message is added periodically:
>>>
>>> 2015-04-10 07:27:29.426 2315 INFO
>>> oslo.messaging._drivers.impl_rabbit
>>> [req-e77c84ab-49f6-40f2-bb20-1c62b23605d6 - - - - -] Reconnecting to
>>> AMQP server on localhost:5672
>>> 2015-04-10 07:27:29.427 2315 INFO
>>> oslo.messaging._drivers.impl_rabbit
>>> [req-e77c84ab-49f6-40f2-bb20-1c62b23605d6 - - - - -] Delaying
>>> reconnect for
>>> 1.0 seconds...
>>> 2015-04-10 07:27:30.442 2315 ERROR
>>> oslo.messaging._drivers.impl_rabbit
>>> [req-e77c84ab-49f6-40f2-bb20-1c62b23605d6 - - - - -] AMQP server on
>>> localhost:5672 is unreachable: [Errno 111] ECONNREFUSED. Trying
>>> again in 30 seconds.
>>>
>>> To solve the problem I edited /etc/cinder/cinder.conf and added:
>>>
>>> rabbit_host = 192.168.67.13 # IP address taken from
>>> /etc/rabbitmq/rabbitmq.config rabbit_port = 5672
>>>
>>> Content of my /etc/rabbitmq/rabbitmq.config:
>>>
>>> [
>>> {rabbit, [ {tcp_listeners, [{"192.168.67.13", 5672}]},
>>> {loopback_users, []},
>>> {log_levels,[{connection, info},{mirroring, info}]} ]
>>> }
>>> ].
>>>
>>> After rebooting, this change solved the recurrent reconnecting to
>>> AMQP problem.
>>> Right now the cinder-scheduler log shows:
>>>
>>> 2015-04-10 07:32:44.063 2525 AUDIT cinder.service [-] Starting
>>> cinder-scheduler node (version 2014.1.3)
>>> 2015-04-10 07:32:44.197 2525 INFO
>>> oslo.messaging._drivers.impl_rabbit
>>> [req-21e86bf9-3fa6-4ab0-9968-616242200c41 - - - - -] Connected to
>>> AMQP server on 192.168.67.13:5672
>>> 2015-04-10 07:32:48.383 2525 INFO
>>> oslo.messaging._drivers.impl_rabbit
>>> [-] Connected to AMQP server on 192.168.67.13:5672
>>>
>>> Next I tried to create a volume, no mater if I do it from the
>>> openstack dashboard or using cinder's or nova's command line
>>> interface, the result is an error. For example trying with cinder command
>>> line:
>>>
>>> # cinder list
>>> +----+--------+--------------+------+-------------+----------+-------------+
>>> | ID | Status | Display Name | Size | Volume Type | Bootable |
>>> | Attached to |
>>> +----+--------+--------------+------+-------------+----------+-------------+
>>> +----+--------+--------------+------+-------------+----------+-------------+
>>>
>>> # cinder create --display-name test 1
>>> +---------------------+--------------------------------------+
>>> | Property | Value |
>>> +---------------------+--------------------------------------+
>>> | attachments | [] |
>>> | availability_zone | nova |
>>> | bootable | false |
>>> | created_at | 2015-04-10T07:57:12.787493 |
>>> | display_description | None |
>>> | display_name | test |
>>> | encrypted | False |
>>> | id | d374b571-5df1-47f3-ae6e-c3218aebb9db |
>>> | metadata | {} |
>>> | size | 1 |
>>> | snapshot_id | None |
>>> | source_volid | None |
>>> | status | creating |
>>> | volume_type | None |
>>> +---------------------+--------------------------------------+
>>>
>>> # cinder list
>>> +--------------------------------------+--------+--------------+------+-------------+----------+-------------+
>>> | ID | Status | Display Name | Size |
>>> Volume Type | Bootable | Attached to |
>>> +--------------------------------------+--------+--------------+------+-------------+----------+-------------+
>>> | d374b571-5df1-47f3-ae6e-c3218aebb9db | error | test | 1 |
>>> None | false | |
>>> +--------------------------------------+--------+--------------+------+-------------+----------+-------------+
>>>
>>> Then I checked the /var/log/cinder/cinder-scheduler.log and found
>>> next
>>> message:
>>>
>>> 2015-04-10 07:36:14.547 2525 WARNING cinder.context [-] Arguments
>>> dropped when creating context: {'user':
>>> u'ad2be0cd57c44177b1ba9b0735ea0f44',
>>> 'tenant': u'90aab64e7e2b45f3891b0f08978e063e', 'user_identity':
>>> u'ad2be0cd57c44177b1ba9b0735ea0f44 90aab64e7e2b45f3891b0f08978e063e
>>> -
>>> - -'}
>>> 2015-04-10 07:36:14.629 2525 ERROR
>>> cinder.scheduler.flows.create_volume
>>> [req-ba5d16aa-5092-4f5f-a4c6-d9481df83bfd
>>> ad2be0cd57c44177b1ba9b0735ea0f44 90aab64e7e2b45f3891b0f08978e063e -
>>> - -] Failed to schedule_create_volume: No valid host was found.
>>>
>>> I have enabled DEBUG by adding debug = True to
>>> /etc/cinder/cinder.conf and found in the cinder-scheduler.log: ... No
>>> backend provided ...
>>> I installed and condifured tgtd according to
>>> http://rconradharris.com/2013/01/14/getting-cinder-up-and-running.ht
>>> m
>>> l
>>>
>>> But the error still remains.
>>>
>>> Do somebody have an idea of how to solve this problem?
>>>
>>> Thanks,
>>> Lluis
>>>
>>>
>>> _______________________________________________
>>> Users mailing list
>>> [email protected]
>>> http://lists.opencontrail.org/mailman/listinfo/users_lists.opencontr
>>> a
>>> il.org
>
> _______________________________________________
> Users mailing list
> [email protected]
> http://lists.opencontrail.org/mailman/listinfo/users_lists.opencontrai
> l.org
_______________________________________________
Users mailing list
[email protected]
http://lists.opencontrail.org/mailman/listinfo/users_lists.opencontrail.org
