Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deployment failure due to db-migrate #2751

Closed
t-young31 opened this issue Oct 18, 2022 · 6 comments
Closed

Deployment failure due to db-migrate #2751

t-young31 opened this issue Oct 18, 2022 · 6 comments
Labels
bug Something isn't working

Comments

@t-young31
Copy link
Contributor

Describe the bug

We've updated to v0.5.1 and are having trouble deploying the TRE. The deployment fails with

make: *** [/home/vscode/AzureTRE/Makefile:344: db-migrate] Error 1
HTTP/1.1 400 Bad Request
Date: Tue, 18 Oct 2022 16:52:04 GMT
Content-Type: text/plain; charset=utf-8
Content-Length: 23
Connection: keep-alive
Server: uvicorn

list index out of range
Error while migrating state store
Error: Process completed with exit code 2.

I've dug into this a little more and the 400 occurs at

migrate_result=$(curl -i -X "POST" "${tre_url}/api/migrations" "${curl_options[@]}" \

I'm pretty certain the secrets are right, but could be proved otherwise!

Steps to reproduce

  1. Run deployment pipeline https://github.com/microsoft/AzureTRE-Deployment/blob/main/.github/workflows/deploy_tre.yml

cc: @marrobi

@t-young31 t-young31 added the bug Something isn't working label Oct 18, 2022
@tamirkamara
Copy link
Collaborator

@t-young31 can you access the app insights (appi*) in the environment in question and run this query to look from exceptions in the time that has happened?

exceptions
| order by timestamp desc

@t-young31
Copy link
Contributor Author

Screenshot 2022-10-19 at 08 39 27

@tamirkamara
Copy link
Collaborator

@t-young31 is the firewall installed in your TRE environment?

@t-young31
Copy link
Contributor Author

hmm, it looks like the firewall has failed to deploy due to something already existing in the tf state

@tamirkamara
Copy link
Collaborator

@t-young31 we think there's a bug where the install action of the firewall returns an ok status despite failing. This is being fixed as part of this: #2747
CC: @stuartleeks

@t-young31
Copy link
Contributor Author

just to close the loop on this one – once the firewall was deployed successfully the migration worked just fine. thanks for the tips!

@marrobi marrobi closed this as completed Oct 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants