[lustre-discuss] rpmbuild error with lustre-2.8.0-3.10.0_327.3.1.el7_lustre.x86_64.x86_64.src.rpm

[Riccardo Veraldi]

The error indeed does exist. It hapened to me too.
For my own Lustre server needs I just fixed it commenting out  two lines 
in the .spec file since I am not running Lustre in High Avilability.



On 29/06/16 11:41, Christopher J. Morrone wrote:
> On 06/29/2016 10:36 AM, Martin Hecht wrote:
>> Hello,
>>
>> I have just seen that you managed to mount with a different kernel, but
>> let me come back to this error when building your own rpms for a
>> specific kernel.
>>
>> Independent if you use it or not, I believe on lustre servers you need
>> to have heartbeat installed nowadays. This is not installed by default
>> on a standard centos server, and it's a new requirement to build the
>> rpms since some 2.x release (it was optional before, and actually using
>> it is still optional). This requirement for building and installing the
>> server rpms is not mentioned in all tutorials and unfortunately the
>> absence of heartbeat is not properly detected by the configure system.
> I'm not sure that is the case.  At LLNL we run our Lustre builds through
> two different mock-based build farms.  Mock creates a build environment
> with only a minimal set of rpms installed, and then the only other
> packages that are included are those that are explicitly named by
> BuildRequires in the spec file.  I don't see anything that requires
> heartbeat, even in our local much-hacked spec file.  And we build just
> fine with the heartbeat scripts included.
>
> But in any event a ticket would be good to open a ticket on this with
> fuller logs of the build included.  Something likely went wrong earlier
> in the build process for the Lustre.ha_v2 script not to have been
> installed (and therefore the .../etc/ha.d/resource.d directory to exist).
>
> Opening a ticket on this and including the full log of the failed build
> would be good.
>
>> It would be better to fail earlier, during configure, with a clear error
>> message, rather than the error during make which you have seen here (has
>> anybody filed a lustre bug about this yet?)
>>
>> If you  aim to build lustre client rpms only, you can use the rpmbuild
>> option --without servers to work around this problem, but If I didn't
>> miss anything in the discussion before you are trying to build the
>> server rpms with zfs, so --without servers is not suitable for you, but
>> mentioning it here might be helpful for others who run into the same
>> trouble.
>>
>> Martin
>>
>> On 06/28/2016 04:55 PM, Yu Chen wrote:
>>> Hello,
>>>
>>> Trying to follow Christopher's advice to rebuild the lustre from src.rpm.
>>> However, got into this error:
>>>
>>> ...........
>>>
>>> make[3]: Nothing to be done for `install-data-am'.
>>>
>>> make[3]: Leaving directory `/home/build/rpmbuild/BUILD/lustre-2.8.0/lustre'
>>>
>>> make[2]: Leaving directory `/home/build/rpmbuild/BUILD/lustre-2.8.0/lustre'
>>>
>>> make[1]: Leaving directory `/home/build/rpmbuild/BUILD/lustre-2.8.0/lustre'
>>>
>>> + :
>>>
>>> + ln -s Lustre.ha_v2
>>> /home/build/rpmbuild/BUILDROOT/lustre-2.8.0-3.10.0_327.3.1.el7_lustre.x86_64.x86_64/etc/ha.d/resource.d/Lustre
>>>
>>> ln: failed to create symbolic link
>>> '/home/build/rpmbuild/BUILDROOT/lustre-2.8.0-3.10.0_327.3.1.el7_lustre.x86_64.x86_64/etc/ha.d/resource.d/Lustre':
>>> No such file or directory
>>>
>>> error: Bad exit status from /var/tmp/rpm-tmp.Rhg32s (%install)
>>> ..........
>>>
>>>
>>> There seems someone posted to the list before about this error too, and no
>>> answers, wondering if anybody has some solutions now?
>>>
>>> Thanks in advance!
>>>
>>> Regards,
>>>
>>> Chen
>>>
>>
>>
>>
>> _______________________________________________
>> lustre-discuss mailing list
>> lustre-discuss at lists.lustre.org
>> http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
>>
> _______________________________________________
> lustre-discuss mailing list
> lustre-discuss at lists.lustre.org
> http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org