Project

General

Profile

Feature #9356

Need to better handle sequential incremental updates

Added by Walden Raines over 4 years ago. Updated about 2 months ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Errata Management
Target version:
-
Difficulty:
medium
Triaged:
Yes
Bugzilla link:
Pull request:
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

Blocks Katello - Tracker #8324: Errata Management FutureNew

History

#1 Updated by Walden Raines over 4 years ago

#2 Updated by Walden Raines over 4 years ago

  • Related to Tracker #8176: Errata Management Incremental Updates added

#3 Updated by Eric Helms over 4 years ago

  • Target version deleted (71)

#4 Updated by Eric Helms over 4 years ago

  • Triaged changed from No to Yes

#5 Updated by Walden Raines about 4 years ago

  • Related to deleted (Tracker #8176: Errata Management Incremental Updates)

#6 Updated by Walden Raines about 4 years ago

#7 Updated by Walden Raines about 4 years ago

#8 Updated by Eric Helms almost 4 years ago

  • Legacy Backlogs Release (now unused) set to 114

#9 Updated by John Mitsch about 2 months ago

  • Target version deleted (Katello Backlog)
  • Status changed from New to Rejected

Thanks for reporting this issue. This issue was created over 4 years ago and hasn't seen an update in 1 year. We are closing this in an effort to keep a realistic backlog. Please open up a new issue that includes a link to this issue if you feel this still needs to be addressed. We can then triage the new issue and reassess.

Also available in: Atom PDF