Debian/buster + bullseye don't ship acccording version numbers via
base-files yet (but just something like "buster/sid"), so translate to
according version numbers for usage with DEBIAN_RELEASE.
Change-Id: Ica5e35976d62b9b3ddf312fdcd62937402e8d170
root@sp1:~# ls -la /var/lib/systemd/coredump/core.perl-fcgi.*
ls: cannot access '/var/lib/systemd/coredump/core.perl-fcgi.*': No such file or directory
root@sp1:~# ls -la /var/lib/systemd/coredump/core.perl-fcgi*
-rw-r----- 1 root root 6873201 Jun 14 06:09 /var/lib/systemd/coredump/core.perl-fcgi-pm.0.6995c001fc28427b99d6684117b10f6a.1241.1528949380000000.lz4
Change-Id: I3115674e10b1ab518977df2121b373383b6db6f7
Core are no longer stored into /var/cores and processed by systemd-coredump,
we need to tune the script to skip well known cores in the new location:
> root@spce:~# ls /var/lib/systemd/coredump/
> core.perl-fcgi.33.bc9842d268f54ce1942f00e595ce2f6e.10926.1528426351000000.lz4
Change-Id: Ib0d751bd26186d2866aa9dc33bb893319fc21f59
The current goss version doesn't work well if service has both
systemd unit and sysv script, see https://github.com/aelsabbahy/goss/pull/343
Change-Id: I8debfef430bd887a9a3fb5383fc7f20c3409cf22
goss was reverted in a previous commit to goss 0.3.1 while
it looks like every goss version sice 0.2.6 are affected:
https://github.com/aelsabbahy/goss/issues/267
So, reverting revert here and updating to the latest 0.3.3 version
(to test and report upstream the latest goss version).
Change-Id: Ife6aec7883fd6d83e3645f728805feaab12c4a06
Unify all templates into a single tree, no more CE vs PRO distinction.
Handle inactive nodes, and CARRIER systems.
Change-Id: Id2800e0cc746233cb69a1b9a09769f26aa9c2a5d
New goss version looks unstable and from time to time gives false positive result
This reverts commit 2a04d50113.
Change-Id: I36a5e2ae75b3b5e31c0d45add8af7985ce1f6952
Recent goss versions provide template support, rely on this
to support different Debian versions at the same time.
NOTE: https://deb.sipwise.com/files/goss-0.3.1-linux-amd64
is available now
Change-Id: I9b51f9799f20626c376e1966f8a587abee3dba58
We have kamilio coredumps in CE stretch, though system-tests
access all /var/cores/core.* and only renames
/var/cores/core.perl-fcgi.sig11* then. This fails of course:
| ================== NOTE: CORE DUMP DETECTED ==================
| = Removing known cores to prevent failing for the known issues:
| = 1) MT#21791: Renaming ngcp-panel cores /var/cores/core.perl-fcgi.sig11*
| ls: cannot access '/var/cores/core.perl-fcgi.sig11*': No such file or directory
| Connection to 192.168.22.197 closed.
| + RC=2
So if we want to rename the /var/cores/core.perl-fcgi.sig11*
only then also test only for them.
Change-Id: I562982943d5b0b0b053cf62c54fba6fa45950331
After upgrade new goss file is not downloaded (because old one exist)
while tests have new syntax for new NGCP version:
> 16:12:19 + ssh -t -t 192.168.23.138 'SKIP_STRICT_HOSTNAME_TEST=false SKIP_DNS_CHECK_TEST=false GOSS_NOCOLOR=true /usr/share/ngcp-tests/testrunner ce'
> ...
> 16:12:23 2016-03-18 16:12:23: Generating /etc/ngcp-tests/pro/goss.json: OK
> 16:12:23 Error: json: cannot unmarshal number into Go value of type string
P.S. yes, we need package here with proper dependencies in system-tests
Change-Id: If22655f306582f2056810d75eeb55e19e96fdbdf
Binary built via:
cd $GOPATH/src/github.com/aelsabbahy/goss/
CGO_ENABLED=0 GOOS=linux GOARCH=amd64 go build -ldflags "-X main.version=mika~git804995a8_with_tap_and_junit" -o release/goss-linux-amd64 github.com/aelsabbahy/goss/cmd/goss
using goss.git based on 804995a8 and including my PRs
https://github.com/aelsabbahy/goss/pull/48 (junit support) +
https://github.com/aelsabbahy/goss/pull/47 (TAP support)
Also use /usr/sbin/goss if it's present and only if it's not
yet there download the according version. This makes
development and testing of custom goss versions easier.
While at it fix string<->integer issues like:
| DEPRICATION WARNING: false: command.exit-status should be an integer not a string
Change-Id: I3dadc0b604db565b11adf1839b11e29437856fd1
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
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)
Michael Prokop
Alexander Lutay
Guillem Jover
Sergii Kipot
Victor Seva