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
(cherry picked from commit edf56d0cd1)
We forget to change home for posix user when we renamed
'sems' to 'ngcp-sems' somewhere in ~mr3.2
It is too late to change it now. Also there is no big deal to have
home pointed to non-existed folder as nobody login under user sems.
Change-Id: I59c722150f7156b07f8a625dae9a72fe8da27e42
(cherry picked from commit 424bd26c5b)
On Debian/stretch we get /nonexistent as the home
for user mysql, while on Debian/jessie it's /var/lib/mysql.
Backported to mr4.5 as systems installed on 2.8 and
upgraded to mr3.8 and then to mr4.5 has '/nonexistent'
due to Percona DB is being used on 2.8
Change-Id: I87d6db988c5d973d5ef814a89e658080e0bd7e50
(cherry picked from commit 9c2db0284a)
Freshly installed systems use IDs 10000/10001 nowadays,
while systems that are upgraded from old(er) releases use IDs 1000/1001.
It happens because in the past users sipwise/cdrexport were
created by installer directly, while currently ngcp-support-access
cares about sipwise/cdrexport user using new id based 10000+
Change-Id: I1a08aa722d1648ebef451c111dea4ff8750a54eb
(cherry picked from commit 284abaa49b)
ngcp-panel/rest-api is very slow to start on
servers builder[1,3,4].mgm
Change-Id: I639b79588a7aedd0879f839d5c5c79f40deccf41
(cherry picked from commit f446d5cb8a)
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
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