coop-cloud/organising
coop-cloud
/
organising
7
0
Fork 0
Code Issues 157 Pull Requests Projects 2 Releases Activity

abra app upgrade -f reports "no published release discovered" #444

New Issue
Closed
opened 2023-04-12 09:29:18 +00:00 by decentral1se · 4 comments
decentral1se commented 2023-04-12 09:29:18 +00:00
Owner
Copy Link

I have a matrix-synapse install which is on the latest catalogue version. I've just upgraded it. While reading #440 I wanted to try upgrade -f to see what it does. It reports:

FATA[0001] no published release discovered for matrix-synapse

I can confirm that I have the latest catalogue locally and the recipe is up-to-date. So, I am not sure what's going on? I was hoping that it would have the same functionality as deploy -f which does work.

I have a matrix-synapse install which is on the latest catalogue version. I've just upgraded it. While reading https://git.coopcloud.tech/coop-cloud/organising/issues/440 I wanted to try `upgrade -f` to see what it does. It reports: > FATA[0001] no published release discovered for matrix-synapse I can confirm that I have the latest catalogue locally and the recipe is up-to-date. So, I am not sure what's going on? I was hoping that it would have the same functionality as `deploy -f` which does work.
decentral1se added the
bug
 label 2023-04-12 09:29:18 +00:00
3wordchant commented 2023-04-12 15:59:37 +00:00
Owner
Copy Link

I've seen this too, also unsure of cause.

I've seen this too, also unsure of cause.
3wordchant commented 2023-04-13 16:16:58 +00:00
Owner
Copy Link

Also happening to me even on a fresh deploy.

-d output.

DEBU[0002] read recipe catalogue from file system cache in /home/user/.abra/catalogue/recipes.json  caller="/abra/pkg/recipe/recipe.go:751 rea
dRecipeCatalogueFS"
DEBU[0002] choosing 3.5.0+v1.81.0 as version to deploy   caller="/abra/cli/internal/deploy.go:78 DeployAction"
DEBU[0002] read global ignore paths: .DS_Store *.swp *.swo *.pyc /doc/tags /.envrc .~*#  caller="/abra/pkg/git/read.go:162 parseExcludesFil
e"
DEBU[0002] discovered clean git status in /home/user/.abra/recipes/matrix-synapse  caller="/abra/pkg/git/read.go:65 IsClean"
DEBU[0002] read 1.0.1+1.48.0, 1.1.0+v1.51.0, 1.2.0+v1.52.0, 1.3.0+v1.55.2, 2.0.0+v1.58.1, 2.1.0+v1.62.0, 2.2.0+v1.68.0, 2.3.0+v1.71.0, 2.4.
0+v1.72.0, 2.5.0+v1.73.0, 2.6.0+v1.74.0, 3.0.0+v1.74.0, 3.1.0+v1.76.0, 3.2.0+v1.77.0, 3.3.0+v1.78.0 as tags for recipe matrix-synapse  call
er="/abra/pkg/recipe/recipe.go:315 EnsureVersion"
FATA[0002] no published release discovered for matrix-synapse  caller="/abra/cli/internal/deploy.go:80 DeployAction" stack="/abra/cli/inter
nal/deploy.go:80                          DeployAction\n/go/pkg/mod/github.com/urfave/cli@v1.22.9/app.go:524     HandleAction\n/go/pkg/mod/
github.com/urfave/cli@v1.22.9/command.go:173 Command.Run\n/go/pkg/mod/github.com/urfave/cli@v1.22.9/app.go:405     (*App).RunAsSubcommand\n
/go/pkg/mod/github.com/urfave/cli@v1.22.9/command.go:378 Command.startApp\n/go/pkg/mod/github.com/urfave/cli@v1.22.9/command.go:102 Command
.Run\n/go/pkg/mod/github.com/urfave/cli@v1.22.9/app.go:277     (*App).Run\n/abra/cli/cli.go:200                                     RunApp\
n/abra/cmd/abra/main.go:22                                main\n/usr/local/go/src/runtime/proc.go:250                    main\n/usr/local/g
o/src/runtime/asm_amd64.s:1594               goexit"
Also happening to me even on a fresh deploy. `-d` output. ``` DEBU[0002] read recipe catalogue from file system cache in /home/user/.abra/catalogue/recipes.json caller="/abra/pkg/recipe/recipe.go:751 rea dRecipeCatalogueFS" DEBU[0002] choosing 3.5.0+v1.81.0 as version to deploy caller="/abra/cli/internal/deploy.go:78 DeployAction" DEBU[0002] read global ignore paths: .DS_Store *.swp *.swo *.pyc /doc/tags /.envrc .~*# caller="/abra/pkg/git/read.go:162 parseExcludesFil e" DEBU[0002] discovered clean git status in /home/user/.abra/recipes/matrix-synapse caller="/abra/pkg/git/read.go:65 IsClean" DEBU[0002] read 1.0.1+1.48.0, 1.1.0+v1.51.0, 1.2.0+v1.52.0, 1.3.0+v1.55.2, 2.0.0+v1.58.1, 2.1.0+v1.62.0, 2.2.0+v1.68.0, 2.3.0+v1.71.0, 2.4. 0+v1.72.0, 2.5.0+v1.73.0, 2.6.0+v1.74.0, 3.0.0+v1.74.0, 3.1.0+v1.76.0, 3.2.0+v1.77.0, 3.3.0+v1.78.0 as tags for recipe matrix-synapse call er="/abra/pkg/recipe/recipe.go:315 EnsureVersion" FATA[0002] no published release discovered for matrix-synapse caller="/abra/cli/internal/deploy.go:80 DeployAction" stack="/abra/cli/inter nal/deploy.go:80 DeployAction\n/go/pkg/mod/github.com/urfave/cli@v1.22.9/app.go:524 HandleAction\n/go/pkg/mod/ github.com/urfave/cli@v1.22.9/command.go:173 Command.Run\n/go/pkg/mod/github.com/urfave/cli@v1.22.9/app.go:405 (*App).RunAsSubcommand\n /go/pkg/mod/github.com/urfave/cli@v1.22.9/command.go:378 Command.startApp\n/go/pkg/mod/github.com/urfave/cli@v1.22.9/command.go:102 Command .Run\n/go/pkg/mod/github.com/urfave/cli@v1.22.9/app.go:277 (*App).Run\n/abra/cli/cli.go:200 RunApp\ n/abra/cmd/abra/main.go:22 main\n/usr/local/go/src/runtime/proc.go:250 main\n/usr/local/g o/src/runtime/asm_amd64.s:1594 goexit" ```
decentral1se added this to the Critical fixes project 2023-05-08 09:45:21 +00:00
decentral1se added the
abra
 label 2023-06-08 09:19:25 +00:00
decentral1se commented 2023-07-25 13:12:14 +00:00
Author
Owner
Copy Link

coop-cloud/abra#329 coming down the tubes...

@3wordchant #444 (comment) seems to be an unrelated issue to do with deploy logic. From the error message, it seems that abra had figured out choosing 3.5.0+v1.81.0 as version to deploy from the catalogue but then found read 1.0.1+1.48.0, 1.1.0+v1.51.0, 1.2.0+v1.52.0, 1.3.0+v1.55.2, 2.0.0+v1.58.1, 2.1.0+v1.62.0, 2.2.0+v1.68.0, 2.3.0+v1.71.0, 2.4. 0+v1.72.0, 2.5.0+v1.73.0, 2.6.0+v1.74.0, 3.0.0+v1.74.0, 3.1.0+v1.76.0, 3.2.0+v1.77.0, 3.3.0+v1.78.0 from the recipe.

It's definitely there:

git for-each-ref refs/tags | grep -i 3.5.0+v1.81.0
b31c1a5642a1c4c801048d5dee16d8ef2b80346d tag	refs/tags/3.5.0+v1.81.0

I can confirm the code of EnsureVersion detects them all:

DEBU[0001] read 1.0.1+1.48.0, 1.1.0+v1.51.0, 1.2.0+v1.52.0, 1.3.0+v1.55.2, 2.0.0+v1.58.1, 2.1.0+v1.62.0, 2.2.0+v1.68.0, 2.3.0+v1.71.0, 2.4.0+v1.72.0, 2.5.0+v1.73.0, 2.6.0+v1.74.0, 3.0.0+v1.74.0, 3.1.0+v1.76.0, 3.2.0+v1.77.0, 3.3.0+v1.78.0, 3.4.0+v1.80.0, 3.5.0+v1.81.0, 3.6.0+v1.81.0, 3.7.0+v1.82.0, 3.8.0+v1.84.1, 3.9.1+v1.87.0 as tags for recipe matrix-synapse

Any ideas why abra couldn't read those tags? Putting some bogus version in the catalogue and then trying to run the commands, I can reproduce the error. So, it just seems the catalogue is out of sync somehow with the local recipe repository? I changed the error message to be more helpful for next time, if we can't get an answer to this now (9f478dac1d/pkg/recipe/recipe.go (L320)).

https://git.coopcloud.tech/coop-cloud/abra/pulls/329 coming down the tubes... @3wordchant https://git.coopcloud.tech/coop-cloud/organising/issues/444#issuecomment-16351 seems to be an unrelated issue to do with `deploy` logic. From the error message, it seems that `abra` had figured out `choosing 3.5.0+v1.81.0 as version to deploy` from the catalogue but then found `read 1.0.1+1.48.0, 1.1.0+v1.51.0, 1.2.0+v1.52.0, 1.3.0+v1.55.2, 2.0.0+v1.58.1, 2.1.0+v1.62.0, 2.2.0+v1.68.0, 2.3.0+v1.71.0, 2.4. 0+v1.72.0, 2.5.0+v1.73.0, 2.6.0+v1.74.0, 3.0.0+v1.74.0, 3.1.0+v1.76.0, 3.2.0+v1.77.0, 3.3.0+v1.78.0` from the recipe. It's definitely there: ``` git for-each-ref refs/tags | grep -i 3.5.0+v1.81.0 b31c1a5642a1c4c801048d5dee16d8ef2b80346d tag refs/tags/3.5.0+v1.81.0 ``` I can confirm the code of `EnsureVersion` detects them all: ``` DEBU[0001] read 1.0.1+1.48.0, 1.1.0+v1.51.0, 1.2.0+v1.52.0, 1.3.0+v1.55.2, 2.0.0+v1.58.1, 2.1.0+v1.62.0, 2.2.0+v1.68.0, 2.3.0+v1.71.0, 2.4.0+v1.72.0, 2.5.0+v1.73.0, 2.6.0+v1.74.0, 3.0.0+v1.74.0, 3.1.0+v1.76.0, 3.2.0+v1.77.0, 3.3.0+v1.78.0, 3.4.0+v1.80.0, 3.5.0+v1.81.0, 3.6.0+v1.81.0, 3.7.0+v1.82.0, 3.8.0+v1.84.1, 3.9.1+v1.87.0 as tags for recipe matrix-synapse ``` Any ideas why `abra` couldn't read those tags? Putting some bogus version in the catalogue and then trying to run the commands, I can reproduce the error. So, it just seems the catalogue is out of sync somehow with the local recipe repository? I changed the error message to be more helpful for next time, if we can't get an answer to this now (https://git.coopcloud.tech/coop-cloud/abra/src/commit/9f478dac1db5ad3295f619728f70e6f81dfd4645/pkg/recipe/recipe.go#L320).
decentral1se self-assigned this 2023-07-25 13:13:35 +00:00
decentral1se added spent time 2023-07-25 13:13:49 +00:00
1 hour 30 minutes
decentral1se commented 2023-07-25 13:24:59 +00:00
Author
Owner
Copy Link

Ah, let's focus on that issue on #414.

Ah, let's focus on that issue on https://git.coopcloud.tech/coop-cloud/organising/issues/414.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
master
Labels
Clear labels   
abra

Everything to do with abra

  
abra-gandi

Abra Gandi plugin

  
awaiting-feedback

Ping/pong on comms

  
backups

   
bug

Something is not working

  
build

Go build related issues

  
ci/cd

Getting the robots into the mix

  
community organising

Opening this thing up

  
contributing

Contributors stuff

  
coopcloud.tech

Our main website

  
democracy

Democratic decision making

  
design

Design thinking required

  
documentation

Let's write things together

  
duplicate

This issue or pull request already exists

  
enhancement

New feature

  
finance

Money things

  
funding

Anything related to grant funding

  
good first issue

Easy start with development

  
help wanted

Need some help

  
installer

Installation related issues

  
kadabra

   
performance

Performance related

  
proposal

Large change which requires feedback & decisin making

  
question

More information is needed

  
recipes.coopcloud.tech

Our recipes catalogue

  
security

Securing our shit

  
test

Unit or integration test suite

  
wontfix

This won't be fixed

No Label
abra
abra-gandi
awaiting-feedback
backups
bug
build
ci/cd
community organising
contributing
coopcloud.tech
democracy
design
documentation
duplicate
enhancement
finance
funding
good first issue
help wanted
installer
kadabra
performance
proposal
question
recipes.coopcloud.tech
security
test
wontfix
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Critical fixes
Assignees
Clear assignees
No Assignees
decentral1se
2 Participants
Notifications
Total Time Spent: 1 hour 30 minutes
decentral1se
1 hour 30 minutes
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#444
No description provided.
Delete Branch "%!s(<nil>)"

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?