Bug 1624034 - Do not prevent host discovery for existing MAC/IP addresses
Summary: Do not prevent host discovery for existing MAC/IP addresses
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Discovery Plugin
Version: 6.3.1
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: Lukas Zapletal
QA Contact: Roman Plevka
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-30 17:17 UTC by Mike McCune
Modified: 2021-12-10 17:14 UTC (History)
10 users (show)

Fixed In Version: tfm-rubygem-foreman_discovery-9.1.5.4-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1565093
Environment:
Last Closed: 2018-10-11 15:18:06 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 23174 0 None None None 2018-08-30 17:17:53 UTC
Red Hat Product Errata RHBA-2018:2915 0 None None None 2018-10-11 15:18:30 UTC

Comment 4 Patrick Creech 2018-09-06 20:53:34 UTC 
Lukas,

The associated merge request failed unit testing.  Mind taking a look?
Comment 5 Lukas Zapletal 2018-09-07 10:03:10 UTC 
Patrick, you need to fix this with another patch: https://github.com/theforeman/foreman/pull/5142 - not related.
Comment 7 Roman Plevka 2018-09-17 21:30:51 UTC 
VERIFIED
on sat6.3.4-1

- the default old behaviour is back: i was able to re-discover the host despite the fact that i had it in the managed hosts.
switching the mentioned setting to TRUE (to error out) indeed prevents the same host from being discovered again (the /facts POST requests receives 422 with a proper message)
Comment 9 errata-xmlrpc 2018-10-11 15:18:06 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:2915
Note You need to log in before you can comment on or make changes to this bug.