Project

General

Profile

Actions
Copy link

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
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

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 open — 0 closed)

Blocks Katello - Tracker #8324: Errata Management FutureNew

Actions
Actions
Copy link
 #1

Updated by Walden Raines almost 10 years ago

Actions
Copy link
 #2

Updated by Walden Raines almost 10 years ago

  • Related to Tracker #8176: Errata Management Incremental Updates added
Actions
Copy link
 #3

Updated by Eric Helms almost 10 years ago

  • Target version deleted (71)
Actions
Copy link
 #4

Updated by Eric Helms over 9 years ago

  • Triaged changed from No to Yes
Actions
Copy link
 #5

Updated by Walden Raines about 9 years ago

  • Related to deleted (Tracker #8176: Errata Management Incremental Updates)
Actions
Copy link
 #6

Updated by Walden Raines about 9 years ago

Actions
Copy link
 #7

Updated by Walden Raines about 9 years ago

Actions
Copy link
 #8

Updated by Eric Helms almost 9 years ago

  • Translation missing: en.field_release set to 114
Actions
Copy link
 #9

Updated by John Mitsch about 5 years ago

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

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.

Actions
Copy link

Also available in: Atom PDF