Bug 1624034 – Do not prevent host discovery for existing MAC/IP addresses

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1624034 - Do not prevent host discovery for existing MAC/IP addresses

Summary:	Do not prevent host discovery for existing MAC/IP addresses

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Satellite 6
Classification:	Red Hat
Component:	Discovery Plugin (Show other bugs)
Sub Component:
Version:	6.3.1
Hardware:	Unspecified Unspecified

Priority	unspecified Severity high (vote)
Target Milestone:	6.3.4
Target Release:	Unused
Assigned To:	Lukas Zapletal
QA Contact:	Roman Plevka
Docs Contact:

URL:	http://projects.theforeman.org/issues...
Whiteboard:
Keywords:	Regression, Triaged

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2018-08-30 13:17 EDT by Mike McCune
Modified:	2018-10-30 09:02 EDT (History)
CC List:	10 users (show)

See Also:
Fixed In Version:	tfm-rubygem-foreman_discovery-9.1.5.4-1
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:	1565093
Environment:
Last Closed:	2018-10-11 11:18:06 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Foreman Issue Tracker	23174	None	None	None	2018-08-30 13:17 EDT
Red Hat Product Errata	RHBA-2018:2915	None	None	None	2018-10-11 11:18 EDT

Groups: None (edit)

Comment 4 Patrick Creech 2018-09-06 16:53:34 EDT

Lukas,

The associated merge request failed unit testing.  Mind taking a look?

Comment 5 Lukas Zapletal 2018-09-07 06:03:10 EDT

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 17:30:51 EDT

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 11:18:06 EDT

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.