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

KuduSync does not delete files that were created by a failed deployment #37

Open
MarkBird opened this issue Apr 8, 2019 · 0 comments
Open

Comments

@MarkBird
Copy link

MarkBird commented Apr 8, 2019

We have encountered this a few times.

  • file migrations/0026_auto_20190408_1538.py is added to source control and pushed to Bitbucket
  • triggers deployment
  • deployment fails
  • we delete migrations/0026_auto_20190408_1538.py and push
  • triggers deployment
  • deployment still fails because the erroneous file still exists

I believe this is happening because on a failed deployment, the manifest is not saved, so when KuduSync looks for the previous manifest to determine what to delete, it doesn't see the file it should be deleting.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant