# rpm -ivh x86_64/lustre-dkms-2.8.57_62_g919224d-1.el7.noarch.rpm
Preparing... ################################# [100%]
Updating / installing...
1:lustre-dkms-2.8.57_62_g919224d-1.################################# [100%]
Loading new lustre-2.8.57_62_g919224d DKMS files...
Building for 3.10.0-327.el7.x86_64
Building initial module for 3.10.0-327.el7.x86_64
configure: WARNING:
Disabling ldiskfs support because complete ext4 source does not exist.
If you are building using kernel-devel packages and require ldiskfs
server support then ensure that the matching kernel-debuginfo-common
and kernel-debuginfo-common-<arch> packages are installed.
configure: WARNING: kernel missing dev_set_rdonly patch for testing
configure: WARNING:
No selinux package found, unable to build selinux enabled tools
Done.
dkms.conf: Error! Directive 'DEST_MODULE_LOCATION' does not begin with
'/kernel', '/updates', or '/extra' in record #0.
dkms.conf: Error! Directive 'DEST_MODULE_LOCATION' does not begin with
'/kernel', '/updates', or '/extra' in record #1.
dkms.conf: Error! Directive 'DEST_MODULE_LOCATION' does not begin with
'/kernel', '/updates', or '/extra' in record #2.
dkms.conf: Error! Directive 'DEST_MODULE_LOCATION' does not begin with
'/kernel', '/updates', or '/extra' in record #3.
dkms.conf: Error! Directive 'DEST_MODULE_LOCATION' does not begin with
'/kernel', '/updates', or '/extra' in record #4.
dkms.conf: Error! Directive 'DEST_MODULE_LOCATION' does not begin with
'/kernel', '/updates', or '/extra' in record #5.
dkms.conf: Error! Directive 'DEST_MODULE_LOCATION' does not begin with
'/kernel', '/updates', or '/extra' in record #6.
dkms.conf: Error! Directive 'DEST_MODULE_LOCATION' does not begin with
'/kernel', '/updates', or '/extra' in record #7.
dkms.conf: Error! Directive 'DEST_MODULE_LOCATION' does not begin with
'/kernel', '/updates', or '/extra' in record #8.
dkms.conf: Error! Directive 'DEST_MODULE_LOCATION' does not begin with
'/kernel', '/updates', or '/extra' in record #9.
dkms.conf: Error! Directive 'DEST_MODULE_LOCATION' does not begin with
'/kernel', '/updates', or '/extra' in record #10.
dkms.conf: Error! Directive 'DEST_MODULE_LOCATION' does not begin with
'/kernel', '/updates', or '/extra' in record #11.
dkms.conf: Error! Directive 'DEST_MODULE_LOCATION' does not begin with
'/kernel', '/updates', or '/extra' in record #12.
dkms.conf: Error! Directive 'DEST_MODULE_LOCATION' does not begin with
'/kernel', '/updates', or '/extra' in record #13.
dkms.conf: Error! Directive 'DEST_MODULE_LOCATION' does not begin with
'/kernel', '/updates', or '/extra' in record #14.
dkms.conf: Error! Directive 'DEST_MODULE_LOCATION' does not begin with
'/kernel', '/updates', or '/extra' in record #15.
dkms.conf: Error! Directive 'DEST_MODULE_LOCATION' does not begin with
'/kernel', '/updates', or '/extra' in record #16.
...
This happened with multiple lustre-review builds of lustre-dkms and lustre-master builds.
James specific concern/issue, of Lustre dkms RPM on target re-build failure due to missing llite_loop module, is now being tracked as part of LU-8700.
Bruno Faccini (Inactive)
added a comment - James specific concern/issue, of Lustre dkms RPM on target re-build failure due to missing llite_loop module, is now being tracked as part of LU-8700 .
Nathaniel Clark (nathaniel.l.clark@intel.com) uploaded a new patch: http://review.whamcloud.com/22663
Subject: LU-8630 build: Fix definition of KMP_MODDIR
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 909c0230df3ada5b3255bcaf75960951cc1ff81b
Gerrit Updater
added a comment - Nathaniel Clark (nathaniel.l.clark@intel.com) uploaded a new patch: http://review.whamcloud.com/22663
Subject: LU-8630 build: Fix definition of KMP_MODDIR
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 909c0230df3ada5b3255bcaf75960951cc1ff81b
Well it is strange that KMP_MODDIR could have not been correctly set when no configure error has occurred.
So this may come from a more tricky configure issue...
You should have a look to the configure log content in either /var/lib/dkms/lustre/<version>/build/config.log or /var/lib/dkms/lustre/<version>/<kernel-version>/<arch>/log/config.log locations.
Bruno Faccini (Inactive)
added a comment - Well it is strange that KMP_MODDIR could have not been correctly set when no configure error has occurred.
So this may come from a more tricky configure issue...
You should have a look to the configure log content in either /var/lib/dkms/lustre/<version>/build/config.log or /var/lib/dkms/lustre/<version>/<kernel-version>/<arch>/log/config.log locations.
[{"id":-1,"name":"My open issues","jql":"assignee = currentUser() AND resolution = Unresolved order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":true},{"id":-2,"name":"Reported by me","jql":"reporter = currentUser() order by created DESC","isSystem":true,"sharePermissions":[],"requiresLogin":true},{"id":-4,"name":"All issues","jql":"order by created DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-5,"name":"Open issues","jql":"resolution = Unresolved order by priority DESC,updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-9,"name":"Done issues","jql":"statusCategory = Done order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-3,"name":"Viewed recently","jql":"issuekey in issueHistory() order by lastViewed DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-6,"name":"Created recently","jql":"created >= -1w order by created DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-7,"name":"Resolved recently","jql":"resolutiondate >= -1w order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-8,"name":"Updated recently","jql":"updated >= -1w order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false}]
Bug
Critical
James specific concern/issue, of Lustre dkms RPM on target re-build failure due to missing llite_loop module, is now being tracked as part of
LU-8700.