date:20141107

[Openstack] [Ironic] Questions about ironic deployment

2014-11-07 Thread Michael Turek


Hello all,

I've been working at getting an ironic setup going (following the 
installation guide 
http://docs.openstack.org/developer/ironic/deploy/install-guide.html).


I'm up to the node creation step and have some questions

1) In regards to the baremetal flavor, how closely do the extra-specs 
need to match the physical node?
a) The node I'm working with has a strange amount of memory, 
65952964 KiB which does not evenly map to the MiB units requested by 
ironic (65952964 KiB / 1024 = 64407.1914063 MiB). What kind of rounding 
should I do?
b) Should the 'local_gb' property of the node be the size (in 
GiB) of the partition where the os will be installed or should it be the 
sum of the partitions?


2) Does pxe_root_gb refer to the size of the partition where the OS will 
be installed or is it something else?


I appreciate any insight, thanks for the help!

-Mike


___
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] Glance timeout error

2014-11-07 Thread Matt Kassawara

Glance shouldn't use the message queue unless you're using ceilometer. The
default configuration file might enable it, but it won't work without
configuring additional options. In glance-api.conf, configure
'notification_driver = noop' to disable it.

On Fri, Nov 7, 2014 at 9:16 AM, varun bhatnagar 
wrote:

> Hi Adrián,
>
> I don't think it is listening on 0.0.0.0:5672
>
> This is the output which I am getting:
>
>
> *Ops-Controller:~ # netstat -tunelp|grep 5672tcp0  0
> :::5672 :::*LISTEN  113
> 69412  30402/beam  Ops-Controller:~ #*
>
> Do I need to configure anything?
> I have already done the steps mentioned in the guide to make rabbitmq
> server up and running.
>
> BR,
> Varun
>
> On Fri, Nov 7, 2014 at 2:58 PM, Adrián Norte  wrote:
>
>>  check if amqp is listening on 0.0.0.0:5672 or somewhere else. if it is
>> listening correctly try restarting amqp and then telnet to it.
>> El 07/11/14 a las 14:41, varun bhatnagar escribió:
>>
>>  Hi Brad/Erik,
>>
>>  Thanks for replying.
>>
>>  I am installing glance service on Ops-Controller & it is able to ping
>> itself.
>>  Firewall is turned off.
>>
>>  I have executed netstat command and this is what it prints:
>>
>>
>>
>> *Ops-Controller:~ # netstat -tunelp|grep 9292 tcp0  0
>> 0.0.0.0:9292 0.0.0.0:*
>> LISTEN  11565443  29864/pythonOps-Controller:~ # *
>>
>>  I also checked the glance-api.log file and this is what it says:
>>
>> 2014-11-04 16:24:45.986 29872 ERROR oslo.messaging._drivers.impl_rabbit
>> [b98ec839-53c8-4ef7-9e52-0426362c76e6 f9b4e4d416cb434b943b0c09e2d97845
>> be16af7ce8864ed7abfac64d64175fc7 - - -] AMQP server on localhost:5672 is
>> unreachable: Socket closed. Trying again in 1 seconds.
>> 2014-11-04 16:24:47.012 29872 INFO oslo.messaging._drivers.impl_rabbit
>> [b98ec839-53c8-4ef7-9e52-0426362c76e6 f9b4e4d416cb434b943b0c09e2d97845
>> be16af7ce8864ed7abfac64d64175fc7 - - -] Reconnecting to AMQP server on
>> localhost:5672
>> 2014-11-04 16:24:47.014 29872 INFO oslo.messaging._drivers.impl_rabbit
>> [b98ec839-53c8-4ef7-9e52-0426362c76e6 f9b4e4d416cb434b943b0c09e2d97845
>> be16af7ce8864ed7abfac64d64175fc7 - - -] Delaying reconnect for 1.0
>> seconds...
>> 2014-11-04 16:24:51.056 29872 ERROR oslo.messaging._drivers.impl_rabbit
>> [b98ec839-53c8-4ef7-9e52-0426362c76e6 f9b4e4d416cb434b943b0c09e2d97845
>> be16af7ce8864ed7abfac64d64175fc7 - - -] AMQP server on localhost:5672 is
>> unreachable: Socket closed. Trying again in 3 seconds.
>> 2014-11-04 16:24:54.060 29872 INFO oslo.messaging._drivers.impl_rabbit
>> [b98ec839-53c8-4ef7-9e52-0426362c76e6 f9b4e4d416cb434b943b0c09e2d97845
>> be16af7ce8864ed7abfac64d64175fc7 - - -] Reconnecting to AMQP server on
>> localhost:5672
>> 2014-11-04 16:24:54.061 29872 INFO oslo.messaging._drivers.impl_rabbit
>> [b98ec839-53c8-4ef7-9e52-0426362c76e6 f9b4e4d416cb434b943b0c09e2d97845
>> be16af7ce8864ed7abfac64d64175fc7 - - -] Delaying reconnect for 1.0
>> seconds...
>> 2014-11-04 16:24:58.106 29872 ERROR oslo.messaging._drivers.impl_rabbit
>> [b98ec839-53c8-4ef7-9e52-0426362c76e6 f9b4e4d416cb434b943b0c09e2d97845
>> be16af7ce8864ed7abfac64d64175fc7 - - -] AMQP server on localhost:5672 is
>> unreachable: Socket closed. Trying again in 5 seconds.
>> 2014-11-04 16:25:03.114 29872 INFO oslo.messaging._drivers.impl_rabbit
>> [b98ec839-53c8-4ef7-9e52-0426362c76e6 f9b4e4d416cb434b943b0c09e2d97845
>> be16af7ce8864ed7abfac64d64175fc7 - - -] Reconnecting to AMQP server on
>> localhost:5672
>> 2014-11-04 16:25:03.118 29872 INFO oslo.messaging._drivers.impl_rabbit
>> [b98ec839-53c8-4ef7-9e52-0426362c76e6 f9b4e4d416cb434b943b0c09e2d97845
>> be16af7ce8864ed7abfac64d64175fc7 - - -] Delaying reconnect for 1.0
>> seconds...
>> 2014-11-04 16:25:07.163 29872 ERROR oslo.messaging._drivers.impl_rabbit
>> [b98ec839-53c8-4ef7-9e52-0426362c76e6 f9b4e4d416cb434b943b0c09e2d97845
>> be16af7ce8864ed7abfac64d64175fc7 - - -] AMQP server on localhost:5672 is
>> unreachable: Socket closed. Trying again in 7 seconds.
>>
>>  The problem still exists. Can you please suggest something.
>>
>> BR,
>>  Varun
>>
>> On Thu, Nov 6, 2014 at 9:47 PM, Erik McCormick <
>> emccorm...@cirrusseven.com> wrote:
>>
>>> I would suggest turning on verbose=true and debug=true in the
>>> glance-api.conf and seeing where it's trying to connect to and what exactly
>>> is happening.
>>>
>>> For a wild guess, any chance you've got a firewall enabled and not
>>> opened the port to your public endpoint interface?
>>>
>>> -Erik
>>>  On Nov 6, 2014 6:23 PM, "varun bhatnagar" 
>>> wrote:
>>>
  Hi,

  I am trying to install glance service on controller and I am
 following instructions given in the installation guide (
 http://docs.openstack.org/icehouse/install-guide/install/zypper/content/glance-verify.html
 )

  The OS is SLES 11, hostname is Ops-Controller & openstack version is
 Icehouse.

  When I was do

