Jira (FACT-548) fact not showing up when run through puppet agent
Title: Message Title Daniele Sluijters updated an issue Facter / FACT-548 fact not showing up when run through puppet agent Change By: Daniele Sluijters Environment: DebianSqueezeandWheezyPuppet3.6.2Facter2.0.2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-548) fact not showing up when run through puppet agent
Title: Message Title
Daniele Sluijters created an issue
Facter / FACT-548
fact not showing up when run through puppet agent
Issue Type:
Bug
Assignee:
Eric Sorenson
Created:
12/Jun/14 2:32 AM
Priority:
Normal
Reporter:
Daniele Sluijters
I have no clue if this is a Facter bug or a Puppet thing. I have a custom Fact which works when I run it through FACTERLIB=/path/to/fact facter and also shows up when distributed through Puppet and run with facter -p and even works when manually kicking puppet agent -t.
However, when relying simply on the agent the fact doesn't work (and because of that disappears from PuppetDB too).
The fact:
Unable to find source-code formatter for language: ruby. Available languages are: actionscript, html, java, _javascript_, none, sql, xhtml, xml
Facter.add(:mysql_type) do
confine :kernel = :linux
mysql_output = Facter::Core::Execution.exec('/usr/bin/pt-mysql-summary --defaults-file=/etc/mysql/debian.cnf --sleep 0 2/dev/null')
setcode do
if mysql_output.include?('Percona XtraDB Cluster (GPL)')
'node'
elsif mysql_output.include?('Is a slave, has 0 slaves connected')
'slave'
elsif mysql_output.include?('Is a slave')
'master'
elsif mysql_output.include?('Is not a slave')
'master'
end
end
end
This is probably the most horrible way to parse replication information into something useful but for all intents and purposes seems to work, except that Puppet just doesn't want it.
I've restarted the agents too, no dice.
Jira (FACT-548) fact not showing up when run through puppet agent
Title: Message Title
Josh Cooper commented on an issue
Re: fact not showing up when run through puppet agent
Daniele Sluijters I don't know if this is the issue, but the fact is executing the pt-mysql-summary command outside of the setcode block. This will cause the command to be executed on every platform, not just the one you confined it to. If you move the command execution into the setcode block, does the issue go away?
Add Comment
Facter / FACT-548
fact not showing up when run through puppet agent
I have no clue if this is a Facter bug or a Puppet thing. I have a custom Fact which works when I run it through {{FACTERLIB=/path/to/fact facter}} and also shows up when distributed through Puppet and run with {{facter -p}} and even works when manually kicking {{puppet agent -t}}. However, when relying simply on the agent the fact doesn't work (and be...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group,
Jira (FACT-548) fact not showing up when run through puppet agent
Title: Message Title
Daniele Sluijters commented on an issue
Re: fact not showing up when run through puppet agent
Josh Cooper The confine doesn't seem to be the issue. We only have machines that match :kernel = :linux, I tried :kernel = 'Linux' too but no dice.
If the confine where the issue I would've expected facter -p, puppet agent -t and the FACTERLIB=. facter to have failed too, but they work just fine. It's just the agent as-a-daemon that seems to be having issues with it.
Add Comment
Facter / FACT-548
fact not showing up when run through puppet agent
I have no clue if this is a Facter bug or a Puppet thing. I have a custom Fact which works when I run it through {{FACTERLIB=/path/to/fact facter}} and also shows up when distributed through Puppet and run with {{facter -p}} and even works when manually kicking {{puppet agent -t}}. However, when relying simply on the agent the fact doesn't work (and be...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving
