Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Redfish BMC update fails. #301

Open
M-Kamalesh opened this issue Mar 1, 2025 · 1 comment
Open

Redfish BMC update fails. #301

M-Kamalesh opened this issue Mar 1, 2025 · 1 comment

Comments

@M-Kamalesh
Copy link

I am using AST2500, updated my code base recently to jan2025 openbmc source code. After that BMC redfish update worked but BIOS and CPLD upgrade failed throwing error in phosphor-software-manager, then came to know there is some update in code-update process recently.
Then I removed that new way of code update in phosphor-software-manager_%.bbappend file

PACKAGECONFIG:remove = "software-update-dbus-interface"

Then tried updating BMC, BIOS and CPLD via redfish now Iam facing issue in bmcweb side. The error message is

{
  "error": {
    "@Message.ExtendedInfo": [
      {
        "@odata.type": "#Message.v1_1_1.Message",
        "Message": "The request failed due to an internal service error.  The service is still operational.",
        "MessageArgs": [],
        "MessageId": "Base.1.19.InternalError",
        "MessageSeverity": "Critical",
        "Resolution": "Resubmit the request.  If the problem persists, consider resetting the service."
      }
    ],
    "code": "Base.1.19.InternalError",
    "message": "The request failed due to an internal service error.  The service is still operational."
  }

Sharing the bmcweb log also

Jan 22 18:31:44 xxxxxx bmcwebd[239]: [INFO http_connection.hpp:272] Request:  0x2453180 HTTP/1.1 POST /redfish/v1/UpdateService/update ::ffff:10.10.84.44
Jan 22 18:31:44 xxxxxx bmcwebd[239]: [DEBUG http_connection.hpp:305] Setting completion handler
Jan 22 18:31:44 xxxxxx bmcwebd[239]: [DEBUG http_response.hpp:258] 0x2457118 setting completion handler
Jan 22 18:31:44 xxxxxx bmcwebd[239]: [DEBUG routing.hpp:653] Matched rule '/redfish/v1/UpdateService/update/' POST / 32
Jan 22 18:31:44 xxxxxx bmcwebd[239]: [DEBUG dbus_privileges.hpp:50] userName = root userRole = priv-admin
Jan 22 18:31:44 xxxxxx bmcwebd[239]: [DEBUG query.hpp:123] setup redfish route
Jan 22 18:31:44 xxxxxx bmcwebd[239]: [DEBUG update_service.hpp:1045] doPost: contentType=application/octet-stream
Jan 22 18:31:44 xxxxxx bmcwebd[239]: [WARNING parsing.hpp:34] Failed to parse content type on request
Jan 22 18:31:45 xxxxxx bmcwebd[239]: [ERROR update_service.hpp:897] error_code = Invalid request descriptor [generic:53]
Jan 22 18:31:45 xxxxxx bmcwebd[239]: [ERROR update_service.hpp:898] error msg = Invalid request descriptor
Jan 22 18:31:45 xxxxxx bmcwebd[239]: [CRITICAL error_messages.cpp:1356] Internal Error /usr/src/debug/bmcweb/1.0+git/redfish-core/lib/update_service.hpp(899:32) `void redfish::handleBMCUp
date(const std::shared_ptr<bmcweb::AsyncResp>&, task::Payload, const MemoryFileDescriptor&, const std::string&, const boost::system::error_code&, const dbus::utility::MapperEndPoints&)`:
Jan 22 18:31:45 xxxxxx bmcwebd[239]: [DEBUG http_response.hpp:248] 0x2457118 calling completion handler
Jan 22 18:31:45 xxxxxx bmcwebd[239]: [DEBUG http_response.hpp:251] 0x2457118 completion handler was valid
Jan 22 18:31:45 xxxxxx bmcwebd[239]: [DEBUG http_response.hpp:86] Moving response containers; this: 0x24553a8; other: 0x2457118
Jan 22 18:31:45 xxxxxx bmcwebd[239]: [INFO complete_response_fields.hpp:23] Response: 500
Jan 22 18:31:45 xxxxxx bmcwebd[239]: [DEBUG http_connection.hpp:696] 0x2453180 doWrite
Jan 22 18:31:45 xxxxxx bmcwebd[239]: [DEBUG http_connection.hpp:768] 0x2453180 timer started
Jan 22 18:31:45 xxxxxx bmcwebd[239]: [INFO http_body.hpp:185] Returning 596 bytes more=false
Jan 22 18:31:45 xxxxxx bmcwebd[239]: [DEBUG http_response.hpp:258] 0x24553a8 setting completion handler
Jan 22 18:31:45 xxxxxx bmcwebd[239]: [DEBUG http_connection.hpp:650] 0x2453180 async_write wrote 908 bytes, ec=Success [system:0]
Jan 22 18:31:45 xxxxxx bmcwebd[239]: [DEBUG http_connection.hpp:684] 0x2453180 Clearing response
Jan 22 18:31:45 xxxxxx bmcwebd[239]: [DEBUG http_response.hpp:210] 0x24553a8 Clearing response containers
Jan 22 18:31:45 xxxxxx bmcwebd[239]: [DEBUG http_connection.hpp:566] 0x2453180 doReadHeaders
Jan 22 18:31:45 xxxxxx bmcwebd[239]: [DEBUG http_connection.hpp:740] 0x2453180 Timer canceled
Jan 22 18:31:45 xxxxxx bmcwebd[239]: [DEBUG http_connection.hpp:490] 0x2453180 async_read_header 0 Bytes
Jan 22 18:31:45 xxxxxx bmcwebd[239]: [WARNING http_connection.hpp:510] 0x2453180 End of stream, closing end of stream [beast.http:1 at /usr/include/boost/beast/http/impl/read.hpp:241:21 i
n function 'void boost::beast::http::detail::read_some_op<AsyncReadStream, DynamicBuffer, isRequest>::operator()(Self&, boost::beast::error_code, std::size_t)']
Jan 22 18:31:45 xxxxxx bmcwebd[239]: [DEBUG http_connection.hpp:354] 0x2453180 Closing socket
Jan 22 18:31:45 xxxxxx bmcwebd[239]: [DEBUG http_response.hpp:269] 0x24553a8 releasing completion handlerfalse
Jan 22 18:31:45 xxxxxx bmcwebd[239]: [DEBUG http_connection.hpp:84] 0x2453180 Connection closed, total 0

I need to know is there anything needed to change in bmcweb side to make work BMC, BIOS and CPLD update via redfish. Like I have changed added change in phosphor-software-manager.
please let me know what things need to be checked for this error.

@edtanous
Copy link
Contributor

edtanous commented Mar 1, 2025

Please fill out the issue template, and include things like which sha1 of openbmc you used, and which machine you built for. “Updated my codebase” makes it sound like you have a fork, in which case this is not a general support forum, but a support forum for openbmc. You are also free to file a bug with whatever issue tracking your fork utilizes.

I do not believe upstream has ever supported cpld update, so you would need to triage your own code modifications there. There are a number of options that could’ve caused what you’re seeing above, but this is not a general support forum and nobody can effectively triage code that is only in your repo. Please try to reproduce on qemu of an upstream system and report the result. If it reproduces there, there’s likely a lot more people that can help.

Will leave open for 1 week to give you a chance to reproduce.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants