The output of 'asterisk -rx "odbc show"' is not a 'current' state while the
cached one, also it reports unreliable data depending on which service is
starting first asterisk or db. See the ticket for the samples here.
Change-Id: I8bbdaba077c92369d6c61711a3d6382474cd2dcb
(cherry picked from commit 5005c9b3d1)
(cherry picked from commit fa975d1ddf)
The glusterfs has ability to listen the next port in range if
the 'base-port' is occupied by some another process.
Which is happens very often on nightly tests in Debian stretch.
I have requested goss improvement to check the port from the range:
> https://github.com/aelsabbahy/goss/issues/311
So far we have to disable the check for the moment as it is unstable:
>> goss validate
> Port: tcp:24009: listening: doesn't match, expect: [true] found: [false]
While glusterfs is OK (but listening port 24010):
> root@sp1:~# netstat -anp | grep glusterfs
> tcp 0 0 0.0.0.0:24010 0.0.0.0:* LISTEN 5412/glusterfsd
>
> root@sp1:~# gluster volume status ngcp
> Status of volume: ngcp
> Gluster process TCP Port RDMA Port Online Pid
> ------------------------------------------------------------------------------
> Brick sp1:/var/lib/glusterfs/export 24010 0 Y 5412
> Brick sp2:/var/lib/glusterfs/export 24009 0 Y 5406
Change-Id: Idaf72caf4388be9b2bf5b0e98f1d4539d9438433
(cherry picked from commit f0f6422211)
P.S. I am not sure why mysql-common is currently installed while it is the current mr5.5+ state.
Change-Id: I24e749bc11be85bf91ff830213385f75d5dcd45d
(cherry picked from commit fce09b1fa4)
This is a plan for mr5.5* as we have no resources to migrate them now.
Sure later in trunk we should confider to migrate on mariadb configs and split my.cnf probably.
Change-Id: Ib97d2734c26d73996bc0b063f087ed6cfdf89f2e
(cherry picked from commit bdea9a534a)
The old test doesn't work for the freshly installed system
when DB has no subscribes. Old command reported nothing
which fails the test.
Change-Id: I1501f407ab8561fd83b1d21f6c3ac8e306ff1231
(cherry picked from commit 2bf023f934)
Check node with role PROXY only, as another nodes has no asterisk running.
Change-Id: I484cc10afda4ec47227177ddd37866fa64a61fa3
(cherry picked from commit 2b2e1def10)
Stretch glusterfs 3.8.5 has a confirmed bug with port bumping on every restart:
c3dee6d353967a77ed4d
We are trying to upgrade glusterfs to version 3.11 or fix port bumping upstream for 3.8.5
so far we have to disable the port check here for now.
Change-Id: I512465fc10b8250d6c4ad861c384fc01ca6ae05b
goss was reverted in a previous commit to goss 0.3.1 while
it looks like every goss version sice 0.2.6 are affected:
https://github.com/aelsabbahy/goss/issues/267
So, reverting revert here and updating to the latest 0.3.3 version
(to test and report upstream the latest goss version).
Change-Id: Ife6aec7883fd6d83e3645f728805feaab12c4a06
Unify all templates into a single tree, no more CE vs PRO distinction.
Handle inactive nodes, and CARRIER systems.
Change-Id: Id2800e0cc746233cb69a1b9a09769f26aa9c2a5d
We always want these to overwrite the previously installed files, even
if locally modified, otherwise bad things happen.
We are not concerned about possibly losing data, because on NGCP /etc is
always managed with git, so the whole history is always available.
Change-Id: I7f1af4eab0da5a3bb4bae6e83472e3da8df23f5c
New goss version looks unstable and from time to time gives false positive result
This reverts commit 2a04d50113.
Change-Id: I36a5e2ae75b3b5e31c0d45add8af7985ce1f6952
Sipwise Jenkins Builder
Alexander Lutay
Guillem Jover
Sergii Kipot