rabbitmq fails after fuel setup: error: [Errno 111] Connection refused

Bug #1612140 reported by Ilya Popov
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
High
Fuel Sustaining
Mitaka
Invalid
High
Fuel Sustaining

Bug Description

MOS 9.0

When you change name of fuel hostname in fuelmenu ("DNS & Hostname" menu item, "hostname" field) from default ("fuel" by default ) to any other e.g. "myfuel" during fuel installation process,
when after installation finished rabbitmq fails to start and fuel masternode will fail to check network configuration or delete environment or network group and will show the following error:

Errno 111] Connection refused will appear. In Astute log we will see the following messages:

2016-08-11 06:45:30 WARNING [1985] TCP connection to AMQP failed: Could not establish TCP connection to any of the configured hosts. Retry 5 sec later...
2016-08-11 06:45:30 INFO [1985] Worker initialization
2016-08-11 06:45:30 WARNING [1971] TCP connection to AMQP failed: Could not establish TCP connection to any of the configured hosts. Retry 5 sec later...
2016-08-11 06:45:30 WARNING [1976] TCP connection to AMQP failed: Could not establish TCP connection to any of the configured hosts. Retry 5 sec later...
2016-08-11 06:45:30 INFO [1971] Worker initialization

Cause of all these errors - rabbitmq isn't started

Changed in fuel:
status: New → Confirmed
importance: Undecided → High
assignee: nobody → Fuel Sustaining (fuel-sustaining-team)
milestone: none → 10.0
Revision history for this message
Oleksiy Molchanov (omolchanov) wrote :

We have already patch for this - https://review.openstack.org/#/c/346694/.

Changed in fuel:
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.