Issue Details (XML | Word | Printable)

Key: ABICLOUD-357
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Blocker Blocker
Assignee: Jaume Devesa
Reporter: Diego Parrilla
Votes: 0
Watchers: 0
Operations

Email this issue
Send issue summary in email
If you were logged in you would be able to see more operations.
Abiquo

Lost IPs when assigning DHCP leases

Created: 01/Dec/09 02:20 PM   Updated: 03/Dec/09 05:07 PM   Resolved: 03/Dec/09 11:50 AM
Component/s: None
Affects Version/s: abicloud-1.0.0-RC1
Fix Version/s: abicloud-1.0.0-RC2

Time Tracking:
Not Specified


 Description  « Hide
DHCP leases are lost. The configuration of the system is:

Server1-->IP/10.0.1.2 and IP/192.168.10.24
Server2-->IP/10.0.1.4 and IP/192.168.10.25

But the log indicates that it's assigning different IPs: 10.0.1.4, 10.0.1.10 and 192.168.10.24. It seems it's retrieving information from a former configuration.

13:08:42.491 [pool-3-thread-8] DEBUG c.a.v.n.i.DHCPConfiguratorOmapilib - Connec
ting to ISC DHCP Server in 127.0.0.1:7911
13:08:42.491 [pool-3-thread-8] INFO c.a.abicloud.omapilib.Connection - Connecti
ng to... "127.0.0.1:7911".
13:08:42.492 [pool-3-thread-8] INFO c.a.abicloud.omapilib.Connection - Connecti
on established!
13:08:42.492 [pool-3-thread-8] DEBUG c.a.v.n.i.DHCPConfiguratorOmapilib - Connec
ted to ISC DHCP Server in 127.0.0.1:7911
13:08:42.493 [pool-3-thread-8] DEBUG c.a.v.n.i.DHCPConfiguratorOmapilib - Adding
 host rule to ISC DHCP Server to 10.0.1.4_host:10.0.1.4:00:50:56:00:d1:dd
13:08:42.493 [pool-3-thread-8] INFO com.abiquo.abicloud.omapilib.Message - Crea
ting emtpy Message Object
13:08:42.493 [pool-3-thread-8] INFO com.abiquo.abicloud.omapilib.Message - com.
abiquo.abicloud.omapilib.model.Host extended with attribute
 name
  31 30 2e 30 2e 31 2e 34 5f 68 6f 73 74

13:08:42.493 [pool-3-thread-8] INFO com.abiquo.abicloud.omapilib.Message - com.
abiquo.abicloud.omapilib.model.Host extended with attribute
 ip-address
  0a 00 01 04

13:08:42.494 [pool-3-thread-8] INFO com.abiquo.abicloud.omapilib.Message - com.
abiquo.abicloud.omapilib.model.Host extended with attribute
 hardware-address
  00 50 56 00 d1 dd

13:08:42.494 [pool-3-thread-8] INFO com.abiquo.abicloud.omapilib.Message - com.
abiquo.abicloud.omapilib.model.Host extended with attribute
 hardware-type
  00 00 00 01

13:08:42.494 [pool-3-thread-8] INFO com.abiquo.abicloud.omapilib.Message - com.
abiquo.abicloud.omapilib.model.Host extended with attribute
 statements
  6f 70 74 69 6f 6e 20 72 6f 75 74 65 72 73 20 31
 30 2e 30 2e 31 2e 31 3b 20 6f 70 74 69 6f 6e 20
73 75 62 6e 65 74 2d 6d 61 73 6b 20 32 35 35 2e
 32 35 35 2e 32 35 35 2e 30 3b

13:08:42.494 [pool-3-thread-8] INFO com.abiquo.abicloud.omapilib.Message - com.
abiquo.abicloud.omapilib.model.Host extended with Message
 create
  00 00 00 01

13:08:42.495 [pool-3-thread-8] INFO com.abiquo.abicloud.omapilib.Message - com.
abiquo.abicloud.omapilib.model.Host extended with Message
 exclusive
  00 00 00 01

13:08:42.495 [pool-3-thread-8] INFO com.abiquo.abicloud.omapilib.Message - Tryi
ng to CREATE com.abiquo.abicloud.omapilib.model.Host
13:08:42.757 [pool-3-thread-8] INFO com.abiquo.abicloud.omapilib.Message - - S
uccessfully CREATEed ...
13:08:42.758 [pool-3-thread-8] INFO com.abiquo.abicloud.omapilib.Message - Effo
rt to assign incoming data to Message Object
13:08:42.758 [pool-3-thread-8] INFO com.abiquo.abicloud.omapilib.Message - com.
abiquo.abicloud.omapilib.model.Host extended with attribute
 ip-address
  0a 00 01 04

13:08:42.758 [pool-3-thread-8] INFO com.abiquo.abicloud.omapilib.Message - com.
abiquo.abicloud.omapilib.model.Host extended with attribute
 name
  31 30 2e 30 2e 31 2e 34 5f 68 6f 73 74

13:08:42.759 [pool-3-thread-8] INFO com.abiquo.abicloud.omapilib.Message - com.
abiquo.abicloud.omapilib.model.Host extended with attribute
 hardware-address
  00 50 56 00 d1 dd

13:08:42.759 [pool-3-thread-8] INFO com.abiquo.abicloud.omapilib.Message - com.
abiquo.abicloud.omapilib.model.Host extended with attribute
 hardware-type
  00 00 00 01

13:08:42.759 [pool-3-thread-8] DEBUG c.a.v.n.i.DHCPConfiguratorOmapilib - Added
host rule to ISC DHCP Server to 10.0.1.4_host:10.0.1.4:00:50:56:00:d1:dd
13:08:42.759 [pool-3-thread-8] DEBUG c.a.v.n.i.DHCPConfiguratorOmapilib - Adding
 host rule to ISC DHCP Server to 10.0.1.10_host:10.0.1.10:00:50:56:33:4c:61
13:08:42.759 [pool-3-thread-8] INFO com.abiquo.abicloud.omapilib.Message - Crea
ting emtpy Message Object
13:08:42.760 [pool-3-thread-8] INFO com.abiquo.abicloud.omapilib.Message - com.
abiquo.abicloud.omapilib.model.Host extended with attribute
 name
  31 30 2e 30 2e 31 2e 31 30 5f 68 6f 73 74

13:08:42.760 [pool-3-thread-8] INFO com.abiquo.abicloud.omapilib.Message - com.
abiquo.abicloud.omapilib.model.Host extended with attribute
 ip-address
  0a 00 01 0a

13:08:42.760 [pool-3-thread-8] INFO com.abiquo.abicloud.omapilib.Message - com.
abiquo.abicloud.omapilib.model.Host extended with attribute
 hardware-address
  00 50 56 33 4c 61

13:08:42.760 [pool-3-thread-8] INFO com.abiquo.abicloud.omapilib.Message - com.
abiquo.abicloud.omapilib.model.Host extended with attribute
 hardware-type
  00 00 00 01

13:08:42.760 [pool-3-thread-8] INFO com.abiquo.abicloud.omapilib.Message - com.
abiquo.abicloud.omapilib.model.Host extended with attribute
 statements
  6f 70 74 69 6f 6e 20 72 6f 75 74 65 72 73 20 31
 30 2e 30 2e 31 2e 31 3b 20 6f 70 74 69 6f 6e 20
 73 75 62 6e 65 74 2d 6d 61 73 6b 20 32 35 35 2e
 32 35 35 2e 32 35 35 2e 30 3b

13:08:42.761 [pool-3-thread-8] INFO com.abiquo.abicloud.omapilib.Message - com.
abiquo.abicloud.omapilib.model.Host extended with Message
 create
  00 00 00 01

