Comment 16 for bug 1721368

Offhand, I would guess the issue is that the machines were added with "juju add-machine ssh:hostname", and a workaround would be to do "juju add-machine ssh:IP".
I haven't done anything to confirm that is the case, so I could be wildly off base. But I'm guessing that the bug is in how Juju is recording what that machine is.
I'm guessing this is elevated priority because of Openstack on s390, but I'm also guessing there might be a quick workaround for people.

I'll try to task someone with at least working through how this could be happening (AFAIK, nobody has explicitly tried to reproduce this bug and get a feel for the scope of it yet, to know how hard it will be to fix.) I also don't know that it has been escalated internally for us to prioritize it, but we should be able to take a little bit of time and see how hard it would be to fix.