TRT-1494: Add monitortest for cloud function on azure

[DennisPeriquet]

Hit an endpoint (on a VM behind a load-balancer in azure) to test azure connectivity during test runs in a way that (attempts to) mimic pods in an Openshift cluster. This way we can compare disruption problems noted in TRT-1466.

This is just a test using an LB/VM in a personal Azure account.

TODO:

• Move the endpoint to an LB/VM on an Openshift owned Azure account.
• Ensure metal sdn test does not have disruption (this test should be skipped on metal)
• Confirm 3 non-metal jobs have 0s disruption on aws-network-liveness

The new resource group is called do-not-delete-trt-liveness at portal.azure.com.

[openshift-ci-robot]

@DennisPeriquet: This pull request references TRT-1493 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 bug to target the "4.16.0" version, but no target version was set.

In response to this:

Hit an endpoint (on a VM behind a load-balancer in azure) to test azure connectivity during test runs in a way that (attempts to) mimic pods in an Openshift cluster. This way we can compare disruption problems noted in TRT-1466.

This is just a test using an LB/VM in a personal Azure account.

TODO:

• Move the endpoint to an LB/VM on an Openshift owned Azure account.

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.

[DennisPeriquet]

/retest

[DennisPeriquet]

This is the IP of the LB in my personal Azure account

[DennisPeriquet]

this has been changed to use a LB in the Openshift azure account

[openshift-ci-robot]

@DennisPeriquet: This pull request references TRT-1493 which is a valid jira issue.

In response to this:

Hit an endpoint (on a VM behind a load-balancer in azure) to test azure connectivity during test runs in a way that (attempts to) mimic pods in an Openshift cluster. This way we can compare disruption problems noted in TRT-1466.

This is just a test using an LB/VM in a personal Azure account.

TODO:

• Move the endpoint to an LB/VM on an Openshift owned Azure account.

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]

@DennisPeriquet: This pull request references TRT-1493 which is a valid jira issue.

In response to this:

Hit an endpoint (on a VM behind a load-balancer in azure) to test azure connectivity during test runs in a way that (attempts to) mimic pods in an Openshift cluster. This way we can compare disruption problems noted in TRT-1466.

This is just a test using an LB/VM in a personal Azure account.

TODO:

• Move the endpoint to an LB/VM on an Openshift owned Azure account.

The new resource group is called do-not-delete-trt-liveness at portal.azure.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.

[DennisPeriquet]

/hold

Until problems in https://issues.redhat.com/browse/TRT-1522 are resolved, this PR is not to merge.

[DennisPeriquet]

/hold

Until problems in https://issues.redhat.com/browse/TRT-1522 are resolved, this PR is not to merge.

[openshift-ci-robot]

@DennisPeriquet: This pull request references TRT-1493 which is a valid jira issue.

In response to this:

Hit an endpoint (on a VM behind a load-balancer in azure) to test azure connectivity during test runs in a way that (attempts to) mimic pods in an Openshift cluster. This way we can compare disruption problems noted in TRT-1466.

This is just a test using an LB/VM in a personal Azure account.

TODO:

• Move the endpoint to an LB/VM on an Openshift owned Azure account.
• Ensure metal sdn test does not have disruption (or we can avoid running this on metal)

The new resource group is called do-not-delete-trt-liveness at portal.azure.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-robot]

@DennisPeriquet: This pull request references TRT-1493 which is a valid jira issue.

In response to this:

Hit an endpoint (on a VM behind a load-balancer in azure) to test azure connectivity during test runs in a way that (attempts to) mimic pods in an Openshift cluster. This way we can compare disruption problems noted in TRT-1466.

This is just a test using an LB/VM in a personal Azure account.

TODO:

• Move the endpoint to an LB/VM on an Openshift owned Azure account.
• Ensure metal sdn test does not have disruption (this test should be skipped on metal)
• Confirm 3 non-metal jobs have 0s disruption on aws-network-liveness

The new resource group is called do-not-delete-trt-liveness at portal.azure.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-robot]

@DennisPeriquet: This pull request references TRT-1493 which is a valid jira issue.

In response to this:

Hit an endpoint (on a VM behind a load-balancer in azure) to test azure connectivity during test runs in a way that (attempts to) mimic pods in an Openshift cluster. This way we can compare disruption problems noted in TRT-1466.

This is just a test using an LB/VM in a personal Azure account.

TODO:

• Move the endpoint to an LB/VM on an Openshift owned Azure account.
• Ensure metal sdn test does not have disruption (this test should be skipped on metal)
• Confirm 3 non-metal jobs have 0s disruption on aws-network-liveness

The new resource group is called do-not-delete-trt-liveness at portal.azure.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.

[DennisPeriquet]

/hold cancel

[dgoodwin]

/lgtm

With A29y on this wouldn't be anything I'd consider critical, however you are watcher next week so feel free to label if you'd like it to go in.

[openshift-trt-bot]

Job Failure Risk Analysis for sha: 433afaa

Job Name	Failure Risk
pull-ci-openshift-origin-master-e2e-aws-ovn-single-node-serial	Low [sig-arch] events should not repeat pathologically for ns/openshift-etcd-operator This test has passed 35.00% of 60 runs on jobs ['periodic-ci-openshift-release-master-nightly-4.16-e2e-aws-ovn-single-node-serial'] in the last 14 days.

[openshift-ci-robot]

@DennisPeriquet: This pull request references TRT-1494 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 bug to target the "4.16.0" version, but no target version was set.

In response to this:

Hit an endpoint (on a VM behind a load-balancer in azure) to test azure connectivity during test runs in a way that (attempts to) mimic pods in an Openshift cluster. This way we can compare disruption problems noted in TRT-1466.

This is just a test using an LB/VM in a personal Azure account.

TODO:

• Move the endpoint to an LB/VM on an Openshift owned Azure account.
• Ensure metal sdn test does not have disruption (this test should be skipped on metal)
• Confirm 3 non-metal jobs have 0s disruption on aws-network-liveness

The new resource group is called do-not-delete-trt-liveness at portal.azure.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]

@DennisPeriquet: 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	4169e1e	link	false	/test e2e-aws-ovn-single-node
ci/prow/e2e-aws-ovn-single-node-serial	4169e1e	link	false	/test e2e-aws-ovn-single-node-serial
ci/prow/e2e-aws-ovn-single-node-upgrade	4169e1e	link	false	/test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-gcp-ovn-rt-upgrade	4169e1e	link	false	/test e2e-gcp-ovn-rt-upgrade

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

Job Failure Risk Analysis for sha: 4169e1e

Job Name	Failure Risk
pull-ci-openshift-origin-master-e2e-aws-ovn-single-node-serial	Low [sig-arch] events should not repeat pathologically for ns/openshift-etcd-operator This test has passed 34.55% of 55 runs on jobs ['periodic-ci-openshift-release-master-nightly-4.16-e2e-aws-ovn-single-node-serial'] in the last 14 days.

[neisw]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: DennisPeriquet, dgoodwin, neisw

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [DennisPeriquet,dgoodwin,neisw]

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]

/retest-required

Remaining retests: 0 against base HEAD 0d6231f and 2 for PR HEAD 4169e1e in total