MON-3775: add tests for CMO collection profiles

[rexagod]

The tests cover the following cases:

• Apply every collection profile, and check if the expected
  ServiceMonitors are available.
• CMO configuration reconciliation after a collection profile is applied
  is checked within the CMO tests itself.
• Prometheus *monitor selectors' reconciliation after a collection
  profile is applied is checked within the CMO tests itself.

Refer: openshift/enhancements#1298

Signed-off-by: Pranshu Srivastava rexagod@gmail.com

[openshift-ci-robot]

@rexagod: This pull request references MON-3775 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.16.0" version, but no target version was set.

In response to this:

The tests cover the following cases:

• Apply every collection profile, and check if appropriate metrics are
  available (or unavailable).
• CMO configuration reconciliation after a collection profile is applied
  is checked within the CMO tests itself.
• Prometheus *monitor selectors' reconciliation after a collection
  profile is applied is checked within the CMO tests itself.

Refer: openshift/enhancements#1298

Signed-off-by: Pranshu Srivastava rexagod@gmail.com

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]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: rexagod
Once this PR has been reviewed and has the lgtm label, please assign deads2k 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:

• OWNERS

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]

@rexagod: This pull request references MON-3775 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.16.0" version, but no target version was set.

In response to this:

The tests cover the following cases:

• Apply every collection profile, and check if the expected
  ServiceMonitors are available.
• CMO configuration reconciliation after a collection profile is applied
  is checked within the CMO tests itself.
• Prometheus *monitor selectors' reconciliation after a collection
  profile is applied is checked within the CMO tests itself.

Refer: openshift/enhancements#1298

Signed-off-by: Pranshu Srivastava rexagod@gmail.com

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-trt-bot]

Job Failure Risk Analysis for sha: e449b02

Job Name

Failure Risk

pull-ci-openshift-origin-master-e2e-aws-ovn-single-node-serial

High [sig-network-edge][Feature:Idling] Unidling [apigroup:apps.openshift.io][apigroup:route.openshift.io] should handle many TCP connections by possibly dropping those over a certain bound [Serial] [Suite:openshift/conformance/serial] This test has passed 98.57% of 70 runs on jobs ['periodic-ci-openshift-release-master-nightly-4.17-e2e-aws-ovn-single-node-serial' 'periodic-ci-openshift-release-master-nightly-4.16-e2e-aws-ovn-single-node-serial'] in the last 14 days.

[openshift-trt-bot]

Job Failure Risk Analysis for sha: a0a9fc1

Job Name

Failure Risk

pull-ci-openshift-origin-master-e2e-aws-ovn-single-node-upgrade

High [sig-cluster-lifecycle] pathological event should not see excessive Back-off restarting failed containers for ns/openshift-marketplace This test has passed 99.89% of 4576 runs on release 4.17 [Overall] in the last week. --- [bz-Node Tuning Operator] clusteroperator/node-tuning should not change condition/Available This test has passed 99.89% of 4576 runs on release 4.17 [Overall] in the last week.

[openshift-trt-bot]

Job Failure Risk Analysis for sha: 62cbbbb

Job Name	Failure Risk
pull-ci-openshift-origin-master-e2e-aws-ovn-single-node-upgrade	High [sig-arch] events should not repeat pathologically for ns/openshift-authentication-operator This test has passed 99.92% of 4719 runs on release 4.17 [Overall] in the last week. --- [bz-Node Tuning Operator] clusteroperator/node-tuning should not change condition/Available This test has passed 99.98% of 4730 runs on release 4.17 [Overall] in the last week.

[openshift-trt-bot]

Job Failure Risk Analysis for sha: 060391d

Job Name	Failure Risk
pull-ci-openshift-origin-master-e2e-aws-ovn-single-node-upgrade	High [bz-Node Tuning Operator] clusteroperator/node-tuning should not change condition/Available This test has passed 99.98% of 4946 runs on release 4.17 [Overall] in the last week.
pull-ci-openshift-origin-master-e2e-aws-ovn-edge-zones	IncompleteTests Tests for this run (102) are below the historical average (2015): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)

[rexagod]

/pj-rehearse periodic-ci-openshift-release-master-ci-4.16-e2e-gcp-ovn-techpreview

[rexagod]

/test e2e-gcp-ovn-techpreview

[rexagod]

/hold cancel

[rexagod]

Ah, it seems monitortests are not intended for techpreview features?

origin/pkg/defaultmonitortests/types.go

Line 58 in a91b2bf

ClusterStabilityDuringTest: monitortestframework.Stable,

[rexagod]

Nomenclature inferred from https://github.com/deads2k/api/blob/master/README.md#defining-featuregate-e2e-tests.

[rexagod]

/test e2e-gcp-ovn-techpreview

[openshift-trt-bot]

Job Failure Risk Analysis for sha: 2b6dd3b

Job Name	Failure Risk
pull-ci-openshift-origin-master-e2e-aws-ovn-ipsec-serial	High [sig-arch] events should not repeat pathologically for ns/openshift-dns This test has passed 100.00% of 48 runs on jobs ['periodic-ci-openshift-release-master-nightly-4.17-e2e-aws-ovn-serial' 'periodic-ci-openshift-release-master-ci-4.17-e2e-aws-ovn-serial'] in the last 14 days. --- [sig-arch] events should not repeat pathologically for ns/openshift-authentication-operator This test has passed 100.00% of 48 runs on jobs ['periodic-ci-openshift-release-master-nightly-4.17-e2e-aws-ovn-serial' 'periodic-ci-openshift-release-master-ci-4.17-e2e-aws-ovn-serial'] in the last 14 days.
pull-ci-openshift-origin-master-e2e-aws-ovn-single-node-upgrade	Low [bz-openshift-apiserver] clusteroperator/openshift-apiserver should not change condition/Available This test has passed 0.00% of 1 runs on release 4.17 [amd64 aws ovn single-node upgrade upgrade-micro] in the last week. Open Bugs openshift-apiserver ClusterOperator should not blip Available=False on brief missing HTTP content-type --- [bz-Storage] clusteroperator/storage should not change condition/Available This test has passed 0.00% of 1 runs on release 4.17 [amd64 aws ovn single-node upgrade upgrade-micro] in the last week. --- [bz-Node Tuning Operator] clusteroperator/node-tuning should not change condition/Available This test has passed 0.00% of 1 runs on release 4.17 [amd64 aws ovn single-node upgrade upgrade-micro] in the last week. --- [bz-Storage] clusteroperator/csi-snapshot-controller should not change condition/Available This test has passed 0.00% of 1 runs on release 4.17 [amd64 aws ovn single-node upgrade upgrade-micro] in the last week. --- Showing 4 of 6 test results

[openshift-ci]

@rexagod: The following test 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/verify	da345ab	link	true	/test verify

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.