Project

General

Profile

Actions

Feature #9356

closed

Need to better handle sequential incremental updates

Added by Walden Raines almost 10 years ago. Updated about 5 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Errata Management
Target version:
-
Difficulty:
medium
Triaged:
Yes
Fixed in Releases:
Found in Releases:

Description

Currently we block incremental updates at an organization level in the UI. We need to do one of the following instead:

  1. Queue the subsequent incremental update task, and somehow handle any errors or no-ops that arise after the first has completed.
  2. Only show systems that the incremental update can actually be applied to in the system selection step. We'd also want to show a list of systems that cannot be updated and explain why.

Option #2 is likely a lot easier than option #1 and is not blocked on dynFlow supporting queuing (as #1 is).


Related issues 1 (1 open0 closed)

Blocks Katello - Tracker #8324: Errata Management FutureNew

Actions
Actions

Also available in: Atom PDF