save full logs in the crashdump (ci) #9808
Assignees
Comments
frezbo
added a commit
to frezbo/talos
that referenced
this issue
Nov 28, 2024
Support saving cluster logs on destroy Fixes: siderolabs#9808 Signed-off-by: Noel Georgi <[email protected]>
frezbo
added a commit
to frezbo/talos
that referenced
this issue
Nov 28, 2024
Support saving cluster logs on destroy Fixes: siderolabs#9808 Signed-off-by: Noel Georgi <[email protected]>
frezbo
added a commit
to frezbo/talos
that referenced
this issue
Nov 28, 2024
Support saving cluster logs on destroy Fixes: siderolabs#9808 Signed-off-by: Noel Georgi <[email protected]>
frezbo
added a commit
to frezbo/talos
that referenced
this issue
Nov 28, 2024
Support saving cluster logs on destroy Fixes: siderolabs#9808 Signed-off-by: Noel Georgi <[email protected]>
frezbo
added a commit
to frezbo/talos
that referenced
this issue
Nov 28, 2024
Support saving cluster logs on destroy Fixes: siderolabs#9808 Signed-off-by: Noel Georgi <[email protected]>
frezbo
added a commit
to frezbo/talos
that referenced
this issue
Nov 28, 2024
Support saving cluster logs on destroy Fixes: siderolabs#9808 Signed-off-by: Noel Georgi <[email protected]>
frezbo
added a commit
to frezbo/talos
that referenced
this issue
Nov 28, 2024
Support saving cluster logs on destroy Fixes: siderolabs#9808 Signed-off-by: Noel Georgi <[email protected]>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Before changes in #9667 and related PRs, the full logs were saved including Docker logs (for Docker-based) and console logs (for QEMU-based).
Proposal: add to the
support.zip(or another file) a dump of all console logs resurrecting code that was there for docker & vm provisioners.The text was updated successfully, but these errors were encountered: