Project

General

Profile

Actions
Copy link

Bug #10004

closed

Discovery of a host with already known IP address fails with: address family must be specified

Added by Lukas Zapletal about 9 years ago. Updated almost 8 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Lukas Zapletal
Category:
Discovery plugin
Target version:
Discovery Plugin 6.0
Difficulty:
Triaged:
Bugzilla link:
Pull request:
https://github.com/theforeman/foreman_discovery/pull/218
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

If a host is being discovered with an IP that is already assigned to an existing Host or Discovered Host, we error out with "address family must be specified".

We should give a proper error instead.

Let's test also against MAC addresess.

Related issues 1 (0 open — 1 closed)

Related to Discovery - Bug #9857: Internal server error when registering discovered host in Foreman 1.8Closed03/21/2015Actions
Actions
Copy link
 #1

Updated by Lukas Zapletal about 9 years ago

  • Related to Bug #9857: Internal server error when registering discovered host in Foreman 1.8 added
Actions
Copy link
 #2

Updated by Lukas Zapletal over 8 years ago

For the record, on Discovery 4.0 the error message is a bit different (still confusing):

{"message":"ERF42-1064 [Foreman::Exception]: Unable to assign subnet, primary interface is missing IP address"
Actions
Copy link
 #3

Updated by The Foreman Bot over 8 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman_discovery/pull/218 added
  • Pull request deleted ()
Actions
Copy link
 #4

Updated by Lukas Zapletal almost 8 years ago

  • Assignee set to Lukas Zapletal
  • Status changed from Ready For Testing to Closed
  • Target version changed from Discovery Plugin 2.0.3 to Discovery Plugin 6.0

Not an issue anymore with Discovery 6.0 and 1.12 core version.

Actions
Copy link

Also available in: Atom PDF