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

net/sysconfig: do not remove all existing settings of /etc/sysconfig/network #5991

Merged
merged 1 commit into from
Feb 14, 2025

Conversation

ani-sinha
Copy link
Contributor

@ani-sinha ani-sinha commented Jan 28, 2025

Proposed Commit Message

In some distros, /etc/sysconfig/network may have important configurations that are necessary for the instance to come up. For example, centos based distros write NOZEROCONF=yes in /etc/sysconfig/network for some instances that require zeroconf to be disabled. Removing these customizations would prevent the instance to come up. So leave the customizations in /etc/sysconfig/network intact except those that we are interested in.

Fixes GH-5990
Signed-off-by: Ani Sinha anisinha@redhat.com

Merge type

  • Squash merge using "Proposed Commit Message"
  • Rebase and merge unique commits. Requires commit messages per-commit each referencing the pull request number (#<PR_NUM>)

Sorry, something went wrong.

Copy link

Hello! Thank you for this proposed change to cloud-init. This pull request is now marked as stale as it has not seen any activity in 14 days. If no activity occurs within the next 7 days, this pull request will automatically close.

If you are waiting for code review and you are seeing this message, apologies! Please reply, tagging TheRealFalcon, and he will ensure that someone takes a look soon.

(If the pull request is closed and you would like to continue working on it, please do tag TheRealFalcon to reopen it.)

@github-actions github-actions bot added the stale-pr Pull request is stale; will be auto-closed soon label Feb 12, 2025
@ani-sinha ani-sinha marked this pull request as ready for review February 12, 2025 09:44
…network

In some distros, /etc/sysconfig/network may have important configurations that
are necessary for the instance to come up. For example, centos based distros
write NOZEROCONF=yes in /etc/sysconfig/network for some instances that require
zeroconf to be disabled. Removing these customizations would prevent the
instance to come up. So leave the customizations in /etc/sysconfig/network
intact except those that we are interested in.

Fixes canonicalGH-5990
Signed-off-by: Ani Sinha <anisinha@redhat.com>
@ani-sinha
Copy link
Contributor Author

Hello! Thank you for this proposed change to cloud-init. This pull request is now marked as stale as it has not seen any activity in 14 days. If no activity occurs within the next 7 days, this pull request will automatically close.

If you are waiting for code review and you are seeing this message, apologies! Please reply, tagging TheRealFalcon, and he will ensure that someone takes a look soon.

(If the pull request is closed and you would like to continue working on it, please do tag TheRealFalcon to reopen it.)

Tagging @TheRealFalcon as the message says 😃

@TheRealFalcon TheRealFalcon removed the stale-pr Pull request is stale; will be auto-closed soon label Feb 12, 2025
@ani-sinha
Copy link
Contributor Author

QE tested this change internally and it seems the change fixed the issue.

@ani-sinha
Copy link
Contributor Author

@TheRealFalcon any idea when this will me merged? We have some internal deadline coming up and this issue is a regression, hence will have to be fixed.

Copy link
Member

@TheRealFalcon TheRealFalcon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@TheRealFalcon TheRealFalcon merged commit fa33131 into canonical:main Feb 14, 2025
22 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Cloud-init should support disabling ZEROCONF
2 participants