-
-
Notifications
You must be signed in to change notification settings - Fork 75
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
"gluster peer probe" getting called on each puppet run #124
Comments
netdata-be
pushed a commit
to nucleus-be/puppet-gluster
that referenced
this issue
Jun 29, 2017
When having multiple interfaces on a gluster cluster. It is now possible to probe each interface and facter will return the other names as well. Otherwise fater will probe each run Fixes voxpupuli#124
mdurell
added a commit
to mdurell/puppet-gluster
that referenced
this issue
Dec 28, 2017
Resolves upstream issue voxpupuli#124
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Affected Puppet, Ruby, OS and module versions/distributions
How to reproduce (e.g Puppet code you use)
Exported resources enabled.
What are you seeing
The first gluster node (test-gluster1.local in this example) comes up fine. The second node (test-gluster2.local) comes up and probes test-gluster1.local as expected. test-gluster1.local then completes the handshaking by probing test-gluster2.local.
However, test-gluster2.local seems to believe it needs to continue probing test-gluster1.local on each puppet run:
2017-06-27 15:22:19 +0100 /Stage[main]/Gluster/Gluster::Peer[test-gluster1.local]/Exec[gluster peer probe test-gluster1.local]/returns (notice): executed successfully
On test-gluster2.local, if you run
facter --puppet gluster_peer_list
It shows the ip address of test-gluster1.local rather than the hostname, this is what I believe is causing the peer probe to be called each time as this does not match the gluster::peer resource title in puppetdb
Looking at the code for the gluster_peer_list fact, it determines the peers from the value of Hostname: in the
gluster peer status
command. If you run this command though, the correct hostname appears under "Other names:"What behaviour did you expect instead
Puppet run without any changes.
The text was updated successfully, but these errors were encountered: