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.
Steps to retest:
1. Sync rhel8 - BaseOS and rhel8 - AppStream
2. Create a cv and add the repos from step #1
3. Create a filter that includes an erratum with an end date of sept. 1, 2020
4. Publish the cv
5. Remove the filter and republish the cv
6. Drill into the 2nd cv version and click on errata tab
7. Filter by updated column so that the latest dates are first
8. Pick a errata from the list to run (I picked RHSA-2021:0471)
9. Run the incremental update command:
hammer content-view version incremental-update --content-view-version-id=<id> --errata-ids=<errata ID>
Expected:
Incremental update should be faster than previously before.
There should be only one "Actions::Pulp::Repository::CopyUnits" in the dynflow console.
Actual:
Incremental update is faster than previously before. On a 6.8.4 sat, the incremental update took 22 minutes while on a 6.7.4 sat took 38 minutes. There is a 15 minutes faster difference from that errata.
There is only one "Actions::Pulp::Repository::CopyUnits" in the dynflow console.
Verified on 6.8.4_01, pulp-rpm-plugins-2.21.3.3-1.el7sat.noarch, tfm-rubygem-katello-3.16.0.20-1.el7sat.noarch
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.4 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-2021:0654
Steps to retest: 1. Sync rhel8 - BaseOS and rhel8 - AppStream 2. Create a cv and add the repos from step #1 3. Create a filter that includes an erratum with an end date of sept. 1, 2020 4. Publish the cv 5. Remove the filter and republish the cv 6. Drill into the 2nd cv version and click on errata tab 7. Filter by updated column so that the latest dates are first 8. Pick a errata from the list to run (I picked RHSA-2021:0471) 9. Run the incremental update command: hammer content-view version incremental-update --content-view-version-id=<id> --errata-ids=<errata ID> Expected: Incremental update should be faster than previously before. There should be only one "Actions::Pulp::Repository::CopyUnits" in the dynflow console. Actual: Incremental update is faster than previously before. On a 6.8.4 sat, the incremental update took 22 minutes while on a 6.7.4 sat took 38 minutes. There is a 15 minutes faster difference from that errata. There is only one "Actions::Pulp::Repository::CopyUnits" in the dynflow console. Verified on 6.8.4_01, pulp-rpm-plugins-2.21.3.3-1.el7sat.noarch, tfm-rubygem-katello-3.16.0.20-1.el7sat.noarch