Bug #3481

Don't have to set a hostname for each interface, but it must be unique if it is set

Added by Aaron Stone over 4 years ago. Updated over 4 years ago.

Status:Closed
Priority:Normal
Assigned To:Aaron Stone
Category:Network
Target version:Sprint 16
Difficulty:trivial Bugzilla link:
Found in release: Pull request:
Story points-
Velocity based estimate-
Release1.3.1Release relationshipAuto

Description

A machine can have additional interfaces, including BMC interfaces, and these may not necessarily have DNS entries.

Currently you can create interfaces with no Name field, but only one in the whole system because of the uniqueness constraint in Rails (not in the DB mind you).

I propose to weaken the constraint such that any number of interfaces can have blank Name field, but if set the field must be unique.

Associated revisions

Revision 18897b8c
Added by Aaron Stone over 4 years ago

Fixes #3481 - Don't have to set a hostname for each interface, but it must be unique if it is set.

Revision 51acbf95
Added by Aaron Stone over 4 years ago

Fixes #3481 - Don't have to set a hostname for each interface, but it must be unique if it is set.

(cherry picked from commit 18897b8cbc9e83bbd70cb515c1704ce149d574f3)

Conflicts:
app/models/nic/managed.rb

History

#2 Updated by Dominic Cleal over 4 years ago

  • Category set to Network
  • Status changed from New to Ready For Testing
  • Target version set to Sprint 16
  • Release set to 1.4.0

#3 Updated by Aaron Stone over 4 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

#4 Updated by Aaron Stone over 4 years ago

Could this ship in 1.3.1?

#5 Updated by Dominic Cleal over 4 years ago

  • Release changed from 1.4.0 to 1.3.1

Sure, done!

Also available in: Atom PDF