Red Hat Bugzilla – Bug 1327030
[RFE] Add extension point to Subnets form for Discovery Proxy
Last modified: 2018-02-21 07:34:46 EST
Description of problem: If we have multiple organization, every time the discovered host goes to the same organization unit and it ignores the organization information defined in subnet. How reproducible: Create a multiple organization, each organization has its own subnet or network address. So based on its subnet it should go to the correct unit automatically but it is getting discovered into first organization only and ignores organization defined in Subnet. Steps to Reproduce: For ex. Create three organizations, and assign only third organization to subnet. provision host using foreman discovery image, provisioning host get discovered into first organization. Actual results: Discovered host goes to first organization and ignores organization specified in subnet. Expected results: Discovered host should go to the organization specified in subnet. Additional info: http://theforeman.org/plugins/foreman_discovery/5.0/#3.1.3OrganizationsandLocations Is the below upstream bug related to this bz? http://projects.theforeman.org/issues/14036
Hello, this will be fixed in Satellite 6.2. At least this will be implemented: http://theforeman.org/plugins/foreman_discovery/5.0/#3.1.3OrganizationsandLocations Note there is one limitation, if Subnet has multiple Org/Locs, it is choosen randomly. This will only work for Subnets with one Organization and/or Location. There is a ticket we are working on next sprint that should add an extra field to the Subnet page.
Per 6.3 planning, moving out non acked bugs to the backlog
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/14036 has been resolved.
QA notes: Verify Discovery Capsule can be set for a Subnet and it works.
Verified. Tested with Satellite 6.3 - Snap 13. See attached screenshot.
Created attachment 1320103 [details] Discovery capsule in Subnet
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/RHSA-2018:0336