Error - 'Failed to connect to Rabbit MQ server' should be exposed to the user

[mrajora-1]

Description

Error - Failed to connect to Rabbit MQ server should be exposed to the user

Expected Behavior

Error - Failed to connect to Rabbit MQ server should be exposed to the user

Actual Behavior

Error - Failed to connect to Rabbit MQ server is seen in the logs but not exposed to the user

Steps to Reproduce

When the Rabbitmq connection is not there, we will not see notifications to OSC, but the error should be exposed to the user.

Additional Information

Relevant excerpt from the logs:

2017-10-26 20:27:21,582 [ERROR| isc-task-pool-32| o.o.c.b.r.c.o.v.n.RabbitMQClient]: Failed to connect to Rabbit MQ server '10.3.241.111' IO Error.null
2017-10-26 20:27:21,583 [INFO | isc-task-pool-32| o.o.c.b.r.c.o.v.n.RabbitMQClient]: Closing RabbitMQ Connection - 10.3.241.111
2017-10-26 20:27:21,586 [INFO | isc-task-pool-32| o.o.c.b.u.VirtualizationConnectorUtil]: Exception encountered when connecting to RabbitMQ, ignoring since we are already connected

Environment

• OSC Version/Build: Build1.0.0-SNAPSHOT-142-g0fb43fe
• Cloud Provider Info:
• Plugin Info:
• Other:

Status

• Reproduced
• In Progress
• Validated => Verified in Version/Build:

securityBroker-Failed-to-Connect-to-RabbitMq.log

[arvindn05]

DE5761