Bug 1618970 - abrt happens whenever try to create a fcoe instance on NICs( ixgbe and bnx2fc)
Summary: abrt happens whenever try to create a fcoe instance on NICs( ixgbe and bnx2fc)
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: fcoe-utils
Version: 29
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Chris Leech
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-19 03:35 UTC by lnie
Modified: 2018-08-19 09:59 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-08-19 09:59:22 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
journal (112.80 KB, text/plain)
2018-08-19 03:35 UTC, lnie
no flags Details
abrt dump (25.93 KB, application/x-gzip)
2018-08-19 03:37 UTC, lnie
no flags Details

Description lnie 2018-08-19 03:35:03 UTC
Created attachment 1476845 [details]
journal

Description of problem:
 
 Following is the reproducer commands on the Intel server,abrt always happens
 after run "systemctl fcoe restart" command:

  systemctl start lldpad 
  ifconfig ens2f0 down
  ifconfig ens2f0 up
  dcbtool sc ens2f0 dcb on
  dcbtool sc ens2f0 pfc e:1 a:1 w:1
  dcbtool sc ens2f0 app:fcoe e:1 a:1 w:1
  cp -f /etc/fcoe/cfg-ethx /etc/fcoe/cfg-ens2f0
 sed -i -e 's/\(MODE=.*\)$/MODE=\"%s\"/' /etc/fcoe/cfg-%s" % (fabric, ens2f0)
 sed -i -e 's/ONBOOT.*/ONBOOT=\"yes\"/' /etc/sysconfig/network-scripts/ifcfg-%s" % ens2f0
 systemctl restart lldpad 
 systemctl restart fcoe 


Version-Release number of selected component (if applicable):
kernel-4.18.0-0.rc8.git2.1.fc29.x86_64
fcoe-utils-1.0.32-6.fc29.x86_64

How reproducible:
always 

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 lnie 2018-08-19 03:37:03 UTC
Created attachment 1476846 [details]
abrt dump

Comment 2 lnie 2018-08-19 09:59:22 UTC
Didn't see this crash any more after upgrade to kernel-4.18.1-300.fc29.x86_64,closing


Note You need to log in before you can comment on or make changes to this bug.