Bug 1405390 - probable 'tar' failure after end of smoke test
Summary: probable 'tar' failure after end of smoke test
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: project-infrastructure
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Nigel Babu
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-16 11:25 UTC by Milind Changire
Modified: 2017-01-31 07:36 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-31 07:36:55 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Milind Changire 2016-12-16 11:25:43 UTC
Smoke failure at https://build.gluster.org/job/smoke/32376/console

There's a:
$ mv '/var/run/gluster/*dump*' /var/log/glusterfs/

before the 'tar' as well.

Please note that single quotes block wildcard expansion.
You might want to instead:

$ find /var/run/gluster -type f -maxdepth 1 -name '*dump*' \
        -exec mv {} /var/log/glusterfs ';'

or just remove the single quotes
or place the wildcard expression in double quotes

Comment 1 Nigel Babu 2017-01-27 10:25:26 UTC
This happens because the /var/log/messages file gets an entry after the tar. But tar exists with status 1. It's okay to ignore this failure. We should probably catch the tar exit status 1 and return that as 0 instead. Or wrap the command with a `|| true`

Comment 2 Nigel Babu 2017-01-31 07:36:55 UTC
This should be fixed up now.


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