Bug 1879273
Summary: | preventing newer RHCOS content from appearing in older z-streams first | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Micah Abbott <miabbott> |
Component: | RHCOS | Assignee: | Micah Abbott <miabbott> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Michael Nguyen <mnguyen> |
Severity: | high | Docs Contact: | |
Priority: | low | ||
Version: | 4.5 | CC: | aos-bugs, bbreard, imcleod, jligon, jokerman, lmeyer, miabbott, mnguyen, nstielau, sdodson, smilner, vlaad, wking |
Target Milestone: | --- | Keywords: | UpcomingSprint |
Target Release: | 4.8.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | No Doc Update | |
Doc Text: | Story Points: | --- | |
Clone Of: | 1879260 | Environment: | |
Last Closed: | 2021-01-26 22:18:58 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1879260 | ||
Bug Blocks: |
Description
Micah Abbott
2020-09-15 19:58:12 UTC
The root cause appears to be the timing of when the z-stream release payloads were created. Release 4.5.9 was created from registry.svc.ci.openshift.org/ocp/release:4.5.0-0.nightly-2020-09-07-062006 Release 4.4.21 was created from registry.svc.ci.openshift.org/ocp/release:4.4.0-0.nightly-2020-09-09-153044 RHEL 8.2 batch 3 content was released on September 8. Since all supported/released RHCOS streams are built from the same RHEL repo, when the repo content is detected as changed, all the RHCOS versions should be built around the same time. In this case, the 4.5.9 release (created Sep 7) used RHCOS 45.82.202009040230-0 (built on Sep 4). When the 4.4.21 release was created (Sep 9), the RHCOS used was 44.82.202009091324-0 (built on Sep 9). What happened in between the creation of the two release payloads was the release of the RHEL 8.2 batch content on Sep 8. This means that all the RHCOS versions were updated on that day; see below for the 4.3, 4.4, and 4.5 builds that correspond to this content change: https://releases-rhcos-art.cloud.privileged.psi.redhat.com/?stream=releases/rhcos-4.3&release=43.82.202009080953.0#43.82.202009080953.0 https://releases-rhcos-art.cloud.privileged.psi.redhat.com/?stream=releases/rhcos-4.4&release=44.82.202009080930-0#44.82.202009080930-0 https://releases-rhcos-art.cloud.privileged.psi.redhat.com/?stream=releases/rhcos-4.5&release=45.82.202009081029-0#45.82.202009081029-0 What did *not* happen was an updated release for 4.5.z, so we end up with the older version (4.4.21) with newer RHEL content. Some suggestions that were made for addressing this: - pause the RHCOS build pipelines when ART does their first z-stream release of the week until the final z-stream is created - pause the machine-os-content promote job when ART does their first z-stream release of the week until the final z-stream is created (I tend to favor the latter, as the RHCOS build pipeline could still do basic sanity testing via qemu and wouldn't be blind to changes for a few days) Higher priority work has prevented action on this; setting UpcomingSprint Higher priority work has prevented this issue from being solved; adding the UpcomingSprint keyword |