kubeovn / kube-ovn / 26858908984

25%

master: 26%

push

github

fix(controller): correct egress sync status field on ACL update failure (#6804)

When the egress ACL update fails, IngressLastSyncSuccess was being set to
false instead of EgressLastSyncSuccess. This was a copy-paste bug from the
ingress block above. The incorrect status caused:

1. Ingress status to become falsely negative — monitoring/alerting thinks
ingress rules are broken when they are fine.
2. Egress status to become falsely positive — monitoring/alerting thinks
egress rules are synced when they actually failed.

Fix by setting EgressLastSyncSuccess = false in the egress error path.

Signed-off-by: Harisudarsan <sudarshanhari561@gmail.com>
(cherry picked from commit 35cd2a69e)

0 of 1 new or added line in 1 file covered. (0.0%)

14226 of 56669 relevant lines covered (25.1%)

0.29 hits per line