Description of problem: * In https://bugzilla.redhat.com/show_bug.cgi?id=1861383 we hit a bug where a new HAProxy validation refused a route that worked on an older OCP version * This resulted in the ingress-controller completely breaking Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: A single route that results in an invalid haproxy config can break the whole ingress-controller Expected results: A single route that results in an invalid haproxy config will not work but not affect any other routes Additional info:
*** This bug has been marked as a duplicate of bug 1861383 ***
@Andrew McDermott Why is this marked as duplicate of 1861383? 1861383 is about one concrete bug we found, this one is about limiting the impact of any bug in that area. A single route should never be able to break the ingress-controller.
(In reply to aaleman from comment #2) > @Andrew McDermott Why is this marked as duplicate of 1861383? 1861383 is > about one concrete bug we found, this one is about limiting the impact of > any bug in that area. A single route should never be able to break the > ingress-controller. (In hindsight) Perhaps I should have done it the other way around. Verifying the config AOT would fix https://bugzilla.redhat.com/show_bug.cgi?id=1861383, though I still need to think how/where that error would be bubbled up.
See also: https://bugzilla.redhat.com/show_bug.cgi?id=1857025 "Creating faulty(bad formatted cert&key) route makes other existing routes inaccessible"
I’m adding UpcomingSprint, because I was occupied by fixing bugs with higher priority/severity, developing new features with higher priority, or developing new features to improve stability at a macro level. I will revisit this bug next sprint.
Target reset from 4.6 to 4.7 while investigation is either ongoing or not yet started. Will be considered for earlier release versions when diagnosed and resolved.
Tagging with UpcomingSprint while investigation is either ongoing or pending. Will be considered for earlier release versions when diagnosed and resolved.
Close/deferred as will add this to our Jira backlog for enhancements.
(In reply to Andrew McDermott from comment #13) > Close/deferred as will add this to our Jira backlog for enhancements. https://issues.redhat.com/browse/NE-557