D-Bus set-property call to set an attribute in PendingAttributes table has unclear behavior.

[souvik1914581]

Issue:

1. Try to set hb_field_core_override attribute using a set-property call using following query:
   busctl set-property xyz.openbmc_project.BIOSConfigManager /xyz/openbmc_project/bios_config/manager xyz.openbmc_project.BIOSConfig.Manager PendingAttributes a{s\(sv\)} 1 "hb_field_core_override" "xyz.openbmc_project.BIOSConfig.Manager.AttributeType.Integer" i 2
   The busctl call above succeeds.
2. Observe journal log to see pldmd sets the value to 0.
3. pldmd[823]: BIOS attribute 'hb_field_core_override' updated to value '0' by BMC 'true'
4. The attribute value always gets set to 0 if we use i, regardless of the value argument given after i, but the busctl call succeeds. There is no indication to the caller that value 0 has been set.
5. To set the required value we need to use following query: busctl set-property xyz.openbmc_project.BIOSConfigManager /xyz/openbmc_project/bios_config/manager xyz.openbmc_project.BIOSConfig.Manager PendingAttributes a{s\(sv\)} 1 "hb_field_core_override" "xyz.openbmc_project.BIOSConfig.Manager.AttributeType.Integer" x 2

Expectation:

busctl set-property should fail if busctl set-property call is executed using i instead of x or it should set the value specified by i argument.

[mdmillerii]

For the casual reader, i is int32 and x int64 .
https://dbus.freedesktop.org/doc/dbus-specification.html

[manojkiraneda]

I debugged the today, looks like it's probably a bug in sdbusplus. The application seems to get an int64_t type with the value 0 despite providing the signature i.

@williamspatrick can you take a look at this ?