13:08:42.761 [pool-3-thread-8] INFO com.abiquo.abicloud.omapilib.Message - com.
abiquo.abicloud.omapilib.model.Host extended with Message
 exclusive
  00 00 00 01

13:08:42.761 [pool-3-thread-8] INFO com.abiquo.abicloud.omapilib.Message - Tryi
ng to CREATE com.abiquo.abicloud.omapilib.model.Host
13:08:42.833 [pool-3-thread-8] INFO com.abiquo.abicloud.omapilib.Message - - S
uccessfully CREATEed ...
13:08:42.833 [pool-3-thread-8] INFO com.abiquo.abicloud.omapilib.Message - Effo
rt to assign incoming data to Message Object
13:08:42.834 [pool-3-thread-8] INFO com.abiquo.abicloud.omapilib.Message - com.
abiquo.abicloud.omapilib.model.Host extended with attribute
 ip-address
  0a 00 01 0a

13:08:42.834 [pool-3-thread-8] INFO com.abiquo.abicloud.omapilib.Message - com.
abiquo.abicloud.omapilib.model.Host extended with attribute
 name
  31 30 2e 30 2e 31 2e 31 30 5f 68 6f 73 74

13:08:42.834 [pool-3-thread-8] INFO com.abiquo.abicloud.omapilib.Message - com.
abiquo.abicloud.omapilib.model.Host extended with attribute
 hardware-address
  00 50 56 33 4c 61

13:08:42.834 [pool-3-thread-8] INFO com.abiquo.abicloud.omapilib.Message - com.
abiquo.abicloud.omapilib.model.Host extended with attribute
 hardware-type
  00 00 00 01

13:08:42.834 [pool-3-thread-8] DEBUG c.a.v.n.i.DHCPConfiguratorOmapilib - Added
host rule to ISC DHCP Server to 10.0.1.10_host:10.0.1.10:00:50:56:33:4c:61
13:08:42.835 [pool-3-thread-8] DEBUG c.a.v.n.i.DHCPConfiguratorOmapilib - Discon
necting from ISC DHCP Server
13:08:42.835 [pool-3-thread-8] INFO c.a.abicloud.omapilib.Connection - Closing13:08:42.835 [pool-3-thread-8] INFO c.a.abicloud.omapilib.Connection - Connecti
on closed successfully!
13:08:42.835 [pool-3-thread-8] DEBUG c.a.v.n.i.DHCPConfiguratorOmapilib - Discon
nected from ISC DHCP Server
13:08:42.835 [pool-3-thread-8] DEBUG c.a.v.n.i.DHCPConfiguratorOmapilib - Connec
ting to ISC DHCP Server in 127.0.0.1:7911
13:08:42.836 [pool-3-thread-8] INFO c.a.abicloud.omapilib.Connection - Connecti
ng to... "127.0.0.1:7911".
13:08:42.836 [pool-3-thread-8] INFO c.a.abicloud.omapilib.Connection - Connecti
on established!
13:08:42.836 [pool-3-thread-8] DEBUG c.a.v.n.i.DHCPConfiguratorOmapilib - Connec
ted to ISC DHCP Server in 127.0.0.1:7911
13:08:42.836 [pool-3-thread-8] DEBUG c.a.v.n.i.DHCPConfiguratorOmapilib - Adding
 host rule to ISC DHCP Server to 192.168.10.24_host:192.168.10.24:00:50:56:3c:3c
:51
13:08:42.837 [pool-3-thread-8] INFO com.abiquo.abicloud.omapilib.Message - Crea
ting emtpy Message Object
13:08:42.837 [pool-3-thread-8] INFO com.abiquo.abicloud.omapilib.Message - com.
abiquo.abicloud.omapilib.model.Host extended with attribute
 name
  31 39 32 2e 31 36 38 2e 31 30 2e 32 34 5f 68 6f
 73 74
13:08:42.837 [pool-3-thread-8] INFO com.abiquo.abicloud.omapilib.Message - com.
abiquo.abicloud.omapilib.model.Host extended with attribute
 ip-address
  c0 a8 0a 18

13:08:42.837 [pool-3-thread-8] INFO com.abiquo.abicloud.omapilib.Message - com.
abiquo.abicloud.omapilib.model.Host extended with attribute
 hardware-address
  00 50 56 3c 3c 51

13:08:42.838 [pool-3-thread-8] INFO com.abiquo.abicloud.omapilib.Message - com.
abiquo.abicloud.omapilib.model.Host extended with attribute
 hardware-type
  00 00 00 01

13:08:42.838 [pool-3-thread-8] INFO com.abiquo.abicloud.omapilib.Message - com.
abiquo.abicloud.omapilib.model.Host extended with attribute
 statements
  6f 70 74 69 6f 6e 20 72 6f 75 74 65 72 73 20 31
 39 32 2e 31 36 38 2e 31 30 2e 31 3b 20 6f 70 74
 69 6f 6e 20 73 75 62 6e 65 74 2d 6d 61 73 6b 20
 32 35 35 2e 32 35 35 2e 32 35 35 2e 30 3b

13:08:42.838 [pool-3-thread-8] INFO com.abiquo.abicloud.omapilib.Message - com.
abiquo.abicloud.omapilib.model.Host extended with Message
 create
  00 00 00 01

13:08:42.838 [pool-3-thread-8] INFO com.abiquo.abicloud.omapilib.Message - com.
abiquo.abicloud.omapilib.model.Host extended with Message
 exclusive
  00 00 00 01

13:08:42.838 [pool-3-thread-8] INFO com.abiquo.abicloud.omapilib.Message - Tryi
ng to CREATE com.abiquo.abicloud.omapilib.model.Host
13:08:42.908 [pool-3-thread-8] INFO com.abiquo.abicloud.omapilib.Message - - S
uccessfully CREATEed ...
13:08:42.909 [pool-3-thread-8] INFO com.abiquo.abicloud.omapilib.Message - Effo
rt to assign incoming data to Message Object
13:08:42.909 [pool-3-thread-8] INFO com.abiquo.abicloud.omapilib.Message - com.
abiquo.abicloud.omapilib.model.Host extended with attribute
 ip-address
  c0 a8 0a 18

13:08:42.909 [pool-3-thread-8] INFO com.abiquo.abicloud.omapilib.Message - com.
abiquo.abicloud.omapilib.model.Host extended with attribute
 name
  31 39 32 2e 31 36 38 2e 31 30 2e 32 34 5f 68 6f
 73 74

13:08:42.910 [pool-3-thread-8] INFO com.abiquo.abicloud.omapilib.Message - com.
abiquo.abicloud.omapilib.model.Host extended with attribute
 hardware-address
  00 50 56 3c 3c 51

13:08:42.910 [pool-3-thread-8] INFO com.abiquo.abicloud.omapilib.Message - com.
abiquo.abicloud.omapilib.model.Host extended with attribute
 hardware-type
  00 00 00 01

