This is a clone of issue OCPBUGS-34708. The following is the description of the original issue:
—
Description of problem:
failed job: https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_cluster-ingress-operator/1023/pull-ci-openshift-cluster-ingress-operator-master-e2e-aws-gatewayapi/1796261717831847936 seeing below error: level=error msg=failed to fetch Cluster: failed to generate asset "Cluster": failed to create cluster: error unpacking terraform: could not unpack the directory for the aws provider: open mirror/openshift/local/aws: file does not exist
Version-Release number of selected component (if applicable):
4.16/4.17
How reproducible:
100%
Steps to Reproduce:
1. create AWS cluster with "CustomNoUpgrade" featureSet is configured install-config.yaml ---------------------- featureSet: CustomNoUpgrade featureGates: [GatewayAPIEnabled=true] 2.
Actual results:
level=error msg=failed to fetch Cluster: failed to generate asset "Cluster": failed to create cluster: error unpacking terraform: could not unpack the directory for the aws provider: open mirror/openshift/local/aws: file does not exist
Expected results:
install should be successful
Additional info:
workaround is to add ClusterAPIInstallAWS=true to feature_gates as well, .e.g featureSet: CustomNoUpgrade featureGates: [GatewayAPIEnabled=true,ClusterAPIInstallAWS=true]
discussion thread: https://redhat-internal.slack.com/archives/C68TNFWA2/p1716887301410459
- clones
-
OCPBUGS-34708 [AWS] install failed with featureSet CustomNoUpgrade is configured
- Closed
- is blocked by
-
OCPBUGS-34708 [AWS] install failed with featureSet CustomNoUpgrade is configured
- Closed
- links to
-
RHBA-2024:4613 OpenShift Container Platform 4.16.z bug fix update