Bug 2055391 - After upgrade products with repositories that had Ignorable Content = drpm can no longer be modified
Summary: After upgrade products with repositories that had Ignorable Content = drpm ca...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Repositories
Version: 6.10.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 6.12.0
Assignee: Samir Jha
QA Contact: Cole Higgins
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-16 20:02 UTC by Justin Sherrill
Modified: 2022-11-16 13:33 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-11-16 13:33:27 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 34432 0 Normal Closed After upgrade products with repositories that had Ignorable Content = drpm can no longer be modified 2022-03-02 17:30:07 UTC
Red Hat Issue Tracker SAT-8435 0 None None None 2022-10-21 15:35:10 UTC
Red Hat Product Errata RHSA-2022:8506 0 None None None 2022-11-16 13:33:37 UTC

Description Justin Sherrill 2022-02-16 20:02:29 UTC
Steps to Reproduce:
1. install foreman 2.3 / katello 3.18 with pulp2
2. create yum repository with ignorable content = drpm
3. upgrade to foreman 2.5 / katello 4.1 with migration to pulp3
4. try to modify the product / repository

Result:
The modification fails with error:
An error occurred saving the Product: Invalid value specified for ignorable content. Permissible values srpm

It appears that drpm is no longer a vailid value for ignorable content (#32658), but the value is not removed during migration

<pre><code class="text">
# hammer repository info --product-id 208 --name "SLES Client 12SP5 ARM" --organization Test
Id:                      1891
Name:                    SLES Client 12SP5 ARM
Label:                   SLES_Client_12SP5_ARM
Description:             
Organisation:            Test
Red Hat Repository:      no
Content Type:            yum
Mirror on Sync:          yes
Url:                     […]
Publish Via HTTP:        yes
Published At:            https://or.supp205.mk/pulp/content/639827e8-06a2-4445-b3cc-293403d48e79/Library/custom/SLES_Client_ARM/SLES_Client_12SP5_ARM/
Relative Path:           639827e8-06a2-4445-b3cc-293403d48e79/Library/custom/SLES_Client_ARM/SLES_Client_12SP5_ARM
Download Policy:         immediate
Ignorable Content Units: drpm, srpm
HTTP Proxy:              
    Id:                1
    Name:              default
    HTTP Proxy Policy: global_default_http_proxy
Product:                 
    Id:   208
    Name: SLES Client ARM64
GPG Key:                 Sync:                    
    Status:         Success
    Last Sync Date: about 1 hour
Created:                 2021/10/18 09:35:17
Updated:                 2021/11/22 11:15:59
Content Counts:          
    Packages:       9
    Source RPMS:    0
    Package Groups: 0
    Errata:         0
    Module Streams: 0

</code></pre>

Comment 1 Justin Sherrill 2022-02-16 20:02:33 UTC
Created from redmine issue https://projects.theforeman.org/issues/34432

Comment 2 Justin Sherrill 2022-02-16 20:02:34 UTC
Upstream bug assigned to None

Comment 3 Justin Sherrill 2022-02-16 20:17:16 UTC
we should handle this on upgrade to 6.10 as part of 6.10 db migrations

Comment 4 Bryan Kearney 2022-03-02 16:05:44 UTC
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/34432 has been resolved.

Comment 10 errata-xmlrpc 2022-11-16 13:33:27 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 (Important: Satellite 6.12 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:8506


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