Deploy ESXi on server with more then one disk

Hello.

When I deploy server with only one disk in it everything works fine. But on servers with two or more disks MAAS don’t create any datastores. It successfully deploy ESXi, configure network, register server in the vCenter. But there are no any datastores. I tried to create datastores in UI on both disks, tried leave datastore only on the disk with the system. In both cases there no datastores after deployment. And only when I deleted second disk in the UI, after comissioning, server succsessfully deploed and created datastore.

Also I can’t choose disk to setup ESXi. In logs I see that maas chose disk by itself

Running command [’/usr/sbin/multipath’, ‘-F’] with allowed return codes [0, 1] (capture=False)
‘custom’ mode but multiple devices given. using first found
mode is ‘custom’. multiple devices given. using ‘/dev/sda’ (first available)
installing in ‘custom’ mode to ‘sda’
writing image to disk {‘type’: ‘dd-gz’, ‘uri’: ‘http://10.15.30.30:5248/images/esxi/amd64/generic/7.0.2-ams/uploaded/root-dd.gz’}, sda

Is it possible to deploy ESXi on servers with more then one disk?

@kiruka4, just checking to see if you resolved this, either?

@billwear One problem is resolved. Now when I change boot disk, MAAS install Esxi exactly on this disk (doesn’t use first available as earlier). I use MAAS v3.1.0.

But on servers with two or more disks there are still no any datastores after deployment. But it’s not the MAAS problem. It is some mistakes in the packer script - https://github.com/canonical/packer-maas/blob/master/vmware-esxi/maas/storage-esxi

1 Like

thank you. i’m not going to close this; instead, i’m going to direct it to our packer guru, whom i will encourage to look at the script.

is there a bug outstanding? if not, can you file one?

@kiruka4, have you filed a bug? if so, can you cross-post the number here?

@billwear, my fault. I posted the issue on the git (https://github.com/canonical/packer-maas/issues/34) but didn’t make a bug report on launchpad.

But I already fixed storage-esxi script for me. I just have to find time to create pull request with my fixes.

Or it still better to create bug report?

1 Like

@kiruka4, we always prefer PRs to bugs, since this still open-source. especially if you already have fixes.