Unable to deploy two different roles if the hardware specs are the same

[goldyfruit]

HI,

We have two servers with the same specs (disk, memory, cpu), the only thing different is the serial number. If the servers are installed in the same time, one of them raised an error about the CMDB file (no entry.....).

If i boot the servers not at the same time, the deployment works.

In the specs file we match the serial number (tag):

generate({'disk0': '32:0',
  'disk1': '32:1',
  'disk2': '32:2',
  'disk3': '32:3',
  'disk4': '32:4',
  'disk5': '32:5',
  'disk6': '32:6',
  'gateway-admin': '10.154.20.3',
  'hostname': 'infra01-2',
  'if_b0': 'eth0',
  'if_b1': 'eth1',
  'if_b2': 'eth2',
  'ip-admin': '10.154.20.13-14',
  'netmask-admin': '255.255.255.0',
  'sn': ('CXXXB2Y1', '9TZUYDEY1'),
  'vlan-admin': '2320',
  'vlan-infra-pub': '1302'})

The spec file:

# -*- python -*-

[
    ('pdisk', 'disk0', 'ctrl', '1'),
    ('pdisk', 'disk0', 'type', 'SAS'),
    ('pdisk', 'disk0', 'id', '32:0'),
    ('pdisk', 'disk0', 'size', '278.875'),
    ('pdisk', 'disk1', 'ctrl', '1'),
    ('pdisk', 'disk1', 'type', 'SAS'),
    ('pdisk', 'disk1', 'id', '32:1'),
    ('pdisk', 'disk1', 'size', '278.875'),
    ('pdisk', 'disk2', 'ctrl', '1'),
    ('pdisk', 'disk2', 'type', 'SAS'),
    ('pdisk', 'disk2', 'id', '32:2'),
    ('pdisk', 'disk2', 'size', '278.875'),
    ('pdisk', 'disk3', 'ctrl', '1'),
    ('pdisk', 'disk3', 'type', 'SAS'),
    ('pdisk', 'disk3', 'id', '32:3'),
    ('pdisk', 'disk3', 'size', '278.875'),
    ('pdisk', 'disk4', 'ctrl', '1'),
    ('pdisk', 'disk4', 'type', 'SAS'),
    ('pdisk', 'disk4', 'id', '32:4'),
    ('pdisk', 'disk4', 'size', '278.875'),
    ('pdisk', 'disk5', 'ctrl', '1'),
    ('pdisk', 'disk5', 'type', 'SAS'),
    ('pdisk', 'disk5', 'id', '32:5'),
    ('pdisk', 'disk5', 'size', '278.875'),
    ('pdisk', 'disk6', 'ctrl', '1'),
    ('pdisk', 'disk6', 'type', 'SAS'),
    ('pdisk', 'disk6', 'id', '32:6'),
    ('pdisk', 'disk6', 'size', '278.875'),
    ('system', 'product', 'serial', '$$sn'),
]

[ErwanAliasr1]

Something is wrong in the way you use the cmdb & specs. Let's speak on chat on Monday to speak about it. (I'm on my phone) Le 26 sept. 2014 15:26, "Gaëtan Trellu" notifications@github.com a écrit :

HI,

We have two servers with the same specs (disk, memory, cpu), the only thing different is the serial number. If the servers are installed in the same time, one of them raised an error about the CMDB file (no entry.....).

If i boot the servers not at the same time, the deployment works.

In the specs file we match the serial number (tag):

generate({'disk0': '32:0', 'disk1': '32:1', 'disk2': '32:2', 'disk3': '32:3', 'disk4': '32:4', 'disk5': '32:5', 'disk6': '32:6', 'gateway-admin': '10.154.20.3', 'hostname': 'infra01-2', 'if_b0': 'eth0', 'if_b1': 'eth1', 'if_b2': 'eth2', 'ip-admin': '10.154.20.13-14', 'netmask-admin': '255.255.255.0', 'sn': ('CTZB2Y1', '9TZB2Y1'), 'vlan-admin': '2320', 'vlan-infra-pub': '1302'})

The spec file:

-- python --

[ ('pdisk', 'disk0', 'ctrl', '1'), ('pdisk', 'disk0', 'type', 'SAS'), ('pdisk', 'disk0', 'id', '32:0'), ('pdisk', 'disk0', 'size', '278.875'), ('pdisk', 'disk1', 'ctrl', '1'), ('pdisk', 'disk1', 'type', 'SAS'), ('pdisk', 'disk1', 'id', '32:1'), ('pdisk', 'disk1', 'size', '278.875'), ('pdisk', 'disk2', 'ctrl', '1'), ('pdisk', 'disk2', 'type', 'SAS'), ('pdisk', 'disk2', 'id', '32:2'), ('pdisk', 'disk2', 'size', '278.875'), ('pdisk', 'disk3', 'ctrl', '1'), ('pdisk', 'disk3', 'type', 'SAS'), ('pdisk', 'disk3', 'id', '32:3'), ('pdisk', 'disk3', 'size', '278.875'), ('pdisk', 'disk4', 'ctrl', '1'), ('pdisk', 'disk4', 'type', 'SAS'), ('pdisk', 'disk4', 'id', '32:4'), ('pdisk', 'disk4', 'size', '278.875'), ('pdisk', 'disk5', 'ctrl', '1'), ('pdisk', 'disk5', 'type', 'SAS'), ('pdisk', 'disk5', 'id', '32:5'), ('pdisk', 'disk5', 'size', '278.875'), ('pdisk', 'disk6', 'ctrl', '1'), ('pdisk', 'disk6', 'type', 'SAS'), ('pdisk', 'disk6', 'id', '32:6'), ('pdisk', 'disk6', 'size', '278.875'), ('system', 'product', 'serial', '$$sn'), ]

— Reply to this email directly or view it on GitHub https://github.com/enovance/edeploy/issues/131.

[ghantoos]

It would be nice to have the cause of this written in this issue after your private discussion. Just so that someone else doesn't fall into the same trap.

Reopening.

[ghantoos]

Looks like it was actually a bug, and not an error user-side; and seems to have been corrected by 9842551 by @fredericlepied. Closing.