anchor.diff:  +
   The output identifies the `Restic` pod that logged the errors.
   +
  -.Example output
  +.PodVolumeRestore CR with Restic pod error
   [source,yaml]
   ----
     completionTimestamp: 2020-05-01T20:49:12Z
  
positive.code: +
  The output identifies the persistent volume with `PodVolumeRestore` errors.
  +
  .Example output
  [source,yaml]
  ----
  status:
  
negative.code: [id="ca-certificate-error-in-console_{context}"]
  == CA certificate error in the {mtc-short} console
  
  If the {mtc-short} console displays a `CA certificate error` message the first time you try to access it, the likely cause is that a cluster uses self-signed CA certificates.
  
  Navigate to the `oauth-authorization-server` URL in the error message and accept the certificate. To resolve this issue permanently, install the certificate authority so that it is trusted.
  
  If the browser displays an `Unauthorized` message after you have accepted the CA certificate, navigate to the {mtc-short} console and then refresh the web page.
  
  [id="oauth-timeout-error-in-console_{context}"]
  == OAuth timeout error in the {mtc-short} console
  
  If the {mtc-short} console displays a `connection has timed out` message after you have accepted a self-signed certificate, the cause is likely to be one of the following:
  
  * Interrupted network access to the OAuth server
  * Interrupted network access to the {product-title} console
  * Proxy configuration blocking access to the OAuth server. See link:https://access.redhat.com/solutions/5514491[MTC console inaccessible because of OAuth timeout error] for details.
  
  To determine the cause:
  
  * Inspect the {mtc-short} console web page with a browser web inspector.
  * Check the `Migration UI` pod log for errors.
  
  [id="backup-storage-location-errors-in-velero-pod-log_{context}"]
  == Backup storage location errors in the Velero pod log
  
  If a `Velero` `Backup` custom resource contains a reference to a backup storage location (BSL) that does not exist, the `Velero` pod log might display the following error messages:
  
  .BSL error messages
  [source,terminal]
  ----
  Error checking repository for stale locks
  
  Error getting backup storage location: backupstoragelocation.velero.io \"my-bsl\" not found
  ----
  
  You can ignore these error messages. A missing BSL cannot cause a migration to fail.
  
  [id="podvolumebackups-timeout-error-in-velero-log_{context}""]
  == Pod volume backup timeout error in the Velero pod log
  
  If a migration fails because `Restic` times out, the `Velero` pod log displays the following error:
  
  .Pod volume backup timeout error
  [source,terminal]
  ----
  level=error msg="Error backing up item" backup=velero/monitoring error="timed out
  waiting for all PodVolumeBackups to complete" error.file="/go/src/github.com/
  heptio/velero/pkg/restic/backupper.go:165" error.function="github.com/heptio/
  velero/pkg/restic.(*backupper).BackupPodVolumes" group=v1
  ----
  
  The default value of `restic_timeout` is one hour. You can increase this parameter for large migrations, keeping in mind that a higher value may delay the return of error messages.
  