Bug 1324978

Summary: [RFE] Provide IPv4 network subnet class option for provider discovery.
Product: Red Hat CloudForms Management Engine Reporter: amogh <amavinag>
Component: ProvidersAssignee: John Hardy <jhardy>
Status: CLOSED WONTFIX QA Contact: Dave Johnson <dajohnso>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.5.0CC: jfrey, jhardy, obarenbo
Target Milestone: GAKeywords: FutureFeature
Target Release: cfme-future   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: provider:discovery
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-28 15:03:35 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description amogh 2016-04-07 18:19:54 UTC 
Description of problem:
current provider discovery does not provide option to specify network subnet. This means, separate discovery needs to be initiated for the providers configured in different network subnet's. while specifying the network range the "To Address" is filled automatically, allowing only "/24" subnet to be discovered. Instead, It would be nice to allow the subnet to be specified and fill "To address" based on the subnet value.

Version-Release number of selected component (if applicable):
5.5.3.3.20160405132708_92d2d67, 5.6.0.0-beta1.20160322143549_f7ea680

How reproducible:
Always.

Steps to Reproduce:
1. Login to the appliance as "admin"
2. Navigate to "Infrastructure -> Providers -> Configuration -> Discover Infrastructure Providers"
3. Observe that "To address" is filled automatically after specifying "From Address", making it only /24 address range.

Actual results:
No option to specify network subnet for provider discovery.

Expected results:
provide subnet option for provider discovery in different networks at a time.
Comment 3 Chris Pelland 2017-08-28 15:03:35 UTC 
This bug has been open for more than a year and is assigned to an older release of CloudForms. 
If you would like to keep this Bugzilla open and if the issue is still present in the latest version of the product, please file a new Bugzilla which will be added and assigned to the latest release of CloudForms.