-
Notifications
You must be signed in to change notification settings - Fork 148
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
Comments
@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?
|
@t-young31 is the firewall installed in your TRE environment? |
hmm, it looks like the firewall has failed to deploy due to something already existing in the tf state |
@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 |
just to close the loop on this one – once the firewall was deployed successfully the migration worked just fine. thanks for the tips! |
Describe the bug
We've updated to v0.5.1 and are having trouble deploying the TRE. The deployment fails with
I've dug into this a little more and the 400 occurs at
AzureTRE/devops/scripts/migrate_state_store.sh
Line 81 in 316b9d1
I'm pretty certain the secrets are right, but could be proved otherwise!
Steps to reproduce
cc: @marrobi
The text was updated successfully, but these errors were encountered: