Project

General

Profile

Bug #21491

incremental update via UI never creates an incremental update

Added by Justin Sherrill over 4 years ago. Updated almost 4 years ago.

Status:
Closed
Priority:
Normal
Category:
Content Views
Target version:
Difficulty:
Triaged:
Bugzilla link:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1506846

Description of problem:

While trying to test out this bz: https://bugzilla.redhat.com/show_bug.cgi?id=1489778 i discovered that incremental update via the UI is broken

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

tfm-rubygem-katello-3.4.5.16-1.el7sat.noarch

How reproducible:
always

Steps to Reproduce:
1. Setup an environment where some system is assigned to a content view, but has some errata applicable that has been filtered out of that content view
2. Go to Errata
3. Select at least one applicable errata
4. SElect apply errata
5. Select at least one applicable host
6. Notice that it shows that an incremental update of the cv will be performed
7. Click confirm

Actual results:

No incremental update is performed, errata is attempted to be applied to the host

Expected results:
incremental update is performed

Additional info:

Associated revisions

Revision 93e7a4e3 (diff)
Added by Justin Sherrill over 4 years ago

Fixes #21491 - properly detect if inc update is needed

A change was made in 0c6a18c that changed this logic
to make the decision of whether to apply this errata to the
host directly or perform an incremental update to base it on
whether an inc update is already in progress. This does not
make any sense, as it should be based on whether the errata
is in the hosts' environments

History

#1 Updated by The Foreman Bot over 4 years ago

  • Assignee set to Justin Sherrill
  • Status changed from New to Ready For Testing
  • Pull request https://github.com/Katello/katello/pull/7041 added

#2 Updated by Brad Buckingham over 4 years ago

  • Target version set to 225

#3 Updated by Justin Sherrill over 4 years ago

  • % Done changed from 0 to 100
  • Status changed from Ready For Testing to Closed

#4 Updated by Justin Sherrill over 4 years ago

  • Legacy Backlogs Release (now unused) set to 295

Also available in: Atom PDF