Description of problem:
After rebooting a system with a configured FCoE target, I find that the tom_fc configuration is lost, although the backstore configuration is still present. I found that I could manually recover the configuration by becoming root, running targetcli and doing "restoreconfig /etc/target/saveconfig.json clear_existing". This makes me think that when the targetcli service is started, FCoE is not fully up so that the tom_fc configuration can't be restored at that time.

Version-Release number of selected component (if applicable):
2.0rc1.fb8

How reproducible:
Every reboot I have done so far.

Steps to Reproduce:
1. Configure an FCoE target
2. Reboot the system
3. Observe target configuration by running targetcli and doing ls

Actual results:
o- / ..................................................................... [...]
  o- backstores .......................................................... [...]
  | o- block ................................................ [0 Storage Object]
  | o- fileio ............................................... [1 Storage Object]
  | | o- lun1 ............................ [/luns/lun1.img (100.0M) deactivated]
  | o- pscsi ................................................ [0 Storage Object]
  | o- ramdisk .............................................. [0 Storage Object]
  o- ib_srpt ....................................................... [Not found]
  o- iscsi .......................................................... [0 Target]
  o- loopback ....................................................... [0 Target]
  o- qla2xxx ....................................................... [Not found]
  o- tcm_fc ........................................................ [Not found]

Expected results:
o- / ..................................................................... [...]
  o- backstores .......................................................... [...]
  | o- block ................................................ [0 Storage Object]
  | o- fileio ............................................... [1 Storage Object]
  | | o- lun1 .............................. [/luns/lun1.img (100.0M) activated]
  | o- pscsi ................................................ [0 Storage Object]
  | o- ramdisk .............................................. [0 Storage Object]
  o- ib_srpt ....................................................... [Not found]
  o- iscsi .......................................................... [0 Target]
  o- loopback ....................................................... [0 Target]
  o- qla2xxx ........................................................ [0 Target]
  o- tcm_fc ......................................................... [1 Target]
    o- 20:00:00:1b:21:87:a6:fa ....................................... [enabled]
      o- acls .......................................................... [1 ACL]
      | o- 20:00:00:1b:21:87:ac:7a .............................. [1 Mapped LUN]
      |   o- mapped_lun1 ............................... [lun1 fileio/lun1 (rw)]
      o- luns .......................................................... [1 LUN]
        o- lun1 ................................. [fileio/lun1 (/luns/lun1.img)]

Additional info:
I assume that either targetcli needs to wait for the configuration to be accepted, or tom_fc would have to be changed to accept a configuration for something not yet running. Things get messy if there are multiple ports with target configurations and the ports don't come up at the same time for any reason, but this failure is seen with only a single FCoE port.