Description of problem:

To be confirmed, but the current behavior of mustnothave appears to be that it will compare fields if the objectDefinition is unnamed and will assume the object needs to be deleted when the objectDefinition has a name provided. With the objectSelector allowing enforcement of unnamed objects, this behavior should be consistent and should perform a robust comparison before deleting the object. As this is a change in behavior and though it is technically a bug, I believe it should NOT be backported and should be documented under the what's new (and anywhere else that may be relevant).

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:

3. ...

Actual results:

Expected results:

Additional info: