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.

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

Add Check resolv.conf is empty to avoid CoreDNS crash #9502

Conversation

yankay
Copy link
Member

@yankay yankay commented Nov 18, 2022

What type of PR is this?

/kind feature

What this PR does / why we need it:

If the /etc/resolv.conf is empty. The kubernetes coredns is in CrashLoopBackOff status with "no nameservers found" error.

The same issue is at:

Which issue(s) this PR fixes:

Fixes #9497 (workaround)

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

Add Check resolv.conf is empty to avoid CoreDNS crash

@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Nov 18, 2022
@yankay yankay force-pushed the add-check-for-resolv-to-avoid-coredns-crash branch 3 times, most recently from 6e6b479 to d3fcf1c Compare November 18, 2022 12:59
@yankay
Copy link
Member Author

yankay commented Nov 22, 2022

HI @oomichi @floryut , would you please review the PR ?
Thanks :-)

@oomichi oomichi changed the title Add Check resolv.conf is emptyto avoid CoreDNS crash Add Check resolv.conf is empty to avoid CoreDNS crash Nov 26, 2022
@yankay yankay force-pushed the add-check-for-resolv-to-avoid-coredns-crash branch from 0afd4aa to 26e437f Compare November 28, 2022 02:45
@oomichi
Copy link
Contributor

oomichi commented Nov 29, 2022

That seems unrelated test failure like:

    TASK [container-engine/cri-o : Remove legacy CRI-O kubic apt repo key] *********
    Monday 28 November 2022  03:37:23 +0000 (0:00:00.049)       0:00:45.250 *******
    skipping: [almalinux8]
    skipping: [fedora]
fatal: [ubuntu20]: FAILED! => {"changed": false, "msg": "Failed to download key at https://download.opensuse.org/repositories/devel:kubic:libcontainers:stable/xUbuntu_20.04/Release.key: HTTP Error 404: Not Found"}
fatal: [debian10]: FAILED! => {"changed": false, "msg": "Failed to download key at https://download.opensuse.org/repositories/devel:kubic:libcontainers:stable/Debian_10/Release.key: HTTP Error 404: Not Found"}

@oomichi
Copy link
Contributor

oomichi commented Nov 29, 2022

Thanks for updating.

/approve

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: oomichi, yankay

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 29, 2022
@yankay
Copy link
Member Author

yankay commented Nov 29, 2022

That seems unrelated test failure like:

    TASK [container-engine/cri-o : Remove legacy CRI-O kubic apt repo key] *********
    Monday 28 November 2022  03:37:23 +0000 (0:00:00.049)       0:00:45.250 *******
    skipping: [almalinux8]
    skipping: [fedora]
fatal: [ubuntu20]: FAILED! => {"changed": false, "msg": "Failed to download key at https://download.opensuse.org/repositories/devel:kubic:libcontainers:stable/xUbuntu_20.04/Release.key: HTTP Error 404: Not Found"}
fatal: [debian10]: FAILED! => {"changed": false, "msg": "Failed to download key at https://download.opensuse.org/repositories/devel:kubic:libcontainers:stable/Debian_10/Release.key: HTTP Error 404: Not Found"}

HI @oomichi

There is the PR to fix the issue. #9525.
Welcome to review it :-)

@yankay
Copy link
Member Author

yankay commented Dec 1, 2022

HI @floryut,
would you please review the PR :-)

@dougsland
Copy link
Contributor

looks sane to me even not seeing it in my env.
/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Dec 2, 2022
@k8s-ci-robot k8s-ci-robot merged commit b9fe301 into kubernetes-sigs:master Dec 2, 2022
@yankay
Copy link
Member Author

yankay commented Dec 2, 2022

Thanks @oomichi @dougsland for the PR review.

@floryut floryut added the kind/feature Categorizes issue or PR as related to a new feature. label Dec 5, 2022
@floryut floryut mentioned this pull request Jan 4, 2023
enneitex pushed a commit to enneitex/kubespray that referenced this pull request Jan 25, 2023
HoKim98 pushed a commit to ulagbulag/kubespray that referenced this pull request Mar 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/feature Categorizes issue or PR as related to a new feature. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Provide an option to disable coredns forward plugin to upstream dns server
5 participants