Comment 15 for bug 216847

Since so many things changed since this - admittedly embarrassing old - bug was reported I thought I retest it before the next LTS comes out.

I looked at the Xenial content and found stuff like:
Not only is it specified "After network.target", but on top there is /etc/network/if-up.d/openssh-server which is intended to restart openssh if later an iface comes up, there it would be able to rebind that IP.

I tested on containers first and it worked right away, setting ListenAddress and restarting.
But well in containers devices might be "up" at a different timing, but even in a KVM Guest, setting ListenAddress again it works just fine.
Mar 24 14:54:43 testxenial-ssh sshd[1293]: Server listening on 192.168.122.131 port 22.

I wondered and wanted to make sure that the test is valid, so I spawned
trusty (LTS), vivid (last reported issue) and wily

But - for me - it was working on all of them - even with several retries it was not even racy.

Therefore I wanted to ask for a retest - at least with Xenial if possible.
Also any detail about the test environment that was used would be great - especially by the last confirmation in vivid.
Does it have to be a special network card that might initialize slowly or anything like it?