Post by iamsarki on Oct 23, 2024 9:50:10 GMT
Hi,
When a client initiates an update that involves restarting the Redfish service, how should the related TaskMonitor behave?
The current flow is as follows:
- The update is started.
- A task is created, and the TaskMonitor responds with a 202 status.
- The service restarts due to the update, and the TaskMonitor responds with a 503 status and a "ServiceTemporarilyUnavailable" message.
- Once the service is back online, the TaskMonitor responds again.
Is this behavior correct?
When a client initiates an update that involves restarting the Redfish service, how should the related TaskMonitor behave?
The current flow is as follows:
- The update is started.
- A task is created, and the TaskMonitor responds with a 202 status.
- The service restarts due to the update, and the TaskMonitor responds with a 503 status and a "ServiceTemporarilyUnavailable" message.
- Once the service is back online, the TaskMonitor responds again.
Is this behavior correct?
