Bug 1805690
Summary: | [UPI][BAREMETAL][OCP4] Unexpected downtimes during cluster upgrades. | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Alejandro Coma <acomabon> |
Component: | Networking | Assignee: | Andrew McDermott <amcdermo> |
Networking sub component: | router | QA Contact: | Hongan Li <hongli> |
Status: | CLOSED DEFERRED | Docs Contact: | |
Severity: | medium | ||
Priority: | medium | CC: | amcdermo, aos-bugs, bbennett, bchardim, dmace, erich, sdodson |
Version: | 4.3.z | Keywords: | Reopened, Upgrades |
Target Milestone: | --- | ||
Target Release: | 4.7.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-10-02 16:20:19 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1809665, 1809668, 1869785 | ||
Bug Blocks: |
Comment 9
Ben Bennett
2020-03-03 16:22:38 UTC
I'm going to mark this as blocked by https://bugzilla.redhat.com/show_bug.cgi?id=1809665 which covers a constellation of upgrade disruption fixes. Moving out to 4.6 Comment #11 still holds true here and: 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. 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. 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 to 4.7 while investigation is either ongoing or not yet started. Will be considered for earlier release versions when diagnosed and resolved. 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. We are tracking this via https://issues.redhat.com/browse/NE-348 which is scheduled for 4.7. |