Otherwise we have an old goss binary file after upgrade
mr4.2->mr4.3 which doesn't understand new goss.json format:
> Error: json: cannot unmarshal array into Go value of type string
P.S. We need a goss Debian package here :-(
Change-Id: Ib3038ea0f42843756d02f52b2a13d718234b0fed
The Jenkins test 'netinstall-test-ngcp-installer' restores plain Debian VM
and install NGCP using ngcp-installer only.
In this case the test should skip some strict host/names checks.
Change-Id: I9b84784ebed0a54ff51aa2baef274f5466879352
At the momment results are not stable due to goss error.
The issue reported to upsteam: https://github.com/aelsabbahy/goss/issues/27
> Failures:
> Port: tcp:1443: ip: doesn't match, expect: [10.15.20.169] found: [127.0.0.1]
> Port: tcp:443: ip: doesn't match, expect: [10.15.20.169] found: [127.0.0.1]
>
> Total Duration: 0.436s
> Count: 259, Failed: 2
It should be re-enabled as soon as goss is fixed.
Change-Id: Iae2db3a29dd77b99733a92ec017ad00012ab0a87
Checking only for *.tt2 files isn't enough, we also have
*.services + *.postbuild files and want to also catch
any files that don't match our file suffix.
Change-Id: Ia7477ac45b4fc9e1ab3cc0188c35424bffeceedb
jenkins TAP plugin produce an exception in case if test was
triggered with absolute path, aka:
> ./testrunner /usr/share/ngcp-tests/ce/
Error:
> Processing '/var/lib/jenkins/../reports/03_no-cores.sh.tap'
> Parsing TAP test result [/var/../reports/03_no-cores.sh.tap].
> org.tap4j.parser.ParserException: Error parsing TAP Stream: Missing TAP Plan.
> at org.tap4j.parser.Tap13Parser.parse(Tap13Parser.java:221)
> at org.tap4j.parser.Tap13Parser.parseFile(Tap13Parser.java:187)
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.
Alexander Lutay
Kirill Solomko
Jenkins User
Victor Seva
Michael Prokop