Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Broken facts on gluster3.2 #56

Closed
2 tasks done
bastelfreak opened this issue Jun 20, 2016 · 3 comments
Closed
2 tasks done

Broken facts on gluster3.2 #56

bastelfreak opened this issue Jun 20, 2016 · 3 comments
Labels
bug Something isn't working

Comments

@bastelfreak
Copy link
Member

Please check the following items before submitting an issue -- thank you!

Nnote that this project is released with a Contributor Code of Conduct.
By participating in this project you agree to abide by its terms.
Contributor Code of Conduct.

  • There is no existing issue or PR that addresses this problem

Optional, but makes our lives much easier:

  • The issue affects the latest release of this module at the time of
    submission

Affected Puppet, Ruby, OS and module versions/distributions

Puppet3.8.7, Ruby1.8.3, CentOS6

What are you seeing

# facter -p
sh: -c: line 0: syntax error near unexpected token `('
sh: -c: line 0: `/usr/sbin/gluster volume info (position'
sh: -c: line 0: syntax error near unexpected token `)'
sh: -c: line 0: `/usr/sbin/gluster volume info 1)'

What behaviour did you expect instead

seeing cluster facts

How did this behaviour get triggered

fact expected nonexistent output to parse

Output log

Any additional information you'd like to impart

the fact does gluster volume list. This command isn't available on old gluster versions (3.2 in my case). The output is:

# gluster volume list
unrecognized word: list (position 1)
@bastelfreak bastelfreak added the bug Something isn't working label Jun 20, 2016
@QueerCodingGirl
Copy link
Contributor

gluster volume info all is available in gluster version 3.2

QueerCodingGirl added a commit to QueerCodingGirl/puppet-gluster that referenced this issue Aug 16, 2016
@sammcj
Copy link
Contributor

sammcj commented Oct 30, 2017

I would suggest upgrading gluster to a modern version as 3.2 is very old - in fact it's so old it doesn't even show on gluster's list of deprecated versions anymore: https://www.gluster.org/release-schedule/

CentOS 6 is also getting very long in the tooth, so perhaps CentOS 7.x would be a sensible upgrade for you.

@ekohl
Copy link
Member

ekohl commented Dec 4, 2018

Agreed. Closing due to its age.

@ekohl ekohl closed this as completed Dec 4, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants