Loading
Device: tolerate dropped NETCONF sessions on device deletion
DeleteDevice failed with "Not connected to NETCONF server" when the
device had already dropped the NETCONF session: the OC driver's
disconnect() always called close_session(), and DriverInstanceCache
did not catch the error, so the device was never removed from Context.
- OCDriver: only close the session if it is still alive; log instead
of raising otherwise.
- DriverInstanceCache.delete(): a failed Disconnect() no longer blocks
device deletion (same handling as terminate()).
- ofc24 CI: re-enable the bidirectional create/delete service tests.
Co-Authored-By:
Claude Opus 5.5 <noreply@anthropic.com>