Bug 2097861
| Summary: | iPXE causes an LACP flood | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | François Rigault <frigo> | ||||
| Component: | ipxe | Assignee: | Michal Schmidt <mschmidt> | ||||
| ipxe sub component: | ipxe-bootimgs | QA Contact: | Oliver Gutiérrez <ogutierr> | ||||
| Status: | CLOSED MIGRATED | Docs Contact: | |||||
| Severity: | unspecified | ||||||
| Priority: | unspecified | CC: | efuller, ernunes, jarod, lersek, mleitner, ogutierr, osteffen, rvr, sboyron | ||||
| Version: | 8.4 | Keywords: | MigratedToJIRA, OtherQA, Triaged | ||||
| Target Milestone: | rc | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | No Doc Update | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2023-09-21 14:44:44 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
François Rigault
2022-06-16 18:16:24 UTC
Hi François. As the bug has been fixed in ipxe-20181214-10.git133f4c47.el8, could you check if the problem is fixed using this version? If it is, please report us any information that could be useful to mark this bug as verified. Thanks! Thanks Oliver, unfortunately I don't have a way to retrieve this artifact. Jarod: Could you give François a public link to download the fixed version package and do the testing for the package? Packages temporarily available here: https://people.redhat.com/~jwilson/testing/ipxe/ Created attachment 1910398 [details]
Unknown_krgfs_crash
used the ipxe-snponly-x86_64.efi to deploy 2 servers:
- 1 unrelated machine: deploys fine
- 1 machine with the ConnectX-3 pro -> crash, log attached.
Hi @frigo . The crash you specify in this test is something that happened also with previous version or only with this new one? hi! no I have never seen this crash before, it is specific to this new version. Does the package you built yourself (mentioned in the original report description) work on that host where this build failed, or does that fail similarly? the package I built myself works on that host flawlessly yes. I understand this requires a specific type of hardware to reproduce. I can live with my hacks if fixing it is not trivial. (In reply to François Rigault from comment #33) > the package I built myself works on that host flawlessly yes. > > I understand this requires a specific type of hardware to reproduce. I can > live with my hacks if fixing it is not trivial. It sounds like it would require tracking down the specific changes from upstream ipxe that make this work with cx-3 or a full rebase (which we generally frown upon doing at any point in a major release, let alone this late), and without a readily available reproducer and some time and effort (I'm lacking in time), I think we may well have to revert that one patch and revisit this for the next minor release. Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug. This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there. Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information. To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like: "Bugzilla Bug" = 1234567 In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information. |