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

Module showed the old schema for ftl schema get even though it built successfully as part of deploy process #2098

Closed
matt2e opened this issue Jul 17, 2024 · 2 comments
Labels
triage Issue needs triaging

Comments

@matt2e
Copy link
Collaborator

matt2e commented Jul 17, 2024

After this: #2095

Module MM shows old schema when calling ftl schema get even though it had been successfully built in the deploy process

Initial thoughts:

  • If it was just built then it seems ok that the old schema is showing up here because we return the active schema (ie active runners > 0)
  • ... but we had started to wait for new deployments of MM to come up, which would normally cause the old deployments to be taken down and new ones to come up... but this seems to indicate that the old ones are still active? Why are old ones still active?
@github-actions github-actions bot added the triage Issue needs triaging label Jul 17, 2024
@ftl-robot ftl-robot mentioned this issue Jul 17, 2024
@bradleydwyer
Copy link
Collaborator

A snapshot of the DB is available if necessary.

@matt2e
Copy link
Collaborator Author

matt2e commented Jul 18, 2024

Fixed in #2110

@matt2e matt2e closed this as completed Jul 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage Issue needs triaging
Projects
None yet
Development

No branches or pull requests

2 participants