Started by an SCM change00553243241.00571557154512eb695bc4491f640a6a47411666986709fbc6abf2eb695bc4491f640a6a47411666986709fbc6abfrefs/remotes/origin/master2eb695bc4491f640a6a47411666986709fbc6abf2eb695bc4491f640a6a47411666986709fbc6abfrefs/remotes/origin/master2eb695bc4491f640a6a47411666986709fbc6abf2eb695bc4491f640a6a47411666986709fbc6abfrefs/remotes/origin/masterhttps://gerrit.osmocom.org/docker-playgroundfalse#451324255update-osmo-ci-on-slaves-dp #451451falsefalse4511195381SUCCESS1688565066316https://jenkins.osmocom.org/jenkins/job/update-osmo-ci-on-slaves-dp/451/build2-deb11build-ansiblettcn3-smlc-test/osmo-stp.cfgttcn3-stp-test/osmo-stp.cfgttcn3-hnbgw-test/osmo-stp.cfgttcn3-bsc-test-vamos/osmo-stp.cfgosmo-stp-master/osmo-stp.cfgnplab-m3ua-test/osmo-stp.cfgnplab-sua-test/osmo-stp.cfgttcn3-bsc-test/osmo-stp.cfgttcn3-sgsn-test/osmo-stp.cfgttcn3-msc-test/osmo-stp.cfgosmo-stp-latest/osmo-stp.cfg2eb695bc4491f640a6a47411666986709fbc6abf1688564935000https://jenkins.osmocom.org/jenkins/user/pespinPau Espin Pedrolpespin@sysmocom.de*/osmo-stp.cfg: Explicitly define role & sctp-role It was recently decided it's a good practice to always specify the role and sctp-role for all ASPs configured in the VTY, since it's an important configuration providing feedback on the network setup expectancies. Change-Id: Ia495bc3c5dd4421e5730c74b2f5dc4e4cdc1a673 2023-07-05 13:48:55 +00002eb695bc4491f640a6a47411666986709fbc6abf*/osmo-stp.cfg: Explicitly define role & sctp-roleeditttcn3-bsc-test/osmo-stp.cfgeditttcn3-smlc-test/osmo-stp.cfgeditnplab-m3ua-test/osmo-stp.cfgeditnplab-sua-test/osmo-stp.cfgeditosmo-stp-latest/osmo-stp.cfgeditttcn3-stp-test/osmo-stp.cfgeditttcn3-hnbgw-test/osmo-stp.cfgeditosmo-stp-master/osmo-stp.cfgeditttcn3-sgsn-test/osmo-stp.cfgeditttcn3-msc-test/osmo-stp.cfgeditttcn3-bsc-test-vamos/osmo-stp.cfggithttps://jenkins.osmocom.org/jenkins/user/pespinPau Espin Pedrol