Started by an SCM change1886e9f0dcc88e9d760b80f9bb01b98410921f8a2c26e9f0dcc88e9d760b80f9bb01b98410921f8a2c2refs/remotes/origin/master6e9f0dcc88e9d760b80f9bb01b98410921f8a2c26e9f0dcc88e9d760b80f9bb01b98410921f8a2c2refs/remotes/origin/master6e9f0dcc88e9d760b80f9bb01b98410921f8a2c26e9f0dcc88e9d760b80f9bb01b98410921f8a2c2refs/remotes/origin/mastergit://git.osmocom.org/docker-playgroundfalse#188515255update-osmo-ci-on-slaves-dp #188188falsefalse188402690SUCCESS1613754965929https://jenkins.osmocom.org/jenkins/view/gerrit/job/update-osmo-ci-on-slaves-dp/188/build2-deb9build-ansible- ttcn3-gbproxy-test/osmo-gbproxy.cfgttcn3-gbproxy-test-fr/osmo-gbproxy.cfg6e9f0dcc88e9d760b80f9bb01b98410921f8a2c21613507069000https://jenkins.osmocom.org/jenkins/user/lynxislynxislynxis@fe80.eugbproxy: update sns configuration to use ip-sns-bind
With libosmocore commit the SNS configuration requires a ip-sns-bind vty configuration
to define the binds which should be use.
Related: SYS#5354
Depends-on: I9ab8092bf286e7d90e92f5702a5404425e959c84 (libosmocore)
Change-Id: I11541540468584fc17a18fa294da5c9813c28d64
2021-02-16 21:24:29 +01006e9f0dcc88e9d760b80f9bb01b98410921f8a2c2gbproxy: update sns configuration to use ip-sns-bindeditttcn3-gbproxy-test-fr/osmo-gbproxy.cfgeditttcn3-gbproxy-test/osmo-gbproxy.cfg
githttps://jenkins.osmocom.org/jenkins/user/lynxislynxis