-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
OCPBUGS-29067: Prepend resolv.conf on the bootstrap node of GCP with custom-dns #8811
OCPBUGS-29067: Prepend resolv.conf on the bootstrap node of GCP with custom-dns #8811
Conversation
@sadasu: This pull request references Jira Issue OCPBUGS-29067, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. In response to this:
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. |
/jira refresh |
@sadasu: This pull request references Jira Issue OCPBUGS-29067, which is valid. 3 validation(s) were run on this bug
No GitHub users were found matching the public email listed for the QA contact in Jira (yunjiang@redhat.com), skipping review request. In response to this:
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. |
ba889eb
to
dffe477
Compare
/retest-required |
dffe477
to
c2e6e96
Compare
@sadasu: This pull request references Jira Issue OCPBUGS-29067, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. In response to this:
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. |
/test ? |
@sadasu: The following commands are available to trigger required jobs:
The following commands are available to trigger optional jobs:
Use
In response to this:
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. |
/jira refresh |
@sadasu: This pull request references Jira Issue OCPBUGS-29067, which is valid. 3 validation(s) were run on this bug
Requesting review from QA contact: In response to this:
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. |
/test e2e-metal-ipi-ovn |
From pre-merge testing performed by @jianli-wei, here are the contents of resolv.conf on the bootstrap node:
|
/retest-required |
@patrickdillon and @barbacbd Could PTAL? |
>&2 echo "NM resolv-prepender: Checking for nameservers in /var/run/NetworkManager/resolv.conf" | ||
while ! grep nameserver /var/run/NetworkManager/resolv.conf; do | ||
>&2 echo "NM resolv-prepender: NM resolv.conf still empty of nameserver" | ||
sleep 0.5 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a reason to check twice a second or did you just intend to check often?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The latter.
#!/bin/bash | ||
IFACE=$1 | ||
STATUS=$2 | ||
case "$STATUS" in |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am a bit confused by the switch here. Can we just move the major block out? The default case isn't doing anything here. Is there another intention ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the code to update resolv.conf does not need to be within the case statement. But, I am using what the on-prem platforms use and wanted to be consistent across all platforms that use in-cluster DNS. But, there is an ongoing effort to change the way resolv.conf is updated for all platforms that do this. This will get updated again at that time.
// Copy platform specific files/units when present with the exception of GCP | ||
// On GCP, copy over platform specific files/units only when UserProvisionedDNS is enabled. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Rather than only copying files when userProvisionedDNS is enabled, it would be better to only conditionally generate the files (and always copy all files). I created an example of how to do this here: sadasu#1
The way this is currently written skips including GCP's custom report-progress.sh script and I don't think that was the intent.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yup. I had considered templating it but didn't take that route because I hadn't seen report-progress.sh script
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated. Slightly different from the suggestion to avoid check for empty templates.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
avoid check for empty templates.
Sounds good!
c2e6e96
to
40f6a23
Compare
When UserProvisionedDNS is enabled during an install on GCP, prepend the NetworkManager generated resolv.conf file on the bootstrap node with the IP of the localhost.
40f6a23
to
f84c973
Compare
/test e2e-metal-ipi-ovn |
/approve |
LGTM. Let's watch the tests |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: patrickdillon 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:
Approvers can indicate their approval by writing |
/retest-required |
/test e2e-gcp-ovn-byo-vpc |
@sadasu: The following tests 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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
11aa461
into
openshift:master
@sadasu: Jira Issue OCPBUGS-29067: Some pull requests linked via external trackers have merged:
The following pull requests linked via external trackers have not merged: These pull request must merge or be unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with Jira Issue OCPBUGS-29067 has not been moved to the MODIFIED state. In response to this:
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. |
[ART PR BUILD NOTIFIER] Distgit: ose-installer-terraform-providers |
[ART PR BUILD NOTIFIER] Distgit: ose-installer-altinfra |
[ART PR BUILD NOTIFIER] Distgit: ose-baremetal-installer |
[ART PR BUILD NOTIFIER] Distgit: ose-installer-artifacts |
When UserProvisionedDNS is enabled during an install on GCP, prepend the NetworkManager generated resolv.conf file on the bootstrap node with the IP of the localhost.