Greetings All,
I'm running into an issue that I don't know whether it is by design or simply a bug and I hope somebody has an answer to this or point me to the documention/articles that describes this rather unexpected behavior.
I'm on vCD 5.1, I have 2 vApps with the same direct networks and when I try to move linux VM from one vApp to another using 'move to...' option, it does not retain the mac and nics of the VM once moved to the destination, instead it adds new nic numbers in the OS with new MAC addresses and sets IPs there.
I'm surprised to find out that the move is really not a move but rather a clonning of VM when looking at it from vCenter, as it creates new dest VM with the same name and upon completion it switches to it, discarding the previous one. That explains why the MAC change happens on all NIC..
I guess the thing that I don't understand is why in the world would it do that? Move should be a move and no MAC changes resulting in new NIC interfaces popping up in OS should take place. It wreaks havoc inside OS and also prevents MAC addresses hardcoding inside ifcfg-eth scripts which is a common practice in Linux on vSphere to avoid possible issues with nic reordering and loss of network connectivity on boot.
Can somebody tell me if this is by design, a bug (if so, is there a patch for it) or maybe I'm doing something wrong.and all this can be avoided.
Will defintely award points for good answers.
P