$ oc describe dv <DataVolume>
oc describe command to analyze and help resolve issues with DataVolumes.
Diagnose DataVolume issues by examining the output of the
generated by the command:
$ oc describe dv <DataVolume>
There are three
Types in the
Conditions section that display:
Events section provides the following additional information:
Type of event
Reason for logging
Source of the event
Message containing additional diagnostic information.
The output from
oc describe does not always contains
An event is generated when either
Both conditions and events react to changes in the state of the DataVolume.
For example, if you misspell the URL during an import operation, the import
generates a 404 message. That message change generates an event with a reason.
The output in the
Conditions section is updated as well.
By inspecting the
Events sections generated by the
command, you determine the state of the DataVolume
in relation to PersistentVolumeClaims (PVCs), and whether or
not an operation is actively running or completed. You might also receive messages
that offer specific details about the status of the DataVolume, and how
it came to be in its current state.
There are many different combinations of conditions. Each must be evaluated in its unique context.
Examples of various combinations follow.
Bound – A successfully bound PVC displays in this example.
Note that the
Bound, so the
If the PVC is not bound, the
When the PVC is bound, an event is generated stating that the PVC is bound.
In this case, the
Message indicates which PVC owns the DataVolume.
Message, in the
Events section, provides further details including how
long the PVC has been bound (
Age) and by what resource (
in this case
Status: Conditions: Last Heart Beat Time: 2020-07-15T03:58:24Z Last Transition Time: 2020-07-15T03:58:24Z Message: PVC win10-rootdisk Bound Reason: Bound Status: True Type: Bound Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Bound 24s datavolume-controller PVC example-dv Bound
Running – In this case, note that
indicating that an event has occurred that caused an attempted
operation to fail, changing the Status from
However, note that
Completed and the
Message field indicates
Events section, the
Message contain additional
troubleshooting information about the failed operation. In this example,
Message displays an inability to connect due to a
404, listed in the
Events section’s first
From this information, you conclude that an import operation was running, creating contention for other operations that are attempting to access the DataVolume:
Status: Conditions: Last Heart Beat Time: 2020-07-15T04:31:39Z Last Transition Time: 2020-07-15T04:31:39Z Message: Import Complete Reason: Completed Status: False Type: Running Events: Type Reason Age From Message ---- ------ ---- ---- ------- Warning Error 12s (x2 over 14s) datavolume-controller Unable to connect to http data source: expected status code 200, got 404. Status: 404 Not Found
Ready – If
True, then the DataVolume is ready
to be used, as in the following example. If the DataVolume is not ready to be
Status: Conditions: Last Heart Beat Time: 2020-07-15T04:31:39Z Last Transition Time: 2020-07-15T04:31:39Z Status: True Type: Ready