Check why the NOTIFICATION_HOST setting may be empty if Jenkins has a relation set before RabbitMQ
Bug #1385218 reported by
Caio Begotti
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Capomastro |
Fix Released
|
Medium
|
Caio Begotti | ||
Bug Description
The order of the relations setup of the charm makes Capomastro not to talk with RabbitMQ and then to Jenkins correctly for some reason. We should check this and retry it if the order was "wrong" somehow.
Related branches
lp:~ce-infrastructure/capomastro/capomastro-jenkins-notifications-1385218
- Sheila Miguez (community): Approve
- Daniel Manrique (community): Approve
-
Diff: 9 lines (+1/-1)1 file modifiedtemplates/capomastro_local_settings.tmpl (+1/-1)
Revision history for this message
| Caio Begotti (caio1982) wrote | #1 |
| Changed in capomastro: | |
| status: | New → Fix Released |
| importance: | Undecided → Medium |
| assignee: | nobody → Caio Begotti (caio1982) |
To post a comment you must log in.
Apparently we just need to wrap the address of the Capomastro instance with http:// and end it with another slash. I had this problem again today, after such a long time without facing it. I tested the wrapping hack and it did the job, even though I don't really understand why it happens at all. Perhaps it's one of those timings issues Juju has because the instance address may not be available in the very exact second the template is called in the charm code...?