[1.9.1] third-party driver not getting installed for storage device

[Larry Michel]

I added an entry for Fusion IO device in drivers.yaml but upon commissioning I am not able to tell whether the 3rd party driver is detected. After deploying the system, I don't see the driver being installed either.

The entry was taken from a 1.8.3 drivers.yaml and it works for that release.

[Andres Rodriguez (andreserl)]

Hi Larry,

Can you please attach logs? We can't really know what's wrong without any of the logs. I guess in this case we need /var/log/maas/maas.log and regiond.log , drivers.yaml, and the curtin install log.

Thanks.

[Larry Michel (lmic)]

curtin log attached.

[Larry Michel (lmic)]

Andres,
Please see attached maas logs.

[Ricardo Bánffy (rbanffy)]

Can you also add the drivers.yaml you used?

[Ricardo Bánffy (rbanffy)]

Adding Larry's drivers.yaml

[Larry Michel (lmic)]

After upgrading to maas 1.9.0+bzr4533-0ubuntu1~trusty1, I was not able to recreated. it started working after I re-commissioned it. I did not immediately see the third-party drivers shown on the UI but I'm guessing it was just a matter of refreshing the page as it was there after deployment. In the install log, Curtin also showed the DKMS section for installing the Fusion IO driver and I was able to access /dev/fioa. I will re-try later today by deleting and re-enlisting and commissioning. If I am not able to recreate then we can mark this as no longer valid.

[Blake Rouse (blake-rouse)]

I am going to mark this as Invalid so we don't forget. It you are able to reproduce please mark it accordingly.

[Larry Michel (lmic)]

I am seeing this being recreated with 1.9.1:

ubuntu@maas-trusty-back-may22:~$ dpkg -l '*maas*'|cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-=====================================-================================-============-===============================================================================
ii maas 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS server all-in-one metapackage
ii maas-cli 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS command line API tool
ii maas-cluster-controller 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS server cluster controller
ii maas-common 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS server common files
ii maas-dhcp 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS DHCP server
ii maas-dns 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS DNS server
ii maas-proxy 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS Caching Proxy
ii maas-region-controller 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS server complete region controller
ii maas-region-controller-min 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS Server minimum region controller
ii python-django-maas 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS server Django web framework
ii python-maas-client 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS python API client
ii python-maas-provisioningserver 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS server provisioning libraries

What's strange is that it was showing the 3rd party drivers section until recently. Then, it's now gone again but neither drivers.yaml nor ppa has changed.

[Larry Michel (lmic)]

I have verified that this works in 2.0. I initially thought that I had recreated until I realized that the service needed to be restarted after updating the drivers.yaml.

So, I am OK with this being a won't fix.

[Andres Rodriguez (andreserl)]

We believe this is no longer an issue in the latest releases of MAAS. Please upgrade to the latest version of MAAS, and If you believe this issue is still present, please re-open this bug report or file a new one.