Re: [Openstack] Glance timeout error

2014-11-07 Thread varun bhatnagar

Hi Adrián,

I don't think it is listening on 0.0.0.0:5672

This is the output which I am getting:


*Ops-Controller:~ # netstat -tunelp|grep 5672tcp0  0
:::5672 :::*LISTEN  113
69412  30402/beam  Ops-Controller:~ #*

Do I need to configure anything?
I have already done the steps mentioned in the guide to make rabbitmq
server up and running.

BR,
Varun

On Fri, Nov 7, 2014 at 2:58 PM, Adrián Norte  wrote:

>  check if amqp is listening on 0.0.0.0:5672 or somewhere else. if it is
> listening correctly try restarting amqp and then telnet to it.
> El 07/11/14 a las 14:41, varun bhatnagar escribió:
>
>  Hi Brad/Erik,
>
>  Thanks for replying.
>
>  I am installing glance service on Ops-Controller & it is able to ping
> itself.
>  Firewall is turned off.
>
>  I have executed netstat command and this is what it prints:
>
>
>
> *Ops-Controller:~ # netstat -tunelp|grep 9292 tcp0  0
> 0.0.0.0:9292 0.0.0.0:*
> LISTEN  11565443  29864/pythonOps-Controller:~ # *
>
>  I also checked the glance-api.log file and this is what it says:
>
> 2014-11-04 16:24:45.986 29872 ERROR oslo.messaging._drivers.impl_rabbit
> [b98ec839-53c8-4ef7-9e52-0426362c76e6 f9b4e4d416cb434b943b0c09e2d97845
> be16af7ce8864ed7abfac64d64175fc7 - - -] AMQP server on localhost:5672 is
> unreachable: Socket closed. Trying again in 1 seconds.
> 2014-11-04 16:24:47.012 29872 INFO oslo.messaging._drivers.impl_rabbit
> [b98ec839-53c8-4ef7-9e52-0426362c76e6 f9b4e4d416cb434b943b0c09e2d97845
> be16af7ce8864ed7abfac64d64175fc7 - - -] Reconnecting to AMQP server on
> localhost:5672
> 2014-11-04 16:24:47.014 29872 INFO oslo.messaging._drivers.impl_rabbit
> [b98ec839-53c8-4ef7-9e52-0426362c76e6 f9b4e4d416cb434b943b0c09e2d97845
> be16af7ce8864ed7abfac64d64175fc7 - - -] Delaying reconnect for 1.0
> seconds...
> 2014-11-04 16:24:51.056 29872 ERROR oslo.messaging._drivers.impl_rabbit
> [b98ec839-53c8-4ef7-9e52-0426362c76e6 f9b4e4d416cb434b943b0c09e2d97845
> be16af7ce8864ed7abfac64d64175fc7 - - -] AMQP server on localhost:5672 is
> unreachable: Socket closed. Trying again in 3 seconds.
> 2014-11-04 16:24:54.060 29872 INFO oslo.messaging._drivers.impl_rabbit
> [b98ec839-53c8-4ef7-9e52-0426362c76e6 f9b4e4d416cb434b943b0c09e2d97845
> be16af7ce8864ed7abfac64d64175fc7 - - -] Reconnecting to AMQP server on
> localhost:5672
> 2014-11-04 16:24:54.061 29872 INFO oslo.messaging._drivers.impl_rabbit
> [b98ec839-53c8-4ef7-9e52-0426362c76e6 f9b4e4d416cb434b943b0c09e2d97845
> be16af7ce8864ed7abfac64d64175fc7 - - -] Delaying reconnect for 1.0
> seconds...
> 2014-11-04 16:24:58.106 29872 ERROR oslo.messaging._drivers.impl_rabbit
> [b98ec839-53c8-4ef7-9e52-0426362c76e6 f9b4e4d416cb434b943b0c09e2d97845
> be16af7ce8864ed7abfac64d64175fc7 - - -] AMQP server on localhost:5672 is
> unreachable: Socket closed. Trying again in 5 seconds.
> 2014-11-04 16:25:03.114 29872 INFO oslo.messaging._drivers.impl_rabbit
> [b98ec839-53c8-4ef7-9e52-0426362c76e6 f9b4e4d416cb434b943b0c09e2d97845
> be16af7ce8864ed7abfac64d64175fc7 - - -] Reconnecting to AMQP server on
> localhost:5672
> 2014-11-04 16:25:03.118 29872 INFO oslo.messaging._drivers.impl_rabbit
> [b98ec839-53c8-4ef7-9e52-0426362c76e6 f9b4e4d416cb434b943b0c09e2d97845
> be16af7ce8864ed7abfac64d64175fc7 - - -] Delaying reconnect for 1.0
> seconds...
> 2014-11-04 16:25:07.163 29872 ERROR oslo.messaging._drivers.impl_rabbit
> [b98ec839-53c8-4ef7-9e52-0426362c76e6 f9b4e4d416cb434b943b0c09e2d97845
> be16af7ce8864ed7abfac64d64175fc7 - - -] AMQP server on localhost:5672 is
> unreachable: Socket closed. Trying again in 7 seconds.
>
>  The problem still exists. Can you please suggest something.
>
> BR,
>  Varun
>
> On Thu, Nov 6, 2014 at 9:47 PM, Erik McCormick  > wrote:
>
>> I would suggest turning on verbose=true and debug=true in the
>> glance-api.conf and seeing where it's trying to connect to and what exactly
>> is happening.
>>
>> For a wild guess, any chance you've got a firewall enabled and not opened
>> the port to your public endpoint interface?
>>
>> -Erik
>>  On Nov 6, 2014 6:23 PM, "varun bhatnagar"  wrote:
>>
>>>  Hi,
>>>
>>>  I am trying to install glance service on controller and I am following
>>> instructions given in the installation guide (
>>> http://docs.openstack.org/icehouse/install-guide/install/zypper/content/glance-verify.html
>>> )
>>>
>>>  The OS is SLES 11, hostname is Ops-Controller & openstack version is
>>> Icehouse.
>>>
>>>  When I was done with the installation I tried doing post installation
>>> steps & when I tried uploading the image in glance using following command:
>>>
>>>  *glance image-create --name "myImage" --disk-format qcow2 \*
>>> *--container-format bare --is-public True --progress <
>>> cirros-0.3.2-x86_64-disk.img*
>>>
>>>
>>>  I got the following error message:
>>>
>>>  *Error communicating with http://Ops-Controller:9292
>>>  timed out*
>>>
>>>  Can

