Comment 4 for bug 1425435

I can't reproduce this with 1.21.3 or 1.22-beta4 in a freshly bootstrapped environment. I also asked frankban to do a separate test with juju-quickstart which uses the same 4.3.0 version of python-jujuclient. I quadruple-checked both fixes mentioned in comment #2 have actually landed and are inside the release package for 1.21.3 in the stable ppa. Can we have some debug logs from the juju machine 0 ? Inside the machine log (at DEBUG level) it will become apparent if the megawatcher's UnitInfo change it sends has the Ports and PortRanges set as per the fixes.