Bug 2065483 - AWS io2 machine fails due to no iops despite it being configured
Summary: AWS io2 machine fails due to no iops despite it being configured
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cloud Compute
Version: 4.9
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.9.z
Assignee: Joel Speed
QA Contact: Huali Liu
Depends On: 2040504
Blocks: 2066675
TreeView+ depends on / blocked
Reported: 2022-03-18 00:09 UTC by Justin Pierce
Modified: 2022-04-11 08:33 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2022-03-29 07:16:24 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift cluster-api-provider-aws pull 436 0 None open Bug 2065483: Ensure IOPS setting is honoured on all supported block device types 2022-03-18 11:41:23 UTC
Red Hat Product Errata RHBA-2022:1022 0 None None None 2022-03-29 07:16:39 UTC

Comment 8 errata-xmlrpc 2022-03-29 07:16:24 UTC
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 (OpenShift Container Platform 4.9.26 bug fix update), and where to find the updated
files, follow the link below.

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


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