-
Feature
-
Resolution: Done
-
Critical
-
None
-
BU Product Work
-
False
-
-
False
-
0% To Do, 0% In Progress, 100% Done
-
0
-
Program Call
Feature Overview
OCP 4 clusters still maintain pinned boot images. We have numerous clusters installed that have boot media pinned to first boot images as early as 4.1. In the future these boot images may not be certified by the OEM and may fail to boot on updated datacenter or cloud hardware platforms. These "pinned" boot images should be updateable so that customers can avoid this problem and better still scale out nodes with boot media that matches the running cluster version.
In phase 1 provided tech preview for GCP.
In phase 2, GCP support goes to GA. Support for other IPI footprints is new and tech preview.
Requirements
- clones
-
-
- Closed
-
- is cloned by
-
-
- Closed
-
- links to
[OCPSTRAT-1170] Updated boot images: Phase 2 (GCP GA, AWS TP)
OpenShift Jira Links Copy Bot
made changes -
| Remote Link |
New:
This issue links to "openshift/openshift-tests-private#19762: [release-4.17] |
OpenShift Jira Links Copy Bot
made changes -
| Remote Link |
New:
This issue links to "openshift/openshift-tests-private#18630: |
Margaret Dineen
made changes -
| Status | Original: Release Pending [ 15735 ] | New: Closed [ 6 ] |
| PX Technical Impact Notes | New: This encompasses a major change to the function and support policy of the product. and CEE should be made aware of the details |
| Link |
New:
This issue is cloned by |
| Status | Original: In Progress [ 10018 ] | New: Release Pending [ 15735 ] |
| Summary | Original: Updated boot images: Phase 2 (GCP GA, Other platforms TP) | New: Updated boot images: Phase 2 (GCP GA, AWS TP) |
OpenShift Jira Automation Bot
made changes -
| Work Type | New: BU Product Work [ 40155 ] |
| Fix Version/s | New: openshift-4.17 [ 12408548 ] |
OpenShift Jira Automation Bot
made changes -
| Labels | Original: 4.17-candidate FAC:Green FPC:TODO-Close-ALL-Epics FPC:TODO-DevComplete-Delivery-Epics MCO RHCOS bootc mco | New: 4.17-candidate FAC:Green FPC:TODO-Close-ALL-Epics MCO RHCOS bootc mco |
OpenShift Jira Automation Bot
made changes -
| Labels | Original: 4.17-candidate FAC:Green FPC:TODO-Close-ALL-Epics MCO RHCOS bootc mco | New: 4.17-candidate FAC:Green FPC:TODO-Close-ALL-Epics FPC:TODO-DevComplete-Delivery-Epics MCO RHCOS bootc mco |
OpenShift Jira Automation Bot
made changes -
| Labels | Original: 4.17-candidate FAC:Green MCO RHCOS bootc mco | New: 4.17-candidate FAC:Green FPC:TODO-Close-ALL-Epics MCO RHCOS bootc mco |
| Status | Original: Release Pending [ 15735 ] | New: In Progress [ 10018 ] |
OpenShift Jira Bot
made changes -
| Discussion Needed | New: Program Call [ 27807 ] |
| Resolution | New: Done [ 1 ] | |
| Status | Original: Refinement [ 15021 ] | New: Release Pending [ 15735 ] |
| PX Impact Score | Original: 10045 | New: 72 |
Metrics Hub
made changes -
| Labels | Original: 4.17-candidate MCO RHCOS bootc mco | New: 4.17-candidate FAC:Green MCO RHCOS bootc mco |
| Status | Original: New [ 10016 ] | New: Refinement [ 15021 ] |
| Description |
Original:
h1. Feature Overview
OCP 4 clusters still maintain pinned boot images. We have numerous clusters installed that have boot media pinned to first boot images as early as 4.1. In the future these boot images *may not be certified by the OEM* and *may fail to boot* on updated datacenter or cloud hardware platforms. These "pinned" boot images should be updateable so that customers can avoid this problem and better still scale out nodes with boot media that matches the running cluster version. In phase 1 provided tech preview for GCP. In phase 2, GCP support goes to GA. Support for other IPI footprints is new and tech preview. h2. Requirements * The MCO will migrate the pinned image for machinesets that do not match the expected RHCOS for that OCP y-stream. * Customers can prevent this process by opting out. |
New:
h1. Feature Overview
OCP 4 clusters still maintain pinned boot images. We have numerous clusters installed that have boot media pinned to first boot images as early as 4.1. In the future these boot images *may not be certified by the OEM* and *may fail to boot* on updated datacenter or cloud hardware platforms. These "pinned" boot images should be updateable so that customers can avoid this problem and better still scale out nodes with boot media that matches the running cluster version. In phase 1 provided tech preview for GCP. In phase 2, GCP support goes to GA. Support for other IPI footprints is new and tech preview. h2. Requirements |
| Description |
Original:
h1. Feature Overview
OCP 4 clusters still maintain pinned boot images. We have numerous clusters installed that have boot media pinned to first boot images as early as 4.1. In the future these boot images *may not be certified by the OEM* and *may fail to boot* on updated datacenter or cloud hardware platforms. These "pinned" boot images should be updateable so that customers can avoid this problem and better still scale out nodes with boot media that matches the running cluster version. In phase 1 a tested and documented process was GA'd for any customer to update their boot images in machinesets on an opt-in basis. Phase 2 is intended on migrating all all customers pinned image on an _opt-out_ basis. h2. Requirements * The MCO will migrate the pinned image for machinesets that do not match the expected RHCOS for that OCP y-stream. * Customers can prevent this process by opting out. |
New:
h1. Feature Overview
OCP 4 clusters still maintain pinned boot images. We have numerous clusters installed that have boot media pinned to first boot images as early as 4.1. In the future these boot images *may not be certified by the OEM* and *may fail to boot* on updated datacenter or cloud hardware platforms. These "pinned" boot images should be updateable so that customers can avoid this problem and better still scale out nodes with boot media that matches the running cluster version. In phase 1 provided tech preview for GCP. In phase 2, GCP support goes to GA. Support for other IPI footprints is new and tech preview. h2. Requirements * The MCO will migrate the pinned image for machinesets that do not match the expected RHCOS for that OCP y-stream. * Customers can prevent this process by opting out. |
| Summary | Original: Updated boot images: Phase 2 | New: Updated boot images: Phase 2 (GCP GA, Other platforms TP) |
| Summary | Original: Updated boot images: Phase 2 - Migration | New: Updated boot images: Phase 2 |
| Summary | Original: Updated boot images: Phase 2 | New: Updated boot images: Phase 2 - Migration |
| Labels | Original: MCO RHCOS bootc mco | New: 4.17-candidate MCO RHCOS bootc mco |
| Labels | Original: 4.17-candidate MCO RHCOS bootc mco | New: MCO RHCOS bootc mco |
| Description |
Original:
h1. Feature Overview
OCP 4 clusters still maintain pinned boot images. We have numerous clusters installed that have boot media pinned to first boot images as early as 4.1. In the future these boot images *may not be certified by the OEM* and *may fail to boot* on updated datacenter or cloud hardware platforms. These "pinned" boot images should be updateable so that customers can avoid this problem and better still scale out nodes with boot media that matches the running cluster version. In phase 1 a tested and documented process was GA'd for any customer to update their boot images in machinesets on an opt-in basis. Phase 2 is intended on migrating all all customers pinned image on an _opt-out_ basis. h2. Requirements * MVP: a documented process to update boot images that works on all footprints with machinesets (IPI). * Stretch/Future goal: automated (but opt-in) process. |
New:
h1. Feature Overview
OCP 4 clusters still maintain pinned boot images. We have numerous clusters installed that have boot media pinned to first boot images as early as 4.1. In the future these boot images *may not be certified by the OEM* and *may fail to boot* on updated datacenter or cloud hardware platforms. These "pinned" boot images should be updateable so that customers can avoid this problem and better still scale out nodes with boot media that matches the running cluster version. In phase 1 a tested and documented process was GA'd for any customer to update their boot images in machinesets on an opt-in basis. Phase 2 is intended on migrating all all customers pinned image on an _opt-out_ basis. h2. Requirements * The MCO will migrate the pinned image for machinesets that do not match the expected RHCOS for that OCP y-stream. * Customers can prevent this process by opting out. |
| Description |
Original:
h1. Feature Overview
OCP 4 clusters still maintain pinned boot images. We have numerous clusters installed that have boot media pinned to first boot images as early as 4.1. In the future these boot images *may not be certified by the OEM* and *may fail to boot* on updated datacenter or cloud hardware platforms. These "pinned" boot images should be updateable so that customers can avoid this problem and better still scale out nodes with boot media that matches the running cluster version. h2. Requirements * MVP: a documented process to update boot images that works on all footprints with machinesets (IPI). * Stretch/Future goal: automated (but opt-in) process. |
New:
h1. Feature Overview
OCP 4 clusters still maintain pinned boot images. We have numerous clusters installed that have boot media pinned to first boot images as early as 4.1. In the future these boot images *may not be certified by the OEM* and *may fail to boot* on updated datacenter or cloud hardware platforms. These "pinned" boot images should be updateable so that customers can avoid this problem and better still scale out nodes with boot media that matches the running cluster version. In phase 1 a tested and documented process was GA'd for any customer to update their boot images in machinesets on an opt-in basis. Phase 2 is intended on migrating all all customers pinned image on an _opt-out_ basis. h2. Requirements * MVP: a documented process to update boot images that works on all footprints with machinesets (IPI). * Stretch/Future goal: automated (but opt-in) process. |
| Labels | Original: 4.16-candidate MCO RHCOS bootc mco | New: 4.17-candidate MCO RHCOS bootc mco |
| Link |
New:
This issue clones |
OCP DocsBot
made changes -
| Link | New: This issue is documented by OSDOCS-9578 [ OSDOCS-9578 ] |
Feature Analysis Color: Green
Estimated Completion Date: Post Feature Complete Team Work Remains
Work Remaining: nan