Comment 8 for bug 1747048

@David Britton,

The panic is coming from the comparison of vsphere config values.

2.3.2 implementation has introduced the ability to specify complex values but the comparison code was not capable of always doing the right thing. [Old implementation had == whereas we needed more sophisticated reflect.DeepEquals].

The good news is that it is now fixed in 2.3.3 and will be forward-ported to develop (2.4+) shortly.

Commit that fixes this issue on 2.3 tip is https://github.com/juju/juju/commit/35e2ceaef8ccde530370d20e8f294451e6267486