Bug 1494445 - Incremental update specified for composite X version Y, but no components updated
Summary: Incremental update specified for composite X version Y, but no components upd...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Errata Management
Version: 6.2.11
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-09-22 09:33 UTC by Lukas Zapletal
Modified: 2021-12-10 15:17 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-11-01 10:23:30 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Lukas Zapletal 2017-09-22 09:33:39 UTC
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.

Comment 2 Brad Buckingham 2017-10-04 20:36:14 UTC
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)

Comment 3 Brad Buckingham 2017-10-06 12:33:36 UTC
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

Comment 5 Lukas Zapletal 2017-11-01 10:23:30 UTC
I am not able to reproduce on

satellite-6.2.10-4.0.el7sat.noarch

Comment 6 kechoi 2019-01-24 19:17:34 UTC
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.


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