Bug 1765614 - Ship updated ostree for s390x support
Summary: Ship updated ostree for s390x support
Keywords:
Status: CLOSED DUPLICATE of bug 1769971
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: RHCOS
Version: 4.3.0
Hardware: s390x
OS: Linux
unspecified
unspecified
Target Milestone: ---
: 4.3.0
Assignee: Micah Abbott
QA Contact: Michael Nguyen
URL:
Whiteboard:
Depends On:
Blocks: OCP/Z_4.2 1769971
TreeView+ depends on / blocked
 
Reported: 2019-10-25 15:12 UTC by Micah Abbott
Modified: 2019-11-07 20:28 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1764703
Environment:
Last Closed: 2019-11-07 20:27:31 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Micah Abbott 2019-10-25 15:12:18 UTC
+++ This bug was initially created as a clone of Bug #1764703 +++

Ship a newer ostree in 4.2.z to enable s390x.

So far, we haven't really had a formal process for shipping host updates on z streams.  Basically we don't do any new builds for "CoreOS parts" (ignition, ostree) and just take base RHEL updates which is mostly security.

Let's use this bug to track signoff for shipping a new ostree in 4.2.z to enable s390x.

A lot of patches went in; it'd be possible to backport but in practice ostree has only merged quite safe changes, we have CI etc.  I think it's better from a testing standpoint to ship a new upstream release.

--- Additional comment from Micah Abbott on 2019-10-23 18:27:35 UTC ---

https://jira.coreos.com/browse/GRPA-1148

--- Additional comment from Eric Paris on 2019-10-24 18:52:15 UTC ---

This bug sets Target Release equal to a z-stream but has no bug in the 'Depends On' field. As such this is not a valid bug state and the target release is being unset.

Any bug targeting 4.1.z must have a bug targeting 4.2 in 'Depends On.'
Similarly, any bug targeting 4.2.z must have a bug with Target Release of 4.3 in 'Depends On.'

Comment 1 Micah Abbott 2019-11-07 20:27:31 UTC
Oops, duplicated this in 1769971

*** This bug has been marked as a duplicate of bug 1769971 ***


Note You need to log in before you can comment on or make changes to this bug.