tree 0e3b428812610dddfbdf306b43d24e5ff95974c8
parent da9dc905da4e6d30125bcca160537cf2cdb2ddf4
author Gunnar Mills <gmills@us.ibm.com> 1741120966 -0600
committer Gunnar Mills <gmills@us.ibm.com> 1741122401 -0600

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>