Details
-
Bug
-
Resolution: Fixed
-
Critical
-
Lustre 2.9.0
-
None
-
3
-
9223372036854775807
Description
I don't know when it broke, but currently server builds on sles12 generate .rpm packages that can't install without --nodeps or --force. The problem appears to be with the Provides and Requires strings in the various kmp packages. They don't match.
I'm guessing it's been broken for a while and just hasn't been noticed. Maybe not noticed because we seldom test with sles12 server builds or maybe our test framework installs with --force options or something.
Here is what I see in packages from a recent sles12 server build in lustre-reviews:
rpm -q --provides -p lustre-kmp-default-2.8.56_34_gf7472b3_k3.12.60_52.54-1.x86_64.rpm | grep lustre-kmp
lustre-kmp = 2.8.56_34_gf7472b3
lustre-kmp = 2.8.56_34_gf7472b3_k3.12.60_52.54
rpm -q --requires -p lustre-osd-ldiskfs-kmp-default-2.8.56_34_gf7472b3_k3.12.60_52.54-1.x86_64.rpm | grep lustre-kmp
lustre-kmp = 2.8.56_34_gf7472b3_k3.12.59_60.41_lustre
Note the Requires string has '41_lustre' on the end and the Provides string has '_52.54'. They don't match at all.
I'm guessing this has something to do with one of the many recent changes in the lustre.spec.in file.
Attachments
Issue Links
- is related to
-
LU-5614 use %kernel_module_package for weak-updates
- Closed