tree 4014cc012a4c217a83a9f556c4e90c57d13f8bbf
parent d59006aec9b402eee63c56f6f480f95d96096283
author Potin Lai <potin.lai@quantatw.com> 1648538215 +0800
committer Potin Lai <potin.lai@quantatw.com> 1648539643 +0800

host-state-manager: fix host0 failure with reading wrong object path

Assign host id into both both chassis service name and object path

Because chassis-state-manager requests two service names (with and
without id) when host id is 0, it does not need to switch back to
"xyz.openbmc_project.State.Chassis" for host0 anymore.

Tested on witherspoon qemu:
root@witherspoon:~# journalctl -u xyz.openbmc_project.State.Host@0.service
Mar 29 07:40:20 witherspoon systemd[1]: Starting Phosphor Host0 State Manager...
Mar 29 07:40:23 witherspoon phosphor-host-state-manager[396]: Check if host is running
Mar 29 07:40:23 witherspoon phosphor-host-state-manager[396]: Chassis power not on, exit
Mar 29 07:40:23 witherspoon phosphor-host-state-manager[396]: Initial Host State will be Off
Mar 29 07:40:23 witherspoon systemd[1]: Started Phosphor Host0 State Manager.

Signed-off-by: Potin Lai <potin.lai@quantatw.com>
Change-Id: Ib5875f2f661c434508a4f108ae7f889532d48efc