Red Hat Bugzilla – Bug 703374
Long option --interface and --target do not work the same as short options
Last modified: 2012-02-21 01:09:19 EST
Description of problem: From the man page: -i, --interface <ethX> Show the information of the FCoE instances created at <ethX>. If <ethX> is not specified the command will show the information of all the FCoE instances created on the system. -t, --target <ethX> Show the information of all the discovered targets from the FCoE instances created at <ethX>. If <ethX> is not specified the command will show the information of all the discovered targets from all the FCoE instances created. The long options indeed need parameters and do not show info of all the FCoE instances created on the system # fcoeadm -t No FCoE interfaces created. # fcoeadm --target fcoeadm: option `--target' requires an argument fcoeadm v1.0.7 Copyright (c) 2009, Intel Corporation. Usage: fcoeadm [-c|--create] <ethX> [-d|--destroy] <ethX> [-r|--reset] <ethX> [-i|--interface] [<ethX>] [-t|--target] [<ethX>] [-l|--lun] [<target port_id> [<lun_id>]] [-s|--stats] <ethX> [-n <interval>] [-v|--version] [-h|--help] # fcoeadm -i No FCoE interfaces created. # fcoeadm --interface fcoeadm: option `--interface' requires an argument fcoeadm v1.0.7 Copyright (c) 2009, Intel Corporation. Usage: fcoeadm [-c|--create] <ethX> [-d|--destroy] <ethX> [-r|--reset] <ethX> [-i|--interface] [<ethX>] [-t|--target] [<ethX>] [-l|--lun] [<target port_id> [<lun_id>]] [-s|--stats] <ethX> [-n <interval>] [-v|--version] [-h|--help] Version-Release number of selected component (if applicable): fcoe-utils-1.0.7-4.el5 How reproducible: 100% Steps to Reproduce: 1. fcoeadm -t 2. fcoeadm --target 3. fcoeadm -i 4. fcoeadm --interface Actual results: Not the same behavior Expected results: Long/short options behave same Additional info: Not an regression, proposing for EL5.8
Created attachment 518500 [details] Make target and interface short and long options work the same
This should be fixed in fcoe-utils-1_0_7-5_el5
fcoe-utils-1.0.7-5.el5 fixed this issue. VERIFY.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2012-0230.html