Project

General

Profile

Bug #17095

Interface facts not imported when Interface is in a different subnet

Added by Timo Goebel over 2 years ago. Updated 10 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Facts
Target version:
Difficulty:
Triaged:
Bugzilla link:
Team Backlog:
Fixed in Releases:
Found in Releases:

Description

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 (diff)
Added by Timo Goebel over 2 years ago

fixes #17095 - ensure subnet belongs to ip from facts

Revision 2bf31522 (diff)
Added by Timo Goebel over 2 years ago

fixes #17095 - ensure subnet belongs to ip from facts

(cherry picked from commit 911c6e9ec797de05c484064ff3ffc67ba53ae53a)

History

#1 Updated by The Foreman Bot over 2 years ago

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

#2 Updated by Timo Goebel over 2 years ago

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

#3 Updated by Dominic Cleal over 2 years ago

  • Legacy Backlogs Release (now unused) set to 189

Also available in: Atom PDF