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

Bug: Quartz jobs start before database init by EF #1206

Closed
hocinehacherouf opened this issue Sep 11, 2022 · 0 comments · Fixed by #1213
Closed

Bug: Quartz jobs start before database init by EF #1206

hocinehacherouf opened this issue Sep 11, 2022 · 0 comments · Fixed by #1213
Assignees
Labels
bug Something isn't working
Milestone

Comments

@hocinehacherouf
Copy link
Contributor

hocinehacherouf commented Sep 11, 2022

Expected Behavior

Quartz jobs must start when EF has finished its migrations.

Current Behavior

Quartz jobs start before EF initializes its migrations

Steps to Reproduce

On a dev env:

  1. Delete any pgdata docker volume (fresh database)
  2. Run Portal solution
@hocinehacherouf hocinehacherouf added the bug Something isn't working label Sep 11, 2022
@hocinehacherouf hocinehacherouf added this to the S40 milestone Sep 11, 2022
@kbeaugrand kbeaugrand moved this to 📝 Todo in IoT Hub Portal Sep 11, 2022
@kbeaugrand kbeaugrand self-assigned this Sep 11, 2022
@kbeaugrand kbeaugrand moved this from 📝 Todo to 🚧 In Progress in IoT Hub Portal Sep 11, 2022
@kbeaugrand kbeaugrand moved this from 🚧 In Progress to 💬 Ready for Review in IoT Hub Portal Sep 11, 2022
@kbeaugrand kbeaugrand moved this from 💬 Ready for Review to 🚧 In Progress in IoT Hub Portal Sep 11, 2022
@kbeaugrand kbeaugrand moved this from 🚧 In Progress to 💬 Ready for Review in IoT Hub Portal Sep 11, 2022
@kbeaugrand kbeaugrand moved this from 💬 Ready for Review to 🚀 Ready in IoT Hub Portal Sep 11, 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
Status: 🚀 Ready
Development

Successfully merging a pull request may close this issue.

2 participants