Timeout label being used as version #451

New Issue

yksflip · 2023-05-24T09:39:25Z

yksflip commented

2023-05-24 09:39:25 +00:00

abra version dev-664edce

abra r rl tries to use the value of the TIMEOUT label as a Version ...

compose.yml

...
        - "coop-cloud.${STACK_NAME}.version=2.3.1+v2.10.2"
        - "coop-cloud.${STACK_NAME}.timeout=${TIMEOUT:-120}"
...

env.sample

TYPE=traefik
TIMEOUT=300

It seems to be a bit random, after trying couple of times it also gets the correct one ...

╭─yksflip@gundula ~/.abra/recipes/traefik  ‹master*›
╰─➤  abra r rl -p traefik
WARN[0000] discovered 300 as currently synced recipe label
WARN[0000] previous git tags detected, assuming this is a new semver release
? current: 2.3.0+v2.10.2, new: 300, correct? No
FATA[0004] exiting as requested
╭─yksflip@gundula ~/.abra/recipes/traefik  ‹master*›
╰─➤  abra r rl -p traefik                                                                                                                                                                                                                                                     1 ↵
WARN[0000] discovered 300 as currently synced recipe label
WARN[0000] previous git tags detected, assuming this is a new semver release
? current: 2.3.0+v2.10.2, new: 300, correct? No
FATA[0001] exiting as requested
╭─yksflip@gundula ~/.abra/recipes/traefik  ‹master*›
╰─➤  abra r rl -p traefik                                                                                                                                                                                                                                                     1 ↵
WARN[0000] discovered 300 as currently synced recipe label
WARN[0000] previous git tags detected, assuming this is a new semver release
? current: 2.3.0+v2.10.2, new: 300, correct? No
FATA[0000] exiting as requested
╭─yksflip@gundula ~/.abra/recipes/traefik  ‹master*›
╰─➤  abra r rl -p traefik                                                                                                                                                                                                                                                     1 ↵
WARN[0000] discovered 2.3.1+v2.10.2 as currently synced recipe label
WARN[0000] previous git tags detected, assuming this is a new semver release
? current: 2.3.0+v2.10.2, new: 2.3.1+v2.10.2, correct? (y/N)

`abra version dev-664edce` `abra r rl` tries to use the value of the *TIMEOUT* label as a Version ... compose.yml ``` ... - "coop-cloud.${STACK_NAME}.version=2.3.1+v2.10.2" - "coop-cloud.${STACK_NAME}.timeout=${TIMEOUT:-120}" ... ``` env.sample ``` TYPE=traefik TIMEOUT=300 ``` It seems to be a bit random, after trying couple of times it also gets the correct one ... ``` ╭─yksflip@gundula ~/.abra/recipes/traefik ‹master*› ╰─➤ abra r rl -p traefik WARN[0000] discovered 300 as currently synced recipe label WARN[0000] previous git tags detected, assuming this is a new semver release ? current: 2.3.0+v2.10.2, new: 300, correct? No FATA[0004] exiting as requested ╭─yksflip@gundula ~/.abra/recipes/traefik ‹master*› ╰─➤ abra r rl -p traefik 1 ↵ WARN[0000] discovered 300 as currently synced recipe label WARN[0000] previous git tags detected, assuming this is a new semver release ? current: 2.3.0+v2.10.2, new: 300, correct? No FATA[0001] exiting as requested ╭─yksflip@gundula ~/.abra/recipes/traefik ‹master*› ╰─➤ abra r rl -p traefik 1 ↵ WARN[0000] discovered 300 as currently synced recipe label WARN[0000] previous git tags detected, assuming this is a new semver release ? current: 2.3.0+v2.10.2, new: 300, correct? No FATA[0000] exiting as requested ╭─yksflip@gundula ~/.abra/recipes/traefik ‹master*› ╰─➤ abra r rl -p traefik 1 ↵ WARN[0000] discovered 2.3.1+v2.10.2 as currently synced recipe label WARN[0000] previous git tags detected, assuming this is a new semver release ? current: 2.3.0+v2.10.2, new: 2.3.1+v2.10.2, correct? (y/N) ```

yksflip added the

bug

label 2023-05-24 09:39:25 +00:00

decentral1se added this to the Critical fixes project 2023-05-24 09:43:00 +00:00

knoflook commented

2023-05-29 13:14:47 +00:00

I'm getting the same error when I was upgrading the wordpress recipe from 2.3.2 to 2.3.3, re-running a few times fixed the problem