Bug 1905727

Summary:	Foreman Discovery Image 3.6.7 Doesn't Allow Static IP Assignment
Product:	Red Hat Satellite	Reporter:	patalber
Component:	Discovery Image	Assignee:	Lukas Zapletal <lzap>
Status:	CLOSED ERRATA	QA Contact:	Roman Plevka <rplevka>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.8.0	CC:	lzap, rabajaj, saydas, zhunting
Target Milestone:	6.9.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:	foreman-discovery-image-3.7.4-2	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1908859 (view as bug list)		Environment:
Last Closed:	2021-04-21 13:24:23 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:

Description patalber 2020-12-08 22:33:59 UTC

Description of problem:
Post-6.8-upgrade (FDI 3.6.7) customer is unable to assign static IP using Foreman Discovery TUI. They boot from the ISO (PXE-less), select manual assignment, provide the IP. It fails to bring the network up. In the logs. they see this:

~~~
waiting for ip address to generate ssl
~~~

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

How reproducible:
100%

Steps to Reproduce:
1. Upgrade to 6.8
2. download the rpm package from https://access.redhat.com/downloads/content/foreman-discovery-image/3.6.7-1.el7sat/noarch/fd431d51/package, extract it and use the ISO file.
3. Try to boot from it and use the manual IP assignment.

Actual results:
The network does not move forward with provisioning a host to the static IP presented

Expected results:
Provisioning via FDI to proceed as it always has

Additional info:

The customer presented the following, which resolved their issue:

"I was able to resolve the issue by downloading Foreman Discovery image 3.5.7 directly from the Foreman website http://downloads.theforeman.org/discovery/. It worked right away, so I will keep using it for now. I don't remember what the old FDI version was in Satellite before 6.8. Interestingly, I don't see 3.6.7, even the nightly build is 3.6.6.

Satellite logs won't help here. If you want to reproduce the issue, please download the rpm package from https://access.redhat.com/downloads/content/foreman-discovery-image/3.6.7-1.el7sat/noarch/fd431d51/package, extract it and use the ISO file. Try to boot from it and use the manual IP assignment. You should not be able to get past that step, so this is before any of Satellite configuration comes into play."

Comment 2 Lukas Zapletal 2021-02-09 11:19:54 UTC

Fixed in 3.7.3. Currently we ship 3.7.2 in 6.9 repos. I will request new FDI build.

Comment 3 Roman Plevka 2021-02-23 17:16:32 UTC

VERIFIED
on sat6.9.0-14.0

successfully set the NW config manually on fdi v3.7.4 and managed to proceed with the discovery.

Comment 6 errata-xmlrpc 2021-04-21 13:24:23 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 (Moderate: Satellite 6.9 Release), 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-2021:1313