ff137a8e56
- What I did This fix removes the possibility of 'localhost' entry getting removed from /etc/hosts file by hostname-config service. Without this change, whenever we change the hostname from 'localhost' to any other name on the config_db.json and reload the config, /etc/hosts file will only have the new hostname on it. But there are multiple sonic utilities (eg: swssconfig) which relies on the hard coded 'localhost' name and they tend to stop working. - How I did it Added a new check on hostname-config.sh script to avid blindly deleting the line containing the old hostname from /etc/hosts file. Now it will delete the old hostname only if its not localhost or when the hostname is not changing. - How to verify it Bring up SONiC on a device with hostname as localhost Edit /etc/sonic/config_db.json to update the 'hostname' filed under DEVICE_METADATA from "hostname" : "localhost" --> "hostname" : "sonic" run config reload -y to reflect the hostname change done on config_db.json file. cat /etc/hosts and check whether both 127.0.0.1 localhost and 127.0.0.1 sonic entry are present on the file. ping localhost should work fine. - Description for the changelog Make hostname-config service more robust in handling SONiC hostname change from localhost to anything else. |
||
|---|---|---|
| .. | ||
| apt | ||
| asn | ||
| bash | ||
| caclmgrd | ||
| cron.d | ||
| ebtables | ||
| environment | ||
| hostcfgd | ||
| hostname | ||
| interfaces | ||
| logrotate | ||
| monit | ||
| ntp | ||
| platform | ||
| process-reboot-cause | ||
| rsyslog | ||
| snmp | ||
| sudoers | ||
| systemd | ||
| updategraph | ||
| warmboot-finalizer | ||