Details
-
Bug
-
Resolution: Fixed
-
Minor
-
Lustre 2.0.0, Lustre 2.1.2, Lustre 2.1.3, Lustre 1.8.8, Lustre 1.8.6
-
None
-
Old Lustre Version: 1.8.6-wc1
Lustre Build: http://newbuild.whamcloud.com/job/lustre-b1_8/100/
New Lustre Version: 2.0.66.0
Lustre Build: http://newbuild.whamcloud.com/job/lustre-master/228/
Clean upgrading (Lustre servers and clients were upgraded all at once) from Lustre 1.8.6-wc1 to Lustre 2.0.66.0 under the following configuration:
OSS1: RHEL5/x86_64
OSS2: RHEL5/x86_64
MDS: RHEL5/x86_64
Client1: RHEL6/x86_64
Client2: RHEL5/x86_64
Old Lustre Version: 1.8.6-wc1 Lustre Build: http://newbuild.whamcloud.com/job/lustre-b1_8/100/ New Lustre Version: 2.0.66.0 Lustre Build: http://newbuild.whamcloud.com/job/lustre-master/228/ Clean upgrading (Lustre servers and clients were upgraded all at once) from Lustre 1.8.6-wc1 to Lustre 2.0.66.0 under the following configuration: OSS1: RHEL5/x86_64 OSS2: RHEL5/x86_64 MDS: RHEL5/x86_64 Client1: RHEL6/x86_64 Client2: RHEL5/x86_64
-
3
-
23,339
-
4234
Description
After the upgrading, sanity test 132 failed on Lustre 2.0.66.0 as follows:
== sanity test 132: som avoids glimpse rpc == 03:17:56 (1312885076) ====> SOM is disabled, 0 glimpse RPC occured sanity test_132: @@@@@@ FAIL: some glimpse RPC is expected
Please refer to the Maloo report for more logs: https://maloo.whamcloud.com/test_sets/a570d34e-c278-11e0-8bdf-52540025f9af
This is an known issue: bug 23339.
Attachments
Issue Links
- Trackbacks
-
Lustre 2.1.2 release testing tracker Lustre 2.1.2 RC2 Tag: v212RC2 Build:
-
Lustre 2.1.3 release testing tracker Lustre 2.1.3 RC1 Tag: v213RC1 Build: