| commit | 1940677a35870b51eaffc50406609124668743d0 | [log] [tgz] |
|---|---|---|
| author | Gunnar Mills <gmills@us.ibm.com> | Tue Mar 04 14:42:46 2025 -0600 |
| committer | Gunnar Mills <gmills@us.ibm.com> | Tue Mar 04 15:06:41 2025 -0600 |
| tree | 0e3b428812610dddfbdf306b43d24e5ff95974c8 | |
| parent | da9dc905da4e6d30125bcca160537cf2cdb2ddf4 [diff] |
Up the default code update timeout This timer is the time to write the image to /tmp/images/, the code update app to untar and create a xyz.openbmc_project.Software.Activation interface. We have seen this take just over 25 seconds a few times, in one case it took 30 seconds, and this times out. We are using a large image, 150MB+, and other requests are going on but believe our use case is valid, so bump the default timeout to 50 seconds. In the times it has timed out, the time appears split between 1 and 2. With 1) writing the image to /tmp/images and inotify firing and 2) phosphor-version-software-manager untarring the image and creating the interface. In the future this code should go away with the new code update, this commit is more to note code updates can be slow due to the BMC's limited resources and larger code update images exist. ``` // Can conclude the timer was set at 13:55:27... Wed Feb 5 13:55:42 2025 xxx phosphor-version-software-manager: Untaring /tmp/images/f285ea12-b506-4182-86bc-b9706f09bc1f to /tmp/images/imagek9D7Iu Wed Feb 5 13:55:52 2025 xxx bmcweb: [ERROR update_service.hpp:427] FW image may has already been uploaded to server Wed Feb 5 13:55:52 2025 xxx bmcweb: [ERROR update_service.hpp:426] Timed out waiting for firmware object being created Wed Feb 5 13:55:52 2025 xxx bmcweb: [CRITICAL error_messages.cpp:287] Internal Error /usr/src/debug/bmcweb/1.0+git/redfish-core/lib/update_service.hpp(438:41) `void redfish::afterAvailbleTimerAsyncWait(const std::shared_ptr<bmcweb::AsyncResp>&, const boost::system::error_code&)`: ``` Tested: Since bumping this timeout haven't hit this timeout. Change-Id: I9f2ce9a24a55d72484113b3fbe226dc76b0bd2a5 Signed-off-by: Gunnar Mills <gmills@us.ibm.com>
This component attempts to be a "do everything" embedded webserver for OpenBMC.
The webserver implements a few distinct interfaces:
bmcweb at a protocol level supports http and https. TLS is supported through OpenSSL.
Bmcweb supports multiple authentication protocols:
Each of these types of authentication is able to be enabled or disabled both via runtime policy changes (through the relevant Redfish APIs) or via configure time options. All authentication mechanisms supporting username/password are routed to libpam, to allow for customization in authentication implementations.
All authorization in bmcweb is determined at routing time, and per route, and conform to the Redfish PrivilegeRegistry.
*Note: Non-Redfish functions are mapped to the closest equivalent Redfish privilege level.
bmcweb is configured per the meson build files. Available options are documented in meson_options.txt
meson setup builddir ninja -C builddir
If any of the dependencies are not found on the host system during configuration, meson will automatically download them via its wrap dependencies mentioned in bmcweb/subprojects.
bmcweb relies on some on-system data for storage of persistent data that is internal to the process. Details on the exact data stored and when it is read/written can seen from the persistent_data namespace.
When SSL support is enabled and a usable certificate is not found, bmcweb will generate a self-signed a certificate before launching the server. Please see the bmcweb source code for details on the parameters this certificate is built with.
bmcweb is capable of aggregating resources from satellite BMCs. Refer to AGGREGATION.md for more information on how to enable and use this feature.