Bug 1904227

Summary: Docker repo sync probelms with 6.7.5 due to python-nectar is not upgraded properly from 6.6 -> 6.7
Product: Red Hat Satellite Reporter: James Jeffers <jjeffers>
Component: PulpAssignee: Evgeni Golov <egolov>
Status: CLOSED ERRATA QA Contact: Lai <ltran>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.7.0CC: aganbat, dhjoshi, jjeffers, mjia, mmccune, saydas, smajumda, vcojot
Target Milestone: 6.8.2Keywords: Regression, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-nectar-1.6.3 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1893561 Environment:
Last Closed: 2020-12-15 13:15:26 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Comment 1 Lai 2020-12-08 18:39:51 UTC
Steps to Test:
 
1. Create the custom product with custom docker repo

Basic Information

Name
    docker
Label
    docker
Description
Backend Identifier
    9e5eacfa-007f-4047-967f-d5769998ebcd
Type
    docker

Sync Settings

Registry URL
    https://registry.redhat.io
Upstream Repository Name
    amq7/amq-streams-bridge-rhel7
Verify SSL
    Yes
Upstream Authorization
    ***** / ********
HTTP Proxy
    Global Default (None)
Publish via HTTPS
    Yes
Publish via HTTP
    Yes
Published At
    <sat server name>
SSL CA Cert
SSL Client Cert
SSL Client Key
Limit Sync Tags

3. sync 

Expected:
Sync successfully

Actual:
Sync successfully

Verified that nectar is python-nectar python-nectar-1.6.4-1.el7sat.noarch
Verified that /var/log/messages shows no error

Verified on 6.8.2 snap 3

Comment 6 errata-xmlrpc 2020-12-15 13:15:26 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.8.2 Async Bug Fix 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-2020:5467

Comment 7 Brad Buckingham 2021-04-20 12:59:16 UTC
*** Bug 1893561 has been marked as a duplicate of this bug. ***