|
[
Permalink
| « Hide
]
Diego Parrilla added a comment - 28/Nov/09 05:04 PM
Upgraded to blocker: ALL the IPs of ALL the virtual machines are affected and the selected IPs are all overwritten.
Reproduced in the last code in SVN.
Seams that each time we save a node, server recalculates de privateIP, Another easy test to reproduce 1º Create a virtual App 2º Add an image 3º Save --> System assign 10.0.1.10 4º Change the image name 5º Save --> System assign 10.0.1.100 6º Change another time the image name 7º Save --> System returns to the 10.0.1.10 (Because it's another time the first free in the list) I think that on saveVirtualAppliance method on virtualApplianceCommand, we generate always a new IP for the modified node. Should be only for the new nodes! Thanks I KNOW what it's happend :P
The problem is that ALWAYS! When the node is not deployed, abiCloud recalculate the private IP if (nodevi.getVirtualMachine().getState().getId() == State.NOT_DEPLOYED) { IPAddress ipaddress = netcommand.requestNewIPAddress(virtualappHBPojo.getVirtualDataCenterHB() .getNetworkType()); netcommand.assignPrivateMACResource(userSession, virtualappHBPojo, (NodeVirtualImageHB) currentNode.toPojoHB(), ipaddress); } This is on updateNetworkResources method of virtualApplianceCommand. The solution is that state = NOT_DEPLOYED and node has not previous IP assigned. Many thanks for the solution, Xavi!
Now it controlls if IP address is already reserved for the node to assign the default value.
|
||||||||||||||||||||||||||||||||||||||