I am working on a PR in an unrelated area and got a PR build failure on kubernetes end to end tests, with

Exception in thread "main" java.lang.RuntimeException: could not find workspace with id: 5ae6b09b-fdec-41af-aaf7-7d94cfc33ef6

I haven’t touched workspace ids; all I did was pull in the latest code. Any idea what this is coming from?

so looking at this it seems like this is a race condition where the

ServerApp

’s

setCustomerIdIfNotSet

is being called before the init container for the scheduler is available

I think this was “introduced” via George’s (by no fault of his own) because we changed exactly where we were waiting for the database.

Alright.

Before we were waiting for the database before this check, now we’re waiting afterwards.

I think what we need to do is either in the code for the ServerApp we need to wait until the initcontainer is done or we need an initcontainer for the server to guarantee this isn’t happening.

I’m going to re-run the job (I expect it’s passing most of the time based off of the string of green master builds).

I’ll try to fix the underlying issue tomorrow.