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
As of systemd v238 the kernel.core_pattern for
sytemd-coredump includes the hostname as well,
see systemd.git commit:
| commit f45b8015513d38ee5f7cc361db9c5b88c9aae704
| Author: Jakub Filak <jakub@thefilaks.net>
| Date: Thu Feb 15 12:12:46 2018 +0100
|
| coredump: accept hostname on command line (#8033)
Change-Id: Iac7a1723cac72848518f6eafe72c2cc2687d36a1
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
On newly installed CE/PRO-mr6.5/trunk the port is listened by InfluxDb.
Restored it into system tests and sent ping to Guillem for rechecking
(he is not available right now, while the test is failing and
prevent building new vagrant images).
Change-Id: I432bc9540525cf11ed343064287840a62f0f44d3
Recently subscriber self-care has been switched to new CSC by
default and the content is generated now by js framework.
https://gerrit.mgm.sipwise.com/#/c/22031/
Testing title (html title is empty now) with simple curl
doesn't work anymore. So fixing here title check to allow
goss check pass successfully.
Change-Id: I7e1c4de6d3a4027c1757590085ad76adc87251b9
This simplifies the pseudo-function calls into proper ones.
Reaname the confusing is_li_enabled into the more descriptive name
is_li_dist.
Change-Id: I42b079945c100aafa37eab9f44307fac940f42a8
Using stringy eval to handle conditional use is one of the few cases
where it seems to be always legitimate to allow it. This is at least
currently required for ngcp-panel.
Change-Id: Id641b87609c916e6e60dfa76d95e996fa18eef7f
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
We cannot keep services in background (like detached 'screen')
as systemd will kill it on client disconnect. Going to use libpam-systemd.
This reverts commit d0036830a4.
Change-Id: I52a623bd90cfa0ea8541ba9d8b9b0d10929f3ee8
Now that ssh is socket activated, and systemd is taking care of the port
listening, we need to update the address to the IPv6 ANY address.
Change-Id: I452082966e57b0981567a4150222422f7e421584
Guillem Jover
Sipwise Jenkins Builder
Mykola Malkov
Manuel Montecelo
Alexander Lutay
Michael Prokop
Sergii Kipot