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 1389020

Summary: Error generating IP when selecting Subnet in Interface
Product: Red Hat Satellite Reporter: Simon Reber <sreber>
Component: ProvisioningAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED ERRATA QA Contact: Ondřej Pražák <oprazak>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.2.3CC: bbuckingham, inecas, jcallaha, mhulan, oprazak, sreber
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-02-21 16:51:07 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:
Embargoed:
Attachments:
Description Flags
Screenshot from the error none

Description Simon Reber 2016-10-26 16:40:56 UTC
Created attachment 1214352 [details]
Screenshot from the error

Description of problem:

When creating a new host and defining the network interface, and error is reported once the subnet is selected.

"Error generating IP: Not Found" and IP address field is then marked red.

The Subnet it self has "IPAM" set to "None" and "Boot mode" is also set to "STATIC"

Version-Release number of selected component (if applicable):

 - satellite-6.2.3-1.0.el7sat.noarch

How reproducible:

 - always


Steps to Reproduce:
1. Configure subnet with IPAM set to non and boot mode to static
2. Create new host and specify network interface
3. Select Subnet in the interface mask

Actual results:

"Error generating IP: Not Found"

Expected results:

No error should be displayed

Additional info:

Comment 2 Marek Hulan 2017-03-06 14:57:02 UTC
I'm sorry I could not get to it sooner. The error message you see can be ignored. It's a UI issue. The backend responses with 404 since no IPAM could find free IP and the UI does not properly distinguish. It has been already fixed in upstream with a bigger refactoring - http://projects.theforeman.org/issues/14666. For the reference, here's the link to the relevant part of the patch https://github.com/theforeman/foreman/pull/3587/files#diff-150923539d83f563f47fbf488e6ee017R53

Comment 6 Ondřej Pražák 2017-08-16 07:21:37 UTC
Verified.

6.3.0 snap 11

Comment 7 Satellite Program 2018-02-21 16:51:07 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/RHSA-2018:0336