Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

WIP: Testing disablement of events MonitorTest for IBMCloud #50250

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

WIP: Testing disablement of events MonitorTest for IBMCloud #50250

wants to merge 1 commit into from

Conversation

cjschaef
Copy link
Member

WORK IN PROGRESS: Testing the disablement of events based MonitorTesting for IBM Cloud, as IBM works on resolving Infrastructure related items.

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Mar 26, 2024
@openshift-ci openshift-ci bot requested review from knobunc and tssurya March 26, 2024 15:57
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Mar 26, 2024

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: cjschaef
Once this PR has been reviewed and has the lgtm label, please assign jluhrsen for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found 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-robot
Copy link
Contributor

@cjschaef, pj-rehearse: unable to determine affected jobs. This could be due to a branch that needs to be rebased. ERROR:

could not determine changed registry steps: could not load step registry: failed to load registry file /var/tmp/gitrepo2981284953/ci-operator/step-registry/openshift/e2e/ibmcloud/ovn/openshift-e2e-ibmcloud-ovn-workflow.yaml: error unmarshaling JSON: while decoding JSON: json: cannot unmarshal string into Go struct field MultiStageTestConfiguration.workflow.steps.env of type api.TestEnvironment
Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse abort to abort all active rehearsals

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

@cjschaef cjschaef force-pushed the ibmcloud_disable_monitor_events branch from 3e4001b to 7ea45ea Compare March 26, 2024 15:59
@cjschaef
Copy link
Member Author

/pj-rehearse periodic-ci-openshift-ovn-kubernetes-master-e2e-ibmcloud-ipi-ovn-periodic

@cjschaef
Copy link
Member Author

/pj-rehearse periodic-ci-openshift-ovn-kubernetes-release-4.15-e2e-ibmcloud-ipi-ovn-periodic

@cjschaef
WIP: Testing disablement of events MonitorTest for IBMCloud
61e15e7 
WORK IN PROGRESS: Testing the disablement of events based
MonitorTesting for IBM Cloud, as IBM works on resolving
Infrastructure related items.
@cjschaef cjschaef force-pushed the ibmcloud_disable_monitor_events branch from 7ea45ea to 61e15e7 Compare March 26, 2024 18:47
@cjschaef
Copy link
Member Author

/pj-rehearse periodic-ci-openshift-ovn-kubernetes-master-e2e-ibmcloud-ipi-ovn-periodic

@openshift-ci-robot
Copy link
Contributor

[REHEARSALNOTIFIER]
@cjschaef: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name Repo Type Reason
periodic-ci-openshift-ovn-kubernetes-release-4.13-e2e-ibmcloud-ipi-ovn-periodic N/A periodic Registry content changed
periodic-ci-openshift-ovn-kubernetes-release-4.12-e2e-ibmcloud-ipi-ovn-periodic N/A periodic Registry content changed
periodic-ci-openshift-ovn-kubernetes-release-4.11-e2e-ibmcloud-ipi-ovn-periodic N/A periodic Registry content changed
periodic-ci-openshift-ovn-kubernetes-release-4.10-e2e-ibmcloud-ipi-ovn-periodic N/A periodic Registry content changed
periodic-ci-openshift-ovn-kubernetes-master-e2e-ibmcloud-ipi-ovn-periodic N/A periodic Registry content changed
periodic-ci-openshift-ovn-kubernetes-release-4.15-e2e-ibmcloud-ipi-ovn-periodic N/A periodic Registry content changed
periodic-ci-openshift-ovn-kubernetes-release-4.14-e2e-ibmcloud-ipi-ovn-periodic N/A periodic Registry content changed
Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse abort to abort all active rehearsals

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

@cjschaef
Copy link
Member Author

cjschaef commented Apr 3, 2024

/pj-rehease periodic-ci-openshift-ovn-kubernetes-release-4.15-e2e-ibmcloud-ipi-ovn-periodic periodic-ci-openshift-ovn-kubernetes-release-4.14-e2e-ibmcloud-ipi-ovn-periodic

@cjschaef
Copy link
Member Author

cjschaef commented Apr 4, 2024

/pj-rehearse periodic-ci-openshift-ovn-kubernetes-release-4.15-e2e-ibmcloud-ipi-ovn-periodic periodic-ci-openshift-ovn-kubernetes-release-4.14-e2e-ibmcloud-ipi-ovn-periodic

@cjschaef
Copy link
Member Author

cjschaef commented Apr 4, 2024

/pj-rehearse periodic-ci-openshift-ovn-kubernetes-release-4.15-e2e-ibmcloud-ipi-ovn-periodic

2 similar comments
@cjschaef
Copy link
Member Author

cjschaef commented Apr 4, 2024

/pj-rehearse periodic-ci-openshift-ovn-kubernetes-release-4.15-e2e-ibmcloud-ipi-ovn-periodic

@cjschaef
Copy link
Member Author

cjschaef commented Apr 8, 2024

/pj-rehearse periodic-ci-openshift-ovn-kubernetes-release-4.15-e2e-ibmcloud-ipi-ovn-periodic

@openshift-ci-robot
Copy link
Contributor

@cjschaef: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@cjschaef
Copy link
Member Author

/pj-rehearse periodic-ci-openshift-ovn-kubernetes-release-4.15-e2e-ibmcloud-ipi-ovn-periodic

@openshift-ci-robot
Copy link
Contributor

@cjschaef: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Apr 11, 2024

@cjschaef: 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/rehearse/periodic-ci-openshift-ovn-kubernetes-release-4.15-e2e-ibmcloud-ipi-ovn-periodic 61e15e7 link unknown /pj-rehearse periodic-ci-openshift-ovn-kubernetes-release-4.15-e2e-ibmcloud-ipi-ovn-periodic
ci/prow/clusterimageset-validate 61e15e7 link true /test clusterimageset-validate

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/test-infra repository. I understand the commands that are listed here.

@openshift-bot
Copy link
Contributor

Issues in openshift/release go stale after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 15d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 12, 2024
@openshift-bot
Copy link
Contributor

Stale issue in openshift/release rot after 15d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 15d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels May 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@knobunc knobunc Awaiting requested review from knobunc

@tssurya tssurya Awaiting requested review from tssurya

Assignees
No one assigned
Labels
do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Milestone
No milestone
3 participants
@cjschaef @openshift-ci-robot @openshift-bot