Update subnets from facts breaks discovery
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.
#3 Updated by Lukas Zapletal 10 months 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
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.
#6 Updated by Lukas Zapletal 9 months ago
- Priority changed from Normal to High
#7 Updated by Lukas Zapletal 9 months 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.
#10 Updated by Lukas Zapletal 8 months ago
- % Done changed from 0 to 100
- Status changed from Ready For Testing to Closed
Applied in changeset foreman_discovery|ae5b4b9430bded576a19fda6d14ab18d868d414e.