openshift
TRT-1493: Add monitortest for cloud function on aws
TODO:
- [ ] Ensure metal sdn test does not have disruption (or we can avoid running this on metal)
Hit an endpoint (on a VM behind a load-balancer in aws) to test aws 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.
Here's a test to see if the LB is working on AWS (should return 200):
url=http://trt-openshift-tests-endpoint-lb-1161093811.us-east-1.elb.amazonaws.com/health
echo $(curl -sk -w "%{http_code}" -o response.txt -H "Audit-ID: 12345" "$url")
The VM/LB has been up for days in the TRT aws account:
$ date
Sun Feb 18 19:28:25 EST 2024
$ url=http://trt-openshift-tests-endpoint-lb-1161093811.us-east-1.elb.amazonaws.com/health
$ echo $(curl -sk -w "%{http_code}" -o response.txt -H "Audit-ID: 12345" "$url")
200
@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 aws) to test aws 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.
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: 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 aws) to test aws 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.
Here's a test to see if the LB is working on AWS (should return 200):
url=http://trt-openshift-tests-endpoint-lb-1161093811.us-east-1.elb.amazonaws.com/health echo $(curl -sk -w "%{http_code}" -o response.txt -H "Audit-ID: 12345" "$url")
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: 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 aws) to test aws 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.
Here's a test to see if the LB is working on AWS (should return 200):
url=http://trt-openshift-tests-endpoint-lb-1161093811.us-east-1.elb.amazonaws.com/health echo $(curl -sk -w "%{http_code}" -o response.txt -H "Audit-ID: 12345" "$url")The VM/LB has been up for days in the TRT aws account:
$ date Sun Feb 18 19:28:25 EST 2024 $ url=http://trt-openshift-tests-endpoint-lb-1161093811.us-east-1.elb.amazonaws.com/health $ echo $(curl -sk -w "%{http_code}" -o response.txt -H "Audit-ID: 12345" "$url") 200
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: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:
/test e2e-aws-jenkins/test e2e-aws-ovn-fips/test e2e-aws-ovn-image-registry/test e2e-aws-ovn-serial/test e2e-gcp-ovn/test e2e-gcp-ovn-builds/test e2e-gcp-ovn-image-ecosystem/test e2e-gcp-ovn-upgrade/test e2e-metal-ipi-ovn-ipv6/test images/test lint/test unit/test verify/test verify-deps
The following commands are available to trigger optional jobs:
/test 4.12-upgrade-from-stable-4.11-e2e-aws-ovn-upgrade-rollback/test e2e-agnostic-ovn-cmd/test e2e-aws/test e2e-aws-csi/test e2e-aws-disruptive/test e2e-aws-etcd-recovery/test e2e-aws-multitenant/test e2e-aws-ovn/test e2e-aws-ovn-cgroupsv2/test e2e-aws-ovn-etcd-scaling/test e2e-aws-ovn-kubevirt/test e2e-aws-ovn-single-node/test e2e-aws-ovn-single-node-serial/test e2e-aws-ovn-single-node-upgrade/test e2e-aws-ovn-upgrade/test e2e-aws-ovn-upi/test e2e-aws-proxy/test e2e-azure/test e2e-azure-ovn-etcd-scaling/test e2e-baremetalds-kubevirt/test e2e-gcp-csi/test e2e-gcp-disruptive/test e2e-gcp-fips-serial/test e2e-gcp-ovn-etcd-scaling/test e2e-gcp-ovn-rt-upgrade/test e2e-gcp-ovn-techpreview/test e2e-gcp-ovn-techpreview-serial/test e2e-metal-ipi-ovn-dualstack/test e2e-metal-ipi-sdn/test e2e-metal-ipi-serial/test e2e-metal-ipi-serial-ovn-ipv6/test e2e-metal-ipi-virtualmedia/test e2e-openstack-ovn/test e2e-openstack-serial/test e2e-vsphere/test e2e-vsphere-ovn-dualstack-primaryv6/test e2e-vsphere-ovn-etcd-scaling/test okd-e2e-gcp
Use /test all to run the following jobs that were automatically triggered:
pull-ci-openshift-origin-master-e2e-agnostic-ovn-cmdpull-ci-openshift-origin-master-e2e-aws-csipull-ci-openshift-origin-master-e2e-aws-ovn-cgroupsv2pull-ci-openshift-origin-master-e2e-aws-ovn-fipspull-ci-openshift-origin-master-e2e-aws-ovn-serialpull-ci-openshift-origin-master-e2e-aws-ovn-single-nodepull-ci-openshift-origin-master-e2e-aws-ovn-single-node-serialpull-ci-openshift-origin-master-e2e-aws-ovn-single-node-upgradepull-ci-openshift-origin-master-e2e-aws-ovn-upgradepull-ci-openshift-origin-master-e2e-gcp-csipull-ci-openshift-origin-master-e2e-gcp-ovnpull-ci-openshift-origin-master-e2e-gcp-ovn-rt-upgradepull-ci-openshift-origin-master-e2e-gcp-ovn-upgradepull-ci-openshift-origin-master-e2e-metal-ipi-ovn-ipv6pull-ci-openshift-origin-master-e2e-metal-ipi-sdnpull-ci-openshift-origin-master-e2e-openstack-ovnpull-ci-openshift-origin-master-imagespull-ci-openshift-origin-master-lintpull-ci-openshift-origin-master-unitpull-ci-openshift-origin-master-verifypull-ci-openshift-origin-master-verify-deps
In response to this:
/test ci/prow/e2e-aws-ovn-serial
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.
![openshift-ci[bot] avatar](https://avatars.githubusercontent.com/in/91280?v=4 "Published by a pub.dev verified publisher"){kind=small}
/override ci/prow/e2e-aws-ovn-serial /override ci/prow/e2e-metal-ipi-ovn-ipv6
@DennisPeriquet: Overrode contexts on behalf of DennisPeriquet: ci/prow/e2e-aws-ovn-serial, ci/prow/e2e-metal-ipi-ovn-ipv6
In response to this:
/override ci/prow/e2e-aws-ovn-serial /override ci/prow/e2e-metal-ipi-ovn-ipv6
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.
@DennisPeriquet: This pull request references TRT-1493 which is a valid jira issue.
In response to this:
TODO:
- [ ] Ensure metal sdn test does not have disruption (or we can avoid running this on metal)
Hit an endpoint (on a VM behind a load-balancer in aws) to test aws 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.
Here's a test to see if the LB is working on AWS (should return 200):
url=http://trt-openshift-tests-endpoint-lb-1161093811.us-east-1.elb.amazonaws.com/health echo $(curl -sk -w "%{http_code}" -o response.txt -H "Audit-ID: 12345" "$url")The VM/LB has been up for days in the TRT aws account:
$ date Sun Feb 18 19:28:25 EST 2024 $ url=http://trt-openshift-tests-endpoint-lb-1161093811.us-east-1.elb.amazonaws.com/health $ echo $(curl -sk -w "%{http_code}" -o response.txt -H "Audit-ID: 12345" "$url") 200
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.
/hold
Until problems in https://issues.redhat.com/browse/TRT-1522 are resolved, this PR is not to merge.
@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-upgrade | 87210091253ff6dcf583351b4ad47482823f914e | link | false | /test e2e-aws-ovn-single-node-upgrade |
| ci/prow/e2e-gcp-csi | 87210091253ff6dcf583351b4ad47482823f914e | link | false | /test e2e-gcp-csi |
| ci/prow/e2e-aws-ovn-single-node-serial | 87210091253ff6dcf583351b4ad47482823f914e | 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/test-infra repository. I understand the commands that are listed here.
@DennisPeriquet: This pull request references TRT-1493 which is a valid jira issue.
In response to this:
TODO:
- [ ] 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
Hit an endpoint (on a VM behind a load-balancer in aws) to test aws 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.
Here's a test to see if the LB is working on AWS (should return 200):
url=http://trt-openshift-tests-endpoint-lb-1161093811.us-east-1.elb.amazonaws.com/health echo $(curl -sk -w "%{http_code}" -o response.txt -H "Audit-ID: 12345" "$url")The VM/LB has been up for days in the TRT aws account:
$ date Sun Feb 18 19:28:25 EST 2024 $ url=http://trt-openshift-tests-endpoint-lb-1161093811.us-east-1.elb.amazonaws.com/health $ echo $(curl -sk -w "%{http_code}" -o response.txt -H "Audit-ID: 12345" "$url") 200
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: This pull request references TRT-1493 which is a valid jira issue.
In response to this:
TODO:
- [x] Ensure metal sdn test does not have disruption (this test should be skipped on metal)
- [x] Confirm 3 non-metal jobs have 0s disruption on aws-network-liveness
Hit an endpoint (on a VM behind a load-balancer in aws) to test aws 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.
Here's a test to see if the LB is working on AWS (should return 200):
url=http://trt-openshift-tests-endpoint-lb-1161093811.us-east-1.elb.amazonaws.com/health echo $(curl -sk -w "%{http_code}" -o response.txt -H "Audit-ID: 12345" "$url")The VM/LB has been up for days in the TRT aws account:
$ date Sun Feb 18 19:28:25 EST 2024 $ url=http://trt-openshift-tests-endpoint-lb-1161093811.us-east-1.elb.amazonaws.com/health $ echo $(curl -sk -w "%{http_code}" -o response.txt -H "Audit-ID: 12345" "$url") 200
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
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.
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: DennisPeriquet, dgoodwin
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~OWNERS~~ [DennisPeriquet,dgoodwin]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
[ART PR BUILD NOTIFIER]
This PR has been included in build openshift-enterprise-tests-container-v4.16.0-202403230015.p0.g710d797.assembly.stream.el8 for distgit openshift-enterprise-tests. All builds following this will include this PR.
