(In reply to Timothée Ravier from comment #0)
> Update Ignition to latest release and specfile with C9S fixes.
> 
> See https://src.fedoraproject.org/rpms/ignition/pull-request/85.

This PR has been merged.

We need someone from RHEL PM to add a `release+` flag to proceed with this change.

(In reply to RHEL Program Management from comment #3)
> A request has been made to complete this BZ as an exception (that is, after
> the deadline).  To facilitate review, the Product Owner (or a delegate) must
> provide an impact statement.  This is done by clicking the [reply] link on
> this comment, and then replying in-line to this message. 
>  This must be done to facilitate review, even if the case appears to be
> obvious, or is already covered elsewhere in the BZ. The exception will not
> be reviewed until this is done.
> 
> ======= Impact Statement ======= 
> 
> What is the benefit of making this change after the deadline? What is the
> impact on customer satisfaction, and on the business?

This is critical to the effort of RHCOS/OCP to be able to consume RHEL 9 content. Although it should not affect the RHEL 9 customers, it would impact the ability of OCP/RHCOS to directly consume that change.

> What is the risk to the release schedule, quality, and the impact of
> diverting resources from other efforts? Will there be enough time to do the
> necessary large-scale, cross-function, regression, stress, or
> fault-insertion testing that may be required to verify this change? 

We don't anticipate any impact on the release schedule. The testing has already been performed on CoreOS variants of RHEL to verify this change.

Hmm.  I think we can also land this in 9.1 or whatever too though, and until then just use some other place.

But, clearly the flip side is it's just a new package that...well it seems *extremely* unlikely it could somehow break something that isn't CoreOS.

Did a simple install of `ignition` on a RHEL 9 VM and it worked correctly.  Confirmed that it was 2.13.0

Since it was never released as part of RHEL 8 (only for OCP), upgrade testing is not applicable.

Moving this to VERIFIED

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (new packages: ignition), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:2583