toolshed/abra
4
2
Fork 18
Code Issues 22 Pull Requests Packages Releases 41 Activity

no logs on rollback #575

New Issue
Closed
opened 2025-06-13 13:28:33 +00:00 by fauno · 2 comments
fauno commented 2025-06-13 13:28:33 +00:00
Member
Copy Link

i was trying to deploy chaotically a local update:

>_ abra app deploy -o -D -C git.sutty.abyaya.la                                                                            
┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓                                                                                         
┃               DEPLOY OVERVIEW               ┃                                                                                         
┃                                             ┃                                                                                         
┃ DOMAIN                git.sutty.abyaya.la   ┃                                                                                         
┃ RECIPE                gitea                 ┃                                                                                         
┃ SERVER                sutty.comun           ┃                                                                                         
┃                       compose.yml           ┃                                                                                         
┃                       compose.sqlite3.yml   ┃                                                                                         
┃                       compose.forgejo.yml   ┃                                                                                         
┃ CONFIG                compose.smtp.yml      ┃                                                                                         
┃                                             ┃                                                                                         
┃ CURRENT DEPLOYMENT    3.3.0+1.23.1-rootless ┃                                                                                         
┃ ENV VERSION           a3b54a62              ┃                                                                                         
┃ NEW DEPLOYMENT        6fd9ce64              ┃                                                                                         
┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛                                                                                         
? proceed? Yes                                                                                                                          
INFO initialising deployment                                                                                                            
INFO polling deployment status                                                                                                          
app: rolled back (retries: 0, healthcheck: healthy)                                                                                     
FATA deploy failed 🛑

but abra app logs wasn't reporting the reason for rolling back, afaict the service was started on the version i intented to deploy.

an abra app undeploy worked correctly.

i was trying to deploy chaotically a local update: ``` >_ abra app deploy -o -D -C git.sutty.abyaya.la ┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓ ┃ DEPLOY OVERVIEW ┃ ┃ ┃ ┃ DOMAIN git.sutty.abyaya.la ┃ ┃ RECIPE gitea ┃ ┃ SERVER sutty.comun ┃ ┃ compose.yml ┃ ┃ compose.sqlite3.yml ┃ ┃ compose.forgejo.yml ┃ ┃ CONFIG compose.smtp.yml ┃ ┃ ┃ ┃ CURRENT DEPLOYMENT 3.3.0+1.23.1-rootless ┃ ┃ ENV VERSION a3b54a62 ┃ ┃ NEW DEPLOYMENT 6fd9ce64 ┃ ┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛ ? proceed? Yes INFO initialising deployment INFO polling deployment status app: rolled back (retries: 0, healthcheck: healthy) FATA deploy failed 🛑 ``` but `abra app logs` wasn't reporting the reason for rolling back, afaict the service was started on the version i intented to deploy. an `abra app undeploy` worked correctly.
fauno commented 2025-06-13 13:29:32 +00:00
Author
Member
Copy Link

docker container ls on the server was showing the previous version running, but i couldn't catch it during the rolled back deploy so i'm not sure if it's helpful info

`docker container ls` on the server was showing the previous version running, but i couldn't catch it during the rolled back deploy so i'm not sure if it's helpful info
decentral1se added the
bug
 label 2025-06-14 22:47:15 +00:00
decentral1se self-assigned this 2025-07-08 09:58:48 +00:00
decentral1se added this to the Abra v0.11.x project 2025-07-08 10:06:51 +00:00
decentral1se moved this to In Progress in Abra v0.11.x on 2025-08-25 10:15:41 +00:00
decentral1se commented 2025-08-29 08:07:45 +00:00
Owner
Copy Link

So, I believe this was a combination of factors.

First, we do not have a warning output that no logs could be collected from the failing deployment. That is now added with #625.

We did some work to make abra app ps / abra app logs (in toolshed/organising#501 and elsewhere) more reliable and report when the container is just exploding and can't deploy. However, I actually realise we still don't have the docker stack ps --no-trunc output anywhere 🤦 This is the real output we always need and shows the error, even when the container refuses to start up.

I will try to bring this into #613 when we make logs visible on the deploy polling screen.

So, I believe this was a combination of factors. First, we do not have a warning output that no logs could be collected from the failing deployment. That is now added with https://git.coopcloud.tech/toolshed/abra/pulls/625. We did some work to make `abra app ps` / `abra app logs` (in https://git.coopcloud.tech/toolshed/organising/issues/501 and elsewhere) more reliable and report when the container is just exploding and can't deploy. However, I actually realise we still don't have the `docker stack ps --no-trunc` output anywhere 🤦 This is the real output we always need and shows the error, even when the container refuses to start up. I will try to bring this into https://git.coopcloud.tech/toolshed/abra/issues/613 when we make logs visible on the deploy polling screen.
decentral1se moved this to Done in Abra v0.11.x on 2025-08-29 08:09:33 +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
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
easy-first-issue
Something for new people to get stuck into. We hope it's easy!
enhancement
New feature
help wanted
Need some help
i10n
Everything to do with localisation
i18n
Everything to do with internationalisation
invalid
Something is wrong
question
More information is needed
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
Milestone
No items
No Milestone
Projects
Clear projects
No project Abra v0.11.x
Assignees
Clear assignees
3wordchant aadil abra-bot ammaratef45 Apfelwurm carla cas coopcloud cyrnel decentral1se fauno iexos jmakdah2 kawaiipunk knoflook kolaente 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#575
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?