Actions
Bug #5961
closedBTS accepts OPSTART without prior SET ATTRIBUTES
Start date:
03/26/2023
Due date:
% Done:
100%
Spec Reference:
Description
For several different Abis MO, osmo-bts appears to accept OPSTART despite no attributes having been set before.
This makes our BTS_Tests_OML fail, likely ever since those tests were written:
- BTS_Tests_OML.TC_bts_opstart_noattr
- RADIO CARRIER: Test OPSTART without SET BTS ATTRIBUTES; expect NACK
- error: Unexpected OPSTART ACK for NM_OC_BTS (1) { bts_nr := 0, trx_nr := 255, ts_nr := 255 }
- BTS_Tests_OML.TC_radio_carrier_opstart_noattr
- RADIO CARRIER: Test OPSTART without SET BTS ATTRIBUTES; expect NACK
- error: Unexpected OPSTART ACK for NM_OC_RADIO_CARRIER (2) { bts_nr := 0, trx_nr := 0, ts_nr := 255 }
- BTS_Tests_OML.TC_ts_opstart_noattr
- BTS: Test OPSTART without SET BTS ATTRIBUTES; expect NACK
- error: Unexpected OPSTART ACK for NM_OC_CHANNEL (3) { bts_nr := 0, trx_nr := 0, ts_nr := 1 }
Related issues
Updated by pespin about 1 year ago
- Related to Bug #5992: osmo-bts: Handle Opstart result from within nm_*_fsm added
Updated by pespin about 1 year ago
- Status changed from New to Feedback
- % Done changed from 0 to 90
remote: https://gerrit.osmocom.org/c/osmo-bts/+/32211 nm: Apply OPSTART through NM FSMs [NEW]
remote: https://gerrit.osmocom.org/c/osmo-bts/+/32212 NM: NACK received OML OPSTART if no attributes were set beforehand [NEW]
Can be closed when these patches are merged.
Updated by pespin about 1 year ago
- Is duplicate of Bug #3789: BTS permits OPSTART of MO without attributes added
Updated by pespin about 1 year ago
- Status changed from Feedback to Resolved
Fixed as described in #5961
Actions