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

TRT-1493: Add monitortest for cloud function on aws #28581

Merged
merged 2 commits into from Mar 23, 2024
Merged

TRT-1493: Add monitortest for cloud function on aws #28581

merged 2 commits into from Mar 23, 2024

Conversation

DennisPeriquet
Copy link
Contributor

@DennisPeriquet DennisPeriquet commented Feb 8, 2024 •
edited

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

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Feb 8, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 8, 2024 •
edited by openshift-ci bot

@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.

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 8, 2024
@DennisPeriquet
Copy link
Contributor Author

/test e2e-gcp-ovn

@DennisPeriquet
Copy link
Contributor Author

/test e2e-aws-ovn-upgrade

@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 12, 2024 •
edited by openshift-ci bot

@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.

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Feb 13, 2024
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Feb 13, 2024
@DennisPeriquet
Copy link
Contributor Author

/retest-required

@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 19, 2024 •
edited by openshift-ci bot

@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.

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Feb 19, 2024
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Feb 19, 2024
@DennisPeriquet
Copy link
Contributor Author

/test ci/prow/e2e-aws-ovn-serial

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Feb 19, 2024

@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-cmd
  • pull-ci-openshift-origin-master-e2e-aws-csi
  • pull-ci-openshift-origin-master-e2e-aws-ovn-cgroupsv2
  • pull-ci-openshift-origin-master-e2e-aws-ovn-fips
  • pull-ci-openshift-origin-master-e2e-aws-ovn-serial
  • pull-ci-openshift-origin-master-e2e-aws-ovn-single-node
  • pull-ci-openshift-origin-master-e2e-aws-ovn-single-node-serial
  • pull-ci-openshift-origin-master-e2e-aws-ovn-single-node-upgrade
  • pull-ci-openshift-origin-master-e2e-aws-ovn-upgrade
  • pull-ci-openshift-origin-master-e2e-gcp-csi
  • pull-ci-openshift-origin-master-e2e-gcp-ovn
  • pull-ci-openshift-origin-master-e2e-gcp-ovn-rt-upgrade
  • pull-ci-openshift-origin-master-e2e-gcp-ovn-upgrade
  • pull-ci-openshift-origin-master-e2e-metal-ipi-ovn-ipv6
  • pull-ci-openshift-origin-master-e2e-metal-ipi-sdn
  • pull-ci-openshift-origin-master-e2e-openstack-ovn
  • pull-ci-openshift-origin-master-images
  • pull-ci-openshift-origin-master-lint
  • pull-ci-openshift-origin-master-unit
  • pull-ci-openshift-origin-master-verify
  • pull-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.

@DennisPeriquet
Copy link
Contributor Author

/test e2e-aws-ovn-serial

@DennisPeriquet
Copy link
Contributor Author

/override ci/prow/e2e-aws-ovn-serial
/override ci/prow/e2e-metal-ipi-ovn-ipv6

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Feb 19, 2024

@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.

@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 19, 2024 •
edited by openshift-ci bot

@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.

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Feb 19, 2024
@DennisPeriquet
Copy link
Contributor Author

/hold

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

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Feb 19, 2024
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Feb 22, 2024
@DennisPeriquet DennisPeriquet force-pushed the trt-1493-aws-liveness branch 2 times, most recently from 91b144e to 4954e76 Compare February 26, 2024 19:59
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Feb 26, 2024

@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 8721009 link false /test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-gcp-csi 8721009 link false /test e2e-gcp-csi
ci/prow/e2e-aws-ovn-single-node-serial 8721009 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.

@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 27, 2024 •
edited by openshift-ci bot

@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.

@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 27, 2024 •
edited by openshift-ci bot

@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
Copy link
Contributor Author

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Feb 27, 2024
@dgoodwin
Copy link
Contributor

/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-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 15, 2024
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Mar 15, 2024

[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

Needs approval from an approver in each of these files:
  • 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

@openshift-merge-bot openshift-merge-bot bot merged commit 710d797 into openshift:master Mar 23, 2024
14 of 22 checks passed
@openshift-bot
Copy link
Contributor

[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.

@DennisPeriquet DennisPeriquet deleted the trt-1493-aws-liveness branch March 27, 2024 20:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@bparees bparees Awaiting requested review from bparees

@spadgett spadgett Awaiting requested review from spadgett

Assignees

@dgoodwin dgoodwin

Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
5 participants
@DennisPeriquet @openshift-ci-robot @dgoodwin @openshift-bot @openshift-merge-robot