Apply the same logic on the process check as was done for the service
check.
Change-Id: I36a515431fb23467d11e0c519cc30a12b1279c13
(cherry picked from commit 14a3162f56)
(cherry picked from commit e1a74ddeab)
On a CE the general.process_handler is always set to 'none'. So we need
to take this into account and mark it as enabled.
Change-Id: Id1347ac027412861a1319a95d1537aaeb778bf6a
(cherry picked from commit d03cb1fd71)
(cherry picked from commit 45669de3d2)
The rate-o-mat service can run in active-active or in active-standby
modes. If the service is enabled and on the proxy nodes, the former
mode means the service will be enabled and running on both peers, the
latter will mean it's in the traditional HA mode and thus only running
on the active node.
Change-Id: I020c8a00706135ed5d432bf8b1b8874cf1b2f532
(cherry picked from commit 6e46a9c67b)
(cherry picked from commit 6a0c11c3ed)
It's an often error after upgrade that this file is missing.
It happens because right after reboot there is no such file and it's not
created by logrotate because we use missingok, notifempty option for
it.
So make it optional.
Change-Id: I4ee18e8ba5e93d19e4b80fd3fcf8197d144f1ea3
(cherry picked from commit 790ca5ce32)
The configuration files specific to the ngcpcfg tool should not be
mixed with the site specific configuration, as that's rather confusing,
more so when the actual ngcpcfg configuration contains references to the
location of the ngcp-config dir itself, which makes it self-referential.
Change-Id: I25bee17e69e9c302d40b1bb55f73a1e88e505a8d
(cherry picked from commit bcd6e12d2a)
Currently we have diff in all tables of 'mysql' schema:
========================
Schema1: transactional=1
Schema2: page_checksum=1 transactional=1
========================
This is harmless diff investigated in TT#108653
So to skip all the specific entities instead of comparing every element
just use regex matching.
Change-Id: I3b9a38c3fbf055724139cbf4b476117b90edbefe
(cherry picked from commit 4c8443a182)
We check that when the pathname exists it is a symlink. We will perform
further consistency checks from «ngcpcfg check».
Change-Id: I3850d9cf23fd77b926d08ae47a6969cac1790cf0
The rtpengine project used to be called rtpengine-ng, and before that
mediaproxy-ng, which was an implementation using the same protocol as
the rtpproxy project. It's about time we rename the config.yml section
so that this is less confusing.
Change-Id: Ia36ab199caf242605d9558f2eb27806215a0a0d2
These are shared files across all PRO/Carrier nodes, but at the time
they were introduced we did not have the concept of a shared-files
subdirectory. All other such shared files have been moved over time to
that subdirectory, but this was still remaining behind. Let's move it
now for consistency, and so that its purpose is more clear.
Change-Id: I45c89245d36706dba5ed1fb47a8bf9124c390dae
Goss doesn't trim the trailing space at the end of process name.
It is a workaround for the issue reported upstream as:
> https://github.com/aelsabbahy/goss/issues/762
It can be reverted as soon as issue is fixed in goss.
Change-Id: Ie3d7e2b3470aed9aa3c5ee3743d950237919dbde
These components are obsolete and not available anymore since mr10.5.
Force them to never be enabled nor running.
Change-Id: I25efecd1714d85b9591ac599d7ae33cdab87dec5
From now on the 'sems' config.yml section is deprecated,
and we have to only use 'b2b'. This commit concerns it.
Change-Id: I8e1a4c480011404a005ea52d66a7f770f97123bf
Starting with mr10.5, the heartbeat-2 support is now obsolete and not
available anymore. Switch all heartbeat-2 service and process checks
to expect them to be disabled. Remove the UDP check, as we have now
removed the RPC port start limitation, so we might end up checking for
an unrelated colliding port.
Change-Id: Ibacaf2d55e45b3f86a5218b92204d180e934e1e2
goss checks the name of the *binary*, not the name of the *process*.
This can be checked from a user perspective via:
| $ systemctl cat ngcp-rest-api | grep ExecStart
| ExecStart=/usr/bin/node --title ngcp-rest-api /usr/share/ngcp-rest-api/server
| $ sudo systemctl status ngcp-rest-api | grep PID
| Main PID: 327024 (node)
| $ ps -p 327024 -o comm
| COMMAND
| node
Underneath, goss looks at the cmdline and stat files inside procfs:
| $ cat /proc/327024/cmdline
| ngcp-rest-api
| $ cat /proc/327024/stat
| 327024 (node) S 1 327024 327024 0 -1 4194560 38500 0 47 0 121 13 0 0 20 0 7 0 552217 704745472 32511 18446744073709551615 1 1 0 0 0 0 0 4096 82434 0 0 0 17 0 0 0 1 0 0 0 0 0 0 0 0 0 0
Since those two don't match with each other, our ngcp-rest-api service,
running under the node binary, isn't identified as such a running process.
NOTE: we're already checking for goss' service named ngcp-rest-api from
within templates/510_init-daemons-ngcp.yaml.tt2, but this doesn't check
if the process is alive. We need to explicitly check for the expected
process name, which we're doing hereby.
Change-Id: Iafa63b8e9fbfeee9edb2c0d48e8ed3514da4804a
The prevalent convention in the project is to use «-» instead of «_» to
split words in options. Switch the options to that, and keep backwards
compatibility option alias that emits a deprecation warning while people
transition to the new names. The alias will be removed on the next LTS.
Clarify --help output.
Change-Id: Ic25ba7a152ce11c3be5106dc58d481add7ca02a8
ngcpcfg-api.service is supposed to be disabled by default, and running
only during ongoing deployments.
Fixes:
| not ok 218 - Service: ngcpcfg-api.service: enabled: doesn't match, expect: [true] found: [false]
| not ok 219 - Service: ngcpcfg-api.service: running: doesn't match, expect: [true] found: [false]
Change-Id: Ide7e17f90b83f205b79db689d2e226df4bc990da
Otherwise the resulting file isn't valid json syntax:
| root@sp1:~# goss --gossfile /etc/ngcp-system-tests/goss.yaml --vars /tmp/ngcp-system-tests.1O3urIHya7.yaml validate --format tap
| Error: could not read json data in /etc/ngcp-system-tests/135_filesys-logfiles.yaml: could not unmarshal "file:\n\n /var/log/messages:\n
| [...]
Change-Id: I3a99570e5069553411a574f02fcd95355a9e3e7f
* comx fileshare service is deprecated and should no longer be
checked for its running state
* add ngcp-rest-api to the running state checks
Change-Id: Id461c280fe4e9d0d0b5700ee8e12fbdcc6467506
We add optional support for ntpd, as some customers have demanded it
back. While preserving timesyncd as the default.
Change-Id: Ib954ee73e21b572beb9655c9ce471702e03f7142
The code was switched to use ngcp_hostname so no need to check the
actual hostname but check ngcp-hostname output.
Change-Id: Ie7a74dfcff9d94c4839c49dac6a4d5dd64e32fcb
Restoring back byllseye image for trunk. 'buster' one
was set temporary just in order to build missed docker image
for 'buster'
This reverts commit 94666c9714.
Change-Id: Ibb4f97d962987ddebdeee6fc38aadcb547af4b75
We still have some internal repos building 'buster' packages and
they will use 'buster' dockers for testing based on $distribution
option. So let's build also buster image for tap-tests.
Change-Id: Ibb3c021fa4ad7856564f02687df028833c5aa983
The package was updated to support pycodestyle in bullseye so we need
to rebuild the docker image now.
Change-Id: Id3b22ff1824225072e77dc1e4237acfd540e3c00
We use quite old pep8 v1.6.2 which in particular misses this
change https://github.com/PyCQA/pycodestyle/pull/502
Let's update Dockerfile to use pycodestyle(former pep8) from
bullseye.
Change-Id: Id29acd80be212cffa127550d9a4deb764a5b5b30
backup.log is created directly by backup-tools without explicitly
setting the group. It's not guaranteed to exist but must be in group
root if it does.
Change-Id: I80092d8f4cf10f98128668b10afa088037ce431d
* Switch to use the ngcp-pushd.socket instead of .service, as the later
gets triggered by the formed when that is activated.
* Mark the .socket unit as enabled only when not using a process_handler,
as otherwise it will be managed by the HA system and be disabled.
Change-Id: I4a07410fe1c9dc17edde3e10921959a170556e1e
This was support to handle the transition period where we were
supporting both buster and bullseye. Which is no longer necessary
starting with mr9.5.
Change-Id: I125f03b5baea172065e1e947f66619cee7eeabe6
The preset for the mariadb@2.service instance was not taken into account
due to the format used, even though monit was taking care of starting
the service. Add a check for the service to be enabled and running to
avoid this happening in the future.
Change-Id: Iafbc684624c58c6b2c4e453b7e1ac4ba52ab2097
Sipwise Jenkins Builder
Guillem Jover
Mykola Malkov
Alexander Lutay
Donat Zenichev
Michael Prokop
Kirill Solomko
Sergii Kipot
Richard Fuchs