web front end is inaccessible if rabbit is down
Bug #1014436 reported by
Julian Edwards
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Invalid
|
Low
|
Unassigned | ||
Bug Description
To recreate:
1. ensure rabbitmq-server is stopped
2. make run and wait until output quiesces
3. try to access the maas web - a service down error is returned
What should happen:
- The front end should load but without longpolling functionality
| Changed in maas: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
Revision history for this message
| Raphaël Badin (rvb) wrote | #1 |
Revision history for this message
| Blake Rouse (blake-rouse) wrote | #2 |
| Changed in maas: | |
| status: | Triaged → Invalid |
To post a comment you must log in.
Could you please paste the error you're seeing?
I'm asking because the front end should already cope with rabbit being down by disabling longpoll (and I'm seeing this behaviour on my local copy right now).
But we still need to make celery start a rabbitmq fixture when running a dev instance (I've removed the need to run rabbitmq when running tests a few weeks back). Right now, it relies on the system rabbitmq.