Nailgun expects exchanges to be setup by puppet

Bug #1445359 reported by Thomas Goirand
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Confirmed
Medium
Fuel Sustaining
Mitaka
Won't Fix
Medium
Fuel Python (Deprecated)
Newton
Confirmed
Medium
Fuel Sustaining

Bug Description

Trying to setup Nailgun in a Debian environment (porting it from CentOS to Debian), when clicking on deploy, nailgun crashes, with connection closed from rabbitmq. It seems that it is trying to connect to exchanges which are normally setup by puppet. This should change, and instead, Nailgun should be able to do this at runtime, by itself, when it needs the named exchanges. Otherwise, it is going to be very difficult to package Nailgun in Debian.

Changed in fuel:
assignee: nobody → Fuel Python Team (fuel-python)
status: New → Confirmed
Changed in fuel:
importance: Undecided → Medium
milestone: none → 7.0
tags: added: qa-agree-7.0
Revision history for this message
Dmitry Borodaenko (angdraug) wrote :
Changed in fuel:
assignee: Fuel Python Team (fuel-python) → Vladimir Sharshov (vsharshov)
Revision history for this message
Vladimir Sharshov (vsharshov) wrote :

Can you provide logs?

Script which provided https://github.com/stackforge/fuel-library/blob/master/deployment/puppet/nailgun/manifests/rabbitmq.pp setup mcollective services. Without it we could not manage nodes.

I do not see any place where we can get problem with exchanges from Nailgun or Astute side excluding credentials.

Revision history for this message
Vladimir Sharshov (vsharshov) wrote :

Guys, we solve problem with Thomas Goirand. We found and fix problem with Astute, Mcollective, RabbitMQ and other components.

Changed in fuel:
status: Confirmed → Invalid
Revision history for this message
Sebastian Kalinowski (prmtl) wrote :

It would be nice to write what was the solution.

Revision history for this message
Dmitry Borodaenko (angdraug) wrote :

+1 to Seb: please explain what was the solution, correct the bug description if necessary, and then close it as Fix Committed, not as Invalid.

Changed in fuel:
status: Invalid → In Progress
Revision history for this message
Thomas Goirand (thomas-goirand) wrote :

Vladimir,

The issue is *not* fixed. Please reopen the bug. We have found a workaround which I can use to move forward to test more stuff in my Debian port, but Nailgun should still have prepared the exchanges by itself.

Changed in fuel:
status: In Progress → Confirmed
Changed in fuel:
assignee: Vladimir Sharshov (vsharshov) → Fuel Python Team (fuel-python)
Revision history for this message
Vladimir Sharshov (vsharshov) wrote :

This bug has workaround. Also it is required for non standard fuel distribution. Moving to 8.0

Changed in fuel:
status: Confirmed → Won't Fix
Dmitry Pyzhov (dpyzhov)
tags: added: feature
Dmitry Pyzhov (dpyzhov)
Changed in fuel:
milestone: 7.0 → 8.0
status: Won't Fix → Confirmed
no longer affects: fuel/8.0.x
Dmitry Pyzhov (dpyzhov)
tags: added: area-python
tags: added: tech-debt
Changed in fuel:
milestone: 8.0 → 9.0
Revision history for this message
Thomas Goirand (thomas-goirand) wrote :

Hi. It's been nearly a year that I have opened this ticket. However, nothing is being done about it. Now is the time: we've completed Fuel 8.0, and we aren't in feature freeze for 9.0 yet. Please, let's have someone done now, before the window closes.

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.