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.

Description of problem:

When executing this command:
===
/tcm_fc/20:00:00:1b:21:59:12:37/acls/ create 20:00:00:10:18:88:E9:49
===

targetcli automatically change "20:00:00:10:18:88:E9:49" to "20:00:00:10:18:88:e9:49"

But when execute this command:
===
/tcm_fc/20:00:00:1b:21:59:12:37/acls/20:00:00:10:18:88:E9:49 create 0 0
===
It fail as:
===
No such path /tcm_fc/20:00:00:1b:21:59:12:37/acls/20:00:00:10:18:88:E9:4B
===

So internally, please allow target to support these type of WWPN:
====
20:00:00:10:18:88:E9:49
20-00-00-10-18-88-E9-49
200000101888E949
200000101888e949
====

Version-Release number of selected component (if applicable):
fcoe-target-utils-2.0rc1.fb16-2.el6.noarch

How reproducible:
100%

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Can't do this. There's only one configuration path for that ACL, it is the colon-separated version with lowercase hex letters.

Closing, but I've opened bug 904284, which is feasible.