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

WIP DO NOT MERGE: DNS Propagation Test #1132

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from
Draft

WIP DO NOT MERGE: DNS Propagation Test #1132

wants to merge 1 commit into from

Conversation

gcs278
Copy link
Contributor

@gcs278 gcs278 commented Aug 20, 2024 •
edited
Loading

PR to test DNS propagation in CI. DO NOT MERGE

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Aug 20, 2024
@openshift-ci openshift-ci bot requested review from candita and rfredette August 20, 2024 01:45
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Aug 20, 2024

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from gcs278. 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

@gcs278 gcs278 force-pushed the dns-propagation-test branch 5 times, most recently from 45a7005 to f69e117 Compare August 20, 2024 21:05
@gcs278
Copy link
Contributor Author

gcs278 commented Aug 21, 2024

/test e2e-aws-operator

@gcs278 gcs278 force-pushed the dns-propagation-test branch from f69e117 to 2f56fcb Compare August 21, 2024 23:05
@gcs278
Copy link
Contributor Author

gcs278 commented Aug 22, 2024

Interesting results. From within the ephemeral cluster, it always resolves within 5 minutes. But from the test runner cluster, it can take anywhere from 5-15 minutes. 15 mins is the max I see. Let's spin again for more data points.
/test e2e-aws-operator

@gcs278 gcs278 force-pushed the dns-propagation-test branch from 2f56fcb to 294d877 Compare August 22, 2024 19:56
@gcs278
Copy link
Contributor Author

gcs278 commented Aug 22, 2024

/test e2e-aws-operator

@gcs278
Copy link
Contributor Author

gcs278 commented Aug 23, 2024

maybe one more
/test e2e-aws-operator

@gcs278
Copy link
Contributor Author

gcs278 commented Sep 3, 2024

openshift-ci AWS account SOA record TTL has been updated from 15 minutes to 1 minute. Let's see if the DNS propagation time is reduced.

/test e2e-aws-operator

@gcs278
Copy link
Contributor Author

gcs278 commented Sep 3, 2024 •
edited
Loading

Nice, now we see 5m negative caching time!
EDIT: correction I was reading wrong values, it's 1 minute!
/test e2e-aws-operator

@gcs278
Copy link
Contributor Author

gcs278 commented Sep 3, 2024

/test e2e-aws-gatewayapi

@gcs278
Copy link
Contributor Author

gcs278 commented Sep 3, 2024

Just spinning one more time to see if it really isn't flaking:
/test e2e-aws-gatewayapi

@gcs278
Copy link
Contributor Author

gcs278 commented Sep 6, 2024

Problem has been resolved and https://issues.redhat.com/browse/OCPBUGS-14966 has been closed.
/close

@openshift-ci openshift-ci bot closed this Sep 6, 2024
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Sep 6, 2024

@gcs278: Closed this PR.

In response to this:

Problem has been resolved and https://issues.redhat.com/browse/OCPBUGS-14966 has been closed.
/close

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.

@gcs278 gcs278 mentioned this pull request Sep 23, 2024
Merged
@gcs278
Copy link
Contributor Author

gcs278 commented Oct 11, 2024

/reopen
Since openshift/release#56785 has merged, I want to use this PR to provide DNS resolution data for IBM Cloud.

@gcs278
Copy link
Contributor Author

gcs278 commented Oct 11, 2024

/open

@openshift-ci openshift-ci bot reopened this Oct 11, 2024
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Oct 11, 2024

@gcs278: Reopened this PR.

In response to this:

/reopen
Since openshift/release#56785 has merged, I want to use this PR to provide DNS resolution data for IBM Cloud.

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.

@gcs278 gcs278 marked this pull request as draft October 11, 2024 17:03
@gcs278
Copy link
Contributor Author

gcs278 commented Oct 11, 2024

/test e2e-ibmcloud-operator

@gcs278 gcs278 force-pushed the dns-propagation-test branch from 294d877 to 894ef62 Compare October 11, 2024 22:00
@gcs278 gcs278 force-pushed the dns-propagation-test branch from a40996f to bd4bcab Compare October 29, 2024 21:02
@gcs278
Copy link
Contributor Author

gcs278 commented Oct 29, 2024

