On 04/11/16 14:32, Peter Huene wrote:
This looks like it may be coming from a custom fact that is overriding
the expected built-in.
Could you run 'facter -d -p mountpoints' and see if the output mentions
discovery of a mountpoints.rb or a change in fact value?
Thanks!
You're exactly right. T
On Nov 4, 2016 3:04 AM, "Jonathan Gazeley"
wrote:
>
> Thanks for your response. Output of those commands follows:
>
> [jg4461@puppet4-prod ~]$ facter -p mountpoints
>
/,/dev,/sys/kernel/security,/sys/fs/cgroup/systemd,/sys/fs/pstore,/sys/kernel/config,/sys/fs/selinux,/dev/mqueue,/dev/hugepages,/sy
Thanks for your response. Output of those commands follows:
[jg4461@puppet4-prod ~]$ facter -p mountpoints
/,/dev,/sys/kernel/security,/sys/fs/cgroup/systemd,/sys/fs/pstore,/sys/kernel/config,/sys/fs/selinux,/dev/mqueue,/dev/hugepages,/sys/kernel/debug,/boot
[jg4461@puppet4-prod ~]$ mount
sysfs
Hi Jonathan -
Can you run facter -p (interested in what mountpoints is) and `mount`, and
paste the output.
Also can you run:
puppet apply -e 'notify { "${::mountpoints}": }; notify {
"${::mountpoints["/"]}": }'
Thanks,
-aj
On Thursday, November 3, 2016 at 2:52:35 AM UTC-7, Jonathan Gazele
