abra app ls -S not reporting latest versions for traefik? #561

New Issue

2025-05-21T18:54:40Z

fauno commented

2025-05-21 18:54:40 +00:00

>_ abra app list -s xxxxx.xxxxx -S
┏━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━┳━━━━━━━━━━┳━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━┳━━━━━━━━━━━━┓
┃     RECIPE     ┃           DOMAIN            ┃   SERVER    ┃  STATUS  ┃  CHAOS   ┃        VERSION        ┃ UPGRADE ┃ AUTOUPDATE ┃
┣━━━━━━━━━━━━━━━━╋━━━━━━━━━━━━━━━━━━━━━━━━━━━━━╋━━━━━━━━━━━━━╋━━━━━━━━━━╋━━━━━━━━━━╋━━━━━━━━━━━━━━━━━━━━━━━╋━━━━━━━━━╋━━━━━━━━━━━━┫
┃ traefik        ┃ traefik.xxxxx.xxxxxx.xx     ┃ xxxxx.xxxxx ┃ deployed ┃ false    ┃ 2.9.1+v2.11.14        ┃ latest  ┃ true       ┃

but looking at traefik.git recipe, it should suggest 3.1.0+v2.11.24, no?

``` >_ abra app list -s xxxxx.xxxxx -S ┏━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━┳━━━━━━━━━━┳━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━┳━━━━━━━━━━━━┓ ┃ RECIPE ┃ DOMAIN ┃ SERVER ┃ STATUS ┃ CHAOS ┃ VERSION ┃ UPGRADE ┃ AUTOUPDATE ┃ ┣━━━━━━━━━━━━━━━━╋━━━━━━━━━━━━━━━━━━━━━━━━━━━━━╋━━━━━━━━━━━━━╋━━━━━━━━━━╋━━━━━━━━━━╋━━━━━━━━━━━━━━━━━━━━━━━╋━━━━━━━━━╋━━━━━━━━━━━━┫ ┃ traefik ┃ traefik.xxxxx.xxxxxx.xx ┃ xxxxx.xxxxx ┃ deployed ┃ false ┃ 2.9.1+v2.11.14 ┃ latest ┃ true ┃ ``` but looking at traefik.git recipe, it should suggest 3.1.0+v2.11.24, no?

fauno commented

2025-05-21 19:11:05 +00:00

i could run abra app upgrade and select 3.1.0+v2.11.24 manually.

i could run `abra app upgrade` and select `3.1.0+v2.11.24` manually.

decentral1se commented

2025-05-23 08:35:28 +00:00

@fauno without --debug logs, this is hard to start to try to figure out. I imagine the local state has changed now but it would also be good to see your local $ABRA_DIR/catalogue/recipes.json contents for traefik. I imagine that a abra app upgrade did a pull of the latest changes and perhaps abra app list does not? If you can provide any further information or try to test again to get some deeper insight into the issue, that'd be much appreciated. I think I have a few tests in mind on how to smoke this out but I am short on time currently.

@fauno without `--debug` logs, this is hard to start to try to figure out. I imagine the local state has changed now but it would also be good to see your local `$ABRA_DIR/catalogue/recipes.json` contents for `traefik`. I imagine that a `abra app upgrade` did a pull of the latest changes and perhaps `abra app list` does not? If you can provide any further information or try to test again to get some deeper insight into the issue, that'd be much appreciated. I think I have a few tests in mind on how to smoke this out but I am short on time currently.

fauno commented

2025-05-23 14:00:51 +00:00

fwiw i had the latest changes on the traefik repo before running abra app upgrade, and had run abra recipe fetch a couple days before, or maybe the same day, but before running abra app ls -S.

now that i upgraded, i see:

┃ traefik        ┃ traefik.xxxxx.xxxxxx.xx     ┃ xxxxx.xxxxx ┃ deployed ┃ false    ┃ 3.1.0+v2.11.24        ┃ 4.1.2+v3.1.2 ┃ true       ┃
┃                ┃                             ┃             ┃          ┃          ┃                       ┃ 4.1.1+v3.1.1 ┃            ┃
┃                ┃                             ┃             ┃          ┃          ┃                       ┃ 4.1.0+v3.1.0 ┃            ┃
┃                ┃                             ┃             ┃          ┃          ┃                       ┃ 4.0.4+v3.0.4 ┃            ┃
┃                ┃                             ┃             ┃          ┃          ┃                       ┃ 4.0.3+v3.0.3 ┃            ┃
┃                ┃                             ┃             ┃          ┃          ┃                       ┃ 4.0.2+v3.0.2 ┃            ┃
┃                ┃                             ┃             ┃          ┃          ┃                       ┃ 4.0.1+v3.0.1 ┃            ┃
┃                ┃                             ┃             ┃          ┃          ┃                       ┃ 4.0.0+v3.0.0 ┃            ┃

