VMware Cloud Director 10.4.2.2
Issue seems to be related with the VM Placement Policy itself since it can be resolved by creating a new 'test' VM Placement Policy
This issue can be resolved by creating a new 'test' VM Placement Policy
After this creation all edits work even for the original 'broken'