Thank you very much for your response.
However, we do not perform an in-service upgrade. Why would the upgrade fail, then?
I read chapter 13 of the ConfD User Guide, but the only reference to my issue is this:
If the upgrade includes new validation points, or the validation logic for existing validation points
has changed, the new validators must connect to ConfD and register for their validation points before
maapi_commit_upgrade() is called.
My case is the second - validation logic has changed. However, I do not have a validation point, unless you consider a 'must' statement a validation point.
It is also not clear to me how performing the code assists me here: how do I permit the new, non-restrictive schema definition in the sequence described?
In short - I still do not understand why a removal of a constraint show fail the upgrade - the constraint is no longer in the schema, so how come confd thinks it's still there?
Your assistance is much appreciated.