/test e2e-ibmcloud-operator

@gcs278 gcs278 force-pushed the dns-propagation-test branch from bd4bcab to eb0651d Compare October 30, 2024 18:03
@gcs278
Copy link
Contributor Author

gcs278 commented Oct 30, 2024

/test e2e-ibmcloud-operator

@gcs278 gcs278 force-pushed the dns-propagation-test branch from eb0651d to 5b37cea Compare October 30, 2024 22:03
@gcs278
Copy link
Contributor Author

gcs278 commented Oct 30, 2024

Working through some warmup bugs in the code. Should be fixed now:
/test e2e-ibmcloud-operator

@gcs278 gcs278 force-pushed the dns-propagation-test branch from 5b37cea to 4479a49 Compare October 31, 2024 02:31
@gcs278
Copy link
Contributor Author

gcs278 commented Oct 31, 2024

One more major bug fix...
/test e2e-ibmcloud-operator

@gcs278 gcs278 force-pushed the dns-propagation-test branch from 4479a49 to 5a4c829 Compare November 11, 2024 19:30
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Nov 11, 2024
@gcs278 gcs278 force-pushed the dns-propagation-test branch from 5a4c829 to 809424c Compare November 11, 2024 19:31
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Nov 11, 2024
@gcs278
Copy link
Contributor Author

gcs278 commented Nov 11, 2024

Fixed the bug, now trying to hone in on a "warmup" period for the LB_ADDRESS:
/test e2e-ibmcloud-operator

@gcs278 gcs278 force-pushed the dns-propagation-test branch from 809424c to 20153a6 Compare November 12, 2024 01:35
@gcs278
Copy link
Contributor Author

gcs278 commented Nov 12, 2024

still trying to find that warmup period...
/test e2e-ibmcloud-operator

@gcs278 gcs278 force-pushed the dns-propagation-test branch from 20153a6 to 2c8d128 Compare November 12, 2024 14:29
@gcs278
Copy link
Contributor Author

gcs278 commented Nov 12, 2024

still trying to find that warmup period...
/test e2e-ibmcloud-operator

@gcs278
Copy link
Contributor Author

gcs278 commented Nov 12, 2024

failed install
/test e2e-ibmcloud-operator

@gcs278
Copy link
Contributor Author

gcs278 commented Nov 13, 2024

Warmup successful between 4-5 minutes. That's a bit odd compared to #1164 which does 3 minutes and is successful.

@gcs278 gcs278 mentioned this pull request Nov 14, 2024
Draft
@gcs278 gcs278 force-pushed the dns-propagation-test branch from 2c8d128 to f3b98e5 Compare November 14, 2024 16:28
@gcs278
Copy link
Contributor Author

gcs278 commented Nov 14, 2024

Running with just 5 minutes to see how reliable it is since #1164 is now failing with 5 minute warmup
/test e2e-ibmcloud-operator

@gcs278 gcs278 force-pushed the dns-propagation-test branch from f3b98e5 to d6f160a Compare November 14, 2024 20:54
@gcs278
Copy link
Contributor Author

gcs278 commented Nov 14, 2024

Warmup of 5 minutes never passed....trying 10 minutes
/test e2e-ibmcloud-operator

@gcs278 gcs278 force-pushed the dns-propagation-test branch from d6f160a to 852736b Compare November 15, 2024 00:52
@gcs278
Copy link
Contributor Author

gcs278 commented Nov 15, 2024

10min warmup worked 100% of the time.
Trying 7min
/test e2e-ibmcloud-operator

@gcs278 gcs278 force-pushed the dns-propagation-test branch from 852736b to e6a0b50 Compare November 15, 2024 14:02
@gcs278
Copy link
Contributor Author

gcs278 commented Nov 15, 2024

7 mins worked 100% of the time.
Trying 6 minutes.
/test e2e-ibmcloud-operator

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Nov 15, 2024

@gcs278: 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/e2e-ibmcloud-operator e6a0b50 link false /test e2e-ibmcloud-operator

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@candita candita Awaiting requested review from candita

@rfredette rfredette Awaiting requested review from rfredette

Assignees
No one assigned
Labels
do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@gcs278 @openshift-merge-robot