Skip to content

Provide call to action any time a we are in a "wait" phase where the process hasn't started in several minutes. #1107

Description

@djwhatle

First implementation for rsync transfer pod is here: #1099

Other places I think we want to provide the user with a warning and a command they can run to troubleshoot when things aren't moving along like we expect:

  • WaitForStaleStagePodsTerminated (if stage pods haven't terminated in 3 minutes)
  • StagePodsCreated (if stage pods aren't all running in 3 minutes)
  • WaitForResticReady (if restic hasn't fully started in 3 minutes)
  • WaitForVeleroReady (if velero hasn't started in 3 minutes)
  • EnsureCloudSecretPropagated (if cloud secret hasn't propagated in 3 minutes)
  • EnsureQuiesced (if applications aren't quiesced in 3 minutes)
  • StageBackupCreated (if backup hasn't started running in 3 minutes)
  • StageRestoreCreated (if restore hasn't started running in 3 minutes)
  • EnsureStagePodsTerminated (if stage pods aren't gone after 3 minutes)
  • Hook Phases (if hook job hasn't at least started running after 3 minutes)
  • FinalRestoreCreated (if restore hasn't started running after 3 minutes)
  • InitialBackupCreated (if backup hasn't started running after 3 minutes)
  • EnsureMigratedDeleted (if rollback hasn't reduced the number of remaining resources in 3 minutes)
  • Anything in DVM that doesn't already have this type of warning in place

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/featureCategorizes issue or PR as related to a new feature.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions