OOZIE-1655 changed oozie-default’s oozie.service.JPAService.create.db.schema to match oozie-site by setting it to false. This caused all or most unit tests to either fail with errors containing "Cannot create PoolableConnectionFactory" or to get stuck. For the unit tests, we need to set the property to true so that it will create the database schema because we don't create it manually like during a regular deployment. This was only working before because oozie-default and oozie-site were not in-sync.
I'm not sure why test-patch in
OOZIE-1655 didn't catch this or why I had to clone into a new folder to reproduce this locally either. Perhaps we're not deleting the database when doing a mvn clean?