13:08:42.910 [pool-3-thread-8] DEBUG c.a.v.n.i.DHCPConfiguratorOmapilib - Added
host rule to ISC DHCP Server to 192.168.10.24_host:192.168.10.24:00:50:56:3c:3c:
51
13:08:42.910 [pool-3-thread-8] DEBUG c.a.v.n.i.DHCPConfiguratorOmapilib - Discon
necting from ISC DHCP Server
13:08:42.910 [pool-3-thread-8] INFO c.a.abicloud.omapilib.Connection - Closing
the connection...
13:08:42.911 [pool-3-thread-8] INFO c.a.abicloud.omapilib.Connection - Connecti
on closed successfully!
13:08:42.911 [pool-3-thread-8] DEBUG c.a.v.n.i.DHCPConfiguratorOmapilib - Discon
nected from ISC DHCP Server
13:08:42.911 [pool-3-thread-8] INFO c.a.v.v.i.VirtualapplianceresourceDeployer
- Checking the virtual Machine: 0fe63374-0905-4406-8582-73da1c1ad28d
13:08:42.911 [pool-3-thread-8] INFO c.a.v.model.AbsVirtualMachine - Changing th
e state to : POWER_UP
13:08:47.311 [pool-3-thread-8] INFO c.a.v.machine.impl.VmwareMachine - [POWER_O
N]0fe63374-0905-4406-8582-73da1c1a
13:08:50.166 [pool-3-thread-8] INFO c.a.v.machine.impl.VmwareMachine - [POWER_O
N] successfuly for VM [0fe63374-0905-4406-8582-73da1c1a]
13:08:50.276 [pool-3-thread-8] INFO c.a.v.model.AbsVirtualMachine - State chang
ed succsfully to :PowerUp
13:08:50.276 [pool-3-thread-8] INFO c.a.v.v.i.VirtualapplianceresourceDeployer
- Checking the virtual Machine: 557f7062-63c0-457a-a63d-73b1bef9806e
13:08:50.277 [pool-3-thread-8] INFO c.a.v.model.AbsVirtualMachine - Changing th
e state to : POWER_UP
13:08:54.764 [pool-3-thread-8] INFO c.a.v.machine.impl.VmwareMachine - [POWER_O
N]557f7062-63c0-457a-a63d-73b1bef9
13:08:59.382 [pool-3-thread-8] INFO c.a.v.machine.impl.VmwareMachine - [POWER_O
N] successfuly for VM [557f7062-63c0-457a-a63d-73b1bef9]
13:08:59.492 [pool-3-thread-8] INFO c.a.v.model.AbsVirtualMachine - State chang
ed succsfully to :PowerUp
13:08:59.493 [pool-3-thread-8] INFO c.a.v.v.i.VirtualapplianceresourceDeployer
- Updating the machines list
13:11:03.068 INFO c.a.a.abicloudws.VirtualApplianceWS - Refreshing the virtual
appliance state: 1
13:11:05.781 [pool-4-thread-12] INFO c.a.a.vsm.plugin.MonitorManager - Receivei
ng a pulling event demand for virtualSystemID: 557f7062-63c0-457a-a63d-73b1bef98
06e and hypervisor address: http://192.168.10.200:443/
13:11:08.281 [pool-4-thread-12] INFO c.a.a.vsm.plugin.esxi.MonitorDemand - The
event sent <?xml version="1.0" encoding="UTF-8"?>
<env:Envelope xmlns:env="http://www.w3.org/2003/05/soap-envelope"
  xmlns:mdo="http://schemas.wiseman.dev.java.net/metadata/messagetypes"
  xmlns:mex="http://schemas.xmlsoap.org/ws/2004/09/mex"
  xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"
  xmlns:wse="http://schemas.xmlsoap.org/ws/2004/08/eventing"
  xmlns:wsen="http://schemas.xmlsoap.org/ws/2004/09/enumeration"
  xmlns:wsman="http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd"
  xmlns:wsmeta="http://schemas.dmtf.org/wbem/wsman/1/wsman/version1.0.0.a/defaul
t-addressing-model.xsd"
  xmlns:wxf="http://schemas.xmlsoap.org/ws/2004/09/transfer" xmlns:xs="http://ww
w.w3.org/2001/XMLSchema">
  <env:Header>
    <wsa:Action env:mustUnderstand="true"
      xmlns:ns11="http://schemas.dmtf.org/wbem/wsman/identity/1/wsmanidentity.xs
d" xmlns:ns12="http://abiquo.com/abicloud/vsm/event.xsd">http://schemas.dmtf.org
/wbem/wsman/1/wsman/Event</wsa:Action>
    <wsa:To env:mustUnderstand="true"
      xmlns:ns11="http://schemas.dmtf.org/wbem/wsman/identity/1/wsmanidentity.xs
d" xmlns:ns12="http://abiquo.com/abicloud/vsm/event.xsd">http://abicloudserver:8
080/server/EventSink</wsa:To>
    <wsa:MessageID env:mustUnderstand="true"
      xmlns:ns11="http://schemas.dmtf.org/wbem/wsman/identity/1/wsmanidentity.xs
d" xmlns:ns12="http://abiquo.com/abicloud/vsm/event.xsd">urn:uuid:5c575ba4-2d4f-
4dfe-b9d9-58a87e408519</wsa:MessageID>
  </env:Header>
  <env:Body>
    <ns12:Event eventType="PoweredOn"
      virtualSystemAddress="http://ESXiAddress"
      virtualSystemID="557f7062-63c0-457a-a63d-73b1bef9806e"
      virtualSystemType="vmx-04"
      xmlns:ns11="http://schemas.dmtf.org/wbem/wsman/identity/1/wsmanidentity.xs
d" xmlns:ns12="http://abiquo.com/abicloud/vsm/event.xsd"/>
  </env:Body>
</env:Envelope>

13:11:08.310 INFO c.a.abiserver.eventing.EventSink - An event was received: eve
nType:PoweredOn virtualSystemAddres: http://ESXiAddress virtualSystemType:vmx-04
 virtualSystemID557f7062-63c0-457a-a63d-73b1bef9806e
13:11:09.053 [pool-4-thread-12] INFO c.a.a.vsm.plugin.MonitorManager - Receivei
ng a pulling event demand for virtualSystemID: 0fe63374-0905-4406-8582-73da1c1ad
28d and hypervisor address: http://192.168.10.200:443/
13:11:11.460 [pool-4-thread-12] INFO c.a.a.vsm.plugin.esxi.MonitorDemand - The
event sent <?xml version="1.0" encoding="UTF-8"?>
<env:Envelope xmlns:env="http://www.w3.org/2003/05/soap-envelope"
  xmlns:mdo="http://schemas.wiseman.dev.java.net/metadata/messagetypes"
  xmlns:mex="http://schemas.xmlsoap.org/ws/2004/09/mex"
  xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"
  xmlns:wse="http://schemas.xmlsoap.org/ws/2004/08/eventing"
  xmlns:wsen="http://schemas.xmlsoap.org/ws/2004/09/enumeration"
  xmlns:wsman="http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd"
  xmlns:wsmeta="http://schemas.dmtf.org/wbem/wsman/1/wsman/version1.0.0.a/defaul
t-addressing-model.xsd"
  xmlns:wxf="http://schemas.xmlsoap.org/ws/2004/09/transfer" xmlns:xs="http://ww
w.w3.org/2001/XMLSchema">
  <env:Header>
    <wsa:Action env:mustUnderstand="true"
      xmlns:ns11="http://schemas.dmtf.org/wbem/wsman/identity/1/wsmanidentity.xs
d" xmlns:ns12="http://abiquo.com/abicloud/vsm/event.xsd">http://schemas.dmtf.org
/wbem/wsman/1/wsman/Event</wsa:Action>
    <wsa:To env:mustUnderstand="true"
      xmlns:ns11="http://schemas.dmtf.org/wbem/wsman/identity/1/wsmanidentity.xs
d" xmlns:ns12="http://abiquo.com/abicloud/vsm/event.xsd">http://abicloudserver:8
080/server/EventSink</wsa:To>
    <wsa:MessageID env:mustUnderstand="true"
      xmlns:ns11="http://schemas.dmtf.org/wbem/wsman/identity/1/wsmanidentity.xs
d" xmlns:ns12="http://abiquo.com/abicloud/vsm/event.xsd">urn:uuid:1c68d318-219f-
4d50-93b6-392ae652c317</wsa:MessageID>
  </env:Header>
  <env:Body>
    <ns12:Event eventType="PoweredOn"
      virtualSystemAddress="http://ESXiAddress"
      virtualSystemID="0fe63374-0905-4406-8582-73da1c1ad28d"
      virtualSystemType="vmx-04"
      xmlns:ns11="http://schemas.dmtf.org/wbem/wsman/identity/1/wsmanidentity.xs
