openbmc / bmcweb

A do everything Redfish, KVM, GUI, and DBus webserver for OpenBMC
Apache License 2.0
154 stars 131 forks source link

Not found error response with BMC dump URI #194

Closed rahulmah closed 3 years ago

rahulmah commented 3 years ago

Started seeing "Not found" response with the recent master build(2.10.0-dev-836-g06dc92d6f) for BMC dump URI.

bash-4.2$ curl -k -H "X-Auth-Token: $bmc_token" -X GET https://${BMC_IP}/redfish/v1/Managers/bmc/LogServices/Dump/Entries
Not Found

bash-4.2$ curl -k -H "X-Auth-Token: $bmc_token" -X GET https://${BMC_IP}/redfish/v1/Managers/bmc/LogServices/Dump/
Not Found

bash-4.2$ curl -k -H "X-Auth-Token: $bmc_token" -X GET https://${BMC_IP}/redfish/v1/Managers/bmc/LogServices/
{
  "@odata.id": "/redfish/v1/Managers/bmc/LogServices",
  "@odata.type": "#LogServiceCollection.LogServiceCollection",
  "Description": "Collection of LogServices for this Manager",
  "Members": [],
  "Members@odata.count": 0,
  "Name": "Open BMC Log Services Collection"
}

$ curl -k -H "X-Auth-Token: $bmc_token" -X POST https://${BMC_IP}/redfish/v1/Managers/bmc/LogServices/Dump/Actions/Oem/OemLogService.CollectDiagnoticData -d '{"DiagnosticDataType" : "Manager", "OEMDiagnosticDataType": ""}'
Not Foundbash-4.2$ curl -k -H "X-Auth-Token: $bmc_token" -X POST https://${BMC_IP}/redfish/v1/Managers/bmc/LogServices/Dump/Actions/LogService.CollectDiagn -d '{"DiagnosticDataType":"Manager"}'
Not Foundbash-4.2
$
edtanous commented 3 years ago

Please edit your original message and fill out the required bug template with the information it requests.

raviteja-b commented 3 years ago

Bmcweb redfish-dump-log flag is disabled by default, this flag needs to be enabled for compiling Bmcweb with dump code. seems in openbmc master Bmcweb recipe does not include this flag

edtanous commented 3 years ago

Closing due to lack of response from submitter, and the failure to use the template. Feel free to reopen once you've followed the template.

rahulmah commented 3 years ago

@edtanous : I don't have permission to reopen this issue. So opened a new defect (https://github.com/openbmc/bmcweb/issues/198) with correct defect templet.