Comment 9 for bug 1910973

We talked through this a bit in the last session with them. One question is:

a) the actual failure seems to be calling 'unit-get private-address' (public?) in a loop
That speaks to something failing talking to the Uniter (if it is cached in the context, then the unit agent shouldn't be calling back to the controller).

Which should be investigated and understood vs just the model around whether this should be available or not.

b) making it strictly lazy probably makes this worse rather than better, but you're right that it could eliminate one of the round trips to the controller on every hook invocation.

c) A better fix would be to have a single API call for all of the context, rather than filling the context out slowly with a bunch of requests.