CEPH-83575592: Automate assume-role at multisite.

[viduship]

CEPH-83575592:sts assume-role at multisite.

The flow of the test is as follows:

1. On the primary zone,

• create 2 users, user1 and user2
• Add role caps to the user1, create a role, and attach role policy.

2. Connect to the secondary zone, and perform the below steps

• test sts assume role call on the secondary zone
• perform s3 bucket creation and other operations via the session token generated with assume role call.

Currently with this automation, we saw that the s3 bucket operations fails on the secondary (https://bugzilla.redhat.com/show_bug.cgi?id=2271399)

logs: will fail at bucket creation (expected)
http://magna002.ceph.redhat.com/ceph-qe-logs/vidushi/580/logs_stst_assumerole_ms

[openshift-ci-robot]

@viduship: No Jira issue with key CEPH-83575592 exists in the tracker at https://issues.redhat.com/.
Once a valid jira issue is referenced in the title of this pull request, request a refresh with /jira refresh.

In response to this:

CEPH-83575592:sts assume-role at multisite..

The flow of the test is as follows:

1. On the primary zone,

• create 2 users, user1 and user2
• Add role caps to the user1, create a role, and attach role policy.

2. Connect to the secondary zone, and perform the below steps

• test sts assume role call on the secondary zone
• perform s3 bucket creation and other operations via the session token generated with assume role call.

Currently with this automation, we saw that the s3 bucket operations fails on the secondary (https://bugzilla.redhat.com/show_bug.cgi?id=2271399)

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.

[openshift-ci-robot]

@viduship: No Jira issue with key CEPH-83575592 exists in the tracker at https://issues.redhat.com/.
Once a valid jira issue is referenced in the title of this pull request, request a refresh with /jira refresh.

In response to this:

CEPH-83575592:sts assume-role at multisite..

The flow of the test is as follows:

1. On the primary zone,

• create 2 users, user1 and user2
• Add role caps to the user1, create a role, and attach role policy.

2. Connect to the secondary zone, and perform the below steps

• test sts assume role call on the secondary zone
• perform s3 bucket creation and other operations via the session token generated with assume role call.

Currently with this automation, we saw that the s3 bucket operations fails on the secondary (https://bugzilla.redhat.com/show_bug.cgi?id=2271399)

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.

[openshift-ci-robot]

@viduship: No Jira issue with key CEPH-83575592 exists in the tracker at https://issues.redhat.com/.
Once a valid jira issue is referenced in the title of this pull request, request a refresh with /jira refresh.

In response to this:

CEPH-83575592:sts assume-role at multisite.

The flow of the test is as follows:

1. On the primary zone,

• create 2 users, user1 and user2
• Add role caps to the user1, create a role, and attach role policy.

2. Connect to the secondary zone, and perform the below steps

• test sts assume role call on the secondary zone
• perform s3 bucket creation and other operations via the session token generated with assume role call.

Currently with this automation, we saw that the s3 bucket operations fails on the secondary (https://bugzilla.redhat.com/show_bug.cgi?id=2271399)

logs: will fail at bucket creation (expected)
http://magna002.ceph.redhat.com/ceph-qe-logs/vidushi/580/logs_stst_assumerole_ms

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.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: ckulal, viduship

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

Needs approval from an approver in each of these files:

• OWNERS

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