DescriptionFix lp 1298703
One failure was a simple list ordering bug.
The other two more complicated. NewAddress always returns an address with the scope of NetworkUnknown. In that case the results from calling unit.Public/PrivateAddress were essentially random.
It feels like there are some other footguns in this area.
Should NewAddress/NewAddresses create NetworkUnknown Address values ? What happens if they leak into the state and back to the client? How many other places are these things leaking into.
I'd like to explore removing NewAddress/NewAddresses in a followup, if they are used only for testing (axw), then they are doing us a disservice.
Thanks to Ian and Andrew for their assistance
https://code.launchpad.net/~dave-cheney/juju-core/104-fix-lp-1298703/+merge/213195
(do not edit description out of merge proposal)
Patch Set 1 #
MessagesTotal messages: 2
|