Geo: Ignore invalid attributes when updating Geo node status
If replication has not caught up properly on the secondary,
it was possible for a primary Geo node to attempt an update
of the GeoNodeStatus entry with a nil
ID, resulting
in an Error 500.
We handle this in two ways:
- On the primary, ignore
id
and other unknown attributes. - On the secondary, never send
id
.
Edited by Stan Hu