Use the same approach as in mr10.3+ - check that not vulnerable version
is installed.
Change-Id: Ie76816bb11479eb40377c8c6b9dc8f989945e213
(cherry picked from commit 5fb8ebfebf)
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)
Remove unnecessary awk core mute on stretch->buster upgrade.
It was a crash produced by newly incomming SSH connection during libc upgrade.
Jenkins was checking upgrade status via SSH on GCloud, as port 4242 was closed.
Now Jenkins has direct access to port 4242 on GCLoud VMs and SSH is not in use.
This reverts commit 4288d67c1f.
Change-Id: Ifdcf62828f6ca63e2d0c6bd103fd0980ad05a111
The random awk crash happens which we cannot catch and trace.
It happens randomly and it produces no harm AFAIK.
We cannot report anything upstream here as we have to trace from core.
Also it is an old/stretch version of gawk which is crashed on stretch->buster
upgrade when gawk dependency libraries libc6, libgmp10, libsigsegv2
were fully/partially upgraded to buster already.
We can only mute it here as for now.
The mute is necessary in mr7.5* branched only
as mr7.5->mr8.0 is buster->buster upgrade already.
Change-Id: I24d15cb799f50cd5dbc0c5c99783d41ee32a780f
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
(cherry picked from commit 2668b137ff)
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
(cherry picked from commit 1f7ebd90d0)
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
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
Sipwise Jenkins Builder
Mykola Malkov
Manuel Montecelo
Alexander Lutay
Guillem Jover
Sergii Kipot
Richard Fuchs
Michael Prokop