|
Ran
|
Jobs
1
|
Files
202
|
Run time
1min
|
Badge
README BADGES
|
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%)
2 existing lines in 1 file now uncovered.13270 of 54868 relevant lines covered (24.19%)
0.28 hits per line
| Lines | Coverage | ∆ | File |
|---|---|---|---|
| 1 |
5.85 |
0.0% | pkg/controller/security_group.go |
| Lines | Coverage | ∆ | File |
|---|---|---|---|
| 2 |
61.61 |
-0.62% | pkg/ovs/ovn-nb-bfd.go |
| ID | Job ID | Ran | Files | Coverage | |
|---|---|---|---|---|---|
| 1 | 26858940715.1 | 202 |
24.19 |
GitHub Action Run |
| Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line |
|---|