diff options
| author | Florian Eckert <fe@dev.tdt.de> | 2023-07-21 12:56:34 +0200 |
|---|---|---|
| committer | Florian Eckert <fe@dev.tdt.de> | 2023-07-24 09:41:51 +0200 |
| commit | 30911865b2791c1eb516559cfb414b17e2be5f64 (patch) | |
| tree | 23e39062505d7b0664a5b11b4b2bb694004dcd31 /lang/python/python-certifi/test.sh | |
| parent | 7513c483ddc0e3c3137869c8e692957436a08925 (diff) | |
modemmanager: do not set proto_notify_error on teardown
If on teardown the 'proto_notify_error' is set to 'MM_TEARDOWN_IN_PROGRESS',
then an error which is set on 'setup' is not visible in the ubus
network.interface.<iface> status output.
{
"up": false,
"pending": false,
"available": true,
"autostart": false,
"dynamic": false,
"proto": "modemmanager",
"data": {
},
"errors": [
{
"subsystem": "dualsim",
"code": "MM_TEARDOWN_IN_PROGRESS"
}
]
}
It alway shows the code 'MM_TEARDWON_IN_PROGRESS'!
By removing the line 'proto_notify_error "${interface}" MM_TEARDOWN_IN_PROGRESS'
in teardown, the last error is show in the proto stack from setup.
Signed-off-by: Florian Eckert <fe@dev.tdt.de>
Diffstat (limited to 'lang/python/python-certifi/test.sh')
0 files changed, 0 insertions, 0 deletions