Bug 2075459 - Set up cluster on aws with rootvolumn io2 failed due to no iops despite it being configured
Summary: Set up cluster on aws with rootvolumn io2 failed due to no iops despite it be...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 4.11
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.11.0
Assignee: Brent Barbachem
QA Contact: Yunfei Jiang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-04-14 09:40 UTC by sunzhaohua
Modified: 2022-08-10 11:07 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-08-10 11:07:06 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift installer pull 5925 0 None open BUG 2075459: IOPS was not being set even when manually configured 2022-05-17 20:05:01 UTC
Red Hat Product Errata RHSA-2022:5069 0 None None None 2022-08-10 11:07:24 UTC

Description sunzhaohua 2022-04-14 09:40:59 UTC
Description of problem:
Set up cluster on aws with io2 storage. Installation fails with:
04-14 16:05:50.380  level=error msg=Error: Error launching source instance: InvalidParameterCombination: The parameter iops must be specified for io2 volumes.
04-14 16:05:50.380  level=error msg=  status code: 400, request id: cf6c0820-5cd3-4a77-ac67-09632d31f818

However, iops are specified in the install-config.


Version-Release number of selected component (if applicable):
4.11.0-0.nightly-2022-04-14-040125

How reproducible:
100%


Steps to Reproduce:
1. ./openshift-install create install-config --dir test
2. Specify io2 storage
3. Specify volume size 100
4. Specify iops: 3000
5. ./openshift-install create cluster --dir test

Actual results:
Installation fails due to 'error launching instance: The parameter iops must be specified for io2 volumes.'

install-config.yaml:
---
apiVersion: v1
controlPlane:
  architecture: amd64
  hyperthreading: Enabled
  name: master
  platform:
    aws:
      rootVolume:
        type: io2
        iops: 3000
        size: 100
  replicas: 3
compute:
- architecture: amd64
  hyperthreading: Enabled
   name: worker
  platform:
    aws:
      rootVolume:
        type: io2
        iops: 3000
        size: 100
  replicas: 3

Expected results:
Installation success.

Additional info:
Similar bug for machineapi: https://bugzilla.redhat.com/show_bug.cgi?id=2065483

Comment 1 sunzhaohua 2022-04-14 10:20:48 UTC
Set up cluster with gp3 storage and set iops and size. Installation success but master iops is reset to 3000.
https://mastern-jenkins-csb-openshift-qe.apps.ocp-c1.prod.psi.redhat.com/job/ocp-common/job/Flexy-install/94183/consoleFull

install-config.yaml:
---
apiVersion: v1
controlPlane:
  architecture: amd64
  hyperthreading: Enabled
  name: master
  platform:
    aws:
      rootVolume:
        type: gp3
        iops: 5000
        size: 100
  replicas: 3
compute:
- architecture: amd64
  hyperthreading: Enabled
   name: worker
  platform:
    aws:
      rootVolume:
        type: gp3
        iops: 5000
        size: 100
  replicas: 3

Comment 3 Patrick Dillon 2022-05-15 20:38:11 UTC
It looks like now that we have updated the aws provider, we need to revisit the decisions in this commihttps://github.com/openshift/installer/commit/a8d800111a6107ce90d851e4bd6fc3be84310cad as to how iops are handled

Comment 5 Yunfei Jiang 2022-06-15 07:43:00 UTC
verified. PASS.

OCP version: 4.11.0-0.nightly-2022-06-14-172335

Comment 7 errata-xmlrpc 2022-08-10 11:07:06 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 (Important: OpenShift Container Platform 4.11.0 bug fix and security 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.

https://access.redhat.com/errata/RHSA-2022:5069


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