d" xmlns:ns12="http://abiquo.com/abicloud/vsm/event.xsd"/>
  </env:Body>
</env:Envelope>

13:11:11.463 INFO c.a.abiserver.eventing.EventSink - An event was received: eve
nType:PoweredOn virtualSystemAddres: http://ESXiAddress virtualSystemType:vmx-04
 virtualSystemID0fe63374-0905-4406-8582-73da1c1ad28d


the connection...

Sort Order: Ascending order - Click to sort in descending order
[ Permalink | « Hide ]
Jaume Devesa added a comment - 01/Dec/09 04:02 PM
I've tried to follow the same steps as you... to check the behaviour of the DHCP synchronizer
I've done the following:
------------------------
STEP 1
-------------------------
Create two nodes:
  - the first one with private ip 10.0.1.10 as private ip and 192.168.6.24 as public ip
  - the second one with 10.0.1.4 as private ip

Deploying I have had the following message:


15:35:29.465 [pool-4-thread-1] DEBUG c.a.v.n.i.DHCPConfiguratorOmapilib - Connecting to ISC DHCP Server in 192.168.6.45:7791
15:35:29.480 [pool-4-thread-1] INFO c.a.abicloud.omapilib.Connection - Connecting to... "192.168.6.45:7791".
15:35:29.526 [pool-4-thread-1] INFO c.a.abicloud.omapilib.Connection - Connection established!
15:35:29.527 [pool-4-thread-1] DEBUG c.a.v.n.i.DHCPConfiguratorOmapilib - Connected to ISC DHCP Server in 192.168.6.45:7791
15:35:29.528 [pool-4-thread-1] DEBUG c.a.v.n.i.DHCPConfiguratorOmapilib - Adding host rule to ISC DHCP Server to 10.0.1.10_host:10.0.1.10:52:54:00:76:a0:d5
15:35:29.547 [pool-4-thread-1] INFO com.abiquo.abicloud.omapilib.Message - Creating emtpy Message Object
15:35:29.552 [pool-4-thread-1] INFO com.abiquo.abicloud.omapilib.Message - com.abiquo.abicloud.omapilib.model.Host extended with attribute
 name
  31 30 2e 30 2e 31 2e 31 30 5f 68 6f 73 74

15:35:29.555 [pool-4-thread-1] INFO com.abiquo.abicloud.omapilib.Message - com.abiquo.abicloud.omapilib.model.Host extended with attribute
 ip-address
  0a 00 01 0a

15:35:29.557 [pool-4-thread-1] INFO com.abiquo.abicloud.omapilib.Message - com.abiquo.abicloud.omapilib.model.Host extended with attribute
 hardware-address
  52 54 00 76 a0 d5

15:35:29.558 [pool-4-thread-1] INFO com.abiquo.abicloud.omapilib.Message - com.abiquo.abicloud.omapilib.model.Host extended with attribute
 hardware-type
  00 00 00 01

15:35:29.561 [pool-4-thread-1] INFO com.abiquo.abicloud.omapilib.Message - com.abiquo.abicloud.omapilib.model.Host extended with attribute
 statements
  6f 70 74 69 6f 6e 20 72 6f 75 74 65 72 73 20 31
 30 2e 30 2e 31 2e 31 3b 20 6f 70 74 69 6f 6e 20
 73 75 62 6e 65 74 2d 6d 61 73 6b 20 32 35 35 2e
 32 35 35 2e 32 35 35 2e 30 3b

15:35:29.562 [pool-4-thread-1] INFO com.abiquo.abicloud.omapilib.Message - com.abiquo.abicloud.omapilib.model.Host extended with Message
 create
  00 00 00 01

15:35:29.563 [pool-4-thread-1] INFO com.abiquo.abicloud.omapilib.Message - com.abiquo.abicloud.omapilib.model.Host extended with Message
 exclusive
  00 00 00 01

15:35:29.564 [pool-4-thread-1] INFO com.abiquo.abicloud.omapilib.Message - Trying to CREATE com.abiquo.abicloud.omapilib.model.Host
15:35:29.684 [pool-4-thread-1] INFO com.abiquo.abicloud.omapilib.Message - - Successfully CREATEed ...
15:35:29.685 [pool-4-thread-1] INFO com.abiquo.abicloud.omapilib.Message - Effort to assign incoming data to Message Object
15:35:29.687 [pool-4-thread-1] INFO com.abiquo.abicloud.omapilib.Message - com.abiquo.abicloud.omapilib.model.Host extended with attribute
 ip-address
  0a 00 01 0a

15:35:29.688 [pool-4-thread-1] INFO com.abiquo.abicloud.omapilib.Message - com.abiquo.abicloud.omapilib.model.Host extended with attribute
 name
  31 30 2e 30 2e 31 2e 31 30 5f 68 6f 73 74

15:35:29.689 [pool-4-thread-1] INFO com.abiquo.abicloud.omapilib.Message - com.abiquo.abicloud.omapilib.model.Host extended with attribute
 hardware-address
  52 54 00 76 a0 d5

15:35:29.690 [pool-4-thread-1] INFO com.abiquo.abicloud.omapilib.Message - com.abiquo.abicloud.omapilib.model.Host extended with attribute
 hardware-type
  00 00 00 01

15:35:29.691 [pool-4-thread-1] DEBUG c.a.v.n.i.DHCPConfiguratorOmapilib - Added host rule to ISC DHCP Server to 10.0.1.10_host:10.0.1.10:52:54:00:76:a0:d5
15:35:29.692 [pool-4-thread-1] DEBUG c.a.v.n.i.DHCPConfiguratorOmapilib - Adding host rule to ISC DHCP Server to 10.0.1.4_host:10.0.1.4:52:54:00:b2:30:6c
15:35:29.693 [pool-4-thread-1] INFO com.abiquo.abicloud.omapilib.Message - Creating emtpy Message Object
15:35:29.695 [pool-4-thread-1] INFO com.abiquo.abicloud.omapilib.Message - com.abiquo.abicloud.omapilib.model.Host extended with attribute
 name
  31 30 2e 30 2e 31 2e 34 5f 68 6f 73 74

15:35:29.697 [pool-4-thread-1] INFO com.abiquo.abicloud.omapilib.Message - com.abiquo.abicloud.omapilib.model.Host extended with attribute
 ip-address
  0a 00 01 04

15:35:29.699 [pool-4-thread-1] INFO com.abiquo.abicloud.omapilib.Message - com.abiquo.abicloud.omapilib.model.Host extended with attribute
 hardware-address
  52 54 00 b2 30 6c

15:35:29.700 [pool-4-thread-1] INFO com.abiquo.abicloud.omapilib.Message - com.abiquo.abicloud.omapilib.model.Host extended with attribute
 hardware-type
  00 00 00 01

15:35:29.703 [pool-4-thread-1] INFO com.abiquo.abicloud.omapilib.Message - com.abiquo.abicloud.omapilib.model.Host extended with attribute
 statements
  6f 70 74 69 6f 6e 20 72 6f 75 74 65 72 73 20 31
 30 2e 30 2e 31 2e 31 3b 20 6f 70 74 69 6f 6e 20
 73 75 62 6e 65 74 2d 6d 61 73 6b 20 32 35 35 2e
 32 35 35 2e 32 35 35 2e 30 3b

15:35:29.704 [pool-4-thread-1] INFO com.abiquo.abicloud.omapilib.Message - com.abiquo.abicloud.omapilib.model.Host extended with Message
 create
  00 00 00 01

15:35:29.705 [pool-4-thread-1] INFO com.abiquo.abicloud.omapilib.Message - com.abiquo.abicloud.omapilib.model.Host extended with Message
 exclusive
  00 00 00 01

