Bug 1677174 - Smoke test are failing for devrpm-el6 and strfmt_errors
Summary: Smoke test are failing for devrpm-el6 and strfmt_errors
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: GlusterFS
Classification: Community
Component: project-infrastructure
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-02-14 08:23 UTC by Ashish Pandey
Modified: 2019-02-14 11:44 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-02-14 11:44:00 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Ashish Pandey 2019-02-14 08:23:18 UTC
Description of problem:
Smoke tests are failing for the patch https://review.gluster.org/#/c/glusterfs/+/22125/ again and again.

Failures are  in 
https://build.gluster.org/job/strfmt_errors/16976/ : FAILURE

https://build.gluster.org/job/devrpm-el6/14789/ : FAILURE

Console logs are -

12:52:42 INFO: Cleaning up build root ('cleanup_on_failure=True')
12:52:42 Start: clean chroot
12:52:49 Finish: clean chroot
12:52:49 ERROR: Command failed: 
12:52:49  # bash --login -c /usr/bin/rpmbuild -bb --target x86_64 --nodeps /builddir/build/SPECS/glusterfs.spec
12:52:49 
12:52:49 Build step 'Execute shell' marked build as failure
12:52:49 Archiving artifacts
12:52:49 Performing Post build task...
12:52:49 Could not match :Build was aborted  : False


I was able to build rpm's on centos VM's.




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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 M. Scherer 2019-02-14 11:07:49 UTC
The log indicate this fail because the build fail: 
https://build.gluster.org/job/devrpm-el6/14789/artifact/RPMS/el6/x86_64/build.log

BUILDSTDERR: error: File not found: /builddir/build/BUILDROOT/glusterfs-7dev-0.19.gite6ec282.el6.x86_64/usr/lib64/glusterfs/7dev/xlator/features/thin-arbiter.so
BUILDSTDERR: error: File not found: /builddir/build/BUILDROOT/glusterfs-7dev-0.19.gite6ec282.el6.x86_64/etc/init.d/gluster-ta-volume
BUILDSTDERR:     File not found: /builddir/build/BUILDROOT/glusterfs-7dev-0.19.gite6ec282.el6.x86_64/usr/lib64/glusterfs/7dev/xlator/features/thin-arbiter.so
BUILDSTDERR:     File not found: /builddir/build/BUILDROOT/glusterfs-7dev-0.19.gite6ec282.el6.x86_64/etc/init.d/gluster-ta-volume

I suspect the problem is in the patch rather than the build system, unless proven otherwise

Comment 2 Ashish Pandey 2019-02-14 11:17:27 UTC
I will try to find out if there is anything wrong with my patch.
However, in the mean time, is it possible to execute the build on any other machine if we have slightest doubt on machine.

Comment 3 M. Scherer 2019-02-14 11:25:55 UTC
We have the same erroer on the strfmt error job, which got executed on others nodes:

https://build.gluster.org/job/strfmt_errors/16974/ builder28
https://build.gluster.org/job/strfmt_errors/16976/ builder17

The job also work fine for other patchs, so I strongly think that a error message speaking of thin-arbitrer, when the patch do change something related to thin-arbitrer, that show a error on 4 differents builders who work fine for others patchs is strongly related to the patch.

Does it work when you try to build in mock locally for you ?

Comment 4 Deepshikha khandelwal 2019-02-14 11:32:08 UTC
As per your mail, I retriggered the build today afternoon and the same issue occurred on builder15 & builder28. So it's most likely the problem of this patch.

Comment 5 M. Scherer 2019-02-14 11:43:44 UTC
So, I found the issue, cf comment on the review, so closing this one.


Note You need to log in before you can comment on or make changes to this bug.