Bug 1464866
| Summary: | [downstream clone - 4.1.3] hosted-engine --upgrade-appliance reports unsupported upgrade path | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | rhev-integ |
| Component: | ovirt-hosted-engine-setup | Assignee: | Simone Tiraboschi <stirabos> |
| Status: | CLOSED ERRATA | QA Contact: | Artyom <alukiano> |
| Severity: | high | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 4.0.7 | CC: | lsurette, mavital, mtessun, nashok, pstehlik, ykaul |
| Target Milestone: | ovirt-4.1.3 | Keywords: | Triaged, ZStream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Downstream appliances versioning schema differs from upstream one and so a version check was too severe. Fixing it for downstream appliances.
|
Story Points: | --- |
| Clone Of: | 1464461 | Environment: | |
| Last Closed: | 2017-07-06 07:30:02 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Integration | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1464461 | ||
| Bug Blocks: | |||
|
Description
rhev-integ
2017-06-26 06:19:36 UTC
Created attachment 1291073 [details]
sosreport from the node
(Originally by Roman Hodain)
appliance version detection here fails because upstream uses a versioning schema like: ovirt-engine-appliance-4.1-20170622.1.el7.centos.noarch.rpm which resolves to "4.1" while downstream use a schema like: rhvm-appliance-4.1.20170621.0-1.el7.noarch.rpm which resolves to "4.1.20170621.0". (Originally by Sandro Bonazzola) *** Bug 1462684 has been marked as a duplicate of this bug. *** Verification steps:
1) Started with host 3.6 with appliance 3.6
2) Add master storage domain
3) Update host packages to 4.0 including appliance
4) Update host packages to 4.1 not including appliance
5) Set global maintenance
6) Run hosted-engine --upgrade-appliance
[ INFO ] This upgrade tool is running on the SPM host
The following appliance have been found on your system:
[1] - The RHEV-M Appliance image (OVA) - 4.0.20170302.0-1.el7ev
[2] - Directly select an OVA file
Please select an appliance (1, 2) [1]: 1
[ INFO ] Verifying its sha1sum
[ INFO ] Checking OVF archive content (could take a few minutes depending on archive size)
[ INFO ] Checking OVF XML content (could take a few minutes depending on archive size)
Please specify the size of the VM disk in GB: [50]:
[ INFO ] Connecting to the Engine
[ INFO ] The hosted-engine storage domain has enough free space to contain a new backup disk.
[ INFO ] Checking version requirements
[ INFO ] Hosted-engine configuration is at a compatible level
[ INFO ] Connecting to the Engine
[ INFO ] All the datacenters and clusters are at a compatible level
[ INFO ] Detecting host timezone.
Enter root password that will be used for the engine appliance (leave it empty to skip):
Confirm appliance root password:
Enter ssh public key for the root user that will be used for the engine appliance (leave it empty to skip):
[WARNING] Skipping appliance root ssh public key
Do you want to enable ssh access for the root user (yes, no, without-password) [yes]:
Please take a backup of the current engine running this command on the engine VM:
engine-backup --mode=backup --archive-compressor=gzip --file=engine_backup.tar.gz --log=engine_backup.log
Then copy the backup archive to this host and input here its path when ready.
...
deployment pass
for invalid upgrade path I have:
[ INFO ] Checking version requirements
[ INFO ] Hosted-engine configuration is at a compatible level
[ INFO ] Connecting to the Engine
[ INFO ] All the datacenters and clusters are at a compatible level
[WARNING] Unsupported upgrade path
This procedure has been designed and tested only for upgrading the engine VM from ['3.6'] to ['4.0'].
Any other usage is highly experimental and potentially dangerous:
Current engine: 4.0
Selected appliance: 4.0.20170302.0-1.el7ev
Do you want to abort the upgrade process? (Yes, No) [Yes]:
We will need this fix for 4.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-2017:1691 |