Re: [Openstack] Glance timeout error

2014-11-07 Thread Adrián Norte

check if amqp is listening on 0.0.0.0:5672 or somewhere else. if it is 
listening correctly try restarting amqp and then telnet to it.

El 07/11/14 a las 14:41, varun bhatnagar escribió:

Hi Brad/Erik,

Thanks for replying.

I am installing glance service on Ops-Controller & it is able to ping 
itself.

Firewall is turned off.

I have executed netstat command and this is what it prints:
/Ops-Controller:~ # netstat -tunelp|grep 9292
tcp0  0 0.0.0.0:9292  
0.0.0.0:*   LISTEN  11565443 29864/python

Ops-Controller:~ #
/

I also checked the glance-api.log file and this is what it says:

2014-11-04 16:24:45.986 29872 ERROR 
oslo.messaging._drivers.impl_rabbit 
[b98ec839-53c8-4ef7-9e52-0426362c76e6 f9b4e4d416cb434b943b0c09e2d97845 
be16af7ce8864ed7abfac64d64175fc7 - - -] AMQP server on localhost:5672 
is unreachable: Socket closed. Trying again in 1 seconds.
2014-11-04 16:24:47.012 29872 INFO oslo.messaging._drivers.impl_rabbit 
[b98ec839-53c8-4ef7-9e52-0426362c76e6 f9b4e4d416cb434b943b0c09e2d97845 
be16af7ce8864ed7abfac64d64175fc7 - - -] Reconnecting to AMQP server on 
localhost:5672
2014-11-04 16:24:47.014 29872 INFO oslo.messaging._drivers.impl_rabbit 
[b98ec839-53c8-4ef7-9e52-0426362c76e6 f9b4e4d416cb434b943b0c09e2d97845 
be16af7ce8864ed7abfac64d64175fc7 - - -] Delaying reconnect for 1.0 
seconds...
2014-11-04 16:24:51.056 29872 ERROR 
oslo.messaging._drivers.impl_rabbit 
[b98ec839-53c8-4ef7-9e52-0426362c76e6 f9b4e4d416cb434b943b0c09e2d97845 
be16af7ce8864ed7abfac64d64175fc7 - - -] AMQP server on localhost:5672 
is unreachable: Socket closed. Trying again in 3 seconds.
2014-11-04 16:24:54.060 29872 INFO oslo.messaging._drivers.impl_rabbit 
[b98ec839-53c8-4ef7-9e52-0426362c76e6 f9b4e4d416cb434b943b0c09e2d97845 
be16af7ce8864ed7abfac64d64175fc7 - - -] Reconnecting to AMQP server on 
localhost:5672
2014-11-04 16:24:54.061 29872 INFO oslo.messaging._drivers.impl_rabbit 
[b98ec839-53c8-4ef7-9e52-0426362c76e6 f9b4e4d416cb434b943b0c09e2d97845 
be16af7ce8864ed7abfac64d64175fc7 - - -] Delaying reconnect for 1.0 
seconds...
2014-11-04 16:24:58.106 29872 ERROR 
oslo.messaging._drivers.impl_rabbit 
[b98ec839-53c8-4ef7-9e52-0426362c76e6 f9b4e4d416cb434b943b0c09e2d97845 
be16af7ce8864ed7abfac64d64175fc7 - - -] AMQP server on localhost:5672 
is unreachable: Socket closed. Trying again in 5 seconds.
2014-11-04 16:25:03.114 29872 INFO oslo.messaging._drivers.impl_rabbit 
[b98ec839-53c8-4ef7-9e52-0426362c76e6 f9b4e4d416cb434b943b0c09e2d97845 
be16af7ce8864ed7abfac64d64175fc7 - - -] Reconnecting to AMQP server on 
localhost:5672
2014-11-04 16:25:03.118 29872 INFO oslo.messaging._drivers.impl_rabbit 
[b98ec839-53c8-4ef7-9e52-0426362c76e6 f9b4e4d416cb434b943b0c09e2d97845 
be16af7ce8864ed7abfac64d64175fc7 - - -] Delaying reconnect for 1.0 
seconds...
2014-11-04 16:25:07.163 29872 ERROR 
oslo.messaging._drivers.impl_rabbit 
[b98ec839-53c8-4ef7-9e52-0426362c76e6 f9b4e4d416cb434b943b0c09e2d97845 
be16af7ce8864ed7abfac64d64175fc7 - - -] AMQP server on localhost:5672 
is unreachable: Socket closed. Trying again in 7 seconds.


