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

Removed extra 'ip addr del' on the lo inteface #15463

Conversation

kenneth-arista
Copy link
Contributor

Why I did it

The 'post-up ip addr del 127.0.0.1/8 dev lo' was thought to be required when the loopback interface subnet mask was narrowed from /8 to /16 (#5353). After testing first reboot, subsequent reboots, config reloads, and systemctl restart networking on linecards and supevisors (DNX VOQ chassis), this cleanup command does not appear to be required.

This change removes the delete command as well as reverts #15080.

Work item tracking
  • Microsoft ADO (number only):

How I did it

How to verify it

Confirmed that ssh connections from supervisor to linecards can be established after first boot, subsequent reboots, config reload and systemctl restart networking tampers.

Which release branch to backport (provide reason below if selected)

  • 201811
  • 201911
  • 202006
  • 202012
  • 202106
  • 202111
  • 202205
  • 202211

Tested branch (Please provide the tested image version)

Description for the changelog

Link to config_db schema for YANG module changes

A picture of a cute animal (not mandatory but encouraged)

The 'post-up ip addr del 127.0.0.1/8 dev lo' was thought to be required
when the loopback interface subnet mask was narrowed from /8 to /16.
After testing first reboot, subsequent reboots, config reloads, and
systemctl restart networking on linecards and supevisors (DNX VOQ
chassis), this cleanup command does not appear to be required. As such,
this change removes it as well as reverts
sonic-net#15080.
@kenneth-arista
Copy link
Contributor Author

Tagging @saiarcot895 @arlakshm

@kenneth-arista
Copy link
Contributor Author

Had an offline discussion with @saiarcot895. This PR doesn't solve the problem he was originally chasing with respect to uninterrupted connectivity to 127.0.0.1. #15080 is the right solution. Closing this PR.

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.

1 participant