15:35:29.706 [pool-4-thread-1] INFO com.abiquo.abicloud.omapilib.Message - Trying to CREATE com.abiquo.abicloud.omapilib.model.Host
15:35:29.749 [pool-4-thread-1] INFO com.abiquo.abicloud.omapilib.Message - - Successfully CREATEed ...
15:35:29.750 [pool-4-thread-1] INFO com.abiquo.abicloud.omapilib.Message - Effort to assign incoming data to Message Object
15:35:29.751 [pool-4-thread-1] INFO com.abiquo.abicloud.omapilib.Message - com.abiquo.abicloud.omapilib.model.Host extended with attribute
 ip-address
  0a 00 01 04

15:35:29.753 [pool-4-thread-1] INFO com.abiquo.abicloud.omapilib.Message - com.abiquo.abicloud.omapilib.model.Host extended with attribute
 name
  31 30 2e 30 2e 31 2e 34 5f 68 6f 73 74

15:35:29.754 [pool-4-thread-1] INFO com.abiquo.abicloud.omapilib.Message - com.abiquo.abicloud.omapilib.model.Host extended with attribute
 hardware-address
  52 54 00 b2 30 6c

15:35:29.755 [pool-4-thread-1] INFO com.abiquo.abicloud.omapilib.Message - com.abiquo.abicloud.omapilib.model.Host extended with attribute
 hardware-type
  00 00 00 01

15:35:29.756 [pool-4-thread-1] DEBUG c.a.v.n.i.DHCPConfiguratorOmapilib - Added host rule to ISC DHCP Server to 10.0.1.4_host:10.0.1.4:52:54:00:b2:30:6c
15:35:29.757 [pool-4-thread-1] DEBUG c.a.v.n.i.DHCPConfiguratorOmapilib - Disconnecting from ISC DHCP Server
15:35:29.758 [pool-4-thread-1] INFO c.a.abicloud.omapilib.Connection - Closing the connection...
15:35:29.759 [pool-4-thread-1] INFO c.a.abicloud.omapilib.Connection - Connection closed successfully!
15:35:29.760 [pool-4-thread-1] DEBUG c.a.v.n.i.DHCPConfiguratorOmapilib - Disconnected from ISC DHCP Server
15:35:29.761 [pool-4-thread-1] DEBUG c.a.v.n.i.DHCPConfiguratorOmapilib - Connecting to ISC DHCP Server in 192.168.6.45:7791
15:35:29.762 [pool-4-thread-1] INFO c.a.abicloud.omapilib.Connection - Connecting to... "192.168.6.45:7791".
15:35:29.765 [pool-4-thread-1] INFO c.a.abicloud.omapilib.Connection - Connection established!
15:35:29.766 [pool-4-thread-1] DEBUG c.a.v.n.i.DHCPConfiguratorOmapilib - Connected to ISC DHCP Server in 192.168.6.45:7791
15:35:29.767 [pool-4-thread-1] DEBUG c.a.v.n.i.DHCPConfiguratorOmapilib - Adding host rule to ISC DHCP Server to 192.168.6.24_host:192.168.6.24:52:54:00:76:84:4e
15:35:29.768 [pool-4-thread-1] INFO com.abiquo.abicloud.omapilib.Message - Creating emtpy Message Object
15:35:29.769 [pool-4-thread-1] INFO com.abiquo.abicloud.omapilib.Message - com.abiquo.abicloud.omapilib.model.Host extended with attribute
 name
  31 39 32 2e 31 36 38 2e 36 2e 32 34 5f 68 6f 73
 74

15:35:29.771 [pool-4-thread-1] INFO com.abiquo.abicloud.omapilib.Message - com.abiquo.abicloud.omapilib.model.Host extended with attribute
 ip-address
  c0 a8 06 18

15:35:29.773 [pool-4-thread-1] INFO com.abiquo.abicloud.omapilib.Message - com.abiquo.abicloud.omapilib.model.Host extended with attribute
 hardware-address
  52 54 00 76 84 4e

15:35:29.774 [pool-4-thread-1] INFO com.abiquo.abicloud.omapilib.Message - com.abiquo.abicloud.omapilib.model.Host extended with attribute
 hardware-type
  00 00 00 01

15:35:29.777 [pool-4-thread-1] INFO com.abiquo.abicloud.omapilib.Message - com.abiquo.abicloud.omapilib.model.Host extended with attribute
 statements
  6f 70 74 69 6f 6e 20 72 6f 75 74 65 72 73 20 31
 39 32 2e 31 36 38 2e 36 2e 31 3b 20 6f 70 74 69
 6f 6e 20 73 75 62 6e 65 74 2d 6d 61 73 6b 20 32
 35 35 2e 32 35 35 2e 32 35 35 2e 30 3b

15:35:29.779 [pool-4-thread-1] INFO com.abiquo.abicloud.omapilib.Message - com.abiquo.abicloud.omapilib.model.Host extended with Message
 create
  00 00 00 01

15:35:29.780 [pool-4-thread-1] INFO com.abiquo.abicloud.omapilib.Message - com.abiquo.abicloud.omapilib.model.Host extended with Message
 exclusive
  00 00 00 01

15:35:29.781 [pool-4-thread-1] INFO com.abiquo.abicloud.omapilib.Message - Trying to CREATE com.abiquo.abicloud.omapilib.model.Host
15:35:29.839 [pool-4-thread-1] INFO com.abiquo.abicloud.omapilib.Message - - Successfully CREATEed ...
15:35:29.840 [pool-4-thread-1] INFO com.abiquo.abicloud.omapilib.Message - Effort to assign incoming data to Message Object
15:35:29.841 [pool-4-thread-1] INFO com.abiquo.abicloud.omapilib.Message - com.abiquo.abicloud.omapilib.model.Host extended with attribute
 ip-address
  c0 a8 06 18

15:35:29.843 [pool-4-thread-1] INFO com.abiquo.abicloud.omapilib.Message - com.abiquo.abicloud.omapilib.model.Host extended with attribute
 name
  31 39 32 2e 31 36 38 2e 36 2e 32 34 5f 68 6f 73
 74

15:35:29.844 [pool-4-thread-1] INFO com.abiquo.abicloud.omapilib.Message - com.abiquo.abicloud.omapilib.model.Host extended with attribute
 hardware-address
  52 54 00 76 84 4e

15:35:29.845 [pool-4-thread-1] INFO com.abiquo.abicloud.omapilib.Message - com.abiquo.abicloud.omapilib.model.Host extended with attribute
 hardware-type
  00 00 00 01

15:35:29.846 [pool-4-thread-1] DEBUG c.a.v.n.i.DHCPConfiguratorOmapilib - Added host rule to ISC DHCP Server to 192.168.6.24_host:192.168.6.24:52:54:00:76:84:4e
15:35:29.847 [pool-4-thread-1] DEBUG c.a.v.n.i.DHCPConfiguratorOmapilib - Disconnecting from ISC DHCP Server
15:35:29.848 [pool-4-thread-1] INFO c.a.abicloud.omapilib.Connection - Closing the connection...
15:35:29.849 [pool-4-thread-1] INFO c.a.abicloud.omapilib.Connection - Connection closed successfully!
15:35:29.850 [pool-4-thread-1] DEBUG c.a.v.n.i.DHCPConfiguratorOmapilib - Disconnected from ISC DHCP Server

and the dhcpd.leases has the following values:

# The format of this file is documented in the dhcpd.leases(5) manual page.
# This lease file was written by isc-dhcp-V3.1.1

