Skip to content

Conversation

@barbacbd
Copy link
Contributor

Removing SimulatePrincipalPolicy as a required permission for Mint and Passthrough modes. Instead it will be required when a credential mode is not set.

@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Nov 13, 2025
@openshift-ci-robot
Copy link
Contributor

@barbacbd: This pull request references Jira Issue OCPBUGS-63305, which is invalid:

  • expected the bug to target the "4.21.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

Removing SimulatePrincipalPolicy as a required permission for Mint and Passthrough modes. Instead it will be required when a credential mode is not set.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@barbacbd
Copy link
Contributor Author

/cc @tthvo
/cc @patrickdillon

@barbacbd
Copy link
Contributor Author

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Nov 13, 2025
@openshift-ci-robot
Copy link
Contributor

@barbacbd: This pull request references Jira Issue OCPBUGS-63305, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.21.0) matches configured target version for branch (4.21.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @gpei

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

Comment on lines 57 to 61
case "":
reqGroups = append(reqGroups, awsconfig.PermissionEmptyCreds)
default:
// Include permissions needed by CCO/cluster for mint creds mode
reqGroups = append(reqGroups, awsconfig.PermissionMintCreds)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
case "":
reqGroups = append(reqGroups, awsconfig.PermissionEmptyCreds)
default:
// Include permissions needed by CCO/cluster for mint creds mode
reqGroups = append(reqGroups, awsconfig.PermissionMintCreds)
default:
// Include permissions needed by installer and CCO to perform permission checks.
if ic.Config.CredentialsMode == "" {
reqGroups = append(reqGroups, awsconfig.PermissionEmptyCreds)
}
// Include permissions needed by CCO/cluster for mint creds mode
reqGroups = append(reqGroups, awsconfig.PermissionMintCreds)

The empty credentialsMode is basically Mint + SimulatePrincipalPolicy for permission check right?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Otherwise, if when the default credential mode is used, the installer says that only SimulatePrincipalPolicy is required, which is not right?

@tthvo
Copy link
Member

tthvo commented Nov 14, 2025

Looks like have a tiny problem 🤔 related to #10081 (comment). Jobs are failing with:

level=warning msg=Action not allowed with tested creds action=iam:CreateAccessKey
level=warning msg=Action not allowed with tested creds action=iam:CreateUser
level=warning msg=Action not allowed with tested creds action=iam:DeleteUserPolicy
level=warning msg=Action not allowed with tested creds action=iam:GetUserPolicy
level=warning msg=Action not allowed with tested creds action=iam:ListAccessKeys
level=warning msg=Action not allowed with tested creds action=iam:PutUserPolicy
level=warning msg=Action not allowed with tested creds action=iam:TagUser
level=warning msg=Tested creds not able to perform all requested actions
level=warning msg=Action not allowed with tested creds action=s3:PutLifecycleConfiguration
level=warning msg=Action not allowed with tested creds action=s3:ListBucketMultipartUploads
level=warning msg=Action not allowed with tested creds action=s3:AbortMultipartUpload
level=warning msg=Action not allowed with tested creds action=iam:GetUserPolicy
level=warning msg=Action not allowed with tested creds action=iam:ListAccessKeys
level=warning msg=Tested creds not able to perform all requested actions
level=fatal msg=failed to fetch Cluster: failed to fetch dependency of "Cluster": failed to generate asset
"Platform Permissions Check": validate AWS credentials: AWS credentials cannot be used to either create
new creds or use as-is
Installer exit with code 1

Removing SimulatePrincipalPolicy as a required permission for Mint and Passthrough modes.
Instead it will be required when a credential mode is not set.
@barbacbd
Copy link
Contributor Author

/retest-required

@patrickdillon
Copy link
Contributor

/approve

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 14, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: patrickdillon

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 14, 2025
@patrickdillon
Copy link
Contributor

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Nov 14, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 14, 2025

@barbacbd: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/okd-scos-e2e-aws-ovn 991c8a0 link false /test okd-scos-e2e-aws-ovn
ci/prow/e2e-aws-ovn-imdsv2 991c8a0 link false /test e2e-aws-ovn-imdsv2
ci/prow/e2e-aws-byo-subnet-role-security-groups 991c8a0 link false /test e2e-aws-byo-subnet-role-security-groups
ci/prow/e2e-aws-ovn-heterogeneous 991c8a0 link false /test e2e-aws-ovn-heterogeneous

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants