Bug 1641021 - gd2-smoke do not seems to clean itself after a crash
Summary: gd2-smoke do not seems to clean itself after a crash
Keywords:
Status: CLOSED CURRENTRELEASE
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: 2018-10-19 12:54 UTC by M. Scherer
Modified: 2019-10-24 10:18 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-07-04 16:42:15 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Description M. Scherer 2018-10-19 12:54:31 UTC 
Description of problem:

During a deploy of ansible config, i found out that ansible was blocked by builder7 and builder33, both who run g2-smoke before being broken.

The tests seems to have failed, and left process running:
https://build.gluster.org/job/gd2-smoke/1958/console
https://build.gluster.org/job/gd2-smoke/1957/console

I will see what is wrong with the builders, but I would at least expect the smoke test to not let old glusterd and etcd process during smoke test.
Comment 1 M. Scherer 2018-10-19 14:48:19 UTC 
Submitted for that:

https://review.gluster.org/#/c/build-jobs/+/21450

From what I see, I think we may also need to unmount the various mounts, not sure of the impact.
Comment 2 Yaniv Kaul 2019-07-01 06:08:12 UTC 
Patch merged. Can we close this?
Comment 3 Michael S. 2019-07-04 16:42:15 UTC 
Yup
Comment 4 M. Scherer 2019-10-24 10:18:39 UTC 
Clear the needinfo
Note You need to log in before you can comment on or make changes to this bug.