[LU-7976] sles builds severely impacted by recent naming changes

• Type: Bug
• Resolution: Not a Bug
• Priority: Critical
• Severity: 3
• Assignee: Bob Glossman (Inactive)
• Reporter: Bob Glossman (Inactive)

Description

It now appears that the recent landing of the mod for "LU-7699 build: Replace version_tag.pl with LUSTRE-VERSION-GEN" has had bad side effects on build and test for any sles version. Bad effects have been seen in both sles11sp3 and sles11sp4.

One effect is lustre-osd-ldiskfs-mount no longer gets installed automatically. The requires string in lustre-osd-ldiskfs doesn't match the provides string in lustre-osd-ldiskfs-mount.

lustre-osd-ldiskfs-mount provides says:
lustre-osd-ldiskfs-mount = 2.8.51_3_g8062fbb-3.0.101_71_lustre_default

lustre-osd-ldiskfs requires says:
lustre-osd-ldiskfs-mount = 2.8.51_3_g8062fbb

They don't match. Before the landing of LU-7699, they did match.

rpm names now are inconsistent in any sles build. some examples:

lustre-modules-2.8.51_3_g8062fbb-3.0.101_71_lustre_default
kernel-default-3.0.101-71_lustre

lustre rpms have '3.0.101_71_lustre_default" in the name
kernel rpms have "3.0.101-71_lustre" in the name

some or all of these unexpected side effects of the name changes block our normal automatic build/test flow on any SLES versions.

Issue Links

• is related to: LU-7699 Overhaul lustre's versioning