Bug 1199081 - preupgrade script should detect whether proper upgrade target
Summary: preupgrade script should detect whether proper upgrade target
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: preupgrade-assistant-contents
Version: 6.7
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Frantisek Kluknavsky
QA Contact: Alois Mahdal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-03-05 12:55 UTC by Petr Hracek
Modified: 2015-03-05 12:56 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-05 12:56:34 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Petr Hracek 2015-03-05 12:55:11 UTC 
Description of problem:
Before alone upgrade done be redhat-upgrade-tool. preupgrade script should detect if redhat-upgrade-tool is executed with proper target version.
If not then upgrade should fail.

Question is if this can be done directly in redhat-upgrade-tool so that we will save time before downloading packages.
I think that redhat-upgrade-tool can detect if version file (generated by preupgrade-assistant-contents) exits and then compare them with command line arguments.
Use cases:

1) If version file doesn't exist then upgrade will stop and doesn't continue.
2) If version file contains version 7.1 then redhat-upgrade-tool should have arguments with 7.1 version too and upgrade continues.
3) If version file contains version 7.1 and redhat-upgrade-tool arguments are  with 7.0 version then it have to stop as well.
4) If version file contains version 7.0 and redhat-upgrade-tool contains 7.1 then upgrade won't be possible too.

I think that this is a good part for redhat-upgrade-tool.

What do you think?
Comment 1 Petr Hracek 2015-03-05 12:56:34 UTC 
I will generate a new bug.
Huge typos from.
Note You need to log in before you can comment on or make changes to this bug.