Skip to content

Commit 499d9dd

Browse files
authored
Add templateinstances to troubleshooting doc (#643)
1 parent 6f4315e commit 499d9dd

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/TROUBLESHOOTING.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -195,7 +195,7 @@ If the issue still persists, [create a new issue](https://github.com/openshift/o
195195
196196
Step 2: Initiate a restore excluding the replicationcontroller and deploymentconfig resources.
197197
```
198-
velero restore create --from-backup=<BACKUP_NAME> -n openshift-adp --include-namespaces <TARGET_NAMESPACE> --exclude-resources replicationcontroller,deploymentconfig --restore-volumes=true
198+
velero restore create --from-backup=<BACKUP_NAME> -n openshift-adp --include-namespaces <TARGET_NAMESPACE> --exclude-resources replicationcontroller,deploymentconfig,templateinstances.template.openshift.io --restore-volumes=true
199199
```
200200
201201
Step 3: Initiate a restore including the replicationcontroller and deploymentconfig resources.
@@ -229,4 +229,4 @@ If the issue still persists, [create a new issue](https://github.com/openshift/o
229229
```
230230
231231
This is a known Velero [issue](https://github.com/vmware-tanzu/velero/issues/4421)
232-
which appears to be in the process of deciding expected behavior.
232+
which appears to be in the process of deciding expected behavior.

0 commit comments

Comments
 (0)