V6 Only FTL is updated not Core and Webinterface

[gr33n]

Expected Behaviour:

sudo pihole -up should update FTL, Core and Webinterface

Actual Behaviour:

Only the FTL is update not the Core and Webinterface
Core version is v6.0.3 (Latest: v6.0.5)
Web version is v6.0.1 (Latest: v6.0.2)
FTL version is v6.0.4 (Latest: v6.0.4)

*** [ DIAGNOSING ]: Core version
[✓] Version: v6.0.3
[i] Remotes: origin GitHub - pi-hole/pi-hole: A black hole for Internet advertisements (fetch)
origin GitHub - pi-hole/pi-hole: A black hole for Internet advertisements (push)
[i] Branch: master
[i] Commit: v6.0.3-0-g0e6d9e74

*** [ DIAGNOSING ]: Web version
[✓] Version: v6.0.1
[i] Remotes: origin GitHub - pi-hole/web: Pi-hole Dashboard for stats and more (fetch)
origin GitHub - pi-hole/web: Pi-hole Dashboard for stats and more (push)
[i] Branch: master
[i] Commit: v6.0.1-0-g42e7279a

*** [ DIAGNOSING ]: FTL version
[✓] Version: v6.0.4
[i] Branch: master
[i] Commit: b7eb53bf

[✓] Detected ARMv7 (or newer) architecture (v7
Application)
[i] Latest FTL binary already installed (v6.0.4), verifying integrity...
[i] Local binary up-to-date. No need to download!
[✓] Installing scripts from /etc/.pihole

[i] Installing configs from /etc/.pihole...

[✓] Installing latest Cron script

[i] Installing latest logrotate script...
[i] Existing logrotate file found. No changes made.
[i] man not installed
[i] Testing if systemd-resolved is enabled
[i] Systemd-resolved is not enabled
[i] Restarting services...
[i] Enabling pihole-FTL service to start on reboot...

Debug Token:

prefer not to hope its not needed.

[Eraser127]

Same problem here last week (updated from v5 to v6 including keeping settings):

Core version is v6.0 (Latest: v6.0.4)
Web version is v6.0 (Latest: v6.0.1)
FTL version is v6.0.2 (Latest: v6.0.2)

now again:

Core version is v6.0.4 (Latest: v6.0.5)
Web version is v6.0.1 (Latest: v6.0.2)
FTL version is v6.0.4 (Latest: v6.0.4)

What did help was to switch to the 'dev' and back to 'master', but that's not the best solution ofcourse. Can always do a clean install, if there's no better solution.

[rdwebdesign]

Please upload a debug log and post just the token URL that is generated after the log is uploaded by running the following command from the Pi-hole host terminal:

pihole -d

or if you run your Pi-hole as a Docker container:

docker exec -it <pihole-container-name-or-id> pihole -d

where you substitute <pihole-container-name-or-id> as required.

[Eraser127]

Debug token:

https://tricorder.pi-hole.net/zscHW4hl/