host 10.0.1.10_host {
  dynamic;
  hardware ethernet 52:54:00:76:a0:d5;
  fixed-address 10.0.1.10;
        supersede routers = 0a:00:01:01;
        supersede subnet-mask = ff:ff:ff:00;
}
host 10.0.1.4_host {
  dynamic;
  hardware ethernet 52:54:00:b2:30:6c;
  fixed-address 10.0.1.4;
        supersede routers = 0a:00:01:01;
        supersede subnet-mask = ff:ff:ff:00;
}
host 192.168.6.24_host {
  dynamic;
  hardware ethernet 52:54:00:76:84:4e;
  fixed-address 192.168.6.24;
        supersede routers = c0:a8:06:01;
        supersede subnet-mask = ff:ff:ff:00;
}

So, hosts are included correctly.

-------------------
STEP 2
-------------------

I undeploy the two machines . Two machines, not the application. I use this option because it comes more difficult to configure for the DHCP:
When you undeploy the whole application, the DHCP deletes all the rules and puts the new ones when the application deploys (the same case than Step 1). When you undeploy only the machines, the DHCP is forced to synchronize their rules. So, I choose the most complex case.

I choose the same IPs as you:

Server1-->IP/10.0.1.2 and IP/192.168.6.24 (10.0.1.2 instead of 10.0.1.10)
Server2-->IP/10.0.1.4 and IP/192.168.6.25 (adding public ip 192.168.6.25)

Powering on the first one:

15:58:25.191 [pool-4-thread-3] DEBUG c.a.v.n.i.DHCPConfiguratorOmapilib - Connecting to ISC DHCP Server in 192.168.6.45:7791
15:58:25.193 [pool-4-thread-3] INFO c.a.abicloud.omapilib.Connection - Connecting to... "192.168.6.45:7791".
15:58:25.195 [pool-4-thread-3] INFO c.a.abicloud.omapilib.Connection - Connection established!
15:58:25.197 [pool-4-thread-3] DEBUG c.a.v.n.i.DHCPConfiguratorOmapilib - Connected to ISC DHCP Server in 192.168.6.45:7791
15:58:25.197 [pool-4-thread-3] DEBUG c.a.v.n.i.DHCPConfiguratorOmapilib - Deleting host rule from ISC DHCP Server to 10.0.1.10_host
15:58:25.198 [pool-4-thread-3] INFO com.abiquo.abicloud.omapilib.Message - Creating emtpy Message Object
15:58:25.200 [pool-4-thread-3] INFO com.abiquo.abicloud.omapilib.Message - com.abiquo.abicloud.omapilib.model.Host extended with attribute
 name
  31 30 2e 30 2e 31 2e 31 30 5f 68 6f 73 74

15:58:25.201 [pool-4-thread-3] INFO com.abiquo.abicloud.omapilib.Message - Trying to OPEN com.abiquo.abicloud.omapilib.model.Host
15:58:25.202 [pool-4-thread-3] INFO com.abiquo.abicloud.omapilib.Message - - Successfully OPENed ...
15:58:25.203 [pool-4-thread-3] INFO com.abiquo.abicloud.omapilib.Message - Effort to assign incoming data to Message Object
15:58:25.205 [pool-4-thread-3] INFO com.abiquo.abicloud.omapilib.Message - com.abiquo.abicloud.omapilib.model.Host extended with attribute
 ip-address
  0a 00 01 0a

15:58:25.206 [pool-4-thread-3] INFO com.abiquo.abicloud.omapilib.Message - com.abiquo.abicloud.omapilib.model.Host extended with attribute
 name
  31 30 2e 30 2e 31 2e 31 30 5f 68 6f 73 74

15:58:25.207 [pool-4-thread-3] INFO com.abiquo.abicloud.omapilib.Message - com.abiquo.abicloud.omapilib.model.Host extended with attribute
 hardware-address
  52 54 00 cd fe d5

15:58:25.208 [pool-4-thread-3] INFO com.abiquo.abicloud.omapilib.Message - com.abiquo.abicloud.omapilib.model.Host extended with attribute
 hardware-type
  00 00 00 01

15:58:25.210 [pool-4-thread-3] INFO com.abiquo.abicloud.omapilib.Message - Trying to DELETE com.abiquo.abicloud.omapilib.model.Host
Dec 1, 2009 3:58:25 PM org.apache.commons.httpclient.HttpMethodDirector executeWithRetry
INFO: I/O exception (java.net.ConnectException) caught when processing request: Connection refused
Dec 1, 2009 3:58:25 PM org.apache.commons.httpclient.HttpMethodDirector executeWithRetry
INFO: Retrying request
Dec 1, 2009 3:58:25 PM org.apache.commons.httpclient.HttpMethodDirector executeWithRetry
INFO: I/O exception (java.net.ConnectException) caught when processing request: Connection refused
Dec 1, 2009 3:58:25 PM org.apache.commons.httpclient.HttpMethodDirector executeWithRetry
INFO: Retrying request
Dec 1, 2009 3:58:25 PM org.apache.commons.httpclient.HttpMethodDirector executeWithRetry
INFO: I/O exception (java.net.ConnectException) caught when processing request: Connection refused
Dec 1, 2009 3:58:25 PM org.apache.commons.httpclient.HttpMethodDirector executeWithRetry
INFO: Retrying request
15:58:25.288 WARN c.a.util.resources.ResourceManager - No Resource matching the bundleBaseName. com/abiquo/abiserver/exception/StorageConnectionException has been found
15:58:25.288 ERROR com.abiquo.util.AbiClassLoader - Exception connecting to Storage System located in http://localhost/ssm/
15:58:25.289 ERROR c.abiquo.abiserver.sanity.SanityJob - Saneable exception in 1 of the SanityStorage modules! Some features could not work properly
15:58:25.532 [pool-4-thread-3] INFO com.abiquo.abicloud.omapilib.Message - - Successfully DELETEed ...
15:58:25.533 [pool-4-thread-3] INFO com.abiquo.abicloud.omapilib.Message - Effort to assign incoming data to Message Object
15:58:25.535 [pool-4-thread-3] INFO com.abiquo.abicloud.omapilib.Message - com.abiquo.abicloud.omapilib.model.Host extended with Message
 result
  00 00 00 00

15:58:25.536 [pool-4-thread-3] DEBUG c.a.v.n.i.DHCPConfiguratorOmapilib - Deleted host rule from ISC DHCP Server to 10.0.1.10_host
15:58:25.537 [pool-4-thread-3] DEBUG c.a.v.n.i.DHCPConfiguratorOmapilib - Disconnecting from ISC DHCP Server
15:58:25.538 [pool-4-thread-3] INFO c.a.abicloud.omapilib.Connection - Closing the connection...
15:58:25.539 [pool-4-thread-3] INFO c.a.abicloud.omapilib.Connection - Connection closed successfully!
15:58:25.540 [pool-4-thread-3] DEBUG c.a.v.n.i.DHCPConfiguratorOmapilib - Disconnected from ISC DHCP Server
15:58:25.541 [pool-4-thread-3] DEBUG c.a.v.n.i.DHCPConfiguratorOmapilib - Connecting to ISC DHCP Server in 192.168.6.45:7791
15:58:25.542 [pool-4-thread-3] INFO c.a.abicloud.omapilib.Connection - Connecting to... "192.168.6.45:7791".
15:58:25.545 [pool-4-thread-3] INFO c.a.abicloud.omapilib.Connection - Connection established!
15:58:25.546 [pool-4-thread-3] DEBUG c.a.v.n.i.DHCPConfiguratorOmapilib - Connected to ISC DHCP Server in 192.168.6.45:7791
15:58:25.547 [pool-4-thread-3] DEBUG c.a.v.n.i.DHCPConfiguratorOmapilib - Adding host rule to ISC DHCP Server to 10.0.1.2_host:10.0.1.2:52:54:00:f4:2a:2d
15:58:25.548 [pool-4-thread-3] INFO com.abiquo.abicloud.omapilib.Message - Creating emtpy Message Object
15:58:25.550 [pool-4-thread-3] INFO com.abiquo.abicloud.omapilib.Message - com.abiquo.abicloud.omapilib.model.Host extended with attribute
 name
  31 30 2e 30 2e 31 2e 32 5f 68 6f 73 74

