OpenStack Compute (nova)

wrong error message of nova-api after failing to login to rabbitmq-server

Bug #918238 reported by Christian Berendt on 2012-01-18

This bug affects 3 people

Affects		Status	Importance	Assigned to	Milestone
	OpenStack Compute (nova)	Won't Fix	Low	Simon Chang

Bug Description

the rabbitmq-server is not unreachable. the error message is wrong, it should be "login failed" or something like that.

log if nova-api:

2012-01-18 14:55:29,625 ERROR nova.rpc [-] AMQP server on 192.168.53.132:5672 is unreachable: Socket closed. Trying again in 1 seconds.

log of rabbitmq-server:

=INFO REPORT==== 18-Jan-2012::14:55:30 ===
starting TCP connection <0.762.0> from 192.168.53.130:42483

=ERROR REPORT==== 18-Jan-2012::14:55:33 ===
exception on TCP connection <0.762.0> from 192.168.53.130:42483
{channel0_error,starting,
                {amqp_error,access_refused,
                            "AMQPLAIN login refused: user 'guest' - invalid credentials",
                            'connection.start_ok'}}

=INFO REPORT==== 18-Jan-2012::14:55:33 ===
closing TCP connection <0.762.0> from 192.168.53.130:42483

Tags:

Thierry Carrez (ttx) on 2012-01-23

Changed in nova:
importance:	Undecided → Low
status:	New → Confirmed

Sailaja Pashumarthy (sailaja-pashumarthy) on 2012-03-16

Changed in nova:
assignee:	nobody → Sailaja Pashumarthy (sailaja-pashumarthy)
status:	Confirmed → In Progress

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2012-04-11: Fix proposed to nova (master)

Fix proposed to branch: master
Review: https://review.openstack.org/6446

Revision history for this message

Thierry Carrez (ttx) wrote on 2012-12-13:

Review was abandoned, could you revive it ?

Revision history for this message

Christian Berendt (berendt) wrote on 2013-08-07:

The proposed patch doesn't fix the issue. It only changes a comment. I'll have a look the next days if this bug is still valid.

Changed in nova:
assignee:	Sailaja Pashumarthy (sailaja-pashumarthy) → nobody
status:	In Progress → New

Matt Riedemann (mriedem) on 2013-08-10

tags:

added: api

Christopher Yeoh (cyeoh-0) on 2013-09-09

Changed in nova:
status:	New → Confirmed

Simon Chang (changsimon) on 2013-11-23

Changed in nova:
assignee:	nobody → Simon Chang (changsimon)

Revision history for this message

Simon Chang (changsimon) wrote on 2013-12-24:

I don’t think we can fix this bug at the moment. The issue roots from RabbitMQ.

RabbitMQ (and therefore Kombu) is not returning the actual error code to the Nova api code at all. By design, RabbitMQ simply disconnects the client connection on authentication error ... As a result IOError is all we can report.

Here’s the traceback:
http://paste.openstack.org/show/56773/

Some resources that document this RabbitMQ behavior:
http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/2010-May/007095.html
http://clojurerabbitmq.info/articles/error_handling.html (see the Authentication Failures section)

RabbitMQ 3.2 (released Oct 2013) introduces “Authentication Failure Notifications”, which allows authentication exceptions to be caught by the client.

http://www.rabbitmq.com/auth-notification.html

I’m not sure if Kombu is capable of processing the new RabbitMQ 3.2 “Authentication Failure Notifications” yet. Pending further investigation.

Revision history for this message

Christopher Yeoh (cyeoh-0) wrote on 2014-06-24:

Sorry doesn't appear to be fixable atm