Bug #23224: Update subnets from facts breaks discovery - Discovery - Foreman

Custom queries

All issues closed in the last 3 weeks
Discovery by votes
Easy and Trivial Issues
Good first issues - Foreman core
Mine
My issues closed in the last 3 weeks
Untriaged and opened in the past two weeks

Actions

Copy link

Bug #23224

closed

Update subnets from facts breaks discovery

Added by Lukas Zapletal over 6 years ago. Updated over 6 years ago.

Status:

Closed

Priority:

High

Assignee:

Ido Kanner

Category:

Discovery plugin

Target version:

Discovery Plugin 13.0

Difficulty:

Triaged:

Bugzilla link:

Pull request:

https://github.com/theforeman/foreman_discovery/pull/436

Fixed in Releases:

Found in Releases:

Red Hat JIRA:

Description

Setting "Update subnets from facts" makes discovery impossible, error is "Unable to assign subnet, primary interface is missing IP address" with warning "Subnet is not defined for host's organization" in logs.

Related issues 1 (0 open — 1 closed)

Related to Foreman - Feature #23768: Fact parser flag keep_subnet to prevent subnet override during fact upload

Closed

Lukas Zapletal

06/01/2018

Actions

Issue # Delay: days Cancel

History
Notes
Property changes
Associated revisions

Actions

Copy link

Updated by Ido Kanner over 6 years ago

Assignee set to Ido Kanner

Actions

Copy link

Updated by Ido Kanner over 6 years ago

Just to make sure, it is about the following request:

PUT /discovered_hosts/:id/

Am I correct with my understanding?

Actions

Copy link

Updated by Lukas Zapletal over 6 years ago

No, that endpoint is actually unused we should consider removing it in V3. The one you are lookging for is: /api/v2/discovered_hosts/facts

https://github.com/theforeman/foreman_discovery/blob/develop/extra/discover-host

Try the script yourself, will discovery you a "fake" host, you can provision the fake host if you disable "discovery_reboot" option in administer settings.

Actions

Copy link

Updated by The Foreman Bot over 6 years ago

Pull request https://github.com/theforeman/foreman_discovery/pull/429 added

Actions

Copy link

Updated by Lukas Zapletal over 6 years ago

Pull request deleted (~~https://github.com/theforeman/foreman_discovery/pull/429~~)

Actions

Copy link

Updated by Lukas Zapletal over 6 years ago

Priority changed from Normal to High

Priority bump: https://community.theforeman.org/t/discovery-is-failed-erf-42-1064/9837/5

Actions

Copy link

Updated by Lukas Zapletal over 6 years ago

So it not like the setting breaks discovery, this is because your subnet is not in hosts taxonomy. Can you check please? For example if you discover a host that does belong to subnet with org A and there is one or more NICs detected in subnet which don't have org A, this error is thrown.

Actions

Copy link