Bug 1710305 - pre-migration step in foreman maintain asks for permission twice.
Summary: pre-migration step in foreman maintain asks for permission twice.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Satellite Maintain
Version: 6.5.0
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: 6.6.0
Assignee: Martin Bacovsky
QA Contact: Jameer Pathan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-15 10:00 UTC by Jameer Pathan
Modified: 2019-10-22 16:37 UTC (History)
8 users (show)

Fixed In Version: foreman-maintain-0.4.8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-22 16:36:54 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 27072 0 Normal Closed pre-migration step in foreman maintain asks for permission twice. 2020-05-13 06:18:32 UTC
Red Hat Product Errata RHBA-2019:3181 0 None None None 2019-10-22 16:37:00 UTC

Description Jameer Pathan 2019-05-15 10:00:55 UTC
Description of problem:
pre-migration step in foreman maintain asks for permission twice.

Version-Release number of selected component (if applicable):
@satellite 6.5.0
@rubygem-foreman_maintain-0.3.3-1.el7sat.noarch

How reproducible:
always

Steps to Reproduce:
1. Run #foreman-maintain upgrade run --target-version 6.5
2. on "Procedures before migrating to Satellite 6.5" it asks twice for permission to continue.

Actual results:


Continue with [Procedures before migrating to Satellite 6.5], [y(yes), n(no), q(quit)] y
Continue with [Procedures before migrating to Satellite 6.5], [y(yes), n(no), q(quit)] y
Running Procedures before migrating to Satellite 6.5                            
================================================================================
disable active sync plans: 
- Total 0 sync plans are now disabled.                                [OK]      
--------------------------------------------------------------------------------

Expected results:

Continue with [Procedures before migrating to Satellite 6.5], [y(yes), n(no), q(quit)] y
Running Procedures before migrating to Satellite 6.5                            
================================================================================
disable active sync plans: 
- Total 0 sync plans are now disabled.                                [OK]      
--------------------------------------------------------------------------------

Additional info:

Comment 3 Kavita 2019-06-18 10:09:17 UTC
Created redmine issue https://projects.theforeman.org/issues/27072 from this bug

Comment 5 Bryan Kearney 2019-08-21 14:03:46 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/27072 has been resolved.

Comment 8 Bryan Kearney 2019-09-05 10:03:54 UTC
Upstream bug assigned to mbacovsk

Comment 9 Bryan Kearney 2019-09-05 10:03:56 UTC
Upstream bug assigned to mbacovsk

Comment 10 Bryan Kearney 2019-09-05 16:03:55 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/27072 has been resolved.

Comment 11 Martin Bacovsky 2019-09-05 19:37:58 UTC
The patch is included in foreman-maintain 0.4.8

Comment 12 Jameer Pathan 2019-09-09 12:27:32 UTC
Verified

Verified with:
- Satellite 6.6.0 snap 19
- rubygem-foreman_maintain-0.4.8-1.el7sat.noarch

Steps to Reproduce:
1. Run #foreman-maintain upgrade run --target-version 6.6.z --whitelist repositories-validate

Observation:
- pre-migration step of foreman maintain didn't ask for permission twice.



Continue with [Procedures before migrating to Satellite 6.6.z], [y(yes), n(no), q(quit)] y
Running Procedures before migrating to Satellite 6.6.z                          
================================================================================
disable active sync plans: 
| Total 0 sync plans are now disabled.                                [OK]      
--------------------------------------------------------------------------------

Comment 15 errata-xmlrpc 2019-10-22 16:36:54 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/RHBA-2019:3181


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