1030-ips: dev ACF can't initiate dump

[ChicagoDuan]

We are unable to initiate dump using the dev acf file, and the web prompts a "Invalid password"

Expected Behavior

Successfully 'Initiate dump' using the generated dev acf file.

Actual Behavior

The dev acf file can be used to login to ASMI, but when we click "Initiate dump" button, we get a "Invalid password" error.
And we will see a pldm error:
Apr 18 11:11:19 p10bmc pldmd[696]: fileAckWithMetaData with token: 4294967295 and status: 1(AcfFileInvalid)

Steps to Reproduce the Problem

1. We followed this step to create and setup the ACF file: https://github.com/ibm-openbmc/ibm-acf/tree/1030.ips#how-to-setup-this-feature
2. Login as service account to eBMC GUI
3. Navigate to Logs ->Dumps
4. Select "Resource Dump" dump type
5. Enter "serialctl -hyp -assign" as the resource selector and enter the ACF Password into the "Password" field and select "Initiate dump" to enable the PHYP console.
6. Error occurred: "Error initiating dump.Invalid password"

[ChicagoDuan]

@mzipse Can you give us some help with this issue? Thanks.

[ChicagoDuan]

@manojkiraneda We saw a pldm error,:
Apr 18 11:11:19 p10bmc pldmd[696]: fileAckWithMetaData with token: 4294967295 and status: 1(AcfFileInvalid)
Can you give us some help with this error? Thanks

[mzipse]

@ChicagoDuan , I assume you have already disabled field mode, correct? Some info from one of our developers...

Not sure where it is failing exactly but one thought is development-key requires field mode = false. Easy enough to check/set.
Get field mode property
busctl get-property xyz.openbmc_project.Software.BMC.Updater /xyz/openbmc_project/software xyz.openbmc_project.Control.FieldMode FieldModeEnabled
Set field mode property
busctl set-property xyz.openbmc_project.Software.BMC.Updater /xyz/openbmc_project/software xyz.openbmc_project.Control.FieldMode FieldModeEnabled b false

[mzipse]

Nevermind. Just saw your steps. Looks like you have field mode disabled. Still investigating.

[ChicagoDuan]

Hi @mzipse , with the help of YangMing and the IBM team, we have resolved this issue. Thank you