Project

General

Profile

Tracker #8176

Errata Management Incremental Updates

Added by Walden Raines almost 6 years ago. Updated about 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Errata Management
Target version:
% Done:

0%

Difficulty:
Triaged:
Yes
Bugzilla link:
Fixed in Releases:
Found in Releases:

Description

As a user I would like to get an emergency errata out to systems as quickly as possible.


Related issues

Blocked by Katello - Feature #8000: Design: as a user I would like to get an emergency errata out to systems as quickly as possibleClosed2014-10-20
Blocked by Katello - Feature #8177: API for select multiple errata, and 'apply them' to multiple content views in multiple environmentsResolved2014-10-29
Blocked by Katello - Feature #8178: UI for select multiple errata, and 'apply them' to multiple content views in multiple environmentsClosed2014-10-29
Blocked by Katello - Feature #8179: CLI for select multiple errata, and 'apply them' to multiple content views in multiple environmentsClosed2014-10-29
Blocked by Katello - Feature #8180: As a user, I would expect errata that are added to a new point release to use dependency resolution to ensure needed dependencies are addedClosed2014-10-29
Blocked by Katello - Feature #8188: API for querying a subset of environments or content views to push new errata to.Closed2014-10-29
Blocked by Katello - Feature #8189: UI for viewing applicable environments or content views an errata applies toClosed2014-10-29
Blocked by Katello - Feature #8190: CLI for viewing applicable environments or content views an errata applies toClosed2014-10-29
Blocked by Katello - Feature #8191: API for initiating an update on all affected systems after applying new errata to content views/environmentsClosed2014-10-29
Blocked by Katello - Feature #8192: UI: support option for initiating and update on all affected systems when performing an updateClosed2014-10-29
Blocked by Katello - Feature #8193: CLI: support option for initiating and update on all affected systems when performing an updateClosed2014-10-29
Blocked by Katello - Feature #8194: Update composite content views and environments with new point releasesClosed2014-10-29
Blocked by Katello - Feature #8249: API for remote action historyClosed2014-11-03
Blocked by Katello - Feature #8251: As a user, i should be able to see what was added as part of an incremental errata updateClosed2014-11-03
Blocked by Katello - Feature #8306: API for selecting multiple *packages*, and 'apply them' to multiple content views in multiple environments.Closed2014-11-06
Blocked by Katello - Feature #8972: Support incremental update via hammerClosed2015-01-15
Blocked by Katello - Bug #9051: systems controller index should handle multiple errata_idsClosed2015-01-20
Blocked by Katello - Bug #9120: better feedback around composites and incremental updatesClosed2015-01-26
Blocked by Katello - Feature #9166: Indicate to the user that an incremental update is in progress (UI)Closed2015-01-29
Blocked by Katello - Feature #9176: Incremental update: show resulting update task in details pane Closed2015-01-30
Blocked by Katello - Bug #9220: apply errata confirm button does not disable when click, nor handle errorsClosed2015-02-04
Blocked by Katello - Bug #9219: cancel button on errata apply does not work properlyClosed2015-02-04
Blocked by Katello - Feature #9223: Indicate to the user that an incremental update is in progress (API)Closed2015-01-29
Blocked by Katello - Bug #9298: errata apply with inc update includes full system info and sends even without checking 'apply to content hosts'Closed2015-02-09
Blocked by Katello - Bug #9309: Monitor > Tasks page throws "Not Implemented error" after an incremental update (with system errata apply)Closed2015-02-10

History

#1 Updated by Walden Raines almost 6 years ago

  • Related to Feature #8000: Design: as a user I would like to get an emergency errata out to systems as quickly as possible added