The problem still exists. Can you please suggest something.

BR,
Varun

On Thu, Nov 6, 2014 at 9:47 PM, Erik McCormick 
mailto:emccorm...@cirrusseven.com>> wrote:


I would suggest turning on verbose=true and debug=true in the
glance-api.conf and seeing where it's trying to connect to and
what exactly is happening.

For a wild guess, any chance you've got a firewall enabled and not
opened the port to your public endpoint interface?

-Erik

On Nov 6, 2014 6:23 PM, "varun bhatnagar" mailto:varun292...@gmail.com>> wrote:

Hi,

I am trying to install glance service on controller and I am
following instructions given in the installation guide

(http://docs.openstack.org/icehouse/install-guide/install/zypper/content/glance-verify.html)

The OS is SLES 11, hostname is Ops-Controller & openstack
version is Icehouse.

When I was done with the installation I tried doing post
installation steps & when I tried uploading the image in
glance using following command:

/glance image-create --name "myImage" --disk-format qcow2 \/
/--container-format bare --is-public True --progress <
cirros-0.3.2-x86_64-disk.img/


I got the following error message:

/Error communicating with http://Ops-Controller:9292 timed out/
/
/
Can anyone tell me what went wrong here.

BR,
Varun

___
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

Re: [Openstack] Glance timeout error

2014-11-07 Thread varun bhatnagar

Hi Brad/Erik,

Thanks for replying.

I am installing glance service on Ops-Controller & it is able to ping
itself.
Firewall is turned off.

I have executed netstat command and this is what it prints:



*Ops-Controller:~ # netstat -tunelp|grep 9292tcp0  0
0.0.0.0:9292 0.0.0.0:*
LISTEN  11565443  29864/pythonOps-Controller:~ # *

I also checked the glance-api.log file and this is what it says:

2014-11-04 16:24:45.986 29872 ERROR oslo.messaging._drivers.impl_rabbit
[b98ec839-53c8-4ef7-9e52-0426362c76e6 f9b4e4d416cb434b943b0c09e2d97845
be16af7ce8864ed7abfac64d64175fc7 - - -] AMQP server on localhost:5672 is
unreachable: Socket closed. Trying again in 1 seconds.
2014-11-04 16:24:47.012 29872 INFO oslo.messaging._drivers.impl_rabbit
[b98ec839-53c8-4ef7-9e52-0426362c76e6 f9b4e4d416cb434b943b0c09e2d97845
be16af7ce8864ed7abfac64d64175fc7 - - -] Reconnecting to AMQP server on
localhost:5672
2014-11-04 16:24:47.014 29872 INFO oslo.messaging._drivers.impl_rabbit
[b98ec839-53c8-4ef7-9e52-0426362c76e6 f9b4e4d416cb434b943b0c09e2d97845
be16af7ce8864ed7abfac64d64175fc7 - - -] Delaying reconnect for 1.0
seconds...
2014-11-04 16:24:51.056 29872 ERROR oslo.messaging._drivers.impl_rabbit
[b98ec839-53c8-4ef7-9e52-0426362c76e6 f9b4e4d416cb434b943b0c09e2d97845
be16af7ce8864ed7abfac64d64175fc7 - - -] AMQP server on localhost:5672 is
unreachable: Socket closed. Trying again in 3 seconds.
2014-11-04 16:24:54.060 29872 INFO oslo.messaging._drivers.impl_rabbit
[b98ec839-53c8-4ef7-9e52-0426362c76e6 f9b4e4d416cb434b943b0c09e2d97845
be16af7ce8864ed7abfac64d64175fc7 - - -] Reconnecting to AMQP server on
localhost:5672
2014-11-04 16:24:54.061 29872 INFO oslo.messaging._drivers.impl_rabbit
[b98ec839-53c8-4ef7-9e52-0426362c76e6 f9b4e4d416cb434b943b0c09e2d97845
be16af7ce8864ed7abfac64d64175fc7 - - -] Delaying reconnect for 1.0
seconds...
2014-11-04 16:24:58.106 29872 ERROR oslo.messaging._drivers.impl_rabbit
[b98ec839-53c8-4ef7-9e52-0426362c76e6 f9b4e4d416cb434b943b0c09e2d97845
be16af7ce8864ed7abfac64d64175fc7 - - -] AMQP server on localhost:5672 is
unreachable: Socket closed. Trying again in 5 seconds.
2014-11-04 16:25:03.114 29872 INFO oslo.messaging._drivers.impl_rabbit
[b98ec839-53c8-4ef7-9e52-0426362c76e6 f9b4e4d416cb434b943b0c09e2d97845
be16af7ce8864ed7abfac64d64175fc7 - - -] Reconnecting to AMQP server on
localhost:5672
2014-11-04 16:25:03.118 29872 INFO oslo.messaging._drivers.impl_rabbit
[b98ec839-53c8-4ef7-9e52-0426362c76e6 f9b4e4d416cb434b943b0c09e2d97845
be16af7ce8864ed7abfac64d64175fc7 - - -] Delaying reconnect for 1.0
seconds...
2014-11-04 16:25:07.163 29872 ERROR oslo.messaging._drivers.impl_rabbit
[b98ec839-53c8-4ef7-9e52-0426362c76e6 f9b4e4d416cb434b943b0c09e2d97845
be16af7ce8864ed7abfac64d64175fc7 - - -] AMQP server on localhost:5672 is
unreachable: Socket closed. Trying again in 7 seconds.

The problem still exists. Can you please suggest something.

BR,
Varun

On Thu, Nov 6, 2014 at 9:47 PM, Erik McCormick 
wrote:

> I would suggest turning on verbose=true and debug=true in the
> glance-api.conf and seeing where it's trying to connect to and what exactly
> is happening.
>
> For a wild guess, any chance you've got a firewall enabled and not opened
> the port to your public endpoint interface?
>
> -Erik
> On Nov 6, 2014 6:23 PM, "varun bhatnagar"  wrote:
>
>> Hi,
>>
>> I am trying to install glance service on controller and I am following
>> instructions given in the installation guide (
>> http://docs.openstack.org/icehouse/install-guide/install/zypper/content/glance-verify.html
>> )
>>
>> The OS is SLES 11, hostname is Ops-Controller & openstack version is
>> Icehouse.
>>
>> When I was done with the installation I tried doing post installation
>> steps & when I tried uploading the image in glance using following command:
>>
>> *glance image-create --name "myImage" --disk-format qcow2 \*
>> *--container-format bare --is-public True --progress <
>> cirros-0.3.2-x86_64-disk.img*
>>
>>
>> I got the following error message:
>>
>> *Error communicating with http://Ops-Controller:9292
>>  timed out*
>>
>> Can anyone tell me what went wrong here.
>>
>> BR,
>> Varun
>>
>> ___
>> 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] (no subject)

