https://bugzilla.redhat.com/show_bug.cgi?id=1555315
--- Comment #3 from Michael Scherer ---
So, if we do not need them, I can safely remove this then.
--
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
https://bugzilla.redhat.com/show_bug.cgi?id=1555315
Michael Scherer changed:
What|Removed |Added
Summary|ansible role to deploy |ansible role to deploy
https://bugzilla.redhat.com/show_bug.cgi?id=1555315
Nigel Babu changed:
What|Removed |Added
CC||nig...@redhat.com
--- Comment #2 from Ni
https://bugzilla.redhat.com/show_bug.cgi?id=1555315
--- Comment #1 from Niels de Vos ---
There should be no need to start rpc.statd on builders. Gluster/NFS will try to
start rpc.statd directly (without init/systemd). The cleanup of the tests kill
rpc.statd in preparation for the next test.
--
https://bugzilla.redhat.com/show_bug.cgi?id=1555315
Bug ID: 1555315
Summary: ansible role to deploy jnkins_builder sometime fail
Product: GlusterFS
Version: mainline
Component: project-infrastructure
Assignee: b...@gluster.org