Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[MIG-563] Logs should indicate relevant Pod events if we are waiting on a Pod #1051

Closed
djwhatle opened this issue Apr 1, 2021 · 0 comments · Fixed by #1052 or #1058
Closed

[MIG-563] Logs should indicate relevant Pod events if we are waiting on a Pod #1051

djwhatle opened this issue Apr 1, 2021 · 0 comments · Fixed by #1052 or #1058
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@djwhatle
Copy link
Contributor

djwhatle commented 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.

{
  "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"
}
@djwhatle djwhatle added the kind/feature Categorizes issue or PR as related to a new feature. label Apr 1, 2021
@djwhatle 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 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 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
1 participant