Bug 2151063
| Summary: | Upgrading an OVN setup to latest OVN (to be released 22.12) is broken when ovn-controllers are upgraded before central components | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux Fast Datapath | Reporter: | Numan Siddique <nusiddiq> |
| Component: | ovn22.06 | Assignee: | Dumitru Ceara <dceara> |
| Status: | CLOSED ERRATA | QA Contact: | Jianlin Shi <jishi> |
| Severity: | urgent | Docs Contact: | |
| Priority: | high | ||
| Version: | FDP 21.K | CC: | ctrautma, dceara, jiji, jishi |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | ovn22.06-22.06.0-93.el8fdp | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-02-09 00:27: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: | |||
|
Description
Numan Siddique
2022-12-06 03:16:16 UTC
Fix posted for review: https://patchwork.ozlabs.org/project/ovn/list/?series=332702&state=* ovn22.06 fast-datapath-rhel-9 clone created at https://bugzilla.redhat.com/show_bug.cgi?id=2155386 ovn22.03 fast-datapath-rhel-8 clone created at https://bugzilla.redhat.com/show_bug.cgi?id=2155388 ovn22.03 fast-datapath-rhel-9 clone created at https://bugzilla.redhat.com/show_bug.cgi?id=2155389 There's currently no downstream build on which we can reproduce the issue. That's because the feature that introduced conditional monitoring for a newly added table was only part of v22.12.0 and v22.12.0 already has the fix. I think we can close this one and its clones as UPSTREAM, what do you think Jianlin? Thanks, Dumitru (In reply to Dumitru Ceara from comment #6) > There's currently no downstream build on which we can reproduce the issue. > That's because the feature that introduced conditional monitoring for a > newly added table was only part of v22.12.0 and v22.12.0 already has the fix. > > I think we can close this one and its clones as UPSTREAM, what do you think > Jianlin? if the bug is for 22.12, then we can close it as UPSTREAM. but this bug is for 22.09, and the patches are backported to 22.09, so closing as UPSTREAM may not be a good solution. Is it possible that you help to compile unfixed 22.12 rpms for us to test this bug? thx > > Thanks, > Dumitru (In reply to Jianlin Shi from comment #7) > (In reply to Dumitru Ceara from comment #6) > > There's currently no downstream build on which we can reproduce the issue. > > That's because the feature that introduced conditional monitoring for a > > newly added table was only part of v22.12.0 and v22.12.0 already has the fix. > > > > I think we can close this one and its clones as UPSTREAM, what do you think > > Jianlin? > > if the bug is for 22.12, then we can close it as UPSTREAM. > but this bug is for 22.09, and the patches are backported to 22.09, so > closing as UPSTREAM may not be a good solution. > Is it possible that you help to compile unfixed 22.12 rpms for us to test > this bug? thx > Sorry for the delay, thanks for verifying this BZ as "SanityOnly". Let's go for that, I don't think there's a real need for more verification at the moment. Regards, Dumitru Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (ovn22.06 bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2023:0680 |