https://bugzilla.redhat.com/show_bug.cgi?id=1641021
Bug ID: 1641021
Summary: gd2-smoke do not seems to clean itself after a crash
Product: GlusterFS
Version: mainline
Component: project-infrastructure
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected], [email protected]
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.
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug
https://bugzilla.redhat.com/token.cgi?t=uxeejNhyTC&a=cc_unsubscribe
_______________________________________________
Gluster-infra mailing list
[email protected]
https://lists.gluster.org/mailman/listinfo/gluster-infra