15:58:25.552 [pool-4-thread-3] INFO com.abiquo.abicloud.omapilib.Message - com.abiquo.abicloud.omapilib.model.Host extended with attribute
 ip-address
  0a 00 01 02

15:58:25.554 [pool-4-thread-3] INFO com.abiquo.abicloud.omapilib.Message - com.abiquo.abicloud.omapilib.model.Host extended with attribute
 hardware-address
  52 54 00 f4 2a 2d

15:58:25.555 [pool-4-thread-3] INFO com.abiquo.abicloud.omapilib.Message - com.abiquo.abicloud.omapilib.model.Host extended with attribute
 hardware-type
  00 00 00 01

15:58:25.562 [pool-4-thread-3] INFO com.abiquo.abicloud.omapilib.Message - com.abiquo.abicloud.omapilib.model.Host extended with attribute
 statements
  6f 70 74 69 6f 6e 20 72 6f 75 74 65 72 73 20 31
 30 2e 30 2e 31 2e 31 3b 20 6f 70 74 69 6f 6e 20
 73 75 62 6e 65 74 2d 6d 61 73 6b 20 32 35 35 2e
 32 35 35 2e 32 35 35 2e 30 3b

15:58:25.563 [pool-4-thread-3] INFO com.abiquo.abicloud.omapilib.Message - com.abiquo.abicloud.omapilib.model.Host extended with Message
 create
  00 00 00 01

15:58:25.564 [pool-4-thread-3] INFO com.abiquo.abicloud.omapilib.Message - com.abiquo.abicloud.omapilib.model.Host extended with Message
 exclusive
  00 00 00 01

15:58:25.565 [pool-4-thread-3] INFO com.abiquo.abicloud.omapilib.Message - Trying to CREATE com.abiquo.abicloud.omapilib.model.Host
15:58:25.646 [pool-4-thread-3] INFO com.abiquo.abicloud.omapilib.Message - - Successfully CREATEed ...
15:58:25.647 [pool-4-thread-3] INFO com.abiquo.abicloud.omapilib.Message - Effort to assign incoming data to Message Object
15:58:25.649 [pool-4-thread-3] INFO com.abiquo.abicloud.omapilib.Message - com.abiquo.abicloud.omapilib.model.Host extended with attribute
 ip-address
  0a 00 01 02

15:58:25.650 [pool-4-thread-3] INFO com.abiquo.abicloud.omapilib.Message - com.abiquo.abicloud.omapilib.model.Host extended with attribute
 name
  31 30 2e 30 2e 31 2e 32 5f 68 6f 73 74

15:58:25.651 [pool-4-thread-3] INFO com.abiquo.abicloud.omapilib.Message - com.abiquo.abicloud.omapilib.model.Host extended with attribute
 hardware-address
  52 54 00 f4 2a 2d

15:58:25.653 [pool-4-thread-3] INFO com.abiquo.abicloud.omapilib.Message - com.abiquo.abicloud.omapilib.model.Host extended with attribute
 hardware-type
  00 00 00 01

15:58:25.654 [pool-4-thread-3] DEBUG c.a.v.n.i.DHCPConfiguratorOmapilib - Added host rule to ISC DHCP Server to 10.0.1.2_host:10.0.1.2:52:54:00:f4:2a:2d
15:58:25.654 [pool-4-thread-3] DEBUG c.a.v.n.i.DHCPConfiguratorOmapilib - Disconnecting from ISC DHCP Server
15:58:25.655 [pool-4-thread-3] INFO c.a.abicloud.omapilib.Connection - Closing the connection...
15:58:25.656 [pool-4-thread-3] INFO c.a.abicloud.omapilib.Connection - Connection closed successfully!
15:58:25.657 [pool-4-thread-3] DEBUG c.a.v.n.i.DHCPConfiguratorOmapilib - Disconnected from ISC DHCP Server
15:58:25.658 [pool-4-thread-3] DEBUG c.a.v.n.i.DHCPConfiguratorOmapilib - Connecting to ISC DHCP Server in 192.168.6.45:7791
15:58:25.659 [pool-4-thread-3] INFO c.a.abicloud.omapilib.Connection - Connecting to... "192.168.6.45:7791".
15:58:25.662 [pool-4-thread-3] INFO c.a.abicloud.omapilib.Connection - Connection established!
15:58:25.663 [pool-4-thread-3] DEBUG c.a.v.n.i.DHCPConfiguratorOmapilib - Connected to ISC DHCP Server in 192.168.6.45:7791
15:58:25.664 [pool-4-thread-3] DEBUG c.a.v.n.i.DHCPConfiguratorOmapilib - Adding host rule to ISC DHCP Server to 192.168.6.25_host:192.168.6.25:52:54:00:6a:0f:95
15:58:25.665 [pool-4-thread-3] INFO com.abiquo.abicloud.omapilib.Message - Creating emtpy Message Object
15:58:25.666 [pool-4-thread-3] INFO com.abiquo.abicloud.omapilib.Message - com.abiquo.abicloud.omapilib.model.Host extended with attribute
 name
  31 39 32 2e 31 36 38 2e 36 2e 32 35 5f 68 6f 73
 74

15:58:25.668 [pool-4-thread-3] INFO com.abiquo.abicloud.omapilib.Message - com.abiquo.abicloud.omapilib.model.Host extended with attribute
 ip-address
  c0 a8 06 19

15:58:25.671 [pool-4-thread-3] INFO com.abiquo.abicloud.omapilib.Message - com.abiquo.abicloud.omapilib.model.Host extended with attribute
 hardware-address
  52 54 00 6a 0f 95

15:58:25.673 [pool-4-thread-3] INFO com.abiquo.abicloud.omapilib.Message - com.abiquo.abicloud.omapilib.model.Host extended with attribute
 hardware-type
  00 00 00 01

15:58:25.675 [pool-4-thread-3] INFO com.abiquo.abicloud.omapilib.Message - com.abiquo.abicloud.omapilib.model.Host extended with attribute
 statements
  6f 70 74 69 6f 6e 20 72 6f 75 74 65 72 73 20 31
 39 32 2e 31 36 38 2e 36 2e 31 3b 20 6f 70 74 69
 6f 6e 20 73 75 62 6e 65 74 2d 6d 61 73 6b 20 32
 35 35 2e 32 35 35 2e 32 35 35 2e 30 3b

15:58:25.676 [pool-4-thread-3] INFO com.abiquo.abicloud.omapilib.Message - com.abiquo.abicloud.omapilib.model.Host extended with Message
 create
  00 00 00 01

15:58:25.677 [pool-4-thread-3] INFO com.abiquo.abicloud.omapilib.Message - com.abiquo.abicloud.omapilib.model.Host extended with Message
 exclusive
  00 00 00 01

15:58:25.678 [pool-4-thread-3] INFO com.abiquo.abicloud.omapilib.Message - Trying to CREATE com.abiquo.abicloud.omapilib.model.Host
15:58:25.886 [pool-4-thread-3] INFO com.abiquo.abicloud.omapilib.Message - - Successfully CREATEed ...
15:58:25.887 [pool-4-thread-3] INFO com.abiquo.abicloud.omapilib.Message - Effort to assign incoming data to Message Object
15:58:25.888 [pool-4-thread-3] INFO com.abiquo.abicloud.omapilib.Message - com.abiquo.abicloud.omapilib.model.Host extended with attribute
 ip-address
  c0 a8 06 19

