executor: return error message from the journal - #134
Conversation
Sorry, something went wrong.
|
@alicefr I am not sure if we will have this issue of cap size in bootc-operator. |
Sorry, something went wrong.
Yeah, it is a good point. But I'm afraid that we will cut the important output. Alternatively, we can filter the lines that starts with error:. Currently, the message looks like: - lastTransitionTime: "2026-08-10T13:45:11Z"
message: |-
bootc stage failed: running bootc switch: Started bootc-operator-switch.service - [systemd-run] /usr/bin/bootc switch ghcr.io/bootc-dev/bink/node@sha256:9ce7d6d15b8558c226b4c41f3b27bf1722897b0c8a66c7a84a2877bca8d049f7.
Switching from image ghcr.io/bootc-dev/bink/node:v1.35-fedora-44 to ghcr.io/bootc-dev/bink/node@sha256:9ce7d6d15b8558c226b4c41f3b27bf1722897b0c8a66c7a84a2877bca8d049f7
Fetching ostree-unverified-registry:ghcr.io/bootc-dev/bink/node@sha256:9ce7d6d15b8558c226b4c41f3b27bf1722897b0c8a66c7a84a2877bca8d049f7
error: Switching: Switching (ostree): Preparing import: Fetching manifest: Target image does not have ostree.bootable label
bootc-operator-switch.service: Main process exited, code=exited, status=1/FAILURE
bootc-operator-switch.service: Failed with result 'exit-code'.
bootc-operator-switch.service: Consumed 210ms CPU time over 1.111s wall clock time, 155.2M memory peak.: exit status 1
|
Sorry, something went wrong.
HarshwardhanPatil07
left a comment
There was a problem hiding this comment.
Valid! thank you very much.. just learning
Sorry, something went wrong.
|
filter sounds good too |
Sorry, something went wrong.
|
@HarshwardhanPatil07 let's add the filter before merging this |
Sorry, something went wrong.
Previously, the output of the systemd unit was only reported in bootc
operator. Now, it is returned as part of the error when bootc switch
fails.
The output for the systemd unit is quite verbose, so we filter for the
lines containing the errors tag. The full output will be reduced from:
bootc stage failed: running bootc switch: Started bootc-operator-switch.service - [systemd-run] /usr/bin/bootc switch ghcr.io/bootc-dev/bink/node@sha256:9ce7d6d15b8558c226b4c41f3b27bf1722897b0c8a66c7a84a2877bca8d049f7.
Switching from image ghcr.io/bootc-dev/bink/node:v1.35-fedora-44 to ghcr.io/bootc-dev/bink/node@sha256:9ce7d6d15b8558c226b4c41f3b27bf1722897b0c8a66c7a84a2877bca8d049f7
Fetching ostree-unverified-registry:ghcr.io/bootc-dev/bink/node@sha256:9ce7d6d15b8558c226b4c41f3b27bf1722897b0c8a66c7a84a2877bca8d049f7
error: Switching: Switching (ostree): Preparing import: Fetching manifest: Target image does not have ostree.bootable label
bootc-operator-switch.service: Main process exited, code=exited, status=1/FAILURE
bootc-operator-switch.service: Failed with result 'exit-code'.
bootc-operator-switch.service: Consumed 210ms CPU time over 1.111s wall clock time, 155.2M memory peak.: exit status 1
to
'bootc stage failed: running bootc switch: error: Switching: Switching
(ostree): Preparing import: Fetching manifest: Target image does not have
ostree.bootable label: exit status 1'
The full message in any case is present in the bootc daemon logs.
Assisted-by: AI
Signed-off-by: Alice Frosi <afrosi@redhat.com>
|
With the filter the message looks like: - lastTransitionTime: "2026-08-11T08:01:46Z"
message: 'bootc stage failed: running bootc switch: error: Switching: Switching
(ostree): Preparing import: Fetching manifest: Target image does not have
ostree.bootable label: exit status 1' |
Sorry, something went wrong.
|
Currently the CI is broken |
Sorry, something went wrong.
|
Thank you! |
Sorry, something went wrong.
|
This was closed by mistake, the fix is still valid |
Sorry, something went wrong.
Previously, the output of the systemd unit was only reported in bootc operator. Now, it is returned as part of the error when bootc switch fails.
The output of the systemd unit might be quite verbose, but it doesn't filter any information to avoid any precious information loss.
Fixes: #133