[LU-10858] lustre-initialization-1 lustre-initialization fails for SLES12 SP2 and SP3

• Type: Bug
• Resolution: Fixed
• Priority: Minor
• Fix Version/s: Lustre 2.11.0
• Severity: 3
• Assignee: Bob Glossman (Inactive)
• Reporter: Maloo

Description

This issue was created by maloo for James Nunez <[e-mail]>

This issue relates to the following test suite run: https://testing.hpdd.intel.com/test_sets/199f17d0-3149-11e8-b74b-52540065bddc

lustre-initialization failed with the following error:

'lustre-initialization failed'

<<Please provide additional information about the failure here>>
Looking at the autotest log, we see that the Lustre tests are not installed

2018-03-26T21:56:49 trevis-18vm1: /usr/lib64/lustre/tests/cfg/: No such file or directory
2018-03-26T21:56:49 pdsh@trevis-18vm1: trevis-18vm1: ssh exited with exit code 1
2018-03-26T21:56:49 trevis-18vm3: /usr/lib64/lustre/tests/cfg/: No such file or directory
2018-03-26T21:56:49 pdsh@trevis-18vm1: trevis-18vm3: ssh exited with exit code 1
2018-03-26T21:56:49 trevis-18vm4: /usr/lib64/lustre/tests/cfg/: No such file or directory
2018-03-26T21:56:49 pdsh@trevis-18vm1: trevis-18vm4: ssh exited with exit code 1
2018-03-26T21:56:49 trevis-18vm2: /usr/lib64/lustre/tests/cfg/: No such file or directory
2018-03-26T21:56:49 pdsh@trevis-18vm1: trevis-18vm2: ssh exited with exit code 1

Yet, looking at the node console logs, I don’t see any failure relating to loading RPMS. Looking at the console logs for all the nodes, they all end with

Welcome to SUSE Linux Enterprise Server 12 SP3  (x86_64) - Kernel 4.4.114-94.11-default (ttyS0).


trevis-18vm2 login: [   80.209414] random: nonblocking pool is initialized

<ConMan> Console [trevis-18vm2] disconnected from <trevis-18:6001> at 03-26 22:56.

This failure started with master build #3731.

Another test session that failed in this way is at
https://testing.hpdd.intel.com/test_sessions/fb84aaa9-888e-4d17-9a76-1cfd67d415aa

VVVVVVV DO NOT REMOVE LINES BELOW, Added by Maloo for auto-association VVVVVVV
lustre-initialization-1 lustre-initialization - 'lustre-initialization failed'

Issue Links

• is related to: LU-10556 lustre client rebuild not building lnetctl

Comments

[James A Simmons]

Its about pulling in the right rpms when you install a lustre binary rpm. Currently you can install rpm a prepackage lustre rpm on a system that could be lacking libyaml and/or libzlib. In that case you think it installed right but then when you go to run it you see a nice crash. Using yum you can grab libyaml and zlib when installing lustre binary rpm with this patch.

[Bob Glossman (Inactive)]

-devel .rpms are fine. both libyaml-devel & zlib-devel exist in both RHEL and SLES.
I question the strategy of enforcing this in the .spec file though.
I thought there are already autoconf tests to check for and enforce the right build environment in these cases.

[Jian Yu]

Its still zlib-devel tho?

Yes. It's still zlib-devel.

[Bob Glossman (Inactive)]

the zlib dependency isn't a problem. the SLES .rpm libz1 has a Provides for the name "zlib"

[James A Simmons]

Oh crap. At least it is a easy fix. Its still zlib-devel tho?

[Jian Yu]

Yes, James.
I just found 'zlib' package was named as 'libz1' on SLES 12.

[Bob Glossman (Inactive)]

yes, this is a problem with naming conventions.
In RHEL the user level libyaml .rpm is named "libyaml" and Provides the symbol libyaml
in SLES the user level libyaml .rpm is named "libyaml-0-2" and has no Provides of the name "libyaml". It only Provides the symbol "libyaml-0-2"

would suggest removing the dependency this mod just added.

[James A Simmons]

Really? That is just adding in build requirements when building from the lustre source rpms. Are those rpms named differently on SLES12SP4?

[Peter Jones]

Bob

Can you please investigate?

Peter

[James Nunez (Inactive)]

Test to see if reverting LU-10556 patch https://review.whamcloud.com/#/c/31710/ will fix this issue.

Revert patch at https://review.whamcloud.com/#/c/31800/