status
dpsctl resource-group status Usage Guide
Query the status of an ongoing asynchronous resource group operation.
Usage
dpsctl resource-group status [operation-id]Flags
Includes global dpsctl options.
Query by Operation ID
--operation-id string operation id
Query by Resource Group
--operation-type string operation type ('activate' or 'update')
--resource-group string resource group name
--help, -h show helpExamples
Check Operation Status
$ dpsctl resource-group status op-12345
{
"operation_id": "op-12345",
"status": "in_progress",
"progress": {
"completed": 5,
"total": 10,
"percentage": 50
},
"message": "Configuring power policies on nodes",
"started_at": "2024-01-15T10:30:00Z",
"details": {
"resource_group": "ml-training-job",
"operation_type": "activate"
}
}Completed Operation
$ dpsctl resource-group status op-67890
{
"operation_id": "op-67890",
"status": "completed",
"progress": {
"completed": 10,
"total": 10,
"percentage": 100
},
"message": "Resource group activation completed successfully",
"started_at": "2024-01-15T10:25:00Z",
"completed_at": "2024-01-15T10:27:30Z",
"duration": "2m30s"
}Failed Operation
$ dpsctl resource-group status op-99999
{
"operation_id": "op-99999",
"status": "failed",
"progress": {
"completed": 3,
"total": 8,
"percentage": 37
},
"message": "BMC connection failed for node004",
"error": "Failed to connect to BMC at https://node004-bmc.example.com: connection timeout",
"started_at": "2024-01-15T10:20:00Z",
"failed_at": "2024-01-15T10:22:15Z"
}Operation Not Found
$ dpsctl resource-group status op-invalid
{
"status": {
"ok": false,
"diag_msg": "Operation 'op-invalid' not found"
}
}Notes
- Operation IDs are returned from asynchronous resource group operations
- Status can be:
in_progress,completed,failed, orcancelled - Progress information includes completion percentage and node counts
- Failed operations include error details for troubleshooting
- Operation history is retained for a limited time (typically 24 hours)