RearPort position count should never be less than the number of mapped FrontPorts #5224
Labels
status: accepted
This issue has been accepted for implementation
type: bug
A confirmed report of unexpected behavior in the application
Environment
Steps to Reproduce
Expected Behavior
This should trigger a validation error, as there are four front ports mapped to it.
Observed Behavior
The rear port is saved without error, leaving the database and cable path in an inconsistent state. (Attempting to modify the orphaned front port yields a validation error as expected.)
The text was updated successfully, but these errors were encountered: