94948bb194
via Redfish Manager This patch adds two new capabilities to the Redfish management interface in Ironic for setting the BMC clock: 1. A manual cleaning step (`set_bmc_clock`) that allows operators to set the BMC clock explicitly by providing datetime and timezone offset. 2. An automated verify step (`verify_bmc_clock`) that, if enabled via configuration, sets the BMC clock during node verification using the current UTC time. These steps aim to prevent certificate validation failures caused by incorrect BMC time, particularly when dealing with TLS certificates. A new configuration option `redfish.enable_verify_bmc_clock` has been added to control the automated verify behavior. The minimum version of `sushy` has also been updated to is 5.7.0 to support these features. Related patches: - https://review.opendev.org/c/openstack/sushy/+/950539 (Add support for Manager DateTime fields in sushy) - https://review.opendev.org/c/openstack/sushy-tools/+/950925 (Fix Manager DateTime field handling in sushy-tools) Partial-Bug: #2041904 Change-Id: I75cbd39a60f8470224dc5a2fe0a4f17c22acd1cd Signed-off-by: Queensly Kyerewaa Acheampongmaa <qacheampong@gmail.com>
18 lines
762 B
YAML
18 lines
762 B
YAML
---
|
|
features:
|
|
- |
|
|
Adds two new capabilities to the Redfish managemnet interface
|
|
for managing the BMC clock.
|
|
|
|
1. A manual cleaning step ``set_bmc_clock`` that allows operators
|
|
to set the BMC's hardware clock to a specific datetime (in ISO8601 format),
|
|
optionally including a datetimelocaloffset.
|
|
|
|
2. An automated verify step ``verify_bmc_clock`` that compares the
|
|
BMC's Redfish datetime to the system UTC time, and automatically
|
|
updates the BMC clock if needed. Verification fails if the difference
|
|
exceeds 1 second after the update.
|
|
|
|
These steps helps ensure BMC clock synchronization in baremetal environments
|
|
where incorrect or drifting BMC clocks may lead to TLS certificate validation failures.
|