Bug 1971015

Summary:	In upgrade, satellite-installer failed with "Failed to call refresh: 'pulpcore-manager migrate --noinput'"
Product:	Red Hat Satellite	Reporter:	Devendra Singh <desingh>
Component:	Installation	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED ERRATA	QA Contact:	Devendra Singh <desingh>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.10.0	CC:	egolov, gtalreja
Target Milestone:	6.10.0	Keywords:	AutomationBlocker, PrioBumpQA, Triaged, UpgradeBlocker, Upgrades
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	python-pulp_2to3_migration-0.11.2	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-11-16 14:11:39 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:

Description Devendra Singh 2021-06-11 16:41:12 UTC

Description of problem: In upgrade, satellite-installer failed with "Failed to call refresh: 'pulpcore-manager migrate --noinput'"


Version-Release number of selected component (if applicable):
6.10 Snap4

How reproducible:
always

Steps to Reproduce:
1. Prepare the 6.9.z setup using the upgrade template.
2. Run the pre-migration steps before running the upgrade for 6.10 snap4.
3. Applied the patch for BZ#1967131
4. Pulp migration completed successfully.
5  Run the upgrade, but it failed in the installer. 


Actual results:
installer failed with "Failed to call refresh: 'pulpcore-manager migrate --noinput' returned 1 instead of one of [0]" error.

Expected results:
In the upgrade, installer should complete successfully. 

Additional info:

Comment 3 Devendra Singh 2021-07-01 18:17:24 UTC

Verified on 6.10 Snap7.

# satellite-maintain upgrade run --target-version 6.10
Checking for new version of satellite-maintain...
Nothing to update, can't find new version of satellite-maintain.
..................................
Confirm to continue with the modification part of the upgrade, [y(yes), n(no), q(quit)] y
Running Procedures before migrating to Satellite 6.10                           
================================================================================
........................................
--------------------------------------------------------------------------------
Unlock packages:                                                      [OK]
--------------------------------------------------------------------------------
Update package(s) :                                                   [OK]
--------------------------------------------------------------------------------
Procedures::Installer::Upgrade: 2021-07-01 12:15:47 [NOTICE] [root] Loading installer configuration. This will take some time.
2021-07-01 12:15:53 [NOTICE] [root] Running installer with log based terminal output at level NOTICE.
2021-07-01 12:15:53 [NOTICE] [root] Use -l to set the terminal output log level to ERROR, WARN, NOTICE, INFO, or DEBUG. See --full-h
........................
2021-07-01 12:29:52 [NOTICE] [configure] 2500 configuration steps out of 2933 steps complete.
2021-07-01 12:32:01 [NOTICE] [configure] 2750 configuration steps out of 2933 steps complete.
2021-07-01 12:33:17 [NOTICE] [configure] System configuration has finished.
Executing: foreman-rake upgrade:run
`/usr/share/foreman` is not writable.
............
I, [2021-07-01T12:33:51.151912 #84838]  INFO -- : Removed 0 orphaned pools
  Success!

Comment 6 errata-xmlrpc 2021-11-16 14:11:39 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 (Moderate: Satellite 6.10 Release), 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/RHSA-2021:4702