This was producing empty values at kamailio.cfg template on CE
with a cluster_set of central type
Thanks to Anibal Cañada for the bugreport
Change-Id: Ib11295611859ef2828dc1d2e6900bf201c20ad7a
(cherry picked from commit 4d297ff3fc)
This was producing empty values at ngcp-ossbss template mysql_values.cfg file
on a cluster_set of central type
Change-Id: I68160a9c5bef078d3154c6e8da6db1e9bcbb07aa
(cherry picked from commit 2437330d4e)
In carrier central.dbhost points to db01a so any connection will use network even db01a|db01b. This connections will be resolved by mysql as sp1|sp2. So we need to add those perms too
Change-Id: Ie09aa15209a9aa5170849a17e383df1d6fc07c4c
(cherry picked from commit 8afc87d5e2)
Otherwise we faced the error during upgrading the second node (sp2):
> Script started on Fri 29 Aug 2014 10:34:23 AM CEST
> Not prompting user for approval because environment variable FORCE_UPGRADE is present.
> /usr/share/ngcp-upgrade-trunk/upgrade-stable-to-trunk - start on Fri Aug 29 10:34:23 CEST 2014
> Looks like you are running Debian 7 already.
> Checking for (possibly) outstanding ngcpcfg changes
> /usr/share/ngcp-ngcpcfg/functions//main: line 78: TEMPLATE_POOL: unbound variable
The node sp1 has been upgraded succesfully but new config ngcpcfg.cfg has been
delievered to sp2 and old ngcpcfg framework failed to start with new config.
Those workaround can be reverted as soon as next LTS release is released.
Change-Id: Idb1f4ca05e88e7a30054ace0c0b47dc0eadf1b7a
On a multi directory config, the services depends on git. Check
first if the git repository exists and warn about it
Change-Id: I52e335c85ecf4a330da44b3088725623f3c04531
We have a regression here for CE during the upgrade mr3.4->trunk:
> Removing proj-data ...
> ...
> Synchronizing data from /etc/ngcp-config/constants.yml
> DBI connect('database=mysql;host=127.0.0.1;port=3306','sipwise',...) failed:
> Can't connect to MySQL server on '127.0.0.1' (111)
> at /usr/sbin/ngcp-sync-constants line 131
> Can't connect to MySQL database mysql: Can't connect to MySQL server on
> '127.0.0.1' (111) at /usr/sbin/ngcp-sync-constants line 131.
It happens because MySQL listens Unix sockets only (due to "skip_networking" in my.cnf)
It doesn't affect newly installed CE trunk,
because it has defaults in /etc/ngcp-config/config.yml:
> database:
> central:
> dbhost: localhost
> pair:
> dbhost: localhost
While upgraded system not yet received those options
(ngcp-upgrade-cfg-schema will be called later).
So, we need to change defaults here to localhost.
MySQL always uses unix sockets for 'localhost'.
Change-Id: I0f07c43ea68ed47b653242cd87ed74e7351dcc1c
From MYSQL documentation:
"If you specify the MASTER_HOST or MASTER_PORT option, the slave
assumes that the master server is different from before
(even if the option value is the same as its current value.)
In this case, the old values for the master binary log file
name and position are considered no longer applicable"
Change-Id: I9be8e0fdab7ce598343df270c2ade0a5095e1f48
`git diff-index --name-only HEAD` was used because it was the
only reasonable way to check for modified files back in Git 1.5.
Sadly this command can't detect files that didn't exist inside
the Git repository at all yet (so if a file was generated for the
very first time the according services script wasn't executed
necessarily).
Instead nowadays we can rely on `git status --porcelain`, which
wasn't available in Git 1.5 back then yet. Even in Debian/squeeze
there's Git version 1.7.2.5-3 available, so it's save to depend
on it. Updated Git package dependency accordingly, also switch
from transitional git-core package to the actual git one.
Tested-by: Alexander Lutay <alutay@sipwise.com>
Jenkins User
Victor Seva
Alexander Lutay
Andreas Granig
Michael Prokop