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
Here's a sample of what the solution I'm proposing looks like. Instead of user having to dig for relevant info like these events, we can just put them in the logs.
{
"level": "info",
"ts": 1617296521280,
"logger": "directvolume|gr7lc",
"msg": "[RUN] (Step 16/22) Waiting for the Rsync daemon pod to run",
"dvm": "a95b82a0-92fd-11eb-876e-1f4707652b42-j5fxj",
"migMigration": "a95b82a0-92fd-11eb-876e-1f4707652b42",
"phase": "WaitForRsyncTransferPodsRunning"
}
{
"level": "info",
"ts": 1617296522250,
"logger": "directvolume|gr7lc",
"msg": "Found abnormal event for Rsync transfer Pod on destination cluster",
"dvm": "a95b82a0-92fd-11eb-876e-1f4707652b42-j5fxj",
"migMigration": "a95b82a0-92fd-11eb-876e-1f4707652b42",
"phase": "WaitForRsyncTransferPodsRunning",
"pod": "mssql-persistent/directvolumemigration-rsync-transfer",
"eventType": "Warning",
"eventReason": "FailedAttachVolume",
"eventMessage": "(combined from similar events): AttachVolume.Attach failed for volume \"pvc-0f061633-a6ef-4604-9020-9b06cb89a660\" : InvalidVolume.NotFound: The volume 'vol-0412f5c8cb6538964' does not exist.\n\tstatus code: 400, request id: efddaa59-a586-4f39-9334-1648afc60e05",
"eventFirstTimestamp": "2021-04-01 11:24:57 -0400 EDT"
}
{
"level": "info",
"ts": 1617296522250,
"logger": "directvolume|gr7lc",
"msg": "Found abnormal event for Rsync transfer Pod on destination cluster",
"dvm": "a95b82a0-92fd-11eb-876e-1f4707652b42-j5fxj",
"migMigration": "a95b82a0-92fd-11eb-876e-1f4707652b42",
"phase": "WaitForRsyncTransferPodsRunning",
"pod": "mssql-persistent/directvolumemigration-rsync-transfer",
"eventType": "Warning",
"eventReason": "FailedMount",
"eventMessage": "Unable to attach or mount volumes: unmounted volumes=[mssql-pvc], unattached volumes=[stunnel-conf stunnel-certs mssql-pvc rsyncd-conf rsync-creds default-token-79xdn]: timed out waiting for the condition",
"eventFirstTimestamp": "2021-04-01 11:50:07 -0400 EDT"
}
{
"level": "info",
"ts": 1617296522250,
"logger": "directvolume|gr7lc",
"msg": "Found non-running Rsync Transfer Pod on destination cluster.",
"dvm": "a95b82a0-92fd-11eb-876e-1f4707652b42-j5fxj",
"migMigration": "a95b82a0-92fd-11eb-876e-1f4707652b42",
"phase": "WaitForRsyncTransferPodsRunning",
"pod": "mssql-persistent/directvolumemigration-rsync-transfer",
"podPhase": "Pending"
}
{
"level": "info",
"ts": 1617296522251,
"logger": "directvolume|gr7lc",
"msg": "Rsync Transfer Pod(s) on destination cluster have not started Running after 10 minutes.",
"dvm": "a95b82a0-92fd-11eb-876e-1f4707652b42-j5fxj",
"migMigration": "a95b82a0-92fd-11eb-876e-1f4707652b42",
"phase": "WaitForRsyncTransferPodsRunning"
}
The text was updated successfully, but these errors were encountered:
djwhatle
changed the title
Logs should indicate relevant Pod events if we are waiting on a Pod
[MIG-455] Logs should indicate relevant Pod events if we are waiting on a Pod
Apr 1, 2021
djwhatle
changed the title
[MIG-455] Logs should indicate relevant Pod events if we are waiting on a Pod
[MIG-588] Logs should indicate relevant Pod events if we are waiting on a Pod
Apr 1, 2021
djwhatle
changed the title
[MIG-588] Logs should indicate relevant Pod events if we are waiting on a Pod
[MIG-563] Logs should indicate relevant Pod events if we are waiting on a Pod
Apr 1, 2021
Here's a sample of what the solution I'm proposing looks like. Instead of user having to dig for relevant info like these events, we can just put them in the logs.
The text was updated successfully, but these errors were encountered: