Skip to content

Commit 0f6feb5

Browse files
authored
Update faq.md: move errors to bottom
1 parent 6088343 commit 0f6feb5

File tree

1 file changed

+6
-5
lines changed

1 file changed

+6
-5
lines changed

docs/faq.md

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -140,11 +140,6 @@ secrets:
140140
external: true
141141
```
142142

143-
## Errors
144-
145-
### "Stack:… is in UPDATE_COMPLETE_CLEANUP_IN_PROGRESS state and cannot be updated"
146-
- This happens if different version of the Defang CLI are used with the same AWS account. Each version one will try to update the CD stack to its version, back and forth. Make sure that all users have the same version of the CLI. Check the CLI version using `defang version`.
147-
148143
### "invalid healthcheck: ingress ports require an HTTP healthcheck on `localhost`.
149144

150145
- This message is displayed when `defang compose up` tries to deploy a service with an "ingress" port, if the service does not have a `healthcheck` which mentions `localhost`. Defang routes a load balancer to your service's ingress ports, and the loadbalancer needs to be able to check the health of the service. To solve this issue, ask yourself these two questions:
@@ -172,3 +167,9 @@ secrets:
172167
healthcheck:
173168
test: ["CMD", "./my-healthcheck"]
174169
```
170+
171+
172+
## Errors
173+
174+
### "Stack:… is in UPDATE_COMPLETE_CLEANUP_IN_PROGRESS state and cannot be updated"
175+
- This happens if different version of the Defang CLI are used with the same AWS account. Each version one will try to update the CD stack to its version, back and forth. Make sure that all users have the same version of the CLI. Check the CLI version using `defang version`.

0 commit comments

Comments
 (0)