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.

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

STOR-1892: Add option to disable all monitors #28815

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

jsafrane
Copy link
Contributor

openshift-tests run --disable-monitor all disables all monitors, so the output and artifacts are not polluted by monitors, and contain the ginkgo test results only.

This is useful when running the tests by a human and not in CI - the monitors are very talkative on stdout. We use openshift-tests as a certification suite for CSI drivers and 3rd party CSI driver vendors are not interested in the OCP health, they're interested in the CSI driver test results.

In addition, when all monitors are disabled, do not collect AdditionalEvents__in_cluster_disruption.json from nodes - there are no monitoring DaemonSets running.

@jsafrane jsafrane changed the title Add option to disable all monitors STOR-1892: Add option to disable all monitors May 20, 2024
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label May 20, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented May 20, 2024

@jsafrane: This pull request references STOR-1892 which is a valid jira issue.

In response to this:

openshift-tests run --disable-monitor all disables all monitors, so the output and artifacts are not polluted by monitors, and contain the ginkgo test results only.

This is useful when running the tests by a human and not in CI - the monitors are very talkative on stdout. We use openshift-tests as a certification suite for CSI drivers and 3rd party CSI driver vendors are not interested in the OCP health, they're interested in the CSI driver test results.

In addition, when all monitors are disabled, do not collect AdditionalEvents__in_cluster_disruption.json from nodes - there are no monitoring DaemonSets running.

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 openshift-ci bot requested review from deads2k and sjenning May 20, 2024 12:32
Copy link
Contributor

openshift-ci bot commented May 20, 2024

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: jsafrane
Once this PR has been reviewed and has the lgtm label, please assign soltysh 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-tests run --disable-monitor all` disables all monitors, so the
output and artifacts are not polluted by monitors, but contain the ginkgo
test results only.

This is useful when running the tests by a human and not in CI.
When no in-cluster monitoring daemon sets run, StartInClusterMonitors() is
not called and `namespace` is empty. Nothing produces
/tmp/artifacts/junit/AdditionalEvents__in_cluster_disruption.json on the
nodes and thus do not collect it.

This removes following error:
  found errors fetching in-cluster data: [failed to list files in disruption event folder on node ip-10-0-19-0.ec2.internal: the server could not find the requested resource ]
Copy link
Contributor

openshift-ci bot commented May 20, 2024

@jsafrane: 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/e2e-aws-ovn-single-node d9a2c99 link false /test e2e-aws-ovn-single-node
ci/prow/e2e-aws-ovn-single-node-upgrade d9a2c99 link false /test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-aws-ovn-single-node-serial d9a2c99 link false /test e2e-aws-ovn-single-node-serial

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.

@openshift-trt-bot
Copy link

Job Failure Risk Analysis for sha: d9a2c99

Job Name Failure Risk
pull-ci-openshift-origin-master-e2e-aws-ovn-single-node-upgrade IncompleteTests
Tests for this run (99) are below the historical average (2301): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)
pull-ci-openshift-origin-master-e2e-aws-ovn-single-node-serial IncompleteTests
Tests for this run (95) are below the historical average (820): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)
pull-ci-openshift-origin-master-e2e-aws-ovn-single-node IncompleteTests
Tests for this run (98) are below the historical average (1745): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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.

None yet

3 participants