Bug #691

Hardcoded ssh protocol in transfer manager (tm_ln.sh) ?

Added by Xavier Espinal about 10 years ago. Updated over 9 years ago.

Status:ClosedStart date:06/23/2011
Priority:NormalDue date:
Assignee:Ruben S. Montero% Done:


Category:Core & System
Target version:-
Resolution:fixed Pull request:
Affected Versions:OpenNebula 3.0


Dear ONE experts,

When configuring ONE configuration file for using the transfer manager to work with LVM (tm_lvm) was found that the ssh protocol is hardcoded in tm_ln.sh file, hence bypassing the LVM protocol:

- ONE configuration file:
[oneadmin@one01 root]$ cat /srv/cloud/one/etc/oned.conf|grep B2 -A2 lvm

TM_MAD = [
name = "tm_lvm",
executable = "one_tm",
arguments = "tm_lvm/tm_lvm.conf" ]

- Original tm_ln.sh file:
[oneadmin@one01 root]$ cat /srv/cloud/one/lib/tm_commands/lvm/tm_ln.orig.sh
exec $TM_COMMANDS_LOCATION/ssh/tm_clone.sh $SRC $DST

- Solved when replaced with modified tm_ln.sh file:
[oneadmin@one01 root]$ cat /srv/cloud/one/lib/tm_commands/lvm/tm_ln.sh
exec $TM_COMMANDS_LOCATION/lvm/tm_clone.sh $SRC $DST



#1 Updated by Ruben S. Montero almost 10 years ago

  • Target version deleted (Release 2.2)

#2 Updated by Tino Vázquez almost 10 years ago

  • Affected Versions OpenNebula 3.0 added

#3 Updated by Ruben S. Montero over 9 years ago

  • Status changed from New to Closed
  • Resolution set to fixed

This should be fixed in 3.4 in the iSCSI drivers. Closing this. If needed we'll re-open it.

Also available in: Atom PDF