Bug 1129574
| Summary: | fipvlan: fip_recv: error 88 Socket operation on non-socket | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Xiaowei Li <xiaoli> | ||||
| Component: | fcoe-utils | Assignee: | Chris Leech <cleech> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | guazhang <guazhang> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 7.1 | CC: | cleech, coughlan, guazhang | ||||
| Target Milestone: | rc | Keywords: | Triaged | ||||
| Target Release: | 7.1 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2020-12-15 07:31:04 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
Xiaowei Li
2014-08-13 08:51:32 UTC
in RHEL 7.0 the similar issue was fixed in bz1049018. so mark it as regression issue. fcoe-utils-1.0.29-7.el7 merged an upstream patch that added additional checks around the FIP socket creation. If for some reason the socket creation fails, it should not continue with these ENOTSOCK errors. Please retest this with fcoe-utils-1.0.29-7.el7 This is not a regression from 7.0, but rather an addition upstream patch for a more complete fix than was merged for bz1049018 On RHEL-7.1, I could't test with the steps in #c0 due to NEW bug 1183917, it blocks me to add FCoE LUNs with anaconda. In additon, the #c0 doesn't describe clear when do I check the result? After step3? In that time, the system has not installed the package of fcoe-utils yet, do you know the additional descriptions about where to check after step3? Thanks, Nancy (In reply to xhe from comment #8) > On RHEL-7.1, I could't test with the steps in #c0 due to NEW bug 1183917, it > blocks me to add FCoE LUNs with anaconda. > > In additon, the #c0 doesn't describe clear when do I check the result? After > step3? In that time, the system has not installed the package of fcoe-utils > yet, do you know the additional descriptions about where to check after > step3? I believe this is all happening in the installer when setting up the destination storage, before package installation begins. FCoE discovery fails and these error messages would be in the anaconda program.log Created attachment 988463 [details]
The installation log of program.log
It doesn't occur on fcoe-utils-1.0.29-7.el7, here is my steps: 1. Select the machine with FCoE bnx2fc, provision system: Distro Tree : RHEL-7.1-20141024.1 Server X86_64 KickStart MetaData: !ignoredisk manual Kernel Option : vnc 2. Use vncviewer to start the installer with anaconda GUI by manual 3. Click INSTALLATION DESTINATION->Add a disk->Add FCoE SAN... Select NIC from checkbox Select 'Use DCB' and 'Use auto VLAN' Click 'Add FCoE Disk(s)' button. 4. Press ^b 2 to use console to check /tmp/program.log [anaconda root@hp-dl388g8-16 ~]# uname -a Linux hp-dl388g8-16.rhts.eng.nay.redhat.com 3.10.0-193.el7.x86_64 [anaconda root@hp-dl388g8-16 ~]# fipvlan -v fipvlan version 1.0.29 [anaconda root@hp-dl388g8-16 ~]# cat /tmp/program.log |grep fipvlan 18:20:50,996 INFO program: Running... fipvlan -c -s -f -fcoe ens3f0 I attached program.log in #c11 Thanks, Nancy After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened. |