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
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.
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.
Doc Text added and RDT flag set to '+.'
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.