Bug 1464724

Summary:	Generate a squashfs with timestamp
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Yuval Turgeman <yturgema>
Component:	ovirt-node-ng	Assignee:	Yuval Turgeman <yturgema>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Qin Yuan <qiyuan>
Severity:	medium	Docs Contact:
Priority:	low
Version:	unspecified	CC:	apinnick, cshao, dfediuck, eedri, mgoldboi, rbarry, yturgema
Target Milestone:	ovirt-4.1.4	Keywords:	ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:	The file name of ovirt-node-ng-image-<timestamp>.squashfs.img now contains a timestamp, which enables versioning.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-02 07:05:41 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Node	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Yuval Turgeman 2017-06-25 05:53:48 UTC

Description of problem:
Today, the build process for ovirt-node-ng creates a file called 'ovirt-node-ng-image.squashfs.img' without a reference for any kind of versioning, making it hard to understand which version is being tested in CI.

Version-Release number of selected component (if applicable):
4.1/Master

How reproducible:
Build the ovirt-node-ng project

Steps to Reproduce:
1. make squashfs


Actual results:
ovirt-node-ng-image.squashfs.img is created

Expected results:
ovirt-node-ng-image-<timestamp>.squashfs.img

Comment 1 cshao 2017-06-26 02:59:47 UTC

Yuval,

QE is not familiar with make squashfs process, so could you help to verify this bug once it is fixed? If you can, I will set the QA Contact to you.

Thanks.

Comment 2 Yuval Turgeman 2017-06-26 06:01:43 UTC

The squashfs is used directly in CI in jenkins, if you look at the artifacts for the ovirt-node-ng job, you'll see a squashfs there without a timestamp.

Comment 3 Avital Pinnick 2017-07-13 11:55:59 UTC

Doc Text added and RDT flag set to '+.'

Comment 5 Qin Yuan 2017-07-14 05:51:49 UTC

Checked the artifacts for the ovirt-node-ng job:

1. In "Project ovirt-node-ng_master_build-artifacts-el7-x86_64", the last successful squashfs is "ovirt-node-ng-image-20170714.squashfs.img".

2. In "Project ovirt-node-ng_ovirt-4.1_build-artifacts-el7-x86_64", the last successful squashfs is "ovirt-node-ng-image-20170714.squashfs.img".

3. In "Project ovirt-node-ng_ovirt-4.1-pre_build-artifacts-el7-x86_64", the last successful squashfs is "ovirt-node-ng-image-20170714.squashfs.img".

4. In "Project ovirt-node-ng_ovirt-4.1-snapshot_build-artifacts-el7-x86_64", the last successful squashfs is "ovirt-node-ng-image-20170714.squashfs.img".

The name of squashfs was changed to ovirt-node-ng-image-<timestamp>.squashfs.img, just as expected, so the bug is verified.