Bug 1526151 - remove --upgrade-to-rhv option
Summary: remove --upgrade-to-rhv option
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-fast-forward-upgrade
Version: 4.2.0
Hardware: All
OS: All
unspecified
high
Target Milestone: ovirt-4.2.4
: ---
Assignee: Douglas Schilling Landgraf
QA Contact: Jiri Belka
URL:
Whiteboard:
Depends On:
Blocks: 1366900
TreeView+ depends on / blocked
 
Reported: 2017-12-14 20:42 UTC by Douglas Schilling Landgraf
Modified: 2019-05-16 13:07 UTC (History)
4 users (show)

Fixed In Version: ovirt-fast-forward-upgrade-1.0.0-1.el7ev
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-06-28 06:48:46 UTC
oVirt Team: Integration
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Douglas Schilling Landgraf 2017-12-14 20:42:05 UTC
Description of problem:

This option might confuse users or make them jump upgrades required.

Comment 2 Jiri Belka 2017-12-15 08:25:30 UTC
(In reply to Douglas Schilling Landgraf from comment #1)
> https://github.com/oVirt/ovirt-engine-hyper-upgrade/pull/11/commits/
> 0fc9fe2e74b10a6e01817524251addfdd4edc92c

so, will that work now with 4.2 beta? if i have 4.1 would i get 4.2 beta or 4.2?

Comment 3 Douglas Schilling Landgraf 2017-12-15 21:26:22 UTC
(In reply to Jiri Belka from comment #2)
> (In reply to Douglas Schilling Landgraf from comment #1)
> > https://github.com/oVirt/ovirt-engine-hyper-upgrade/pull/11/commits/
> > 0fc9fe2e74b10a6e01817524251addfdd4edc92c
> 
> so, will that work now with 4.2 beta? if i have 4.1 would i get 4.2 beta or
> 4.2?

For now 4.2beta, later we will add the 4.2 GA data.

Comment 4 Jiri Belka 2018-01-12 08:44:36 UTC
forgotten '--upgrade-to' in help output:

# rpm -qf `which ovirt-engine-hyper-upgrade`
ovirt-engine-hyper-upgrade-1.0.0-4.el7ev.noarch

# ovirt-engine-hyper-upgrade --help
usage: ovirt-engine-hyper-upgrade [-h] [--backup] [--backup-dir BACKUP_DIR]

Tool to upgrade RHV environments

optional arguments:
  -h, --help            show this help message and exit
  --backup              Execute engine-backup before upgrade
  --backup-dir BACKUP_DIR
                        Directory where the engine-backup will save the output
                        If not provided, it will use /tmp

Example of use:
ovirt-engine-hyper-upgrade --upgrade-to-rhv=4.1
                           ^^^^^^^^^^^^^^^^^^^^^^ here

line https://github.com/dougsland/ovirt-engine-hyper-upgrade/blob/0fc9fe2e74b10a6e01817524251addfdd4edc92c/src/ovirt-engine-hyper-upgrade#L483

Comment 6 Jiri Belka 2018-02-21 16:54:59 UTC
there's no build in d/s for this and version defined in 'fixed in version' is not one which has the fix.

plz move to on_qa when there is rpm ready, we do not test diffs or package it ourselves.

Comment 7 Jiri Belka 2018-03-05 16:07:05 UTC
# ovirt-engine-hyper-upgrade --help
usage: ovirt-engine-hyper-upgrade [-h] [--backup] [--backup-dir BACKUP_DIR]

Tool to upgrade RHV environments

optional arguments:
  -h, --help            show this help message and exit
  --backup              Execute engine-backup before upgrade
  --backup-dir BACKUP_DIR
                        Directory where the engine-backup will save the output
                        If not provided, it will use /tmp

Example of use:
ovirt-engine-hyper-upgrade 

# rpm -qf `which ovirt-engine-hyper-upgrade`
ovirt-engine-hyper-upgrade-1.0.0-5.el7ev.noarch

Comment 8 Franta Kust 2019-05-16 13:07:24 UTC
BZ<2>Jira Resync


Note You need to log in before you can comment on or make changes to this bug.