abra app upgrade reports success even if app is still running old version of one service #615

New Issue

3wordchant · 2024-05-07T18:56:26Z

3wordchant commented

2024-05-07 18:56:26 +00:00

Deploy nextcloud 27
abra app upgrade ...
INFO[0094] Successfully deployed...

Except:

➜ abra app ps foo.bar.com
+--------------+----------------------+---------------+------------------------+---------+----------+
| SERVICE NAME |        IMAGE         |    CREATED    |         STATUS         |  STATE  |  PORTS   |
+--------------+----------------------+---------------+------------------------+---------+----------+
| web          | nginx:1.25.3         | 2 minutes ago | Up 2 minutes (healthy) | running | 80/tcp   |
| db           | mariadb:10.5         | 2 minutes ago | Up 2 minutes (healthy) | running | 3306/tcp |
| cron         | nextcloud:28.0.5-fpm | 2 minutes ago | Up 2 minutes           | running | 9000/tcp |
| cache        | redis:7.2.4-alpine   | 5 days ago    | Up 5 days (healthy)    | running | 6379/tcp |
| app          | nextcloud:27.1.5-fpm | 2 weeks ago   | Up 2 weeks (healthy)   | running | 9000/tcp |
+--------------+----------------------+---------------+------------------------+---------+----------+

3wordchant added the

bug

label 2024-05-07 18:56:26 +00:00

decentral1se commented

2024-05-14 06:35:59 +00:00

I guess the runtime reported success, so abra just did the same...

In this case, would you propose to add an additional check or some logic for abra?

I guess the runtime reported success, so `abra` just did the same... In this case, would you propose to add an additional check or some logic for `abra`?

Sign in to join this conversation.

No Milestone

No project

No Assignees

2 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: coop-cloud/organising#615

abra app upgrade reports success even if app is still running old version of one service #615

`abra app upgrade` reports success even if app is still running old version of one service #615