Command Reference: edf report ready

Description

The edf report ready command checks whether or not certain control-plane HPE Ezmeral Data Fabric on Kubernetes cluster components, such as CLDB and MFS pods, are ready for an upgrade or maintenance procedure.

When you use the edf shutdown cluster command, pods are shut down and are rebooted, but the pods are put into a wait state immediately after the reboot, which prevents the pods from becoming operational. You use the edf report ready to determine if pods have rebooted and are ready for you to continue with your upgrade or maintenance procedure.

Usage

This command must be executed from the admincli pod of a Kubernetes Data Fabric cluster.

This command can take a couple of minutes to complete. You might notice a delay between the display of the second and the third lines of the output. If the pods are ready for upgrade, you can proceed with upgrade or other maintenance tasks.

Example

The following example shows the output when the pods are not ready:

edf report ready
2021/06/14 23:22:34 [edf reports]: [INFO] Checking if pods are stabilized for upgrade. This may take a minute or two.
2021/06/14 23:22:35 [edf reports]: [INFO] Valid MapR user ticket found, skipping ticket generation
2021/06/14 23:24:31 [edf reports]: [ERROR] Pods are not ready for upgrade
2021/06/14 23:24:31 [edf reports]: [ERROR] Check out /tmp/report-20210614232234 for details

The following example shows the output when the pods are ready:

edf report ready
2021/06/14 23:28:01 [edf reports]: [INFO] Checking if pods are stabilized for upgrade. This may take a minute or two.
2021/06/14 23:28:02 [edf reports]: [INFO] Valid MapR user ticket found, skipping ticket generation
2021/06/14 23:29:52 [edf reports]: [INFO] Pods are ready