When updating to 1.10.x, the orders.orderer column is changed to foreign key to the provider table, not the user table. Also, the column is changed to be NOT NULL.
However the liquibase changeset to add the constraint to make orders NOT NULL comes before the changeset that migrates users to providers (and which make sure all NULL orderer entries are set to map the Unknown Provider).
So, an upgrade to 1.10 would fail for all implementations that have values of NULL in the orderer column of the order table.
The fix to this would be move to the changeset that adds the constraint ("201403011348") so that it is AFTER the changeset that migrates users to providers ("201402051638-
(Interesting, from the dates in the changeset ids above, it looks like the changeset that adds the NOT NULL constraint was originally after the migration changeset).
I think this can simply be fixed by moving the NOT NULL changeset later in the liquibase migration file without impacting any existing users.
[~djazayeri] Wyclif Luyima, thoughts?