When doing SW FCoE based testing my WWPN is tab-completed with an extra ':' at the end of the string that must be manually removed before the command will succeed. [root@vmF18t ~]# targetcli targetcli shell version 2.0rc1.fb19 Copyright 2011 by RisingTide Systems LLC and others. For help on commands, type 'help'. /> ls / o- / ............................................................................................ [...] o- backstores ................................................................................. [...] | o- block ....................................................................... [0 Storage Object] | o- fileio ...................................................................... [1 Storage Object] | | o- lun1 ........................................ [/luns/lun1.img (4.0GiB) write-back deactivated] | o- pscsi ....................................................................... [0 Storage Object] | o- ramdisk ..................................................................... [0 Storage Object] o- iscsi ................................................................................ [0 Targets] o- loopback ............................................................................. [0 Targets] o- qla2xxxx ............................................................................. [0 Targets] o- tcm_fc ............................................................................... [0 Targets] /> cd /tcm_fc /tcm_fc> create wwn=20:00:90:e2:ba:37:91:fb: (<----- HERE see the last colon) Could not create Target in configFS. /tcm_fc> create wwn=20:00:90:e2:ba:37:91:fb (<----- manually removed) Created target 20:00:90:e2:ba:37:91:fb.
python-configshell-1.1.fb7-1.fc18,python-rtslib-2.1.fb30-1.fc18,targetcli-2.0rc1.fb18-2.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/python-configshell-1.1.fb7-1.fc18,python-rtslib-2.1.fb30-1.fc18,targetcli-2.0rc1.fb18-2.fc18
Package python-configshell-1.1.fb7-1.fc18, python-rtslib-2.1.fb30-1.fc18, targetcli-2.0rc1.fb18-2.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing python-configshell-1.1.fb7-1.fc18 python-rtslib-2.1.fb30-1.fc18 targetcli-2.0rc1.fb18-2.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-3177/python-configshell-1.1.fb7-1.fc18,python-rtslib-2.1.fb30-1.fc18,targetcli-2.0rc1.fb18-2.fc18 then log in and leave karma (feedback).
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.