Bug 1508353

Summary:	After upgrade to sat 6.3, running 'foreman-maintain upgrade run' gives error for scenario
Product:	Red Hat Satellite	Reporter:	Kavita <kgaikwad>
Component:	Satellite Maintain	Assignee:	Kavita <kgaikwad>
Status:	CLOSED ERRATA	QA Contact:	Katello QA List <katello-qa-list>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.3.0	CC:	apatel, bbuckingham, ehelms, inecas, kgaikwad, ktordeur, nkathole, sabnave, sthirugn
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	foreman-maintain-0.0.11	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-11-13 15:13:22 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:
Bug Depends On:
Bug Blocks:	1496794

Description Kavita 2017-11-01 09:52:53 UTC

Description of problem:
There is a satellite server which was upgraded to sat 6.3 using foreman-maintain.

If you run command again - foreman-maintain upgrade run
Output:
  Could not find scenario satellite_6_3_pre_upgrade_check, found 0 scenarios


Version-Release number of selected component (if applicable):
rubygem-foreman_maintain-0.0.10-1.el7sat.noarch

How reproducible:


Steps to Reproduce:
1. Start upgrading satellite server to sat 6.3 using foreman-maintain
2. In case satellite-installer failed due to some reason, try to re-run below command -
foreman-maintain upgrade run
3. It gives error for scenario

Actual results:
Could not find scenario satellite_6_3_pre_upgrade_check, found 0 scenarios


Expected results:
It should continue with upgrading process where it failed previously.

Additional info:

Comment 2 Nikhil Kathole 2017-11-01 12:34:34 UTC

*** Bug 1508349 has been marked as a duplicate of this bug. ***

Comment 3 Ivan Necas 2017-11-02 07:59:45 UTC

Fixed in foreman-maintain-0.0.11,
https://github.com/theforeman/foreman-packaging/pull/1909

Comment 4 sthirugn@redhat.com 2017-11-09 16:30:07 UTC

Verified in rubygem-foreman_maintain-0.0.11-1.el7sat.noarch.

Successfully cloned a db using clone tool, upgraded with rubygem-foreman_maintain.

After upgrading to 6.3 beta:

# foreman-maintain upgrade run --target-version 6.3
Can't upgrade to 6.3
Possible target versions are:
6.3.z

# foreman-maintain upgrade check
--target-version not specified
Possible target versions are:
6.3.z

Comment 6 Nikhil Kathole 2017-11-13 10:32:50 UTC

*** Bug 1512464 has been marked as a duplicate of this bug. ***

Comment 7 errata-xmlrpc 2017-11-13 15:13:22 UTC

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/RHEA-2017:3192