Bug 1625344
Summary: | unable to update or install openvswitch 2.10 if openvswitch 2.9 is currently installed | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Rick Alongi <ralongi> |
Component: | openvswitch2.10 | Assignee: | Flavio Leitner <fleitner> |
Status: | CLOSED NOTABUG | QA Contact: | Rick Alongi <ralongi> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 7.6 | CC: | atragler, ctrautma, fbaudin, fleitner, ovs-qe, qding, ralongi, rkhan |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-09-14 18:38:54 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
Rick Alongi
2018-09-04 16:58:46 UTC
Hi This is by design so that customers/users using openvswitch-2.9 does not update to newer streams without the Layered Product be ready to consume it. When the product is ready, it will release an updated package that will obsolete the previous streams, in this case 2.9, and requires the new one, in this case 2.10. Once the installation is moved to a newer stream, the following updates within the same stream should happen normally and smoothly and again it should not allow moving to any other streams (older or newer than the current one). I think OSP and RHV already have their special packages. Perhaps you could use them to unlock and test the upgrade. fbl (In reply to Flavio Leitner from comment #2) > Hi > > This is by design so that customers/users using openvswitch-2.9 does not > update to newer streams without the Layered Product be ready to consume it. > > When the product is ready, it will release an updated package that will > obsolete the previous streams, in this case 2.9, and requires the new one, > in this case 2.10. > > Once the installation is moved to a newer stream, the following updates > within the same stream should happen normally and smoothly and again it > should not allow moving to any other streams (older or newer than the > current one). > > I think OSP and RHV already have their special packages. Perhaps you could > use them to unlock and test the upgrade. > > fbl Please see BZ1625344 for info related to performing the upgrade using the rhelosp 14 repo. (In reply to Rick Alongi from comment #3) > Please see BZ1625344 for info related to performing the upgrade using the > rhelosp 14 repo. Hm, that BZ is actually this one, maybe a copy&paste error? Anyways, it would be a bug if yum updates from 2.9 to 2.10 without the LP special package. Going to close this one, but feel free to drop me an email/ping on irc. Perhaps it was bz#1625355 ? If so, it's closed too. |