Skip to content

Commit

Permalink
Update Troubleshooting guide
Browse files Browse the repository at this point in the history 
Signed-off-by: hmsayem <[email protected]>
  • Loading branch information
@hmsayem
hmsayem committed Apr 18, 2022
1 parent acb586d commit 9550bf8
Showing 1 changed file with 11 additions and 11 deletions.
22 changes: 11 additions & 11 deletions docs/guides/troubleshooting/how-to-troubleshoot/index.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -60,13 +60,13 @@ If the phase of the `BackupConfiguration` is `NotReady`, you should describe the
kubectl describe backupconfiguration <backupconfiguration name> -n <namespace>
```

Now, check the `Status` section of `BackupConfiguration`. Make sure all the `conditions` are `True`. If there is any issue during backup setup, you should see the error in the respective condition. If any of the conditions is `False`, the backup stays in the `NotReady` phase. The conditions that cause a `BackupConfiguration` to become `NotReady` are given bellow:
Now, check the `Status` section of `BackupConfiguration`. Make sure all the `conditions` are `True`. If there is any issue during backup setup, you should see the error in the respective condition. If any of the conditions is `False`, the backup stays in the `NotReady` phase. The conditions that may cause a `BackupConfiguration` to become `NotReady` are given bellow:

| Reason | Message |
| ------------- | ------------- |
| RepositoryNotAvailable | Repository does not exist |
| Reason | Message |
| ------------------------- | ----------------------------- |
| RepositoryNotAvailable | Repository does not exist |
| BackendSecretNotAvailable | Backend Secret does not exist |
| TargetNotAvailable | Backup target does not exist |
| TargetNotAvailable | Backup target does not exist |

### Backup Failed

Expand Down Expand Up @@ -106,7 +106,7 @@ Inspect the log carefully. You should notice the respective error that leads to

## Troubleshoot Restore Issues

In this section, we are going to explain how to troubleshoot backup issues.
In this section, we are going to explain how to troubleshoot restore issues.

### Restore Pending

Expand All @@ -116,13 +116,13 @@ If the phase of the `RestoreSession` is `pending`, you should describe the respe
kubectl describe restoresession <restoresession name> -n <namespace>
```

Now, check the `Status` section of `RestoreSession`. Make sure all the `conditions` are `True`. If there is any issue during backup setup, you should see the error in the respective condition. If any of the conditions is `False`, the `RestoreSession` stays in the `Pending` phase. The conditions that cause a `RestoreSession` to stay in `Pending` phase are given bellow:
Now, check the `Status` section of `RestoreSession`. Make sure all the `conditions` are `True`. If there is any issue during restore setup, you should see the error in the respective condition. If any of the conditions is `False`, the `RestoreSession` stays in the `Pending` phase. The conditions that may cause a `RestoreSession` to stay in `Pending` phase are given bellow:

| Reason | Message |
| ------------- | ------------- |
| RepositoryNotAvailable | Repository does not exist |
| Reason | Message |
| ------------------------- | ----------------------------- |
| RepositoryNotAvailable | Repository does not exist |
| BackendSecretNotAvailable | Backend Secret does not exist |
| TargetNotAvailable | Backup target does not exist |
| TargetNotAvailable | Backup target does not exist |

### Restore Failed

Expand Down

0 comments on commit 9550bf8

Please sign in to comment.