-
Type:
Bug
-
Status: To Do (View Workflow)
-
Priority:
Medium
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: XOS
-
Labels:None
-
Story Points:3
-
Epic Link:
When an object is deleted, it can't be updated in the data model, yet the synchronizers continue to try to update some backend state. This happens until the reaper kills off the object.
The solution is probably to have the synchronizers accept changes to feedback fields while models are in deleted state.
Example error message:
ERROR:multistructlog:OrderedDict([('synchronizer_name', 'kubernetes'), ('e', <_Rendezvous of RPC that terminated with (StatusCode.UNKNOWN, Exception calling application: KubernetesConfigMap matching query does not exist.)>), ('event', 'Could not update backend status field!')]) Traceback (most recent call last): File "/opt/xos/synchronizers/new_base/event_loop.py", line 319, in set_object_error always_update_timestamp=True) File "/usr/local/lib/python2.7/dist-packages/xosapi/orm.py", line 286, in save self.stub.invoke("Update%s" % self._wrapped_class.__class__.__name__, self._wrapped_class, metadata=metadata) File "/usr/local/lib/python2.7/dist-packages/xosapi/orm.py", line 576, in invoke return method(request, metadata=metadata) File "/usr/local/lib/python2.7/dist-packages/grpc/_channel.py", line 487, in __call__ return _end_unary_response_blocking(state, call, False, deadline) File "/usr/local/lib/python2.7/dist-packages/grpc/_channel.py", line 437, in _end_unary_response_blocking raise _Rendezvous(state, None, None, deadline) _Rendezvous: <_Rendezvous of RPC that terminated with (StatusCode.UNKNOWN, Exception calling application: KubernetesConfigMap matching query does not exist.)>
| # | Subject | Branch | Project | Status | CR | V |
|---|---|---|---|---|---|---|
| 10438,1 | CORD-3088 Prevent misleading error messages when updating deleted objs | master | xos | Status: MERGED | +2 | +1 |