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.
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."
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