Reduce the log level for UBA connection failures from Error to Warning so that cooks are not failed if you are offline or lose connection during a build.

Development Pipeline & Plugins
, ,
1

Hi all!

The log level of Error in the UBA connection failure can cause log monitoring components in BuildGraph/UAT to fail an otherwise successful cook, if you fail to connect to UBA.

Since UBA is not essential and the cook can just complete the work locally, this failure seems too severe and should instead be logged as a warning.

I observed this happen after we had set up UBA with a server endpoint that requires a VPN connection. I started my build via BuildGraph that included compilation + cook. I started while connected to VPN, but some time during compilation I lost connection. The build proceeded to the cook stage, but then could not contact Horde, and ultimately failed the build right at the end due to the error log from LogUbaHorde, even though the cook was successful.

I have raised a PR on Github to show the suggested fix for this https://github.com/EpicGames/UnrealEngine/pull/14363/changes

Cheers!

[Attachment Removed]

2

Steps to Reproduce
Add a simple Horde config to your games’ `DefaultEngine.ini`

[Horde]
ServerUrl="https://www.example.com/"

Run a cook using BuildGraph

UBA will fail to connect to the provided Server URL and you will see this in the log at the end of the cook

LogInit: Display: Warning/Error Summary (Unique only)
LogInit: Display: -----------------------------------
LogInit: Display: LogUbaHorde: Error: Failed to create HttpClient for UbaAgent

The cook will complete successfully but the overall build will fail as there was a UBA connection error

[Attachment Removed]

3

Hi Jacob, thank you for the PR we have assigned to a team member and will completing that merge soon.

Thanks

Matthew

[Attachment Removed]