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 1978789

Summary: Repo metadata not generated during incremental update with Pulp 3
Product: Red Hat Satellite Reporter: Ian Ballou <iballou>
Component: Content ViewsAssignee: Ian Ballou <iballou>
Status: CLOSED ERRATA QA Contact: Danny Synk <dsynk>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.9.0CC: pcreech
Target Milestone: 6.10.0Keywords: Regression, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: tfm-rubygem-katello-4.0.2 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-11-16 14:12:20 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 2021-07-02 18:09:42 UTC
Description of problem:

After incremental update, the content view repository does not have the new packages hosted via Pulp 3

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


How reproducible: always


Steps to Reproduce:
1. Incrementally add a package to a content view version
2. See that the new packages are not hosted at /pulp/content or /pulp/repos and thus clients cannot download the new packages
3.

Actual results:
Clients cannot download the new packages

Expected results:
Clients can download the new packages

Additional info:

Comment 1 Bryan Kearney 2021-07-02 20:05:17 UTC
Upstream bug assigned to iballou

Comment 2 Bryan Kearney 2021-07-02 20:05:19 UTC
Upstream bug assigned to iballou

Comment 3 Danny Synk 2021-09-16 18:58:45 UTC
Verified on Satellite 6.10, snap 18.

Steps to Test:
1. Synchronize the rhel-7-server-rpms repo and add it to a content view.
2. Create a content filter on the content view with Inclusion Type 'Include' and Content Type `Errata - by Date and Type.' Include all errata types in the filter. Set the Date Type to 'Issued On' and the End Date to 1 May 2021.
3. Publish the content view.
4. Add a single erratum to the content view that was issued after the end date of the content filter rule:

~~~
# hammer erratum list | grep RHSA-2021:3325
617  | RHSA-2021:3325 | security    | Moderate: bind security update                                                   | 2021-08-31 | 2021-08-31
# hammer content-view version incremental-update --content-view-version-id 5 --errata-ids 617
[....................................................................................................................................................] [100%]
Content View: rhel7_incremental_test version 3.2
Added Content:
  Errata:
        RHSA-2021:3325
  Packages:
        bind-9.11.4-26.P2.el7_9.7.x86_64
        bind-chroot-9.11.4-26.P2.el7_9.7.x86_64
        bind-export-libs-9.11.4-26.P2.el7_9.7.i686
        bind-export-libs-9.11.4-26.P2.el7_9.7.x86_64
        bind-libs-9.11.4-26.P2.el7_9.7.i686
        bind-libs-9.11.4-26.P2.el7_9.7.x86_64
        bind-libs-lite-9.11.4-26.P2.el7_9.7.i686
        bind-libs-lite-9.11.4-26.P2.el7_9.7.x86_64
        bind-license-9.11.4-26.P2.el7_9.7.noarch
        bind-pkcs11-9.11.4-26.P2.el7_9.7.x86_64
        bind-pkcs11-libs-9.11.4-26.P2.el7_9.7.i686
        bind-pkcs11-libs-9.11.4-26.P2.el7_9.7.x86_64
        bind-pkcs11-utils-9.11.4-26.P2.el7_9.7.x86_64
        bind-utils-9.11.4-26.P2.el7_9.7.x86_64
~~~

5. Register a RHEL 7 host to Satellite and associate it with the content view created above.
6. Install a package from the erratum added in the incremental update (I installed bind).

Expected Results:
The package version added in the incremental update (bind-9.11.4-26.P2.el7_9.7.x86_64.rpm) is installed along with its dependencies.

Actual Results:
The package version added in the incremental update (bind-9.11.4-26.P2.el7_9.7.x86_64.rpm) is installed along with its dependencies.

Comment 6 errata-xmlrpc 2021-11-16 14:12:20 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