[RFE] Remotely set the Redfish BMC clock

Bug #2041904 reported by Julia Kreger
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ironic
Triaged
Wishlist
Unassigned
Sushy
Triaged
Wishlist
Unassigned

Bug Description

During the PTG (https://etherpad.opendev.org/p/ironic-ptg-october-2023), it was discussed that how setting the BMC clock would prevent issues with short lived x509 certificates and TLS endpoints which were being accesssed by the BMC. For example: If your using virtual media, the and the clock is not right, then it would be problematic if the HTTPS certificate on the server is only valid for a short period of time.

In order to prevent a human from having to fix the clock, the right course of action seems to be to add support to post the time to the BMC on the management endpoint. This may not impact the overall system clock. That is a vendor specific behavior and cannot be standardized upon, but the internal OS runtime clock of the BMC's OS seems like an easy thing to address as part of a step in the redfish driver, if available.

https://redfish.dmtf.org/schemas/v1/Manager.v1_18_0.json

Related: https://redfishforum.com/thread/910/mechanism-set-hardware-clock-redfish

description: updated
summary: - [RFE] Remotely set the BMC clock
+ [RFE] Remotely set the Redfish BMC clock
Dmitry Tantsur (divius)
Changed in ironic:
status: New → Triaged
Changed in sushy:
status: New → Triaged
Changed in ironic:
importance: Undecided → Wishlist
Changed in sushy:
importance: Undecided → Wishlist
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.