[LU-474] fix release build issues

• Status: Resolved
• Project: Lustre
• Affects Version/s: Lustre 1.8.7
• Type: Bug
• Priority: Minor
• Reporter: Brian Murrell (Inactive)
• Assignee: WC Triage
• Resolution: Fixed
• Severity: 3

Description

We need to fix release builds so that kernels don't have git hashes in their version. This is done because a kernel is reused from a previous not-on-tag build. I guess release builds should force a kernel build.

Need to allow the -wc1 and -WC1 monikers in tags.

Issue Links

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

Comments

[Build Master (Inactive)]

Integrated in lustre-dev » x86_64,client,el5,inkernel #340
LU-474 build: document the build release versions (Revision 031ac0dee72ad07599905122a852d20cc6127b98)

Result = SUCCESS
Mikhail Pershin : 031ac0dee72ad07599905122a852d20cc6127b98
Files :

• lustre/doc/VERSIONING

[Build Master (Inactive)]

Integrated in lustre-dev » i686,client,el6,inkernel #340
LU-474 build: document the build release versions (Revision 031ac0dee72ad07599905122a852d20cc6127b98)

Result = SUCCESS
Mikhail Pershin : 031ac0dee72ad07599905122a852d20cc6127b98
Files :

• lustre/doc/VERSIONING

[Build Master (Inactive)]

Integrated in lustre-dev » i686,server,el5,inkernel #340
LU-474 build: document the build release versions (Revision 031ac0dee72ad07599905122a852d20cc6127b98)

Result = SUCCESS
Mikhail Pershin : 031ac0dee72ad07599905122a852d20cc6127b98
Files :

• lustre/doc/VERSIONING

[Build Master (Inactive)]

Integrated in lustre-dev » x86_64,server,el6,inkernel #340
LU-474 build: document the build release versions (Revision 031ac0dee72ad07599905122a852d20cc6127b98)

Result = SUCCESS
Mikhail Pershin : 031ac0dee72ad07599905122a852d20cc6127b98
Files :

• lustre/doc/VERSIONING

[Build Master (Inactive)]

Integrated in lustre-dev » i686,client,el5,inkernel #340
LU-474 build: document the build release versions (Revision 031ac0dee72ad07599905122a852d20cc6127b98)

Result = SUCCESS
Mikhail Pershin : 031ac0dee72ad07599905122a852d20cc6127b98
Files :

• lustre/doc/VERSIONING

[Build Master (Inactive)]

Integrated in lustre-dev » x86_64,server,el5,inkernel #340
LU-474 build: document the build release versions (Revision 031ac0dee72ad07599905122a852d20cc6127b98)

Result = SUCCESS
Mikhail Pershin : 031ac0dee72ad07599905122a852d20cc6127b98
Files :

• lustre/doc/VERSIONING

[Build Master (Inactive)]

Integrated in lustre-dev » x86_64,client,el6,inkernel #340
LU-474 build: document the build release versions (Revision 031ac0dee72ad07599905122a852d20cc6127b98)

Result = SUCCESS
Mikhail Pershin : 031ac0dee72ad07599905122a852d20cc6127b98
Files :

• lustre/doc/VERSIONING

[Jodi Levi (Inactive)]

Please let me know if there is more work needed on this ticket and I will reopen.

[Brian Murrell (Inactive)]

How do I see what was landed? The hash URLs above all don't lead to anything.

[Brian Murrell (Inactive)]

How do I see what was landed? The hash URLs above all don't lead to anything.

Can anyone answer this question? I'm trying to answer Jodi's previous question about whether any more work needs doing here.

[Jodi Levi (Inactive)]

Try going here to see the patches that have landed for LU-474.

http://review.whamcloud.com/#q,status:merged++message:LU-474,n,z

[Brian Murrell (Inactive)]

OK. So given the review pointers you provided I see only an update to the lustre/doc/VERSIONING file and nothing else. Updating this file does nothing at all to solve the problem this bug is open for. The problem this bug describes requires a build code fix.

[Andreas Dilger]

It looks like this was fixed with patch http://review.whamcloud.com/18107 "LU-7699 build: Replace version_tag.pl with LUSTRE-VERSION-GEN"