#2 Updated by Walden Raines almost 6 years ago

  • Related to deleted (Feature #8000: Design: as a user I would like to get an emergency errata out to systems as quickly as possible)

#3 Updated by Walden Raines almost 6 years ago

  • Blocked by Feature #8000: Design: as a user I would like to get an emergency errata out to systems as quickly as possible added

#4 Updated by Walden Raines almost 6 years ago

  • Related to Feature #8177: API for select multiple errata, and 'apply them' to multiple content views in multiple environments added

#5 Updated by Walden Raines almost 6 years ago

  • Related to deleted (Feature #8177: API for select multiple errata, and 'apply them' to multiple content views in multiple environments)

#6 Updated by Walden Raines almost 6 years ago

  • Blocked by Feature #8177: API for select multiple errata, and 'apply them' to multiple content views in multiple environments added

#7 Updated by Walden Raines almost 6 years ago

  • Blocked by Feature #8178: UI for select multiple errata, and 'apply them' to multiple content views in multiple environments added

#8 Updated by Walden Raines almost 6 years ago

  • Blocked by Feature #8179: CLI for select multiple errata, and 'apply them' to multiple content views in multiple environments added

#9 Updated by Walden Raines almost 6 years ago

  • Blocked by Feature #8180: As a user, I would expect errata that are added to a new point release to use dependency resolution to ensure needed dependencies are added added

#13 Updated by Walden Raines almost 6 years ago

  • Blocked by Feature #8186: UI for selecting multiple *packages*, and 'apply them' to multiple content views in multiple environments. added

#14 Updated by Walden Raines almost 6 years ago

  • Blocked by Feature #8187: CLI for selecting multiple *packages*, and 'apply them' to multiple content views in multiple environments. added

#15 Updated by Walden Raines almost 6 years ago

  • Blocked by Feature #8188: API for querying a subset of environments or content views to push new errata to. added

#16 Updated by Walden Raines almost 6 years ago

  • Blocked by Feature #8189: UI for viewing applicable environments or content views an errata applies to added

#17 Updated by Walden Raines almost 6 years ago

  • Blocked by Feature #8190: CLI for viewing applicable environments or content views an errata applies to added

#18 Updated by Walden Raines almost 6 years ago

  • Blocked by Feature #8191: API for initiating an update on all affected systems after applying new errata to content views/environments added

#19 Updated by Walden Raines almost 6 years ago

  • Blocked by Feature #8192: UI: support option for initiating and update on all affected systems when performing an update added

#20 Updated by Walden Raines almost 6 years ago

  • Blocked by Feature #8193: CLI: support option for initiating and update on all affected systems when performing an update added

#21 Updated by Walden Raines almost 6 years ago

  • Blocked by Feature #8194: Update composite content views and environments with new point releases added

#22 Updated by Walden Raines almost 6 years ago

  • Blocked by Feature #8195: Repoclosure should optionally be run at some point during the process to tell me if there is a dependency issue, either afterwards or as part of the process halting the push to an environment added

#23 Updated by Walden Raines almost 6 years ago

  • Subject changed from Emergency Errata to Errata Management Incremental Updates

#24 Updated by Walden Raines almost 6 years ago

#25 Updated by Walden Raines almost 6 years ago

  • Related to Feature #8251: As a user, i should be able to see what was added as part of an incremental errata update added

#26 Updated by Walden Raines almost 6 years ago

  • Related to deleted (Feature #8251: As a user, i should be able to see what was added as part of an incremental errata update)

#27 Updated by Walden Raines almost 6 years ago

  • Blocked by Feature #8251: As a user, i should be able to see what was added as part of an incremental errata update added

#28 Updated by Walden Raines almost 6 years ago

  • Blocked by deleted (Feature #8195: Repoclosure should optionally be run at some point during the process to tell me if there is a dependency issue, either afterwards or as part of the process halting the push to an environment)

#29 Updated by Walden Raines almost 6 years ago

  • Related to Feature #8195: Repoclosure should optionally be run at some point during the process to tell me if there is a dependency issue, either afterwards or as part of the process halting the push to an environment added

#30 Updated by Walden Raines almost 6 years ago

  • Blocked by Feature #8306: API for selecting multiple *packages*, and 'apply them' to multiple content views in multiple environments. added

#31 Updated by Justin Sherrill over 5 years ago

  • Related to Feature #8645: add incremental update to bats testing added

#32 Updated by Walden Raines over 5 years ago

  • Blocked by deleted (Feature #8187: CLI for selecting multiple *packages*, and 'apply them' to multiple content views in multiple environments.)

#33 Updated by Walden Raines over 5 years ago

  • Blocked by deleted (Feature #8186: UI for selecting multiple *packages*, and 'apply them' to multiple content views in multiple environments.)

#34 Updated by Eric Helms over 5 years ago

  • Target version changed from 62 to 63

#35 Updated by Justin Sherrill over 5 years ago

  • Blocked by Feature #8972: Support incremental update via hammer added

#36 Updated by Justin Sherrill over 5 years ago

  • Blocked by Bug #9051: systems controller index should handle multiple errata_ids added

#37 Updated by Eric Helms over 5 years ago

  • Target version deleted (63)

#38 Updated by Justin Sherrill over 5 years ago

  • Blocked by Bug #9120: better feedback around composites and incremental updates added

#39 Updated by Walden Raines over 5 years ago

  • Related to Feature #9166: Indicate to the user that an incremental update is in progress (UI) added

#40 Updated by Walden Raines over 5 years ago

  • Related to deleted (Feature #9166: Indicate to the user that an incremental update is in progress (UI))

#41 Updated by Walden Raines over 5 years ago

  • Blocked by Feature #9166: Indicate to the user that an incremental update is in progress (UI) added

#42 Updated by Walden Raines over 5 years ago

  • Blocked by Feature #9176: Incremental update: show resulting update task in details pane added

#43 Updated by Justin Sherrill over 5 years ago

  • Blocked by Bug #9220: apply errata confirm button does not disable when click, nor handle errors added

#44 Updated by Justin Sherrill over 5 years ago

  • Blocked by Bug #9219: cancel button on errata apply does not work properly added

#45 Updated by Walden Raines over 5 years ago

  • Blocked by Feature #9223: Indicate to the user that an incremental update is in progress (API) added

#46 Updated by Justin Sherrill over 5 years ago

  • Blocked by Bug #9298: errata apply with inc update includes full system info and sends even without checking 'apply to content hosts' added

#47 Updated by Justin Sherrill over 5 years ago

  • Blocked by Bug #9309: Monitor > Tasks page throws "Not Implemented error" after an incremental update (with system errata apply) added

#48 Updated by Walden Raines over 5 years ago

  • Related to Feature #9356: Need to better handle sequential incremental updates added

#49 Updated by Walden Raines almost 5 years ago

  • Related to deleted (Feature #8195: Repoclosure should optionally be run at some point during the process to tell me if there is a dependency issue, either afterwards or as part of the process halting the push to an environment)

#50 Updated by Walden Raines almost 5 years ago

  • Related to deleted (Feature #8645: add incremental update to bats testing)

#51 Updated by Walden Raines almost 5 years ago

  • Related to deleted (Feature #9356: Need to better handle sequential incremental updates)

#52 Updated by Walden Raines almost 5 years ago

  • Status changed from New to Closed

Moving remaining tasks to Errata Management Future (http://projects.theforeman.org/issues/8324) and closing.

#53 Updated by Eric Helms over 4 years ago

  • Status changed from Closed to Resolved

#54 Updated by Eric Helms about 4 years ago

  • Legacy Backlogs Release (now unused) set to 166

Also available in: Atom PDF