Google Git
Sign in
gbmc / gbmcweb / 5c551ad4f20007f661eb9634063a510f53e7d918
commit5c551ad4f20007f661eb9634063a510f53e7d918[log] [tgz]
authorgBMC Team <gbmc-core@google.com>Fri Oct 17 15:02:27 2025 -0700
committerCopybara-Service <copybara-worker@google.com>Fri Oct 17 15:03:14 2025 -0700
treef139e0042310d08883851d5e8b1e3896dc5bb38f
parenta2b31213608d8e269268c1756bf71803bf463e5d [diff]
Automated g4 rollback of changelist 820752538.

*** Reason for rollback ***

Autorollback has determined with high confidence that [cl/820752538](http://cl/820752538) has broken the TAP targets listed below. Autorollback is designed to address the situations where inaccuracy is most common, but you could still get unlucky.

[cl/820752538](http://cl/820752538) has been rolled back.

*To reverse this rollback*, the *author* of the CL can send an [UndoAutorollback request](http://go/undo-tap-autorollback)

NOTE! CLs sent with [TBR](https://goto2.corp.google.com/TBR) must be reviewed after-the-fact -- giving your LGTM does not mean you agree with the rollback, but simply acknowledges that you are aware of it. You will not be able to remove yourself from the attention set until you LGTM it.

TAP Autorollback strongly suspects that at least one of the following TAP targets was broken by [cl/820752538](http://cl/820752538):
  1. //platforms/syshealth/netdoc/injectors/pictor_collector:pictor_collector_main ([Investigate](https://dashboards.corp.google.com/_26a783b8_f185_4d7c_9d42_273c59ef8981?p=FINGERPRINT:14683431245238958917&p=CULPRIT:820752538&f=target:eq://platforms/syshealth/netdoc/injectors/pictor_collector:pictor_collector_main&f=flags:eq:CAgQAogBAQ%3D%3D))
  2. //platforms/syshealth/netdoc/injectors/pictor_collector/helpers:pictor_local_lib_test ([Investigate](https://dashboards.corp.google.com/_26a783b8_f185_4d7c_9d42_273c59ef8981?p=FINGERPRINT:4548448836537397275&p=CULPRIT:820752538&f=target:eq://platforms/syshealth/netdoc/injectors/pictor_collector/helpers:pictor_local_lib_test&f=flags:eq:CAgQAogBAQ%3D%3D))
  3. //production/borg/pod/datacenter-software/pictor-collector:checkargs_11_test ([Investigate](https://dashboards.corp.google.com/_26a783b8_f185_4d7c_9d42_273c59ef8981?p=FINGERPRINT:7991455891961730037&p=CULPRIT:820752538&f=target:eq://production/borg/pod/datacenter-software/pictor-collector:checkargs_11_test&f=flags:eq:CAMQAg%3D%3D))
  4. //platforms/syshealth/netdoc/injectors/pictor_collector:pictor_orion_fetcher_test ([Investigate](https://dashboards.corp.google.com/_26a783b8_f185_4d7c_9d42_273c59ef8981?p=FINGERPRINT:7178284852188168336&p=CULPRIT:820752538&f=target:eq://platforms/syshealth/netdoc/injectors/pictor_collector:pictor_orion_fetcher_test&f=flags:eq:CAgQAogBAQ%3D%3D))
  5. //platforms/syshealth/netdoc/injectors/pictor_collector:pictor_collector_main ([Investigate](https://dashboards.corp.google.com/_26a783b8_f185_4d7c_9d42_273c59ef8981?p=FINGERPRINT:14683431245238958917&p=CULPRIT:820752538&f=target:eq://platforms/syshealth/netdoc/injectors/pictor_collector:pictor_collector_main&f=flags:eq:CAMQAg%3D%3D))

See all potential target breakages [here](https://dashboards.corp.google.com/_66539fc6_9f33_40c8_9e29_a4c9a36ab87f?p=CHANGELIST:820752538). We had 5 pieces of evidence when we created this message.

Feedback: [go/tapautorollback-faq#how-can-i-give-feedback](http://go/tapautorollback-faq#how-can-i-give-feedback)

*** Original change description ***

Replace hostname with entity ID in FeedPayload

So that HDB can get the correct device name from feed.

Tested:
Unit tests

***

PiperOrigin-RevId: 820841771
Change-Id: Ia51bab480cbc04b7d97f87ce19939859c98768e8
1 file changed
tree: f139e0042310d08883851d5e8b1e3896dc5bb38f
  1. .github/
  2. config/
  3. g3/
  4. http/
  5. include/
  6. install/
  7. plugins/
  8. redfish-core/
  9. redfish_authorization/
  10. scripts/
  11. src/
  12. static/
  13. subprojects/
  14. test/
  15. tlbmc/
  16. .clang-format
  17. .clang-tidy
  18. .clang-tidy-ignore
  19. .dockerignore
  20. .gitignore
  21. .markdownlint.yaml
  22. .openbmc-enforce-gitlint
  23. .openbmc-no-clang
  24. .openbmc-no-sanitize
  25. .prettierignore
  26. .shellcheck
  27. AGGREGATION.md
  28. CLIENTS.md
  29. COMMON_ERRORS.md
  30. copy.bara.sky
  31. DBUS_USAGE.md
  32. DEVELOPING.md
  33. gcovr.cfg
  34. HEADERS.md
  35. LICENSE
  36. meson.build
  37. meson_options.txt
  38. OEM_SCHEMAS.md
  39. OWNERS
  40. PLUGINS.md
  41. README.md
  42. README_GOOGLE.md
  43. Redfish.md
  44. run-ci
  45. setup.cfg
  46. TESTING.md
  47. UNIT_TESTING.md
README.md

OpenBMC webserver

This project is Google's version of BMCWeb.

See Readme Google for Google added features. The following is the original README of OpenBMC/BMCWeb.

==============================================================================

This component attempts to be a “do everything” embedded webserver for OpenBMC.

Features

The webserver implements a few distinct interfaces:

  • DBus event websocket. Allows registering on changes to specific dbus paths, properties, and will send an event from the websocket if those filters match.
  • OpenBMC DBus REST api. Allows direct, low interference, high fidelity access to dbus and the objects it represents.
  • Serial: A serial websocket for interacting with the host serial console through websockets.
  • Redfish: A protocol compliant, DBus to Redfish translator.
  • KVM: A websocket based implementation of the RFB (VNC) frame buffer protocol intended to mate to webui-vue to provide a complete KVM implementation.

Protocols

bmcweb at a protocol level supports http and https. TLS is supported through OpenSSL.

AuthX

Authentication

Bmcweb supports multiple authentication protocols:

  • Basic authentication per RFC7617
  • Cookie based authentication for authenticating against webui-vue
  • Mutual TLS authentication based on OpenSSL
  • Session authentication through webui-vue
  • XToken based authentication conformant to Redfish DSP0266

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.

Authorization

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.

Configuration

bmcweb is configured per the meson build files. Available options are documented in meson_options.txt

Compile bmcweb with default options

meson 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.

Use of persistent data

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.

TLS certificate generation

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.

Redfish Aggregation

bmcweb is capable of aggregating resources from satellite BMCs. Refer to AGGREGATION.md for more information on how to enable and use this feature.