diff options
author | Pau Espin Pedrol <pespin@sysmocom.de> | 2020-10-01 16:14:44 +0200 |
---|---|---|
committer | laforge <laforge@osmocom.org> | 2020-10-15 05:55:36 +0000 |
commit | 12e15479d69b226ea1fb6a2f2a478b6df3dd6682 (patch) | |
tree | 459a99c58849d3c3776f1ed0c6019ea35cab535e /tests | |
parent | 737bb2f47b3547c05f4ed6b5da99d058eebfabcf (diff) |
Set all NM OML objects to Locked by default
Before they were set with a value of 0, which had no related enum field,
but since in general all comparsions are done against NM_STATE_UNLOCKED
they also hold valid.
The major change in behavior with this patch is upon OML link down,
where gsm_bts_mo_reset() is called on all objects. This way, upon OML
re-establishment we have again all objects as Locked again, which is the
expected default value as per TS 12.21.
Change-Id: I68ae0bc51a565f903b47cf72f3e3dd6f1a2d2651
Diffstat (limited to 'tests')
-rwxr-xr-x | tests/ctrl_test_runner.py | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/tests/ctrl_test_runner.py b/tests/ctrl_test_runner.py index 2ccbfe8d0..55a4ca68c 100755 --- a/tests/ctrl_test_runner.py +++ b/tests/ctrl_test_runner.py @@ -292,7 +292,7 @@ class TestCtrlBSC(TestCtrlBase): r = self.do_get('bts.0.rf_state') self.assertEqual(r['mtype'], 'GET_REPLY') self.assertEqual(r['var'], 'bts.0.rf_state') - self.assertEqual(r['value'], 'inoperational,unlocked,on') + self.assertEqual(r['value'], 'inoperational,locked,on') r = self.do_set('rf_locked', '1') self.assertEqual(r['mtype'], 'SET_REPLY') |