Operating System: Windows
Platform: PC

$ cat version.properties
org.opendaylight.controller.version = 0.1
org.opendaylight.controller.build.scm.version = 60b06b4e58f33d4fbd44da3d8cc982a7d26880d0
org.opendaylight.controller.build.user = root
org.opendaylight.controller.build.workspace = **********
org.opendaylight.controller.build.timestamp = 1404131807720
org.opendaylight.controller.build.machine = **********

Information in this link may be relevant:
http://superuser.com/questions/393812/supresss-the-no-such-file-or-directory-message-from-find

> Can opendaylight start properly with such error?

Yes.

This is the guilty line in run.sh (with comment):

1. clean available optional configurations (links)
   find configuration/initial -type l -exec rm {} \;

The problem is that while run.sh detects the directory where it is located
RUNSH_DIR=$(dirname $0)
it does not cd there, so the "find" command may start from unrelated directory, with no configuration/initial sub-branch; hence the error is printed.

But usually there are no optional configurations present, no links for the find command to remove, so ODL will start properly.

The fix is easy: prepend ${RUNSH_DIR}/ before appropriate relative paths (there are more of them, not just the first find).

Now, let me see if I can submit a patch.

I have received a warning "commit subject >65 characters" but here is this:
https://git.opendaylight.org/gerrit/#/c/8485/

Commit was merged.
My understanding of interactions between Jenkins jobs is not deep enough to deduce which build contains the full ODL with this fix, but you can simply replace run.sh with the new version, for example from here: https://git.opendaylight.org/gerrit/gitweb?p=integration.git;a=blob;f=distributions/base/src/assemble/resources/run.sh;h=ece3a515193b591427696bfafad428bfeeb555dc;hb=bea9f341e6503a72083db5c9c973001f587498a7

This bug is part of the project to Move all ADSAL associated component bugs to ADSAL.