(no idea why gitea would have line wraps on code blocks...)

fwiw i had the latest changes on the traefik repo before running `abra app upgrade`, and had run `abra recipe fetch` a couple days before, or maybe the same day, but before running `abra app ls -S`. now that i upgraded, i see: ``` ┃ traefik ┃ traefik.xxxxx.xxxxxx.xx ┃ xxxxx.xxxxx ┃ deployed ┃ false ┃ 3.1.0+v2.11.24 ┃ 4.1.2+v3.1.2 ┃ true ┃ ┃ ┃ ┃ ┃ ┃ ┃ ┃ 4.1.1+v3.1.1 ┃ ┃ ┃ ┃ ┃ ┃ ┃ ┃ ┃ 4.1.0+v3.1.0 ┃ ┃ ┃ ┃ ┃ ┃ ┃ ┃ ┃ 4.0.4+v3.0.4 ┃ ┃ ┃ ┃ ┃ ┃ ┃ ┃ ┃ 4.0.3+v3.0.3 ┃ ┃ ┃ ┃ ┃ ┃ ┃ ┃ ┃ 4.0.2+v3.0.2 ┃ ┃ ┃ ┃ ┃ ┃ ┃ ┃ ┃ 4.0.1+v3.0.1 ┃ ┃ ┃ ┃ ┃ ┃ ┃ ┃ ┃ 4.0.0+v3.0.0 ┃ ┃ ``` (no idea why gitea would have line wraps on code blocks...)

decentral1se commented

2025-05-27 06:47:03 +00:00

I have more logs from @iexos showing another reproduction for this. It's definitely a 🐛

decentral1se added the bug label 2025-05-27 06:47:10 +00:00

decentral1se added this to the Abra v0.11.x project 2025-05-27 06:47:19 +00:00

decentral1se referenced this issue

2025-05-27 07:02:21 +00:00

UX difficulties encountered when working with recipes #563

iexos referenced a pull request that will close this issue

2025-05-27 15:27:26 +00:00

fix #561 #565

decentral1se added the critical fix label 2025-06-05 12:22:44 +00:00

decentral1se self-assigned this 2025-07-08 09:59:39 +00:00

decentral1se moved this to In Progress in Abra v0.11.x on 2025-08-12 12:20:30 +00:00

decentral1se commented

2025-08-12 12:35:39 +00:00

@fauno @iexos sorry for the massive delay. I've spent time diagnosing this from the issues / provided logs/patches / running the tests / etc. From the logs of @iexos and provided fix #565 I realised that that is indeed the perfect fix 😅 I am running the integration suite now to ensure there is no further regression. The root cause is 1. old abra always set the chaosVersion (fixed in #479) 2. new abra made a decision based on this label (see 6fb41e5300) which caused this issue to appear between abra versions 🙈 That makes it near impossible to test reliably so I'm just gonna run everything and if it passes, merge #565 Sorry again for the delay but glad to be more sure what is going on at least now and reasonably certain there will be no further regression 🙏

@fauno @iexos sorry for the massive delay. I've spent time diagnosing this from the issues / provided logs/patches / running the tests / etc. From the logs of @iexos and provided fix https://git.coopcloud.tech/toolshed/abra/pulls/565 I realised that that is indeed the perfect fix 😅 I am running the integration suite now to ensure there is no further regression. The root cause is 1. old abra always set the `chaosVersion` (fixed in https://git.coopcloud.tech/toolshed/abra/pulls/479) 2. new abra made a decision based on this label (see https://git.coopcloud.tech/toolshed/abra/commit/6fb41e530011e131a0386ccdd0dd279881c04905) which caused this issue to appear between `abra` versions 🙈 That makes it near impossible to test reliably so I'm just gonna run everything and if it passes, merge https://git.coopcloud.tech/toolshed/abra/pulls/565 Sorry again for the delay but glad to be more sure what is going on at least now and reasonably certain there will be no further regression 🙏

❤️ 1

decentral1se referenced this issue

2025-08-12 12:45:59 +00:00

fix #561 #565

decentral1se closed this issue

2025-08-12 13:10:17 +00:00

decentral1se referenced this issue from a commit

2025-08-12 13:10:18 +00:00

fix: app ls -S didn't show updates sometimes (#561)

decentral1se moved this to Done in Abra v0.11.x on 2025-08-12 13:10:38 +00:00

Sign in to join this conversation.