Feature #2210
closedosmo-gsm-tester: allow verification that a BTS has connected to the NITB
100%
Description
Provide API that queries the NITB CTRL interface whether a given BTS is indeed connected.
Also: a bts
resource object has been registered with a given nitb which would normally have started: so, on bts.start()
we can by default include a check to wait for / verify that the BTS has actually connected to the NITB, without individual tests to do this explicitly over and over (should be possible to do it explicitly as well).
Updated by pespin almost 7 years ago
- Status changed from New to In Progress
- Assignee changed from 55360 to pespin
Updated by pespin almost 7 years ago
- Status changed from In Progress to Feedback
- Assignee changed from pespin to neels
- % Done changed from 0 to 80
Patch available for review: https://gerrit.osmocom.org/#/c/2692/1
Updated by neels almost 7 years ago
- Status changed from Feedback to In Progress
- Assignee changed from neels to pespin
Updated by pespin almost 7 years ago
- Status changed from In Progress to Feedback
Updated by neels almost 7 years ago
- Status changed from Feedback to In Progress
I generally don't agree with putting an issue in Feedback status because a patch is available on gerrit. It is still your responsibility to keep the patch updated and solve problems; the gerrit feedback is not the same as a redmine ticket feedback, where you assign a ticket to someone to request feedback. I think after posting the patch link, the ticket should remain In Progress until the patch is submitted.
Updated by pespin over 6 years ago
New patchset available:
remote: https://gerrit.osmocom.org/5274 OsmoNitb: Introduce bts_is_connected API
remote: https://gerrit.osmocom.org/5275 OsmoBsc: Introduce bts_is_connected API
remote: https://gerrit.osmocom.org/5276 suites: Wait for BTS to connect to BSC before continuing
Updated by pespin over 6 years ago
- Status changed from In Progress to Resolved
- % Done changed from 80 to 100