Open FarahRasheed1 opened 1 month ago
Pretty sure this is because all chassis resets are routed to one dbus path, not a per-chassis path. I think @wltu had some patches a while back trying to clean this behavior up, but I don't know where they landed.
Thanks for the bug report!
I assume this is also being worked by @mox669 who is doing the multi-host implementation.
Yup, I had found https://gerrit.openbmc.org/c/openbmc/bmcweb/+/45396 which at a first look might fix this bug, but figured since there were no open issues, I may as well open it to keep track of it.
Is this the right place to submit this?
Bug Description
Problem
Sending a POST request to reset an invalid chassis that does not exist returns 200 OK. I reproduced this on QEMU, see logs below.
It looks like the service is not validating the chassis ID correctly for
Chassis.Reset
action , leading it to respond with 200 OK even when the chassis doesn't exist.Curl command:
Response:
Logs
Sep 17 14:48:32 romulus phosphor-chassis-state-manager[291]: Change to Chassis Requested Power State: xyz.openbmc_project.State.Chassis.Transition.PowerCycle
Version
Additional Information
No response