SPLAT_2628: Pext/OPCT: increase verbosity and timeouts for opct flow#74522
Conversation
openshift-ci
bot
added
the
do-not-merge/work-in-progress
|
Skipping CI for Draft Pull Request. |
|
/pj-rehearse periodic-ci-openshift-release-master-nightly-4.19-opct-external-aws-ccm |
|
@mtulio: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/test all |
OPCT flow requires more time to run because it runs both kube and ocp conformance test workflows, as well the install and destroy overhead in UPI method - which already consumes more time between steps. The step also increase data collection with standard gather from CI, as well include a new step to collect opct namespace information using must-gather tool
|
OPCT rehearsal job is now passing, I will push a new commit to fix the step name (registry-metadata), nothing that can affect the readiness. /pj-rehearse ack |
|
@mtulio: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
openshift-ci-robot
added
the
rehearsals-ack
|
/verified by #74522 (comment) |
openshift-ci-robot
added
the
verified
|
@mtulio: This PR has been marked as verified by 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. |
mtulio
force-pushed
the
SPLAT-2628-opct-timeout
branch
from
1181ac7 to
12fc282
Compare
openshift-ci
bot
removed
the
do-not-merge/work-in-progress
|
[REHEARSALNOTIFIER]
Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
openshift-ci-robot
removed
the
rehearsals-ack
/pj-rehearse ack |
|
@mtulio: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
openshift-ci-robot
added
the
rehearsals-ack
|
@mtulio: This PR has been marked as verified by 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. |
|
/lgtm |
|
@mtulio: 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. |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mtulio, vr4manta, xueqzhan The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci
bot
added
the
approved
…penshift#74522) OPCT flow requires more time to run because it runs both kube and ocp conformance test workflows, as well the install and destroy overhead in UPI method - which already consumes more time between steps. The step also increase data collection with standard gather from CI, as well include a new step to collect opct namespace information using must-gather tool
…penshift#74522) OPCT flow requires more time to run because it runs both kube and ocp conformance test workflows, as well the install and destroy overhead in UPI method - which already consumes more time between steps. The step also increase data collection with standard gather from CI, as well include a new step to collect opct namespace information using must-gather tool
4 participants
OPCT flow requires more time to run because it runs both kube and ocp conformance test workflows, as well the install and destroy overhead in UPI method - which already consumes more time between steps.
The step also increase data collection with standard gather from CI, as well include a new step to collect opct namespace information using must-gather tool
The main goal is to increase readiness in the failed jobs[1] as well increase verbosity for dev monitoring every day.
[1] https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-release-master-nightly-4.19-opct-external-aws-ccm/1996831003401785344
WRT https://issues.redhat.com/browse/SPLAT-2628