hpilo kernel module not available during commissioning

[Craig Bender]

Need to enable HBAMode on H420ar controllers, however hpssacli does not support this controller. The methods used to enable HBA Mode on these controllers require using either the hprest or hponcfg utilities that require the hpilo kernel module, which is missing from the maas boot resources.

[Blake Rouse (blake-rouse)]

MAAS images used the Ubuntu cloud-image and pulls the same kernel and initrd. The hpilo driver is in linux-kernel-extra and should not be included in the cloud-image or the MAAS images. If you need this driver during commissioning then I would install it with a commissioning script using apt.

[Blake Rouse (blake-rouse)]

This is an example of how to get hpilo loaded. I test this in the ephemeral environment.

sudo apt-get update && sudo DEBIAN_FRONTEND=noninteractive apt-get --no-install-recommends -y -o Dpkg::Options::="--force-confdef" -o Dpkg::Options::="--force-confold" install linux-image-extra-$(uname -r) && sudo modprobe hpilo

[Lee Trager (ltrager)]

Two things to add to Blake's comment

1. You should probably set the shebang to #!/bin/bash -e so if the install or modprobe fail the script stops and MAAS captures the failure
2. MAAS runs scripts in lexigraphical order so you need to name the script so it comes first

This script(http://paste.ubuntu.com/24786310/) will install linux-image-extra-$(uname -r) and load the module. You just need to add the command to enable HBA mode. The following command allows you to upload the script via the CLI, this can also be done on the settings page.

maas <profile> node-scripts create name=00-hpilo description='Load the hpilo driver during commissioning' type=commissioning script@=00-hpilo

My only concern with this is the driver won't be loaded during deployment. Please let us know if this method works for you or if you need the driver during deployment.

[Christian Reis (kiko)]

This is something which we should think hard about how to fix. The commissioning environment is where all our hardware configuration will happen, and if the person deploying needs to know to type these special incantations to get the modules they need, it's going to lead them to fail or at least really slow them down.

Every significant end-user deployment will need to do hardware configuration of at least HBAs as part of hardware commissioning. We should make sure that the necessary modules -- and commands, as we also futz about looking for hpssacli and hprest -- for that hardware configuration are already present.

[Christian Reis (kiko)]

(and yes, Blake's workaround is what we ended up using in this instance, but it's certainly slowed things down here)

[Launchpad Janitor (janitor)]

[Expired for maas-images because there has been no activity for 60 days.]