Steps to reproduce:
1. Deploy FUEL/MOS 8.0 environment in any configuration
2. Try to get stack list
Observed result:
command won't be executed
Following error in heat-engine log:
2015-11-27 08:32:54.423 8539 INFO oslo.messaging._drivers.impl_rabbit [-] Connecting to AMQP server on 192.168.0.3:5673
2015-11-27 08:32:54.440 8539 INFO oslo.messaging._drivers.impl_rabbit [-] Connected to AMQP server on 192.168.0.3:5673
2015-11-27 08:32:55.187 31950 ERROR oslo.messaging._drivers.impl_rabbit [-] AMQP server on 127.0.0.1:5672 is unreachable: [Errno 111] ECONNREFUSED. Trying again in 2 seconds.
2015-11-27 08:32:55.705 31951 ERROR oslo.messaging._drivers.impl_rabbit [-] AMQP server on 127.0.0.1:5672 is unreachable: [Errno 111] ECONNREFUSED. Trying again in 2 seconds.
Seems that at the beginning heat-engine successfully connected to AMQP server, but lately it started to send requests to invalid url.
I found very strange set of heat-engine processes on the controller:
root@node-1:~# ps -aux | grep heat-engine
heat 3281 1.1 0.9 278860 69544 ? S Nov23 68:42 /usr/bin/python /usr/bin/heat-engine
heat 3411 0.0 1.5 405028 107568 ? S Nov23 4:13 /usr/bin/python /usr/bin/heat-engine
heat 3412 0.0 1.4 401484 103772 ? S Nov23 4:02 /usr/bin/python /usr/bin/heat-engine
root 3568 0.0 0.0 8864 648 pts/23 S+ 08:31 0:00 grep --color=auto heat-engine
heat 31950 0.3 1.1 294940 83264 ? S Nov23 19:51 /usr/bin/python /usr/bin/heat-engine --config-file=/etc/heat/heat.conf --log-file=/var/log/heat/heat-engine.log
heat 31951 0.3 1.1 294964 83256 ? S Nov23 19:50 /usr/bin/python /usr/bin/heat-engine --config-file=/etc/heat/heat.conf --log-file=/var/log/heat/heat-engine.log
There are a few heat-engine processes which run without config file, so they use default amqp server ip and port. This processes were run be pcs.
It is not clear why there are another two heat-engine processes.
Steps to reproduce:
1. Deploy FUEL/MOS 8.0 environment in any configuration
2. Try to get stack list
Observed result:
command won't be executed
Following error in heat-engine log:
2015-11-27 08:32:54.423 8539 INFO oslo.messaging. _drivers. impl_rabbit [-] Connecting to AMQP server on 192.168.0.3:5673 _drivers. impl_rabbit [-] Connected to AMQP server on 192.168.0.3:5673 _drivers. impl_rabbit [-] AMQP server on 127.0.0.1:5672 is unreachable: [Errno 111] ECONNREFUSED. Trying again in 2 seconds. _drivers. impl_rabbit [-] AMQP server on 127.0.0.1:5672 is unreachable: [Errno 111] ECONNREFUSED. Trying again in 2 seconds.
2015-11-27 08:32:54.440 8539 INFO oslo.messaging.
2015-11-27 08:32:55.187 31950 ERROR oslo.messaging.
2015-11-27 08:32:55.705 31951 ERROR oslo.messaging.
Seems that at the beginning heat-engine successfully connected to AMQP server, but lately it started to send requests to invalid url.
I found very strange set of heat-engine processes on the controller: heat-engine heat-engine heat-engine heat-engine --config- file=/etc/ heat/heat. conf --log-file= /var/log/ heat/heat- engine. log heat-engine --config- file=/etc/ heat/heat. conf --log-file= /var/log/ heat/heat- engine. log
root@node-1:~# ps -aux | grep heat-engine
heat 3281 1.1 0.9 278860 69544 ? S Nov23 68:42 /usr/bin/python /usr/bin/
heat 3411 0.0 1.5 405028 107568 ? S Nov23 4:13 /usr/bin/python /usr/bin/
heat 3412 0.0 1.4 401484 103772 ? S Nov23 4:02 /usr/bin/python /usr/bin/
root 3568 0.0 0.0 8864 648 pts/23 S+ 08:31 0:00 grep --color=auto heat-engine
heat 31950 0.3 1.1 294940 83264 ? S Nov23 19:51 /usr/bin/python /usr/bin/
heat 31951 0.3 1.1 294964 83256 ? S Nov23 19:50 /usr/bin/python /usr/bin/
There are a few heat-engine processes which run without config file, so they use default amqp server ip and port. This processes were run be pcs.
It is not clear why there are another two heat-engine processes.