Hello,
I'm unable to reproduce this behavior. To see about which mounts Puppet knows
about, use 'puppet resource mount' or 'puppet resource mount
/pub/fedora/site/candidates/30'
# puppet resource mount /mnt/home
mount { '/mnt/home':
ensure => 'mounted',
device => '/home',
dump => '0',
fstype => 'none',
options => 'rw,bind,seclabel,relatime,errors=remount-ro',
pass => '0',
target => '/etc/fstab',
}
-----Original message-----
From: Michael Watters <watter...@gmail.com>
Sent: Friday 7th June 2019 16:02
To: Puppet Users <puppet-users@googlegroups.com>
Subject: [Puppet Users] Puppet does not recognize bind mounts
I'm having an issue with puppet repeatedly attempting to mount resources which
are configured as bind mounts on one of my nodes. Here is a copy of the
relevant lines from my manifest.
$koji_fedora_releases = ['28', '29', '30']
$koji_fedora_releases.each |$release| {
['released', 'testing'].each |$tag| {
mount { "/pub/fedora/org/${tag}/${release}":
ensure => mounted,
device =>
"/storage/projects/koji/repos-dist/aos-${release}-${tag}/latest",
fstype => 'none',
options => 'rw,bind',
}
}
}
The agent is able to successfully apply these resources however it attempts to
remount the directories every time that puppet runs. For example, here is the
output on the agent side.
Notice:
/Stage[main]/Site::Fileserver01/Mount[/pub/fedora/site/candidates/30]/ensure:
current_value unmounted, should be mounted (noop)
Info: /Stage[main]/Site::Fileserver01/Mount[/pub/fedora/site/candidates/30]:
Scheduling refresh of Mount[/pub/fedora/site/candidates/30]
Notice: /Stage[main]/Site::Fileserver01/Mount[/pub/fedora/site/candidates/30]:
Would have triggered 'refresh' from 1 events
Info: /Stage[main]/Site::Fileserver01/Mount[/pub/fedora/site/candidates/30]:
Scheduling refresh of Mount[/pub/fedora/site/candidates/30]
Notice:
/Stage[main]/Site::Fileserver01/Mount[/pub/fedora/site/released/30]/ensure:
current_value unmounted, should be mounted (noop)
Info: /Stage[main]/Site::Fileserver01/Mount[/pub/fedora/site/released/30]:
Scheduling refresh of Mount[/pub/fedora/site/released/30]
Notice: /Stage[main]/Site::Fileserver01/Mount[/pub/fedora/site/released/30]:
Would have triggered 'refresh' from 1 events
Info: /Stage[main]/Site::Fileserver01/Mount[/pub/fedora/site/released/30]:
Scheduling refresh of Mount[/pub/fedora/site/released/30]
Notice:
/Stage[main]/Site::Fileserver01/Mount[/pub/fedora/site/testing/30]/ensure:
current_value unmounted, should be mounted (noop)
Info: /Stage[main]/Site::Fileserver01/Mount[/pub/fedora/site/testing/30]:
Scheduling refresh of Mount[/pub/fedora/site/testing/30]
Notice: /Stage[main]/Site::Fileserver01/Mount[/pub/fedora/site/testing/30]:
Would have triggered 'refresh' from 1 events
Info: /Stage[main]/Site::Fileserver01/Mount[/pub/fedora/site/testing/30]:
Scheduling refresh of Mount[/pub/fedora/site/testing/30]
These lines are repeated for each bind mount resource.
How does puppet actually verify that a device is mounted? The source
directories *are* mounted and I'm able to access data in each directory without
an issue.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to puppet-users+unsubscr...@googlegroups.com
<mailto:puppet-users+unsubscr...@googlegroups.com> .
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/198a335b-9582-4053-ae52-50cc15bf02b1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/zarafa.5cff66f0.7f7e.52b6d4cd1fd0327d%40anjie.dontpanic.nl.
For more options, visit https://groups.google.com/d/optout.
