Bug 1486822
| Summary: | drop package redhat-support-plugin-rhev | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Greg Sheremeta <gshereme> |
| Component: | redhat-support-plugin-rhev | Assignee: | Greg Sheremeta <gshereme> |
| Status: | CLOSED ERRATA | QA Contact: | Pavol Brilla <pbrilla> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.2.0 | CC: | didi, eedri, gshereme, lsurette, melewis, pstehlik, rbalakri, sbonazzo, srevivo, ykaul, ylavi |
| Target Milestone: | ovirt-4.2.0 | Keywords: | CodeChange, Tracking |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Deprecated Functionality | |
| Doc Text: |
With this update, the redhat-support-plugin-rhev package has been deprecated. The documentation functionality of the redhat-support-plugin-rhev package has been merged into the rhvm-doc package in Red Hat Virtualization 4.2.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-05-15 17:31:29 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | UX | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1488084 | ||
| Bug Blocks: | |||
|
Description
Greg Sheremeta
2017-08-30 15:09:35 UTC
Things to test: 1. the package isn't there in a fresh 4.2 install 2. the package is removed when upgrading from 4.1 3. the Red Hat Documentation tab still shows Adding patch to fix rhvm-setup-plugin (In reply to Eyal Edri from comment #2) > Adding patch to fix rhvm-setup-plugin Fixed the number. Moved to POST for now. Also, why is the component being the plugin itself? If it should be removed, it should not exist, right? Do we build it for 4.2? Perhaps bug should be on rhvm-setup-plugins (if the functionality is only there), or we need a tracker with more bugs as needed (e.g. on docs, TestOnly). Current version of the added patch handles (1.) in comment 1, and also drops it from versionlock on upgrades, but does not remove it. What happens if it's not removed? Will this break functionality? Affect the system in any other way, except for wasting a bit of disk space? If so: 1. The engine should conflict with it 2. If that's not enough (not sure), engine-setup should remove it. Otherwise, I'd just keep it untouched, letting the users remove it manually. They can use 'yum autoremove' or whatever other means. We also do not remove other dependencies we do not need anymore during upgrades. (In reply to Yedidyah Bar David from comment #3) > (In reply to Eyal Edri from comment #2) > > Adding patch to fix rhvm-setup-plugin > > Fixed the number. > > Moved to POST for now. > > Also, why is the component being the plugin itself? This is a deprecation bug, meaning it should be used for document the redhat-support-plugin-rhev package has been droppped. > If it should be removed, it should not exist, right? We need the component for tracking bugs to this component for versions < 4.2 > Do we build it for 4.2? No > Perhaps bug should be on rhvm-setup-plugins (if the functionality is only there), or we need a > tracker with more bugs as needed (e.g. on docs, TestOnly). This should be the one on docs. We may open other bugs for needed components > Current version of the added patch handles (1.) in comment 1, and also drops > it from versionlock on upgrades, but does not remove it. > > What happens if it's not removed? Will this break functionality? Affect the > system in any other way, except for wasting a bit of disk space? If so: > 1. The engine should conflict with it > 2. If that's not enough (not sure), engine-setup should remove it. > > Otherwise, I'd just keep it untouched, letting the users remove it manually. > They can use 'yum autoremove' or whatever other means. We also do not remove > other dependencies we do not need anymore during upgrades. As far as I understood rhevm-docs package should Obsolete: redhat-support-plugin-rhev < 4.2.0 Provide: redhat-support-plugin-rhev = 4.2.0 Handling the removal on upgrade since the rhevm-docs package now provide links previously provided by this package. Opened a new bug for rhvm-setup-plugins, moving back to MODIFIED. > > What happens if it's not removed? Will this break functionality? Actually yes. It must be removed. > As far as I understood rhevm-docs package should > Obsolete: redhat-support-plugin-rhev < 4.2.0 > Provide: redhat-support-plugin-rhev = 4.2.0 > > Handling the removal on upgrade since the rhevm-docs package now provide > links previously provided by this package. Right, it's a UI plugin that used to be provided by redhat-support-plugin-rhev and now lives in rhvm-doc. rhvm-doc 4.2 has Obsoletes: redhat-support-plugin-rhev I did not add Provides: redhat-support-plugin-rhev I don't think I should, unless I am missing something. Installing:
ovirt-engine noarch 4.2.0-0.4.master.el7 rhv-4.2.0-latest 1.9 M
replacing ovirt-engine-userportal.noarch 4.1.5.2-0.1.el7
rhvm noarch 4.2.0-0.4.master.el7 rhv-4.2.0-latest 8.0 k
replacing rhevm.noarch 4.1.5.2-0.1.el7
rhvm-branding-rhv noarch 4.2.0-0.2.beta.20171031013156.el7ev rhv-4.2.0-latest 47 k
replacing rhevm-branding-rhev.noarch 4.1.5-0.el7ev
rhvm-doc noarch 4.2.0-0.1.master.201708301538.el7ev rhv-4.2.0-latest 7.0 k
replacing redhat-support-plugin-rhev.noarch 4.1.0-1.el7
replacing rhevm-doc.noarch 4.1.7-1.el7ev
....
output continues
The documentation text flag should only be set after 'doc text' field is provided. Please provide the documentation text and set the flag to '?' again. 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-2018:1466 BZ<2>Jira Resync |