SREP-4053: Register rosa-e2e cluster profile#76494
SREP-4053: Register rosa-e2e cluster profile#76494dustman9000 wants to merge 1 commit intoopenshift:mainfrom
Conversation
openshift-ci-robot
added
the
jira/valid-reference
|
@dustman9000: This pull request references ROSA-683 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the initiative to target the "4.22.0" version, but no target version was set. DetailsIn response to this:
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
added
the
rehearsals-ack
Add ci-secret-bootstrap entry for rosa-e2e Vault secret (selfservice/rosa-e2e/) and boskos quota slices for 3 dedicated AWS accounts (rosa-e2e-prow-ci-01/02/03) in us-west-2. These accounts are managed in app-interface under osd-staging-1 payer and are dedicated to the rosa-e2e nightly CI jobs.
dustman9000
force-pushed
the
rosa-e2e-cluster-profile
branch
from
9a274bc to
17ab91b
Compare
dustman9000
changed the title
|
@dustman9000: This pull request references SREP-4053 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.22.0" version, but no target version was set. DetailsIn response to this:
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. |
1 similar comment
|
@dustman9000: This pull request references SREP-4053 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.22.0" version, but no target version was set. DetailsIn response to this:
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. |
|
[REHEARSALNOTIFIER] Note: If this PR includes changes to step registry files ( Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
@dustman9000: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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. |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: bmeng, dustman9000 The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
3 participants
Summary
Register the
rosa-e2ecluster profile for dedicated rosa-e2e CI testing.rosa-e2eto ci-secret-bootstrap (Vault secret atselfservice/rosa-e2e/)rosa-e2e-quota-sliceto boskos generator with 3 slots in us-west-2The Vault secret is already populated with AWS credentials and OCM token.
AWS accounts (managed in app-interface):
All under osd-staging-1 payer, owned by SRE Platform Team.
This profile will be used by the rosa-e2e nightly periodic job (PR #76427).
Jira: https://redhat.atlassian.net/browse/SREP-4053
Fixes: SREP-4053