Bug 2028273

Summary: Cannot pull container content - TypeError: wrong argument type String (expected OpenSSL/X509)
Product: Red Hat Satellite Reporter: Eric Helms <ehelms>
Component: Container Management - ContentAssignee: Justin Sherrill <jsherril>
Status: CLOSED ERRATA QA Contact: addubey
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.11.0CC: egolov, pcreech, vijsingh
Target Milestone: 6.11.0Keywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-07-05 14:30:33 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 Eric Helms 2021-12-01 20:59:15 UTC
This error occurs when trying to pull container content with Satellite 7.0 snaps:

podman pull `hostname`/test_organization-test_product-foremanbusybox


This appears to be caused by the rubygem-foreman_azure_rm plugin as removing said plugin fixes the issue.

Comment 1 Justin Sherrill 2021-12-02 13:12:31 UTC
Created redmine issue https://projects.theforeman.org/issues/34070 from this bug

Comment 2 Bryan Kearney 2021-12-03 12:06:01 UTC
Upstream bug assigned to jsherril

Comment 3 Bryan Kearney 2021-12-03 12:06:03 UTC
Upstream bug assigned to jsherril

Comment 4 Bryan Kearney 2021-12-04 00:05:59 UTC
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/34070 has been resolved.

Comment 5 addubey 2022-03-14 05:39:38 UTC
Verified.


Tested on: Satellite-7.0.0. Snap 12.0


Steps followed: 

1. Sync a docker repository.
2. Register a content host with the satellite and try pulling container content.



Observation: Container content can be pulled with the presence of the foreman_azure_rm plugin.

Comment 9 errata-xmlrpc 2022-07-05 14:30:33 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.11 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-2022:5498