Bug 1125367
Summary: | engine-setup fails immediately unless rhevm-reports-setup and rhevm-dwh-setup are upgraded first | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | wdaniel |
Component: | ovirt-engine-setup | Assignee: | Yedidyah Bar David <didi> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Petr Matyáš <pmatyas> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.4.1-1 | CC: | bazulay, benglish, dfediuck, ecohen, iheim, jspahr, rbalakri, Rhev-m-bugs, sbonazzo, sherold, sradco, yeylon, ylavi |
Target Milestone: | --- | ||
Target Release: | 3.5.0 | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | integration | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-09-30 09:41:45 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
wdaniel
2014-07-31 16:18:11 UTC
maybe a documentation bug? Maybe also a missing conflict on older 3.4.0 setup plugins for dwh / reports, looks like they were not upgraded (In reply to wdaniel from comment #0) > Additional info: > > The end of the engine-setup script still prompts the user to upgrade the > other setup packages, even though the step was already performed in order to > complete engine-setup: Not sure what exactly you refer to in "though the step was already performed in order to complete engine-setup". > > > [ INFO ] Stage: Closing up > > --== SUMMARY ==-- > > [ INFO ] DWH and/or Reports were found on this system. > To upgrade them, please run the following commands: > # yum update rhevm-dwh rhevm-reports Do you mean that you updated these packages as well? And still got this error? > # engine-setup > > Our docs don't currently reflect this, do we need a doc bug as well? From my POV there is no bug :-) If the docs indeed say to upgrade only rhevm-setup (which I guess they do), and engine-setup checks and sees that there is also an update for other packages that are required for it to run well, and it instructs the user to update these as well, is that a problem? Anyway, we might want to update the documentation. We can also prevent this error by adding to rhevm-setup 3.4.1: Conflicts: rhevm-dwh-setup < 3.4.1 Conflicts: rhevm-reports-setup < 3.4.1 I didn't check if this will be enough for yum to update them as well. We definitely do not want to Require them. I didn't check the current documentation. For 3.4, the setup code of dwh and reports was rewritten. They are now not separate utilities, but are plugins for the same engine-setup tool used to setup/upgrade the engine. 3.3->3.4 upgrade: ================= In principle, in the upgrade path 3.3->3.4, we allow two options. In both, I assume that engine/dwh/reports 3.3 are installed and setup. Option 1 - Engine first, dwh/reports later: 1. yum update rhevm-setup 2. engine-setup 3. yum install rhevm-dwh-setup rhevm-reports-setup 4. engine-setup Steps 3 and 4 also "update" the engine, if there are updates, and always do some steps that every run of engine-setup does. Option 2 - All at once: 1. yum update rhevm-setup 2. yum install rhevm-dwh-setup rhevm-reports-setup (These two can actually be run at once by: yum install rhevm-setup rhevm-dwh-setup rhevm-reports-setup) 3. engine-setup 3.4.z updates: ============== Assuming engine/dwh/reports 3.4.z were already setup (either new or upgraded from earlier), a next run of 'engine-setup' will check for updates for any of the already-installed setup components (engine, dwh and reports) and will refuse to run if any are found, emitting the above message. So if all are setup, all setup packages must be updated by yum prior to running engine-setup. I read the correspondence on the support case leading to opening this bug, and it seemed as if some information is missing. I hope now all is clear. Also other issues (such as the text suggesting to update dwh/reports also if already done) were already fixed in other bugs, and 3.4.2 should be fine in this regard. What else is needed? Not sure about the procedure for requesting documentation update. Doron? Yaniv now told me that it was already updated in the docs, as can be seen in [1]. Thanks, Yaniv! [1] https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.4/html/Installation_Guide/Upgrading_to_Red_Hat_Enterprise_Virtualization_Manager_3.4.html You must update reports and dwh with engine for now on, documentation was changed to reflect that. Please yum update all setup packages or it will fail by design. |