search

ublue-os / ublue-update

Small maintenance/update program written in python intended for use in Universal Blue
Apache License 2.0
10 stars 16 forks source link

U-Blue Update Systemd service reports failure when sucessfully run #113

Closed Nitrousoxide closed 3 days ago

Nitrousoxide commented 3 months ago

Checking the status it reports a failure exit code, though all of the checks appear to succeed:

Brian@fedora ~> systemctl status ublue-update.service
× ublue-update.service - Universal Blue Update Oneshot Service
     Loaded: loaded (/usr/lib/systemd/system/ublue-update.service; static)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: failed (Result: exit-code) since Mon 2024-05-13 07:38:57 EDT; 3min 25s ago
TriggeredBy: ● ublue-update.timer
    Process: 143586 ExecStart=/usr/bin/ublue-update (code=exited, status=1/FAILURE)
   Main PID: 143586 (code=exited, status=1/FAILURE)
        CPU: 375ms

May 13 07:38:56 fedora systemd[1]: Starting ublue-update.service - Universal Blue Update Oneshot Service...
May 13 07:38:57 fedora ublue-update[143586]: [2024-05-13 07:38:57,422] ublue_update.update_checks.system:INFO | No system update available.
May 13 07:38:57 fedora ublue-update[143586]: [2024-05-13 07:38:57,424] ublue_update.update_inhibitors.hardware:INFO | System passed hardware checks
May 13 07:38:57 fedora ublue-update[143586]: [2024-05-13 07:38:57,424] ublue_update.cli:INFO | System passed all update checks
May 13 07:38:57 fedora systemd[1]: ublue-update.service: Main process exited, code=exited, status=1/FAILURE
May 13 07:38:57 fedora systemd[1]: ublue-update.service: Failed with result 'exit-code'.
May 13 07:38:57 fedora systemd[1]: Failed to start ublue-update.service - Universal Blue Update Oneshot Service.
Brian@fedora /u/s/ublue-os> systemctl start ublue-update.service
Job for ublue-update.service failed because the control process exited with error code.
See "systemctl status ublue-update.service" and "journalctl -xeu ublue-update.service" for details.
Brian@fedora /u/s/ublue-os [1]> echo $status
1

Manually running the python script appears to give the same result, checking my exit code for it, and it looks to report a success, so I don't know why systemd is reporting this as a failure.

Brian@fedora ~> /usr/bin/ublue-update
[2024-05-13 07:45:07,888] ublue_update.update_checks.system:INFO | No system update available.
[2024-05-13 07:45:07,890] ublue_update.update_inhibitors.hardware:INFO | System passed hardware checks
[2024-05-13 07:45:07,890] ublue_update.cli:INFO | System passed all update checks
Brian@fedora ~> echo $status
0

Running ujust update manually works fine and correctly updates everything.

gerblesh commented 3 months ago

does the systemd service update packages properly or is it just ujust update?

Nitrousoxide commented 3 months ago

Only ujust update seems to actually update anything.

It's not updated anything in the background in a few weeks.

Brian@fedora ~> rpm-ostree status
State: idle
Deployments:
● ostree-unverified-registry:ghcr.io/ublue-os/bazzite-gnome:stable
                   Digest: sha256:57678826d4131c5154bfeec4d8dfa7b2873eda880fa6524b5e05c6da449d85ad
                  Version: 40.20240510.0 (2024-05-10T17:00:08Z)
          LayeredPackages: btrfs-assistant snapper
                Initramfs: '"-I /etc/crypttab /etc/modprobe.d/amdgpu.conf"' 

  ostree-unverified-registry:ghcr.io/ublue-os/bazzite-gnome:stable
                   Digest: sha256:1a7a9e5229cfe2ba234ba78292c411b3d53755f39dfe1fa77239e8367c745f2a
                  Version: 40.20240427.0 (2024-04-27T22:34:27Z)
          LayeredPackages: btrfs-assistant snapper
                Initramfs: '"-I /etc/crypttab /etc/modprobe.d/amdgpu.conf"' 

  ostree-unverified-registry:ghcr.io/ublue-os/bazzite-gnome:stable
                   Digest: sha256:8668faa3881d87c73f1394f104c42c7613036b3d6bd502fac36c8f44bb914900
                  Version: 39.20240419.0 (2024-04-19T17:03:42Z)
          LayeredPackages: btrfs-assistant snapper
            LocalPackages: sunshine-0.21.0-1.x86_64
                Initramfs: '"-I /etc/crypttab /etc/modprobe.d/amdgpu.conf"' 
                   Pinned: yes

  ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-gnome:latest
                   Digest: sha256:bc069b2d8f9d6e0008654ccb88127725a5b20559ddca77e176d1c3b6d9d02e81
                Timestamp: 2024-01-27T01:59:41Z
            LocalPackages: lact-0.5.0-0.x86_64 sunshine-0.21.0-1.x86_64
                Initramfs: '"-I /etc/crypttab /etc/modprobe.d/amdgpu.conf"' 
                   Pinned: yes
