You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/migration-error-messages.adoc
+45-31Lines changed: 45 additions & 31 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,42 +12,53 @@ This section describes common error messages you might encounter with the {mtc-f
12
12
[id="ca-certificate-error-in-console_{context}"]
13
13
== CA certificate error in the {mtc-short} console
14
14
15
-
If a `CA certificate error` message is displayed the first time you try to access the {mtc-short} console, the likely cause is the use of self-signed CA certificates in one of the clusters.
15
+
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.
16
16
17
-
To resolve this issue, navigate to the `oauth-authorization-server` URL displayed in the error message and accept the certificate. To resolve this issue permanently, add the certificate to the trust store of your web browser.
17
+
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.
18
18
19
-
If an `Unauthorized` message is displayed after you have accepted the certificate, navigate to the {mtc-short} console and refresh the web page.
19
+
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.
20
20
21
21
[id="oauth-timeout-error-in-console_{context}"]
22
22
== OAuth timeout error in the {mtc-short} console
23
23
24
-
If a `connection has timed out` message is displayed in the {mtc-short} console after you have accepted a self-signed certificate, the causes are likely to be the following:
24
+
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:
25
25
26
26
* Interrupted network access to the OAuth server
27
27
* Interrupted network access to the {product-title} console
28
-
* Proxy configuration that blocks access to the `oauth-authorization-server` URL. See link:https://access.redhat.com/solutions/5514491[MTC console inaccessible because of OAuth timeout error] for details.
28
+
* 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.
29
29
30
-
You can determine the cause of the timeout.
30
+
To determine the cause:
31
31
32
-
.Procedure
32
+
* Inspect the {mtc-short} console web page with a browser web inspector.
33
+
* Check the `Migration UI` pod log for errors.
33
34
34
-
. Navigate to the {mtc-short} console and inspect the elements with the browser web inspector.
== Backup storage location errors in the Velero pod log
37
+
38
+
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:
== Pod volume backup timeout error in the Velero pod log
44
52
45
-
If a migration fails because Restic times out, the following error is displayed in the `Velero` pod log.
53
+
If a migration fails because `Restic` times out, the `Velero` pod log displays the following error:
46
54
47
-
.Example output
55
+
.Pod volume backup timeout error
48
56
[source,terminal]
49
57
----
50
-
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
58
+
level=error msg="Error backing up item" backup=velero/monitoring error="timed out
59
+
waiting for all PodVolumeBackups to complete" error.file="/go/src/github.com/
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.
== Restic verification errors in the MigMigration custom resource
73
84
74
-
If data verification fails when migrating a persistent volume with the file system data copy method, the following error is displayed in the `MigMigration` CR.
85
+
If data verification fails when migrating a persistent volume with the file system data copy method, the `MigMigration` CR displays the following error:
75
86
76
-
.Example output
87
+
.MigMigration CR status
77
88
[source,yaml]
78
89
----
79
90
status:
@@ -94,7 +105,7 @@ status:
94
105
A data verification error does not cause the migration process to fail.
95
106
====
96
107
97
-
You can check the `Restore` CR to identify the source of the data verification error.
108
+
You can check the `Restore` CR to troubleshoot the data verification error.
== `restic: permission denied` error for NFS storage
164
+
== Restic permission error when migrating from NFS storage with root_squash enabled
155
165
156
-
If you are migrating data from NFS storage and `root_squash` is enabled, `Restic` maps to `nfsnobody` and does not have permission to perform the migration. The following error is displayed in the `Restic` pod log.
166
+
If you are migrating data from NFS storage and `root_squash` is enabled, `Restic` maps to `nfsnobody` and does not have permission to perform the migration. The `Restic` pod log displays the following error:
0 commit comments