Check for getty process without path information and arguments,
because on systemd powered systems we have:
| /sbin/agetty tty1 38400
while sysvinit powered systemd run:
| /sbin/getty 38400 tty1
| /sbin/getty 38400 tty2
| /sbin/getty 38400 tty3
| /sbin/getty 38400 tty4
| /sbin/getty 38400 tty5
| /sbin/getty 38400 tty6
As soon as one "getty" process is available that should be fine enough
for us, no matter whether it's /sbin/agetty or /sbin/getty.
(Of course it would be even better if we'd have regex support
in the tests, but that's not available in upstream code...)
We are not going to check exect tty numer avialability,
otherwise test will failed in case is someone loged in to
this console. Lets check at least some terminal avialability.
We have no DNS records for freshly installed VMs/Vagrant/Amazon images.
So, we have to skip the test there. It is enabled by default for
other test cases as it is useful itself.
We can conside to configure DNS for freshly installed VMs one day.
In failing tests it's hard to parse very long cmdlines, so reduce
it as much as possible and still sensible. Also fix quoting of
the heartbeat command line for YAML format.
Jenkins User
Alexander Lutay
Michael Prokop