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

[release-4.14] OPNET-355: Use NM's dns-change event for resolv.conf #4185

Conversation

openshift-cherrypick-robot

This is an automated cherry-pick of #4133

/assign mkowalski

NetworkManager starting from 1.42.2-12.el9_2 and 1.36.0-17.el8_6 adds a
new event `dns-change` which is fired whenever a change to the DNS
configuration happens. Thanks to this we no longer need to piggyback on
other events (like `up` or `dhcp-change`) to detect when we need to
potentially fix the content of `/etc/resolv.conf`.

This change will reduce the overall number of calls to
`resolv_prepender` as now it will be called only if DNS configuration
could have been changed.

We are still keeping the timeout for the `resolv_prepender` function
because it is not expected that it would be running for longer than one
minute.

Closes: OPNET-355
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Feb 13, 2024

@openshift-cherrypick-robot: Ignoring requests to cherry-pick non-bug issues: OPNET-355

In response to this:

This is an automated cherry-pick of #4133

/assign mkowalski

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.

@mkowalski
Copy link
Contributor

/lgtm
/label backport-risk-assessed
/label cherry-pick-approved

Copy link
Contributor

openshift-ci bot commented Feb 13, 2024

@mkowalski: Can not set label backport-risk-assessed: Must be member in one of these teams: [openshift-patch-managers]

In response to this:

/lgtm
/label backport-risk-assessed
/label cherry-pick-approved

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.

Copy link
Contributor

openshift-ci bot commented Feb 13, 2024

@mkowalski: Can not set label cherry-pick-approved: Must be member in one of these teams: []

In response to this:

/lgtm
/label backport-risk-assessed
/label cherry-pick-approved

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 openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 13, 2024
Copy link
Contributor

openshift-ci bot commented Feb 13, 2024

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: mkowalski, openshift-cherrypick-robot
Once this PR has been reviewed and has the lgtm label, please assign jkyros for approval. 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

1 similar comment
Copy link
Contributor

openshift-ci bot commented Feb 13, 2024

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: mkowalski, openshift-cherrypick-robot
Once this PR has been reviewed and has the lgtm label, please assign jkyros for approval. 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

Copy link
Contributor

openshift-ci bot commented Feb 13, 2024

@openshift-cherrypick-robot: 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/okd-scos-e2e-aws-ovn 64909bf link false /test okd-scos-e2e-aws-ovn
ci/prow/e2e-aws-ovn-upgrade 64909bf link true /test e2e-aws-ovn-upgrade
ci/prow/unit 64909bf link true /test unit

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.

@mkowalski
Copy link
Contributor

/label backport-risk-assessed

Copy link
Contributor

openshift-ci bot commented Feb 16, 2024

@mkowalski: Can not set label backport-risk-assessed: Must be member in one of these teams: [openshift-patch-managers]

In response to this:

/label backport-risk-assessed

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.

@mkowalski
Copy link
Contributor

/close

Need to be handled manually (there are 3 commits in a bundle to be backported)

@openshift-ci openshift-ci bot closed this Feb 27, 2024
Copy link
Contributor

openshift-ci bot commented Feb 27, 2024

@mkowalski: Closed this PR.

In response to this:

/close

Need to be handled manually (there are 3 commits in a bundle to be backported)

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants