The migration 026 for rewriting contraints to be space-separated worked for staging. When run on production it had errors due to some of the bundles on production being older than the more restrictive bundle proofing requirements. Those bundles were in essence grandfathered in and never subject to the stricter rules. At least one bundle had an obsolete 'cpu' constraint and that caused the migration to fail since it was not checking for the thrown ValueError in this situation.
The migration now checks for ValueError and will remove the affected bundle from the target database and proceed.
The functions are now noted to throw ValueError.
Test was added for this situation and logging checked.