transfer managers assume PATH setting
|Assignee:||Jaime Melis||% Done:|
|Category:||Drivers - Auth|
|Target version:||Release 2.0|
The TMs assume that 'mkfs' is on the path -- that's not the case with a default setup of (at least) Centos 5.4. It seems like TMs ought to try to operate under almost any kind of configuration.
I suggest one or both of:
. changing the invocations of 'mkfs' to '/sbin/mkfs', which should work for modern Linuxes (http://www.pathname.com/fhs/2.2/fhs-3.14.html)
. adding the ability to test for environmental dependencies during 'onehost create'.
There may well be other commands beyond 'mkfs' that can fail, btw. That's just one I happened to run into.
#5 Updated by Jaime Melis about 9 years ago
We can also add a feature described by Dan Yocum, regarding the swap partitions:
I propose that this should be solved by creating the swap partition with the label of "SWAP" which then can be used in the VM /etc/fstab to specify the swap partition. For example, this will be the line in the VM fstab:
LABEL=SWAP swap swap defaults 0 0
The scripts that need to be changed are ~oneadmin/lib/*/tm_mkswap.sh and simply add the "-L SWAP" option to the mkswap command.