Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1292750

Summary: "Suggest new" link for IP address on interface model window doesn't work
Product: Red Hat Satellite Reporter: Sachin Ghai <sghai>
Component: ProvisioningAssignee: Marek Hulan <mhulan>
Status: CLOSED ERRATA QA Contact: Sachin Ghai <sghai>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.0.4CC: bbuckingham, bkearney
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
URL: http://projects.theforeman.org/issues/12859
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-27 09:00:46 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Sachin Ghai 2015-12-18 09:38:10 UTC 
I defined two interfaces 1) Primary and 2) Provisioning with different subnets. However, for none of them the "suggest New" IP link works. I didn't get any error in firebug nor in any logs. Nothing happens on clicking the link.

reproducible with version:
foreman-release-1.11.0-0.develop.201512091815git0e9b35e.el7.noarch
Comment 1 Sachin Ghai 2015-12-18 09:38:15 UTC 
Created from redmine issue http://projects.theforeman.org/issues/12859
Comment 2 Sachin Ghai 2015-12-18 09:38:27 UTC 
Upstream bug assigned to mhulan
Comment 4 Bryan Kearney 2016-01-12 11:01:08 UTC 
Moving to POST since upstream bug http://projects.theforeman.org/issues/12859 has been closed
-------------
Marek Hulán
Introduced by (accidental) removing of emptying the IP field, for more details see https://github.com/theforeman/foreman/pull/2650/files#diff-63d9ef3bbe6ac020529a197ac7aa171bL523ac020529a197ac7aa171bL523

Not a blocker but should be fixed in 1.10.1 I think
-------------
Marek Hulán
Applied in changeset commit:d03db507341885416e99f518c66f8931e5d42dab.
Comment 7 Sachin Ghai 2016-04-11 12:00:35 UTC 
Verified with sat6beta snap6.2


The reported issue has been fixed. I can see newly generated IP on clicking 'suggest new' link from webUI:


here are the production.log:
===========================
2016-04-09 07:08:13 [app] [I] Started POST "/subnets/freeip" for 10.67.7.83 at 2016-04-09 07:08:13 -0400
2016-04-09 07:08:13 [app] [I] Processing by SubnetsController#freeip as JSON
2016-04-09 07:08:13 [app] [I]   Parameters: {"subnet_id"=>"1", "host_mac"=>"", "organization_id"=>"1", "location_id"=>"2", "taken_ips"=>["192.168.100.32", ""]}
2016-04-09 07:08:15 [app] [I] Completed 200 OK in 2085ms (Views: 0.2ms | ActiveRecord: 4.9ms)

And If I associate a static subnet where dhcp proxy is not set, webUI stick with old ip.
Comment 9 errata-xmlrpc 2016-07-27 09:00:46 UTC 
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-2016:1500