The hostname-config.sh script rewrites the hostname and appends #20394
+7
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why I did it
The hostname-config.sh script rewrites the hostname and appends the 127.0.0.1 new hostname mapping to the /etc/hosts list. However, it does not handle the case where the file does not exist, resulting in the hostname not being updated in /etc/hosts.
When /etc/hosts is missing, it causes the sudo command to be blocked for a while and displays an "unable to resolve host" error message.
Work item tracking
How I did it
This patch adds a workaround in hostname-config.sh to create a default /etc/hosts if it does not exist, ensuring the hostname is updated properly.
How to verify it
Which release branch to backport (provide reason below if selected)
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)