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 1635339

Summary: Foreman-Discovery-Image 3.4.4.1-1 does not re-initialize broadcom NICs after kexec
Product: Red Hat Satellite Reporter: Skip Wyatt <awyatt>
Component: Discovery ImageAssignee: Lukas Zapletal <lzap>
Status: CLOSED WONTFIX QA Contact: Jitendra Yejare <jyejare>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.3.3CC: lzap, rabajaj
Target Milestone: UnspecifiedKeywords: Triaged
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: 2020-05-01 14:14:52 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:
Bug Depends On:    
Bug Blocks: 1635749    
Attachments:
Description Flags
Error message from dracut shell none

Description Skip Wyatt 2018-10-02 16:48:22 UTC
Created attachment 1489520 [details]
Error message from dracut shell

Description of problem:
Foreman-Discovery-Image 3.4.4.1-1 does not re-initialize boradcom NICS after kexec

Version-Release number of selected component (if applicable):
Foreman-Discovery-Image 3.4.4.1-1
Dell R640


How reproducible:
Consistently

Steps to Reproduce:
1. Boot system with FDI
2. System get IP address the kexecs
3. NIC link drops, NIC throws bnxt_en 0000:19:00:0: VPD access failed

Actual results:
System drops to dracut shell

Expected results:
system continues to install via anaconda

Additional info:
When using FDI 3.5 from upstream, this works as intended.

Comment 1 jcallaha 2018-10-02 17:04:41 UTC
Satellite 6.4 will be shipping with the versions or higher.

foreman-discovery-image-3.5.3-1.iso
foreman-discovery-image-3.5.3-1.iso-img
foreman-discovery-image-3.5.3-1.iso-vmlinuz

Comment 3 Lukas Zapletal 2018-10-03 15:19:03 UTC
This is likely old RHEL, the new FDI is build on top of RHEL 7.5. Please use this build which is the final FDI build for Satellite 6.4:

http://people.redhat.com/~lzapleta/scratch/fdi/foreman-discovery-image-3.5.3-1.el7sat.noarch.rpm

We plan to update FDI in Satellite 6.3, associated the tracking BZ. Thanks for the report!

Comment 4 Bryan Kearney 2020-05-01 14:14:52 UTC
Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact Red Hat Technical Support. Thank you.