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.
1) Sync 7Server repo and some product
2) Create a COMPOSITE CV with RHEL repo above and the product.
3) Create RPM include filter named Base_Rpm and check "Include all RPMs with no errata."
4) Create Errata (Date and Type) include filter named Errata_To, check all errata types and set End Date to 03-August-2017
5) Publish CV
6) Install RHEL 7.0 client (no updates), register and attach to the CV
Now try incremental errata update:
1) Content - Errata - select the RHEL7 repository
2) Click on Applicable
3) Search for "type = security"
4) Search and select all
5) Click Apply
6) Do not check "Apply Errata to all host"
7) Confirm
The customer is getting:
Incremental update specified for composite %{name} version %{version}, but no components updated.
On Satellite 6.3 environment with:
satellite-6.3.0-19.0.beta.el7sat.noarch
tfm-rubygem-katello-3.4.5.1-1.el7sat.noarch
I do not see the option to "Apply Errata to all host" as described. With that workflow,
- user sees "Apply to Content Hosts"
- selects 1 or more hosts
- clicks 'Next', which is disabled until they select at least one host
(NOTE: will be trying this on 6.2 as well; however, wanted to add note to BZ while it is fresh)
I have been unable to reproduce this issue on either Satellite 6.2.12 or 6.3. Do we have an internal reproducer? Is there something that I am missing in the scenario below?
On both releases, scenario was:
1) Go to Content -> Errata - select the RHEL7 repository
2) Click on Applicable
3) Search for "type = security"
4) Search and select all
5) Click Apply
6) Select one or more hosts
7) Click Next
8) Do not check "Apply Errata to all host"
8) Click Confirm
I have reproduced this on satellite-6.3.5-1.el7sat.noarch
To reproduce, one of the other hosts must be using a content view that has not yet been updated with the errata, but is part of the composite view that requires updating.
1) Sync 7Server repo and some product 2) Create a COMPOSITE CV with RHEL repo above and the product. 3) Create RPM include filter named Base_Rpm and check "Include all RPMs with no errata." 4) Create Errata (Date and Type) include filter named Errata_To, check all errata types and set End Date to 03-August-2017 5) Publish CV 6) Install RHEL 7.0 client (no updates), register and attach to the CV Now try incremental errata update: 1) Content - Errata - select the RHEL7 repository 2) Click on Applicable 3) Search for "type = security" 4) Search and select all 5) Click Apply 6) Do not check "Apply Errata to all host" 7) Confirm The customer is getting: Incremental update specified for composite %{name} version %{version}, but no components updated.