Brian@fedora ~> systemctl status ublue-update.service
× ublue-update.service - Universal Blue Update Oneshot Service
     Loaded: loaded (/usr/lib/systemd/system/ublue-update.service; static)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: failed (Result: exit-code) since Fri 2024-05-24 20:55:59 EDT; 4 da>
TriggeredBy: ● ublue-update.timer
    Process: 428482 ExecStart=/usr/bin/ublue-update (code=exited, status=1/FAIL>
   Main PID: 428482 (code=exited, status=1/FAILURE)
        CPU: 307ms

May 24 20:55:57 fedora systemd[1]: Starting ublue-update.service - Universal Bl>
May 24 20:55:59 fedora ublue-update[428482]: [2024-05-24 20:55:59,133] ublue_up>
May 24 20:55:59 fedora ublue-update[428482]: [2024-05-24 20:55:59,133] ublue_up>
May 24 20:55:59 fedora ublue-update[428482]: [2024-05-24 20:55:59,134] ublue_up>
May 24 20:55:59 fedora systemd[1]: ublue-update.service: Main process exited, c>
May 24 20:55:59 fedora systemd[1]: ublue-update.service: Failed with result 'ex>
May 24 20:55:59 fedora systemd[1]: Failed to start ublue-update.service - Unive>
Brian@fedora ~ [3]> systemctl start ublue-update.service
Job for ublue-update.service failed because the control process exited with error code.
See "systemctl status ublue-update.service" and "journalctl -xeu ublue-update.service" for details.
Brian@fedora ~ [1]> systemctl status ublue-update.service
× ublue-update.service - Universal Blue Update Oneshot Service
     Loaded: loaded (/usr/lib/systemd/system/ublue-update.service; static)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: failed (Result: exit-code) since Tue 2024-05-28 23:02:38 EDT; 5s ago
TriggeredBy: ● ublue-update.timer
    Process: 589499 ExecStart=/usr/bin/ublue-update (code=exited, status=1/FAILURE)
   Main PID: 589499 (code=exited, status=1/FAILURE)
        CPU: 470ms

May 28 23:02:37 fedora systemd[1]: Starting ublue-update.service - Universal Blue Update Oneshot Service...
May 28 23:02:38 fedora ublue-update[589499]: [2024-05-28 23:02:38,585] ublue_update.update_checks.system:INFO | S>
May 28 23:02:38 fedora ublue-update[589499]: [2024-05-28 23:02:38,587] ublue_update.update_inhibitors.hardware:IN>
May 28 23:02:38 fedora ublue-update[589499]: [2024-05-28 23:02:38,587] ublue_update.cli:INFO | System passed all >
May 28 23:02:38 fedora systemd[1]: ublue-update.service: Main process exited, code=exited, status=1/FAILURE
May 28 23:02:38 fedora systemd[1]: ublue-update.service: Failed with result 'exit-code'.
May 28 23:02:38 fedora systemd[1]: Failed to start ublue-update.service - Universal Blue Update Oneshot Service.

Running ujust update works successfully though

start:

Brian@fedora ~ [3]> ujust update

── 23:05:36 - System update ────────────────────────────────────────────────────
Pulling manifest: ostree-unverified-registry:ghcr.io/ublue-os/bazzite-gnome:stable
Importing: ostree-unverified-registry:ghcr.io/ublue-os/bazzite-gnome:stable (digest: sha256:e7d73879b80cef2a6bd07e549b7ed29514dcd80ad2275a7c93cd364ccc8ea209)
ostree chunk layers needed: 65 (2.2 GB)
custom layers needed: 3 (2.7 GB)
Checking out tree cab28de... done
...

After:

Brian@fedora ~> rpm-ostree status
State: idle
Deployments:
  ostree-unverified-registry:ghcr.io/ublue-os/bazzite-gnome:stable
                   Digest: sha256:e7d73879b80cef2a6bd07e549b7ed29514dcd80ad2275a7c93cd364ccc8ea209
                  Version: 40.20240528.0 (2024-05-28T16:59:41Z)
            SecAdvisories: 4 low, 6 moderate, 2 important
                     Diff: 257 upgraded, 18 removed, 146 added
          LayeredPackages: btrfs-assistant snapper
                Initramfs: '"-I /etc/crypttab /etc/modprobe.d/amdgpu.conf"' 

● ostree-unverified-registry:ghcr.io/ublue-os/bazzite-gnome:stable
                   Digest: sha256:57678826d4131c5154bfeec4d8dfa7b2873eda880fa6524b5e05c6da449d85ad
                  Version: 40.20240510.0 (2024-05-10T17:00:08Z)
          LayeredPackages: btrfs-assistant snapper
                Initramfs: '"-I /etc/crypttab /etc/modprobe.d/amdgpu.conf"' 

  ostree-unverified-registry:ghcr.io/ublue-os/bazzite-gnome:stable
                   Digest: sha256:1a7a9e5229cfe2ba234ba78292c411b3d53755f39dfe1fa77239e8367c745f2a
                  Version: 40.20240427.0 (2024-04-27T22:34:27Z)
          LayeredPackages: btrfs-assistant snapper
                Initramfs: '"-I /etc/crypttab /etc/modprobe.d/amdgpu.conf"' 

  ostree-unverified-registry:ghcr.io/ublue-os/bazzite-gnome:stable
                   Digest: sha256:8668faa3881d87c73f1394f104c42c7613036b3d6bd502fac36c8f44bb914900
                  Version: 39.20240419.0 (2024-04-19T17:03:42Z)
          LayeredPackages: btrfs-assistant snapper
            LocalPackages: sunshine-0.21.0-1.x86_64
                Initramfs: '"-I /etc/crypttab /etc/modprobe.d/amdgpu.conf"' 
                   Pinned: yes

  ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-gnome:latest
                   Digest: sha256:bc069b2d8f9d6e0008654ccb88127725a5b20559ddca77e176d1c3b6d9d02e81
                Timestamp: 2024-01-27T01:59:41Z
            LocalPackages: lact-0.5.0-0.x86_64 sunshine-0.21.0-1.x86_64
                Initramfs: '"-I /etc/crypttab /etc/modprobe.d/amdgpu.conf"' 
                   Pinned: yes
Brian@fedora ~>
Nitrousoxide commented 3 months ago

after rebooting into the new image, still the same issue, so nothing got fixed in the interim updates

Brian@fedora ~> rpm-ostree status
State: idle
^[[ADeployments:
● ostree-unverified-registry:ghcr.io/ublue-os/bazzite-gnome:stable
                   Digest: sha256:e7d73879b80cef2a6bd07e549b7ed29514dcd80ad2275a7c93cd364ccc8ea209
                  Version: 40.20240528.0 (2024-05-28T16:59:41Z)
          LayeredPackages: btrfs-assistant snapper
                Initramfs: '"-I /etc/crypttab /etc/modprobe.d/amdgpu.conf"' 

  ostree-unverified-registry:ghcr.io/ublue-os/bazzite-gnome:stable
                   Digest: sha256:57678826d4131c5154bfeec4d8dfa7b2873eda880fa6524b5e05c6da449d85ad
                  Version: 40.20240510.0 (2024-05-10T17:00:08Z)
          LayeredPackages: btrfs-assistant snapper
                Initramfs: '"-I /etc/crypttab /etc/modprobe.d/amdgpu.conf"' 

  ostree-unverified-registry:ghcr.io/ublue-os/bazzite-gnome:stable
                   Digest: sha256:8668faa3881d87c73f1394f104c42c7613036b3d6bd502fac36c8f44bb914900
                  Version: 39.20240419.0 (2024-04-19T17:03:42Z)
          LayeredPackages: btrfs-assistant snapper
            LocalPackages: sunshine-0.21.0-1.x86_64
                Initramfs: '"-I /etc/crypttab /etc/modprobe.d/amdgpu.conf"' 
                   Pinned: yes

  ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-gnome:latest
                   Digest: sha256:bc069b2d8f9d6e0008654ccb88127725a5b20559ddca77e176d1c3b6d9d02e81
                Timestamp: 2024-01-27T01:59:41Z
            LocalPackages: lact-0.5.0-0.x86_64 sunshine-0.21.0-1.x86_64
                Initramfs: '"-I /etc/crypttab /etc/modprobe.d/amdgpu.conf"' 
                   Pinned: yes
Brian@fedora ~> /usr/bin/ublue-update
[2024-05-28 23:39:24,773] ublue_update.update_checks.system:INFO | No system update available.
[2024-05-28 23:39:24,776] ublue_update.update_inhibitors.hardware:INFO | System passed hardware checks
[2024-05-28 23:39:24,776] ublue_update.cli:INFO | System passed all update checks
Brian@fedora ~> echo $status
0
Brian@fedora ~> systemctl start ublue-update.service
Job for ublue-update.service failed because the control process exited with error code.
See "systemctl status ublue-update.service" and "journalctl -xeu ublue-update.service" for details.
Brian@fedora ~ [1]> echo $status
1
Brian@fedora ~>
gerblesh commented 2 months ago

You appear to have rebased to an unsigned image? I'm not sure if that's affecting anything but the container policy likely is preventing rpm-ostree from updating

gerblesh commented 2 months ago

try rebasing to a signed image using rpm-ostree rebase ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-gnome:stable this will likely fix the issue

gmpinder commented 2 months ago

I'm also having the same issue and I'm on a signed image

$> systemctl status ublue-update.service
× ublue-update.service - Universal Blue Update Oneshot Service
     Loaded: loaded (/usr/lib/systemd/system/ublue-update.service; static)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: failed (Result: exit-code) since Mon 2024-06-10 09:43:45 EDT; 3h 56min ago
TriggeredBy: ● ublue-update.timer
    Process: 24820 ExecStart=/usr/bin/ublue-update (code=exited, status=1/FAILURE)
   Main PID: 24820 (code=exited, status=1/FAILURE)
        CPU: 415ms

Jun 10 09:43:43 jerry-desktop systemd[1]: Starting ublue-update.service - Universal Blue Update Oneshot Service...
Jun 10 09:43:44 jerry-desktop ublue-update[24820]: [2024-06-10 09:43:44,934] ublue_update.update_checks.system:INFO | System update available.
Jun 10 09:43:44 jerry-desktop ublue-update[24820]: [2024-06-10 09:43:44,936] ublue_update.update_inhibitors.hardware:INFO | System passed hardware checks
Jun 10 09:43:44 jerry-desktop ublue-update[24820]: [2024-06-10 09:43:44,936] ublue_update.cli:INFO | System passed all update checks
Jun 10 09:43:45 jerry-desktop systemd[1]: ublue-update.service: Main process exited, code=exited, status=1/FAILURE
Jun 10 09:43:45 jerry-desktop systemd[1]: ublue-update.service: Failed with result 'exit-code'.
Jun 10 09:43:45 jerry-desktop systemd[1]: Failed to start ublue-update.service - Universal Blue Update Oneshot Service.
$> rpm-ostree status
State: busy
Transaction: upgrade
  Initiator: client(id:cli dbus:1.254 unit:tmux-spawn-25ba0e44-0b86-4683-92de-512d934a819d.scope uid:1000)
Deployments:
● ostree-image-signed:docker://registry.gitlab.com/wunker-bunker/wunker-os/jp-desktop-nvidia
                   Digest: sha256:71d0b2d33cb1756ddf359dc3b420b1f327a36f47a42cb6cb977c71728d726e04
                  Version: 40.20240607.0 (2024-06-09T10:43:03Z)
          LayeredPackages: mold
                Initramfs: '"-I /etc/crypttab /usr/lib/modprobe.d/nvidia.conf"'

  ostree-image-signed:docker://registry.gitlab.com/wunker-bunker/wunker-os/jp-desktop-nvidia
                   Digest: sha256:30c60a9fe9232c0cd255d9e0979ee7b0b29a4a896ba28687d6ae8616b817d103
                  Version: 40.20240531.0 (2024-06-01T10:43:23Z)
          LayeredPackages: mold
                Initramfs: '"-I /etc/crypttab /usr/lib/modprobe.d/nvidia.conf"'

(ignore the busy state, I kicked off a manual upgrade before copy/pasting here)

Nitrousoxide commented 2 months ago

try rebasing to a signed image using rpm-ostree rebase ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-gnome:stable this will likely fix the issue

Rebasing seems to have worked for me.

Brian@fedora ~ [3]> systemctl status ublue-update.service
○ ublue-update.service - Universal Blue Update Oneshot Service
     Loaded: loaded (/usr/lib/systemd/system/ublue-update.service; static)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: inactive (dead) since Mon 2024-06-10 14:00:00 EDT; 4s ago
TriggeredBy: ● ublue-update.timer
    Process: 9445 ExecStart=/usr/bin/ublue-update (code=exited, status=0/SUCCESS)
   Main PID: 9445 (code=exited, status=0/SUCCESS)
        CPU: 9.871s

Jun 10 13:59:14 fedora flatpak[9585]: system: Updated runtime/org.freedesktop.Platform.ffmpeg_full.i386/x86_64/23.08 from flathub
Jun 10 13:59:15 fedora flatpak[9585]: libostree pull from 'flathub' for runtime/org.freedesktop.Platform/x86_64/23.08 complete
                                      security: GPG: summary+commit 
                                      security: SIGN: disabled http: TLS
                                      delta: parts: 2 loose: 3
                                      transfer: secs: 0 size: 3.8 MB
Jun 10 13:59:15 fedora flatpak[9585]: system: Pulled runtime/org.freedesktop.Platform/x86_64/23.08 from flathub
Jun 10 13:59:16 fedora flatpak[9585]: system: Updated runtime/org.freedesktop.Platform/x86_64/23.08 from flathub
Jun 10 13:59:17 fedora ublue-update[9445]: [2024-06-10 13:59:17,608] ublue_update.cli:INFO | Running update for user: 'Brian'
Jun 10 13:59:17 fedora sudo[9841]:     root : PWD=/ ; USER=Brian ; ENV=DISPLAY=:0 XDG_RUNTIME_DIR=/run/user/1000 DBUS_SESSION_BUS_ADDRESS=unix:>
Jun 10 14:00:00 fedora ublue-update[9445]: [2024-06-10 14:00:00,037] ublue_update.cli:INFO | System update complete
Jun 10 14:00:00 fedora systemd[1]: ublue-update.service: Deactivated successfully.
Jun 10 14:00:00 fedora systemd[1]: Finished ublue-update.service - Universal Blue Update Oneshot Service.
Jun 10 14:00:00 fedora systemd[1]: ublue-update.service: Consumed 9.871s CPU time, 2.0G memory peak, 0B memory swap peak.
Brian@fedora ~ [3]> 
Brian@fedora ~ [3]> rpm-ostree status
State: idle
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-gnome:stable
                   Digest: sha256:731eea9f7dcb5d28beec5e764f01b1dc3c8ded8d437ab90f34e967a2ab5206d6
                  Version: 40.20240609.0 (2024-06-09T18:07:43Z)
          LayeredPackages: btrfs-assistant snapper
                Initramfs: '"-I /etc/crypttab /etc/modprobe.d/amdgpu.conf"' 

  ostree-unverified-registry:ghcr.io/ublue-os/bazzite-gnome:stable
                   Digest: sha256:5aeb9564d04bab9992aad1464fabfa098cb84d70b7a6da0cfd368adf809cfc3f
                  Version: 40.20240607.0 (2024-06-07T17:01:41Z)
          LayeredPackages: btrfs-assistant snapper
                Initramfs: '"-I /etc/crypttab /etc/modprobe.d/amdgpu.conf"' 

  ostree-unverified-registry:ghcr.io/ublue-os/bazzite-gnome:stable
                   Digest: sha256:8668faa3881d87c73f1394f104c42c7613036b3d6bd502fac36c8f44bb914900
                  Version: 39.20240419.0 (2024-04-19T17:03:42Z)
          LayeredPackages: btrfs-assistant snapper
            LocalPackages: sunshine-0.21.0-1.x86_64
                Initramfs: '"-I /etc/crypttab /etc/modprobe.d/amdgpu.conf"' 
                   Pinned: yes

  ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-gnome:latest
                   Digest: sha256:bc069b2d8f9d6e0008654ccb88127725a5b20559ddca77e176d1c3b6d9d02e81
                Timestamp: 2024-01-27T01:59:41Z
            LocalPackages: lact-0.5.0-0.x86_64 sunshine-0.21.0-1.x86_64
                Initramfs: '"-I /etc/crypttab /etc/modprobe.d/amdgpu.conf"' 
                   Pinned: yes
Brian@fedora ~>
SNThrailkill commented 4 weeks ago

Seeing the same issue. Am on a signed image.

systemctl status ublue-update.service
× ublue-update.service - Universal Blue Update Oneshot Service
     Loaded: loaded (/usr/lib/systemd/system/ublue-update.service; static)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
             /usr/lib/systemd/system/ublue-update.service.d
             └─override.conf
     Active: failed (Result: exit-code) since Fri 2024-08-09 21:43:19 CDT; 7s ago
TriggeredBy: ● ublue-update.timer
    Process: 9842 ExecStart=/usr/bin/ublue-update (code=exited, status=1/FAILURE)
   Main PID: 9842 (code=exited, status=1/FAILURE)
        CPU: 242ms

Aug 09 21:43:18 Fedora systemd[1]: Starting ublue-update.service - Universal Blue Update Oneshot Service...
Aug 09 21:43:19 Fedora ublue-update[9842]: [2024-08-09 21:43:19,477] ublue_update.update_checks.system:INFO | No system update available.
Aug 09 21:43:19 Fedora ublue-update[9842]: [2024-08-09 21:43:19,479] ublue_update.update_inhibitors.hardware:INFO | System passed hardware checks
Aug 09 21:43:19 Fedora ublue-update[9842]: [2024-08-09 21:43:19,479] ublue_update.update_inhibitors.custom:INFO | System passed custom checks
Aug 09 21:43:19 Fedora ublue-update[9842]: [2024-08-09 21:43:19,479] ublue_update.cli:INFO | System passed all update checks
Aug 09 21:43:19 Fedora systemd[1]: ublue-update.service: Main process exited, code=exited, status=1/FAILURE
Aug 09 21:43:19 Fedora systemd[1]: ublue-update.service: Failed with result 'exit-code'.
Aug 09 21:43:19 Fedora systemd[1]: Failed to start ublue-update.service - Universal Blue Update Oneshot Service.
trevnels commented 4 weeks ago

It seems like topgrade recently added a (Y/N) prompt to acknowledge breaking changes, which ublue-update might not be handling properly. Manually running topgrade --config /usr/share/ublue-update/topgrade-(user|system).toml and acknowledging the prompt looks like it's fixed things for me.

liaralabs commented 2 weeks ago

Running the topgrade command manually appears to only fix the issue until I reboot my computer -- have to rerun it after every restart in order to kick things back to functional.

Edit: debugged my issue and looks like my specific issue was due to running a custom built image, updating from my own repo/image and using a fork of this script pushed in bazzite. Fixed by updating image-ref in /usr/share/ublue-os/image-info.json to point to my actual repo during build

elgabo86 commented 1 week ago

set TOPGRADE_SKIP_BRKC_NOTIFY=true makes bypass the prompt.