2014-11-07 Thread Sadia Bashir

Hi All,

I fixed the "stack_user_domain ID not set in heat.conf falling back to
using default" error by following links given below:

http://hardysteven.blogspot.fr/2014/04/heat-auth-model-updates-part-2-stack.html
http://docs.openstack.org/developer/keystone/cli_examples.html

but soon after this I started getting oslo rootwrap error in nova.log,
openvswitch-agent.log and in celometer-api.log files while glance, keystone
and heat commands and services are working correctly.

I followed the link:
https://ask.openstack.org/en/question/29758/why-does-nova-api-fail-icehouse-usrbinnova-rootwrap-not-found/
to resolve the problem but even after reinstalling and reconfiguring nova
and neutron services, verified existence of nova and neutron rootwrap files
in /usr/bin/, I am still getting these errors:

nova-api.log:

2014-11-07 13:40:30.609 30639 TRACE nova Traceback (most recent call last):
2014-11-07 13:40:30.609 30639 TRACE nova   File "/usr/bin/nova-api", line
10, in 
2014-11-07 13:40:30.609 30639 TRACE nova sys.exit(main())
2014-11-07 13:40:30.609 30639 TRACE nova   File
"/usr/lib/python2.7/dist-packages/nova/cmd/api.py", line 53, in main
2014-11-07 13:40:30.609 30639 TRACE nova server =
service.WSGIService(api, use_ssl=should_use_ssl)
2014-11-07 13:40:30.609 30639 TRACE nova   File
"/usr/lib/python2.7/dist-packages/nova/service.py", line 330, in __init__
2014-11-07 13:40:30.609 30639 TRACE nova self.manager =
self._get_manager()
2014-11-07 13:40:30.609 30639 TRACE nova   File
"/usr/lib/python2.7/dist-packages/nova/service.py", line 374, in
_get_manager
2014-11-07 13:40:30.609 30639 TRACE nova return manager_class()
2014-11-07 13:40:30.609 30639 TRACE nova   File
"/usr/lib/python2.7/dist-packages/nova/api/manager.py", line 30, in __init__
2014-11-07 13:40:30.609 30639 TRACE nova
self.network_driver.metadata_accept()
2014-11-07 13:40:30.609 30639 TRACE nova   File
"/usr/lib/python2.7/dist-packages/nova/network/linux_net.py", line 666, in
metadata_accept
2014-11-07 13:40:30.609 30639 TRACE nova iptables_manager.apply()
2014-11-07 13:40:30.609 30639 TRACE nova   File
"/usr/lib/python2.7/dist-packages/nova/network/linux_net.py", line 434, in
apply
2014-11-07 13:40:30.609 30639 TRACE nova self._apply()
2014-11-07 13:40:30.609 30639 TRACE nova   File
"/usr/lib/python2.7/dist-packages/nova/openstack/common/lockutils.py", line
249, in inner
2014-11-07 13:40:30.609 30639 TRACE nova return f(*args, **kwargs)
2014-11-07 13:40:30.609 30639 TRACE nova   File
"/usr/lib/python2.7/dist-packages/nova/network/linux_net.py", line 454, in
_apply
2014-11-07 13:40:30.609 30639 TRACE nova attempts=5)
2014-11-07 13:40:30.609 30639 TRACE nova   File
"/usr/lib/python2.7/dist-packages/nova/network/linux_net.py", line 1211, in
_execute
2014-11-07 13:40:30.609 30639 TRACE nova return utils.execute(*cmd,
**kwargs)
2014-11-07 13:40:30.609 30639 TRACE nova   File
"/usr/lib/python2.7/dist-packages/nova/utils.py", line 165, in execute
2014-11-07 13:40:30.609 30639 TRACE nova return
processutils.execute(*cmd, **kwargs)
2014-11-07 13:40:30.609 30639 TRACE nova   File
"/usr/lib/python2.7/dist-packages/nova/openstack/common/processutils.py",
line 195, in execute
2014-11-07 13:40:30.609 30639 TRACE nova cmd=sanitized_cmd)
2014-11-07 13:40:30.609 30639 TRACE nova ProcessExecutionError: Unexpected
error while running command.
2014-11-07 13:40:30.609 30639 TRACE nova Command: sudo nova-rootwrap
/etc/nova/rootwrap.conf iptables-save -c
2014-11-07 13:40:30.609 30639 TRACE nova Exit code: 1
2014-11-07 13:40:30.609 30639 TRACE nova Stdout: u''
2014-11-07 13:40:30.609 30639 TRACE nova Stderr: u'Traceback (most recent
call last):\n  File "/usr/bin/nova-rootwrap", line 6, in \n  $
2014-11-07 13:40:30.609 30639 TRACE nova
2014-11-07 13:40:30.701 30652 INFO nova.openstack.common.service [-] Parent
process has died unexpectedly, exiting
2014-11-07 13:40:30.702 30647 INFO nova.openstack.common.service [-] Parent
process has died unexpectedly, exiting
2014-11-07 13:40:30.702 30645 INFO nova.openstack.common.service [-] Parent
process has died unexpectedly, exiting
2014-11-07 13:40:30.702 30652 INFO nova.wsgi [-] Stopping WSGI server.
2014-11-07 13:40:30.702 30647 INFO nova.wsgi [-] Stopping WSGI server.
2014-11-07 13:40:30.702 30645 INFO nova.wsgi [-] Stopping WSGI server.
2014-11-07 13:40:30.702 30652 INFO nova.wsgi [-] WSGI server has stopped.
2014-11-07 13:40:30.703 30647 INFO nova.wsgi [-] WSGI server has stopped.
2014-11-07 13:40:30.703 30645 INFO nova.wsgi [-] WSGI server has stopped.
2014-11-07 13:40:30.705 30651 INFO nova.openstack.common.service [-] Parent
process has died unexpectedly, exiting
2014-11-07 13:40:30.706 30650 INFO nova.openstack.common.service [-] Parent
process has died unexpectedly, exiting
2014-11-07 13:40:30.701 30649 INFO nova.openstack.common.service [-] Parent
process has died unexpectedly, exiting
2014-11-07 13:40:30.706 30651 INFO nova.wsgi [-] Stopping WSGI server.

==

[Openstack] [Ironic] Questions about ironic deployment

Re: [Openstack] Glance timeout error

Re: [Openstack] Glance timeout error

Re: [Openstack] Glance timeout error

Re: [Openstack] Glance timeout error

Re: [Openstack] (no subject)

6 matches

Site Navigation

Mail list logo

Footer information