toolshed/abra
4
2
Fork 18
Code Issues 37 Pull Requests 6 Packages Releases 40 Activity

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

New Issue
Closed
opened 2025-05-21 18:54:40 +00:00 by fauno · 5 comments
fauno commented 2025-05-21 18:54:40 +00:00
Member
Copy Link
>_ 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
Author
Member
Copy Link

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
Owner
Copy Link

@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
Author
Member
Copy Link

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
Owner
Copy Link

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

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 "next" project 2025-05-27 06:47:19 +00:00
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 added the
red abya yala
 label 2025-07-08 10:02:24 +00:00
decentral1se moved this to In Progress in Abra "next" on 2025-08-12 12:20:30 +00:00
decentral1se commented 2025-08-12 12:35:39 +00:00
Owner
Copy Link

@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 moved this to Done in Abra "next" on 2025-08-12 13:10:38 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something is not working
build
go build related issues
ci/cd
Building things with CI/CD
contributing
Dealing with contributing
critical fix
https://docs.coopcloud.tech/federation/resolutions/passed/010/
design
UI/UX
documentation
Documenting all the things
duplicate
This issue or pull request already exists
enhancement
New feature
help wanted
Need some help
invalid
Something is wrong
meta
relating to the project or repo itself
question
More information is needed
red abya yala
Work funded by Calyx institute for Red Abya Yala
release
Release management
release-candidate
Related to the new release candidate
security
Security related
test
Unit/integration testing
wontfix
This won't be fixed
No Label
bug
critical fix
red abya yala
Milestone
No items
No Milestone
Projects
Clear projects
No project Abra "next"
Assignees
Clear assignees
3wordchant abra-bot ammaratef45 Apfelwurm carla cas coopcloud decentral1se fauno jmakdah2 kawaiipunk knoflook lambdabundesverband moritz p4u1 ripclap simon sixsmith trav val yksflip
No Assignees decentral1se
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: toolshed/abra#561
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?