Bug 1758821
| Summary: | [FD-8] Initialize openvswitch2.12 stream with Open vSwitch 2.12.0. | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux Fast Datapath | Reporter: | Flavio Leitner <fleitner> |
| Component: | openvswitch2.11 | Assignee: | Flavio Leitner <fleitner> |
| Status: | CLOSED ERRATA | QA Contact: | Rick Alongi <ralongi> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | FDP 19.F | CC: | ctrautma, jhsiao, kfida, ovs-qe, ovs-team, qding, ralongi |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1758820 | Environment: | |
| Last Closed: | 2019-12-11 12:06:53 UTC | Type: | --- |
| 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: | 1758820 | ||
| Bug Blocks: | |||
|
Description
Flavio Leitner
2019-10-06 00:28:15 UTC
Hi Flavio, What does the bug do? Please give suggestion on how to do the verification? Thanks Qijun This is a bug requesting to start the openvswitch2.12 stream. We need to make sure that it's not seen as an upgrade from openvswitch or openvswitch10/11 and that 2.12 works without regressions. That's all. fbl Hi Flavio, Can you clarify what you mean by "make sure that it's not seen as an upgrade from openvswitch or openvswitch10/11" in c#3? Do you mean to make sure you cannot upgrade from an earlier stream to this new stream directly without a wrapper/key file? Thanks, Rick (In reply to Rick Alongi from comment #4) That's correct! fbl Testing complete on 2.12, no regressions found. https://docs.google.com/spreadsheets/d/1IvcypoK1lqVZPB4_QX-s6bZ_bwNBXa_p0Bwv2TeRjEA/edit#gid=0 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, 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-2019:4207 |