In a few areas, when updating runtime configure, a new config uuid is used (not the uuid set to target uuid). The new uuid is generaged randomly, this causes issues:
1. if update requires a reboot but the new uuid does not come with reboot required bit, it will looks like the config is up to date, but system is not.
2. if update does not require a reboot but the new uuid comes with reboot require bit, the node becomes "config changed reboot required", until a reboot occurs.
In a few areas, when updating runtime configure, a new config uuid is used (not the uuid set to target uuid). The new uuid is generaged randomly, this causes issues:
1. if update requires a reboot but the new uuid does not come with reboot required bit, it will looks like the config is up to date, but system is not.
2. if update does not require a reboot but the new uuid comes with reboot require bit, the node becomes "config changed reboot required", until a reboot occurs.