It’s not an error but an expected behaviour when the DB is running migrations.
It’s been mentioned in the release notes too:
