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
We forget to change home for posix user when we renamed
'sems' to 'ngcp-sems' somewhere in ~mr3.2
It is too late to change it now. Also there is no big deal to have
home pointed to non-existed folder as nobody login under user sems.
Change-Id: I59c722150f7156b07f8a625dae9a72fe8da27e42
Recent goss versions provide template support, rely on this
to support different Debian versions at the same time.
NOTE: https://deb.sipwise.com/files/goss-0.3.1-linux-amd64
is available now
Change-Id: I9b51f9799f20626c376e1966f8a587abee3dba58
It will fix the error on Debian stretch:
> User: sshd: home: doesn't match, expect: ["/var/run/sshd"] found: ["/run/sshd"] 0 ms
Change-Id: I1688699663ccb72681772fdcd80df8b4991caba6
- Use canonical homepage URL.
- Bump debhelper compatibility to 9.
- Bump Standards-Version to 3.9.8.
- Wrap and sort debian/control fields.
- Remove unused ${perl:Depends} substvar.
- Use canonical debian/copright Format field URL.
- Update copyright years.
- Merge Files stanzas for the same license into a single stanza.
- Move license location on filesystem into a Comment field.
- Remove unnecessary .dirs file.
Change-Id: I2b3b7b6815acd2f0d56949836f9d9d95c63b722c
We have kamilio coredumps in CE stretch, though system-tests
access all /var/cores/core.* and only renames
/var/cores/core.perl-fcgi.sig11* then. This fails of course:
| ================== NOTE: CORE DUMP DETECTED ==================
| = Removing known cores to prevent failing for the known issues:
| = 1) MT#21791: Renaming ngcp-panel cores /var/cores/core.perl-fcgi.sig11*
| ls: cannot access '/var/cores/core.perl-fcgi.sig11*': No such file or directory
| Connection to 192.168.22.197 closed.
| + RC=2
So if we want to rename the /var/cores/core.perl-fcgi.sig11*
only then also test only for them.
Change-Id: I562982943d5b0b0b053cf62c54fba6fa45950331
Freshly installed systems use IDs 10000/10001 nowadays,
while systems that are upgraded from old(er) releases use IDs 1000/1001.
It happens because in the past users sipwise/cdrexport were
created by installer directly, while currently ngcp-support-access
cares about sipwise/cdrexport user using new id based 10000+
Change-Id: I1a08aa722d1648ebef451c111dea4ff8750a54eb
On Debian/stretch we get /nonexistent as the home
for user mysql, while on Debian/jessie it's /var/lib/mysql.
Change-Id: I87d6db988c5d973d5ef814a89e658080e0bd7e50
coreutils on jessie behaves like:
| sipwise@spce:~$ ls -la /var/cores/core.*
| ls: cannot access /var/cores/core.*: No such file or directory
... while on stretch we get:
| root@spce:~# ls -la /var/cores/core.*
| ls: cannot access '/var/cores/core.*': No such file or directory
Change-Id: Idb26193f28d0003a42a9fddf59dc5d06d630b6cf
For some unknown for me reason they are different on CE and PRO.
From the installer code they should be 0750,
while something changes them to 0755 for PRO only.
I spend two hours trying to find the reason here - no luck.
Updating the test to fix tests with the actual state and
continue with upgrade fixes here.
Change-Id: I9fce3d3ede0289360824b8bc8e64b8426aa8451b
Alexander Lutay
Sipwise Jenkins Builder
Guillem Jover
Sergii Kipot
Michael Prokop
Kirill Solomko