[LU-1143] release package building should not re-use kernel Created: 26/Feb/12  Updated: 29/May/17  Resolved: 29/May/17

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: Lustre 2.2.0, Lustre 2.1.2, Lustre 1.8.7
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Brian Murrell (Inactive) Assignee: WC Triage
Resolution: Cannot Reproduce Votes: 0
Labels: None

Story Points: 1
Severity: 3
Rank (Obsolete): 10639

 Description   

Currently when we build release [candidate] releases, the kernel could be reused from a previous build. This has no operational impact but it does mean that package versioning looks messy. For example, from the 2.1.1 release:

kernel-2.6.32-220.el6_lustre.g4554b65.x86_64.rpm

The "g4554b65" in the version is because for the release a kernel was reused from a previous non-RC build which is what caused the git hash to be included in the version. Had a new kernel build for the RC release been forced it would not have had the git hash in it because it would have been built from a tagged release.



 Comments   
Comment by Andreas Dilger [ 29/May/17 ]

Close old ticket.

Generated at Sat Feb 10 01:13:53 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.