15:58:25.890 [pool-4-thread-3] INFO com.abiquo.abicloud.omapilib.Message - com.abiquo.abicloud.omapilib.model.Host extended with attribute
 name
  31 39 32 2e 31 36 38 2e 36 2e 32 35 5f 68 6f 73
 74

15:58:25.891 [pool-4-thread-3] INFO com.abiquo.abicloud.omapilib.Message - com.abiquo.abicloud.omapilib.model.Host extended with attribute
 hardware-address
  52 54 00 6a 0f 95

15:58:25.892 [pool-4-thread-3] INFO com.abiquo.abicloud.omapilib.Message - com.abiquo.abicloud.omapilib.model.Host extended with attribute
 hardware-type
  00 00 00 01

15:58:25.894 [pool-4-thread-3] DEBUG c.a.v.n.i.DHCPConfiguratorOmapilib - Added host rule to ISC DHCP Server to 192.168.6.25_host:192.168.6.25:52:54:00:6a:0f:95
15:58:25.895 [pool-4-thread-3] DEBUG c.a.v.n.i.DHCPConfiguratorOmapilib - Disconnecting from ISC DHCP Server
15:58:25.896 [pool-4-thread-3] INFO c.a.abicloud.omapilib.Connection - Closing the connection...
15:58:25.897 [pool-4-thread-3] INFO c.a.abicloud.omapilib.Connection - Connection closed successfully!
15:58:25.898 [pool-4-thread-3] DEBUG c.a.v.n.i.DHCPConfiguratorOmapilib - Disconnected from ISC DHCP Server

And the dchpd.leases file is the following:

host 10.0.1.4_host {
  dynamic;
  hardware ethernet 52:54:00:56:09:2a;
  fixed-address 10.0.1.4;
        supersede routers = 0a:00:01:01;
        supersede subnet-mask = ff:ff:ff:00;
}
host 10.0.1.10_host {
  dynamic;
  hardware ethernet 52:54:00:cd:fe:d5;
  fixed-address 10.0.1.10;
        supersede routers = 0a:00:01:01;
        supersede subnet-mask = ff:ff:ff:00;
}
host 192.168.6.24_host {
  dynamic;
  hardware ethernet 52:54:00:9a:80:24;
  fixed-address 192.168.6.24;
        supersede routers = c0:a8:06:01;
        supersede subnet-mask = ff:ff:ff:00;
}
host 10.0.1.10_host {
  dynamic;
  deleted;
}
host 10.0.1.2_host {
  dynamic;
  hardware ethernet 52:54:00:f4:2a:2d;
  fixed-address 10.0.1.2;
        supersede routers = 0a:00:01:01;
        supersede subnet-mask = ff:ff:ff:00;
}
host 192.168.6.25_host {
  dynamic;
  hardware ethernet 52:54:00:6a:0f:95;
  fixed-address 192.168.6.25;
        supersede routers = c0:a8:06:01;
        supersede subnet-mask = ff:ff:ff:00;
}

Please note the 10.0.1.10 host has been deleted. 10.0.1.2 and 192.168.6.25 has beed added.

Everything is OK...
Did I following the same steps as you?

[ Permalink | « Hide ]
Diego Parrilla added a comment - 01/Dec/09 10:45 PM
It have reproduce it: if you just modify the IPs of the nodes, don't click on save, don't move the nodes, only modify the IPs, it seems that the last change committed is not recognized.

[ Permalink | « Hide ]
Diego Parrilla added a comment - 02/Dec/09 01:13 AM
There is something very wrong. I can see in the screen 10.0.1.3 (PRIVATE) and 192.168.10.24 (PUBLIC), but I have this in the dhcp.leases. Seems the information on screen is not persisted or comitted:

# The format of this file is documented in the dhcpd.leases(5) manual page.
# This lease file was written by isc-dhcp-V3.1.1

host 10.0.1.10_host {
  dynamic;
  hardware ethernet 00:50:56:33:4c:61;
  fixed-address 10.0.1.10;
        supersede routers = 0a:00:01:01;
        supersede subnet-mask = ff:ff:ff:00;
}

and these information in the database:

#
# Data for the `rasd` table (LIMIT 0,500)
#

INSERT INTO `rasd` (`address`, `addressOnParent`, `allocationUnits`, `automaticAllocation`, `automaticDeallocation`, `caption`, `changeableType`, `configurationName`, `connectionResource`, `consumerVisibility`, `description`, `elementName`, `generation`, `hostResource`, `instanceID`, `limitResource`, `mappingBehaviour`, `otherResourceType`, `parent`, `poolID`, `reservation`, `resourceSubType`, `resourceType`, `virtualQuantity`, `weight`) VALUES
  ('00:50:56:33:4c:61',NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,'MAC Address asociated to private Network','MAC Address',NULL,NULL,'16b1078b-f322-4a15-b11a-1a29c8b35bfe',NULL,NULL,NULL,NULL,NULL,NULL,'0',10,NULL,NULL),
  ('00:50:56:12:c5:58',NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,'MAC Address asociated to public Network','MAC Address',NULL,NULL,'c9e160d9-8316-4bc1-9607-7c0cec14cfbd',NULL,NULL,NULL,NULL,NULL,NULL,'1',10,NULL,NULL);

COMMIT;

The PublicIP table has this information:

#
# Data for the `publicip` table (LIMIT 0,500)
#

INSERT INTO `publicip` (`id`, `ip`, `netMask`, `idGateway`, `idDataCenter`, `idEnterprise`, `idNode`, `quarantine`) VALUES
  (1,'192.168.10.24',24,1,1,1,6,0),
  (2,'192.168.10.25',24,1,1,1,NULL,0),
  (3,'192.168.10.26',24,1,1,1,NULL,0),
  (4,'192.168.10.27',24,1,1,1,NULL,0),
  (5,'192.168.10.28',24,1,1,NULL,NULL,0),
  (6,'192.168.10.29',24,1,1,NULL,NULL,0),
  (7,'192.168.10.30',24,1,1,NULL,NULL,0),
  (8,'192.168.10.31',24,1,1,NULL,NULL,0),
  (9,'192.168.10.32',24,1,1,NULL,NULL,0);

COMMIT;

[ Permalink | « Hide ]
Jaume Devesa added a comment - 02/Dec/09 09:45 AM
When you say: "It have reproduce it: if you just modify the IPs of the nodes, don't click on save, don't move the nodes, only modify the IPs, it seems that the last change committed is not recognized." The change commited only affects in database, dhcp sychronize its new values in deploy time.

Database table seems to be coherent with your assigments.. The problems it should be in DHCPSynchronizer in virtualfactory... Unless you have the dhcptype table with the column 'addressDHCP' with empty values.

I will try to reproduce again. Meanwhile, can I see your 'dhcptype' table please?

[ Permalink | « Hide ]
Diego Parrilla added a comment - 02/Dec/09 10:25 AM
If I can see on the screen 10.0.1.3 (PRIVATE) and 192.168.10.24 (PUBLIC), it does not sound to me like very coherent with the information in the database for the private IP and the information in the dhcp.lease is totally different.

00:50:56:33:4c:61 --> 10.0.1.10

10.0.1.3 has a different generated MAC.

The dhcptype table

INSERT INTO `dhcptype` (`dhcptypeID`, `networktypeID`, `addressDHCP`, `netmask`, `ipgateway`) VALUES
  (1,1,'127.0.0.1:7911','255.255.255.0','10.0.1.1'),
  (2,1,'127.0.0.1:7911','255.255.255.0','192.168.10.1');

[ Permalink | « Hide ]
Jaume Devesa added a comment - 03/Dec/09 11:50 AM
Finally I could reproduce your problem. There was a Flex issue when you change the IPs.
The Flex client didn't refresh the application entity and the network object was the previous one.
Atlassian JIRA (v4.0.1#471) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for abiquo. Try JIRA - bug tracking software for your team.