Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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.
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.
The official life cycle policy can be reviewed here:
http://redhat.com/rhel/lifecycle
This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:
https://access.redhat.com/
Description of problem: [fcoe-utils]fcoeadm: Command failed, fcoeadm failed to destroy fcoe interface Version-Release number of selected component (if applicable): 2.6.32-592.el6.i686.debug How reproducible: often Steps to Reproduce: 1. setup fcoe instance 2. destroy fcoe instance Actual results: [root@storageqe-13 fcoeadm_destroy]# fcoeadm -i Description: 82599ES 10-Gigabit SFI/SFP+ Network Connection Revision: 01 Manufacturer: Intel Corporation Serial Number: 001B21591234 Driver: ixgbe 4.0.1-k Number of Ports: 1 Symbolic Name: fcoe v0.1 over eth0.802-fcoe OS Device Name: host19 Node Name: 0x1000001B21591236 Port Name: 0x2000001B21591236 FabricName: 0x2322000573B27F01 Speed: 10 Gbit Supported Speed: 1 Gbit, 10 Gbit MaxFrameSize: 1452 FC-ID (Port ID): 0x750005 State: Online Symbolic Name: fcoe v0.1 over eth1.802-fcoe OS Device Name: host20 Node Name: 0x1000001B21591237 Port Name: 0x2000001B21591237 FabricName: 0x2322000573B27F01 Speed: 10 Gbit Supported Speed: 1 Gbit, 10 Gbit MaxFrameSize: 1452 FC-ID (Port ID): 0x750004 State: Online [root@storageqe-13 fcoeadm_destroy]# fcoeadm -d eth0.802-fcoe fcoeadm: Command failed Try 'fcoeadm --help' for more information. Expected results: eth0.802-fcoe could be destroyed with option of '-d' Additional info: