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

Retry in sync_dns_scheduler if migration not finished #2154

Merged
merged 2 commits into from
Apr 10, 2019

Conversation

beyhan
Copy link
Member

@beyhan beyhan commented Mar 12, 2019

We have to ensure that the migration has finshed succesfully in the
sync_dns_scheduler, before we can load the db Models. Otherwise the
sync-dns job gets into an inconsistent state since the db is still being
migrated or DB being upgraded.

#164325756

Co-authored-by: Sebastian Heid [email protected]
Co-authored-by: Vladimir Videlov [email protected]
Co-authored-by: Denis Langer [email protected]

What is this change about?

Fix #2150

What tests have you run against this PR?

All unit and integration tests.
Also manually verified functionality by delaying the database migration by 30 seconds.

Does this PR introduce a breaking change?

No.

Tag your pair, your PM, and/or team!

@s4heid && @videlov && @langered

@cf-gitbot
Copy link

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/164576311

The labels on this github issue will be updated when the story is started.

@cfdreddbot
Copy link

✅ Hey beyhan! The commit authors and yourself have already signed the CLA.

We have to ensure that the migration has finshed succesfully in the
sync_dns_scheduler, before we can load the db Models. Otherwise the
sync-dns job gets into an inconsistent state since the db is still being
migrated or DB being upgraded.

[#164325756](https://www.pivotaltracker.com/story/show/164325756)

Co-authored-by: Sebastian Heid <[email protected]>
Co-authored-by: Vladimir Videlov <[email protected]>
Co-authored-by: Denis Langer <[email protected]>
@langered langered force-pushed the ensure-migration-sync-dns-job branch from 1d070b4 to beb0061 Compare March 13, 2019 08:17
Thread doesn't propagate exceptions but silently terminates if join is
not called. Hence we only can use the ensure block to shut down the
process or use Thread.abort_on_exception.

[#164600574](https://www.pivotaltracker.com/story/show/164600574)
@NautiluX
Copy link

This change fixes this related issue where it director-sync-dns doesn't stop if an exception occurs.

@jfmyers9 jfmyers9 merged commit 707534c into master Apr 10, 2019
@mrosecrance mrosecrance deleted the ensure-migration-sync-dns-job branch April 19, 2021 22:38
selzoc added a commit that referenced this pull request May 8, 2024
Previous to this commit, the integration tests used a very very old
version of UAA (3.5.0) from an s3 bucket that needed Java 8.  Updates to
the integration Docker image that raised the JDK from 8->17 caused this
very old version to explode.

This commit represents a major refactoring of how UAA runs in the
integration specs.
* The UAA version now tracks the version in bosh-deployment
* There is only 1 UAA started, as opposed to 1 per spec process
* The UAA version is from uaa-release, and is templated accordingly

Java upgrade PRs:
* #2154
* #2515
* #2516

Co-authored-by: Aram Price <[email protected]>
Co-authored-by: Chris Selzo <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

director_sync_dns process is in running state but with broken Sequel state
5 participants