Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: ====================== The ansible cleanup in gluster infra doesn't remove the filesystem entries from the /etc/fstab. Version-Release number of selected component (if applicable): ============================================================ gluster-ansible-infra-1.0.1-1.el7rhgs.noarch How reproducible: ================ 100% Steps to Reproduce: ================== 1.Create a playbook that deploys gluster bricks 2.The entries are added to /etc/fstab 3.Now run the gluster ansible cleanup playbook, the filesystem entries still persists Actual results: ============== The filesystem entries still persists Expected results: ================ The entries should be cleaned Additional info: ===============
bipin, I was not able to reproduce this. What was the configuration that you used? Is it possible that the entries you were seeing were from previous run? Which you may not have cleaned up using the reset role. With the attached playbooks I got the expected results.
Created attachment 1491621 [details] Playbooks to create and clean up bricks CLI: $ ansible-playbook -i mount.inv create_brick.yml $ ansible-playbook -i mount.inv cleanup.yml
Sac, Used the latest gluster playbook provided by Gobinda. I again could reproduce the issue. I am attaching the gluster inventory and cleanup file used.
(In reply to bipin from comment #3) > Sac, > > Used the latest gluster playbook provided by Gobinda. I again could > reproduce the issue. I am attaching the gluster inventory and cleanup file > used. Ah! We both were referring to different things. I was referring to gluster.infra role. I’ll talk to Gobinda, this is a bug in the playbook.
(In reply to Sachidananda Urs from comment #6) > (In reply to bipin from comment #3) > > Sac, > > > > Used the latest gluster playbook provided by Gobinda. I again could > > reproduce the issue. I am attaching the gluster inventory and cleanup file > > used. > > Ah! We both were referring to different things. > I was referring to gluster.infra role. I’ll talk to Gobinda, this is a bug > in the playbook. Thanks for the clarification Sac!
(In reply to bipin from comment #7) > (In reply to Sachidananda Urs from comment #6) > > (In reply to bipin from comment #3) > > > Sac, > > > > > > Used the latest gluster playbook provided by Gobinda. I again could > > > reproduce the issue. I am attaching the gluster inventory and cleanup file > > > used. > > > > Ah! We both were referring to different things. > > I was referring to gluster.infra role. I’ll talk to Gobinda, this is a bug > > in the playbook. > > Thanks for the clarification Sac! Commit: https://github.com/gluster/gluster-ansible/pull/53/commits/6f4359b19f774 fixes the issue.
(In reply to Sachidananda Urs from comment #8) > (In reply to bipin from comment #7) > > (In reply to Sachidananda Urs from comment #6) > > > (In reply to bipin from comment #3) > > > > Sac, > > > > > > > > Used the latest gluster playbook provided by Gobinda. I again could > > > > reproduce the issue. I am attaching the gluster inventory and cleanup file > > > > used. > > > > > > Ah! We both were referring to different things. > > > I was referring to gluster.infra role. I’ll talk to Gobinda, this is a bug > > > in the playbook. > > > > Thanks for the clarification Sac! > > Commit: > https://github.com/gluster/gluster-ansible/pull/53/commits/6f4359b19f774 > fixes the issue. As the fix is already merged upstream, moving this bug to MODIFIED
(In reply to SATHEESARAN from comment #9) > (In reply to Sachidananda Urs from comment #8) > > (In reply to bipin from comment #7) > > > (In reply to Sachidananda Urs from comment #6) > > > > (In reply to bipin from comment #3) > > > > > Sac, > > > > > > > > > > Used the latest gluster playbook provided by Gobinda. I again could > > > > > reproduce the issue. I am attaching the gluster inventory and cleanup file > > > > > used. > > > > > > > > Ah! We both were referring to different things. > > > > I was referring to gluster.infra role. I’ll talk to Gobinda, this is a bug > > > > in the playbook. > > > > > > Thanks for the clarification Sac! > > > > Commit: > > https://github.com/gluster/gluster-ansible/pull/53/commits/6f4359b19f774 > > fixes the issue. > > As the fix is already merged upstream, moving this bug to MODIFIED Ignore my comment above. This bug lacking 3 way-acks, can't moved to MODIFIED
Verified with gluster-ansible-1.0.3 Executing gluster cleanup playbook, fstab entries are removed
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:3428