Let us introduce a system-wide symlink from /var/backup to /ngcp-data/backup, to
fix recurrent problems like the missing /var/backup/cdr or
/var/backup/ngcp-upgrade backups taking too much space.
This should have happened when changing the partition schema to use /ngcp-data/
and have a root partition with minimal amount of space, because there were
several paths migrated to /ngcp-data like /var/backup, and we failed to migrate
all those paths in sync with the change to the partitioning and also failed to
have a back-up solution like this symlink.
Some (hopefully most, or all!) of the problems have been sorted out by now, but
they've been biting us years after the change, like this TT#72908, so maybe it
can still save some pain in the future, and there's little cost to it.
Change-Id: Ief4ba33bf57bb5f02cc54b000b64540667ebba48
(cherry picked from commit 25d4f5e9c1,
fixing whitespace)
We had to downgrade prosody in mr7.5 and have to check it is
still old/pinned version in use until we are ready for the upgrade.
See workfront ticket 66583 for more details here.
Change-Id: I7cad16c1d08beb57d52eca5f83fbcc1d21dba7c9
On early upgrades mr5.5->mr6.5 GTID was not reconfigured on
the very first upgraded node... It is a test to ensure we
have covered all the upgrade scenarios.
Change-Id: I40433f536402c52b582911fc18bd4021ed050bbf
Currently Jenkins abort upgrade testing if unknown cores detected
to allow investigation. Right now rtpegine often fails but Richard
is going to the vacation and we need to continue LTS testing here.
Temporary disable rtpegine cores reporting until the issue is solved.
Change-Id: I77d2b55a89078804d60446e23dc7eef1e1921798
(cherry picked from commit 9401bc6013)
We should not assume monit is always running and enabled, that depends
on whether it is configured as the current process_handler. This will
make it easier to remove in the future.
Change-Id: I8851728228dd3e46323d9745ed04da49b18ff928
The missing test were detected while working on another ticket.
Good to have them here as they are very important for NGCP.
Change-Id: I73afe7332dc1f60b412b9415fef1ce402829dd2b
While syncing with the Debian packaging, the binary names have changed.
Update the expected names.
Change-Id: I8c836f09898126f3749adfe15ff4b3bee59469c8
While using ngcp-licensed is not incorrect, it is an alias generated by
systemd only when the main service file is enabled. To make the check
more robust we should check for the actual canonical service name which
is ngcp-license-client.service.
Change-Id: I512563d247104474482c485ec1780bdaf32034a2
Our current policy is: all services must have .service files
(better Type=notify) to be fully integrated into ngcpcfg preset.
We need to be sure newly added services will not use systemd 'generator.late'
for automatic .service files generation.
Change-Id: Id199020be6c30f5f954496fe02c6b2fe125365fb
Otherwise we have an error here:
> root@spce:~# /usr/share/ngcp-tests/testrunner
> ...
> Error: yaml: line 3: found unknown escape character
Change-Id: I377a5796754a9310148c8361cb397e54722c8cfa
While we have lua5.1 on Debian/stretch, it's lua5.2 on Debian/buster
and lua5.3 is available as well in buster, so instead of hardcoding
the lua version 5.1, let's support whatever lua5.X version is used.
Fixes:
| not ok 34 - Command: pgrep -c -f '[l]ua5.1 /usr/bin/prosody': stdout: patterns not found: [1]
While at it, drop the unnecessary '[l]' approach, which
is a nice trick to avoid matching the grep process itself
within a `ps aux | grep ...`, but doesn't apply to
pgrep, thanks to Manuel Montecelo for spotting this leftover.
Change-Id: I3c62ddefbaf5a22f623b779426621ebaafec26b2
In CE this dir was created and used only to keep sipwise.cnf file.
Now sipwise.cnf is generated from constants.yml so no need to place it
to shared-files so there is no such dir on CE.
Add explicit check of this dir to PRO checks.
Change-Id: I35503275c8fb22b731a37747c649e9691a6674c2
Change permission of generated configs - all of them do not have 'write'
permission.
Add new sipwise_extra.cnf file to check.
Remove old non-existing
/etc/ngcp-config/shared-files/mysql/sipwise.cnf.
Change-Id: Ia08438e43783067a339de5b4cf764ce79a5c53c2
This policy is giving bad advice. The <> operator is security unsafe, as
it interprets filenames as if passed to the two-form open function,
which means it can do code injection via crafted filenames.
While reading from <STDIN> directly might not always be correct, its
consequences are far milder than the damage inflicted by the diamond
operator.
Change-Id: I0fdf097be3b5e2a3a483f2e5d80f4fdb1f17911b
After changes to restore /etc/mysql/my.cnf to keep using "alternatives" and the
configuration moving to mariadb.cnf, as the packages coming from Debian, modify
these tests to check the new expected scenario.
Change-Id: If43c842e633151e895754f6a345472cdb9c9888c
This file is needed for when mariadb-common invokes update-alternatives with
this file as argument, otherwise it aborts the upgrade and the system is left in
a broken state.
Change-Id: Icd42ab9d0def6bc3ccbdea307f5bc6416ec96fad
The .postbuild config has been removed from /etc/mysql/grants.yml
as a result the file is installed with 0400 perms.
Fix the test accordingly.
P.S. Makefile contains 0600, but ngcpcfg removes write for everyone on apply.
Change-Id: I16830fc14c262261dc5a4c20c47bda7f296d95bc
We have not been using /var/cores for a while, since starting to use
systemd-coredump around releases mr6.2 or mr6.3, so this file is now
unnecessary.
However, there was a script creating the file and this test ensuring that it
existed and no core dump files were present.
It's not particularly tied to TT#46902, but it got discovered while working on
it and the task also touches the area of "core dump" files.
Change-Id: If75fcfa28a75359033ab4efddec503da401e61bb
The kernel.core_pattern we get now is the same being used in Debian 10
(Buster), remove the conditional.
Change-Id: I47815ef465e59d7ab058289e6d3a9ee6220d8799
kernel.sysr=1 was set for Vagrant VMs only and missing
on the real hardware AND for old releases, also it is
going to be removed from installer as well, since it
was committed to debug Proxmox issues only (review pending).
No need to test it here. Also it will fix system-tests
for upgrade 2.8->...->mr6.5 which is currently failing:
> KernelParam: kernel.sysrq: value: doesn't match, expect: ["1"] found: ["438"]
(it happens as kernel.sysrq was not set for old releases).
Change-Id: Id3b449ab9a8b48df4404233c418263029e289359
Sipwise Jenkins Builder
Manuel Montecelo
Alexander Lutay
Guillem Jover
Sergii Kipot
Richard Fuchs
Michael Prokop
Mykola Malkov