-
Notifications
You must be signed in to change notification settings - Fork 1.9k
[th/dpu-operator-resolve-ip] change how to determine IP address of queue-manager (2) #65299
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.
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
base: master
Are you sure you want to change the base?
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: thom311 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 |
/pj-rehearse pull-ci-openshift-dpu-operator-main-make-e2e-test |
@thom311: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
e930414
to
89f22bd
Compare
/pj-rehearse pull-ci-openshift-dpu-operator-main-make-e2e-test |
@thom311: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
The script talks to the queue-manager service (via HTTPS API). That service runs in MP+ cluster, and we get the DNS name of the openshift route from the vault. So far, we could not resolve that DNS name, so the vault also configured the IP address. The problem is, that the route periodically changes IP address, so we need to frequently update the configuration (after it breaks). Instead, use the DNS servers from [1]. Those seem able to resolve this name. [1] https://github.com/openshift/release/blob/master/clusters/build-clusters/common_managed/dns.yaml
89f22bd
to
9c27d72
Compare
/pj-rehearse pull-ci-openshift-dpu-operator-main-make-e2e-test |
@thom311: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
[REHEARSALNOTIFIER]
Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
/pj-rehearse pull-ci-openshift-dpu-operator-main-make-e2e-test |
@thom311: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
/pj-rehearse pull-ci-openshift-dpu-operator-main-make-e2e-test |
@thom311: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
@thom311: The following test failed, say
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. |
/pj-rehearse ack |
@thom311: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
Try again to resolve the DNS name from the queue-manager service running in MP+.
This is a re-spin of #64568