Merge lp:~michael.nelson/charms/trusty/logstash/fix-missing-host-client-changed into lp:~canonical-is-sa/charms/trusty/logstash/logstash2
Status: | Merged |
---|---|
Merged at revision: | 57 |
Proposed branch: | lp:~michael.nelson/charms/trusty/logstash/fix-missing-host-client-changed |
Merge into: | lp:~canonical-is-sa/charms/trusty/logstash/logstash2 |
Diff against target: |
13 lines (+2/-1) 1 file modified
hooks/client-relation-changed (+2/-1) |
To merge this branch: | bzr merge lp:~michael.nelson/charms/trusty/logstash/fix-missing-host-client-changed |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Michael Foley (community) | Approve | ||
Review via email: mp+276941@code.launchpad.net |
Commit message
Add guard for first client-
Description of the change
We hit this issue on ci [1], but turns out it was reproducible locally (I'd only tested upgrading).
After a bit of debugging (by writing relations to a tmp file, because the issue disappears before you can do resolved --retry), I found the relation data for this can look like:
[{u'private-
The first client has all the data, the second does not yet.
. This change just adds a guard for that scenario.
Tested locally.
[1] https:/
+1