-
Bug
-
Resolution: Won't Do
-
Undefined
-
None
-
4.14.z
Description of problem:
We should not require the s3:DeleteObject permission for installs when the `preserveBootstrapIgnition` option is set in the install-config.
Version-Release number of selected component (if applicable):
4.14+
How reproducible:
always
Steps to Reproduce:
1. Use an account without the permission 2. Set `preserveBootstrapIgnition: true` in the install-config.yaml 3. Try to deploy a cluster
Actual results:
INFO Credentials loaded from the "denys3" profile in file "/home/cloud-user/.aws/credentials" INFO Consuming Install Config from target directory WARNING Action not allowed with tested creds action=s3:DeleteBucket WARNING Action not allowed with tested creds action=s3:DeleteObject WARNING Action not allowed with tested creds action=s3:DeleteObject WARNING Tested creds not able to perform all requested actions FATAL failed to fetch Cluster: failed to fetch dependency of "Cluster": failed to generate asset "Platform Permissions Check": validate AWS credentials: current credentials insufficient for performing cluster installation
Expected results:
No permission errors.
Additional info:
- blocks
-
OCPBUGS-33509 [AWS CAPI install] "platform.aws.preserveBootstrapIgnition: true" does not work.
- Closed
-
OCPBUGS-35044 aws: do not require s3:Delete* perms if `preserveBootstrapIgnition` is set
- Closed
- is cloned by
-
OCPBUGS-35044 aws: do not require s3:Delete* perms if `preserveBootstrapIgnition` is set
- Closed
- is related to
-
CORS-2890 Provision AWS with CAPI (no mgmt cluster)
- Testing
-
OCPBUGS-26016 [enterprise-4.14] Issue in file installing/installing_aws/installing-aws-user-infra.adoc
- Closed
- links to