Bug 1467585
| Summary: | [Docs][Upgrade][4.1] Missing info about engine-upgrade-check | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Jiri Belka <jbelka> |
| Component: | Documentation | Assignee: | Byron Gravenorst <bgraveno> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Megan Lewis <melewis> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.1.4 | CC: | jbelka, lbopf, lsurette, rbalakri, srevivo, ykaul, ylavi |
| Target Milestone: | ovirt-4.1.6 | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-11-08 03:33:49 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Docs | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Jiri Belka
2017-07-04 09:38:06 UTC
Assigning to Byron for review. Byron, we've never included engine-upgrade-check in the context of a version-to-version upgrade before, so it might be worth confirming what the expected user behaviour is (e.g. 4.1 is released, does a customer on 4.0 need to run engine-upgrade-check to know that 4.1 is available, if they have to enable the 4.1 repos to do so anyway?) |