Details
-
Improvement
-
Resolution: Fixed
-
Major
-
Lustre 2.1.0, Lustre 1.8.6
-
None
-
Test Infrastructure
-
9078
Description
Problem: Currently in Maloo it's not possible to filter by branch and so the value of the results is not maximized. Maloo cannot do this filtering because the information is not supplied by the yml results.
Solution: Add 2 entries to the node . yml files beneath the lbat entries. These entries should be marked branch and revision and take the following format. ** Marks the new entries
os_distribution: CentOS release 5.6
lustre_version: jenkins-g51b658e-PRISTINE-2.6.18-238.9.1.el5
lustre_build: http://build.whamcloud.com/job/lustre-reviews/626
-
- lustre_branch: master
- lustre_revision: 30a8e418ef966c8eb5b4ade9166bd1751233e5e4
kernel_version: 2.6.18-238.9.1.el5
Updates will be required to Maloo to interpret these new fields, this changes are covered in TT-119
Attachments
Issue Links
- Trackbacks
-
Lustre 1.8.x known issues tracker While testing against Lustre b18 branch, we would hit known bugs which were already reported in Lustre Bugzilla https://bugzilla.lustre.org/. In order to move away from relying on Bugzilla, we would create a JIRA
-
Changelog 1.8 Changes from version 1.8.7wc1 to version 1.8.8wc1 Server support for kernels: 2.6.18308.4.1.el5 (RHEL5) Client support for unpatched kernels: 2.6.18308.4.1.el5 (RHEL5) 2.6.32220.13.1.el6 (RHEL6) Recommended e2fsprogs version: 1.41.90....