Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 2173724

Summary:	Run container-repair-media-type script on upgrade
Product:	Red Hat Satellite	Reporter:	Ian Ballou <iballou>
Component:	Satellite Maintain	Assignee:	wclark
Status:	CLOSED ERRATA	QA Contact:	Lukas Pramuk <lpramuk>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.11.5	CC:	ahumbe, ehelms, ipanova, lpramuk, osousa, wclark
Target Milestone:	6.13.2	Keywords:	Triaged, Upgrades, WorkAround
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	rubygem-foreman_maintain-1.2.10	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	2214585 (view as bug list)		Environment:
Last Closed:	2023-07-12 15:37: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:

Description Ian Ballou 2023-02-27 18:36:41 UTC

To repair those affected by https://bugzilla.redhat.com/show_bug.cgi?id=2102078 , a repair script needs to be run. By running at upgrade time, we reduce the risk of users hitting the related `podman pull` error.

*** Repair command: `pulpcore-manager container-repair-media-type`

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

Satellite 6.11 up, depending on if users have corrupt Pulp contents from the original BZ.

(Satellite 6.10 too but we didn't backport the fix there).

Comment 2 wclark 2023-03-27 19:01:12 UTC

Created redmine issue https://projects.theforeman.org/issues/36233 from this bug

Comment 3 Lukas Pramuk 2023-06-13 13:50:25 UTC

FailedQA.

@Satellite 6.13.2 Snap 1
rubygem-foreman_maintain-1.2.9-1.el8sat.noarch

any satellite-maintain upgrade sub-command is failing now:

# satellite-maintain upgrade list-versions
Checking for new version of satellite-maintain...
Nothing to update, can't find new version of satellite-maintain.
uninitialized constant Procedures::Pulpcore::ContainerRepairMediaType
Did you mean?  Procedures::Pulpcore::RepairContainerMediaType

>>> there are typos in the following scenarios: definitions/scenarios/upgrade_to_capsule_6_13.rb, definitions/scenarios/upgrade_to_satellite_6_13.rb

Comment 6 Lukas Pramuk 2023-06-28 12:20:55 UTC

VERIFIED.

@Satellite 6.13.2 Snap 2
rubygem-foreman_maintain-1.2.10-1.el8sat.noarch

by Upgrades Automation running ystream upgrade from 6.12 to 6.13.2:

# foreman-maintain upgrade run --plaintext --whitelist=repositories-validate,repositories-setup,non-rh-packages --target-version 6.13 -y
...

Running Migration scripts to Satellite 6.13
================================================================================
Setup repositories:                                                   [SKIPPED]
--------------------------------------------------------------------------------
Enable the given stream modules:                                      [OK]
--------------------------------------------------------------------------------
Unlock packages:                                                      [OK]
--------------------------------------------------------------------------------
Update package(s) :                                                   [OK]
--------------------------------------------------------------------------------
Procedures::Installer::Upgrade:                                       [OK]
--------------------------------------------------------------------------------
Execute upgrade:run rake task:                                        [OK]
--------------------------------------------------------------------------------

>>> 6.13 ystream upgrade is now successful

Comment 15 errata-xmlrpc 2023-07-12 15:37: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 (Satellite 6.13.2 Async Update), 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-2023:4043