puppet-gluster
puppet-gluster copied to clipboard
Unsorted arrays can cause issues with gluster volume commands
Affected Puppet, Ruby, OS and module versions/distributions
- Puppet: 4.9.4
- Ruby: 2.1.9p490 (2016-03-30 revision 54437)
- Distribution: RHEL 7
- Module version: current master and all previous releases
How to reproduce (e.g Puppet code you use)
Change the order but not the membership of bricks in a volume.
What are you seeing
gluster volume commands fail because there is no real change to the underlying subsystem. The commands run but return an error.
What behaviour did you expect instead
I expect nothing to happen unless the brick membership changes
Output log
Sorry, I lost this when I was debugging.
Any additional information you'd like to impart
I have a simple patch I will submit against this issue as a pull request.