Bug #17095

Interface facts not imported when Interface is in a different subnet

Added by Timo Goebel 10 months ago. Updated 9 months ago.

Assigned To:Timo Goebel
Target version:-
Difficulty: Bugzilla link:
Found in release:1.12.0 Pull request:https://github.com/theforeman/foreman/pull/3971
Story points-
Velocity based estimate-
Release1.14.0Release relationshipAuto


When interfaces are set via Facts, this may fail when

a) the ip address does not match the subnet
Error "IP does not match selected subnet"

b) a subnet is set, but the interface has no ip address
Error: "Ip6 can't be blank"

When setting the ip based on facts, we should update the subnet field accordingly.

Associated revisions

Revision 911c6e9e
Added by Timo Goebel 9 months ago

fixes #17095 - ensure subnet belongs to ip from facts


#1 Updated by The Foreman Bot 10 months ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/3971 added

#2 Updated by Timo Goebel 9 months ago

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

#3 Updated by Dominic Cleal 9 months ago

  • Release set to 1.14.0

Also available in: Atom PDF