FAQ
John

Cheers for the response.

I've added another file to the gist -
https://gist.github.com/fatmcgav/4722199#file-oracle-pp. This is a snippet
from the top-level manifest that is responsible for calling the *'remove' *define
using *'create_resources'*.

And yes, by "various permutations", I do mean various different
dependencies...

I was trying to force the relationship cycle so that all the volumes are
unmounted and directories removed before removing the parent directory "file
{ $tier1_prefix: ..}"

Cheers
Gavin
On Friday, 8 February 2013 17:49:44 UTC, jcbollinger wrote:


On Friday, February 8, 2013 11:07:11 AM UTC-6, Gavin Williams wrote:

Any ideas?
That would be a lot easier to analyze in the context of the relevant
manifests, but it looks like you are specifying a lot of unneeded
relationships. Also, Puppet's output may be a bit misleading because
although there is only the one group of resources, there are actually at
least six cycles in it:

Act::Util::Linux::Nfs_mount[PUTEST01_datafiles] =>
Mount[/data/tier1/oracle/oradata/PUTEST01/datafiles] =>
Act::Util::Linux::Nfs_mount[PUTEST01_datafiles]

Act::Util::Linux::Nfs_mount[PUTEST01_redologs] =>
File[/data/tier1/oracle/oradata/PUTEST01/redologs] =>
Act::Util::Linux::Nfs_mount[PUTEST01_redologs]

Act::Util::Linux::Nfs_mount[PUTEST01_tempfiles] =>
Mount[/data/tier1/oracle/oradata/PUTEST01/tempfiles] =>
Act::Util::Linux::Nfs_mount[PUTEST01_tempfiles]

Act::Util::Linux::Nfs_mount[PUTEST01_archive] =>
Mount[/data/tier2/oracle/archivelogs/PUTEST01] =>
Act::Util::Linux::Nfs_mount[PUTEST01_archive]

Act::Util::Linux::Nfs_mount[PUTEST01_diag] =>
Mount[/data/tier2/oracle/diag/PUTEST01] =>
Act::Util::Linux::Nfs_mount[PUTEST01_diag]

File[/data/tier1/oracle/oradata/PUTEST01/redologs] =>
Act::Util::Linux::Nfs_mount[PUTEST01_redologs] =>
Act::Util::Linux::Nfs_mount[PUTEST01_tempfiles] =>
Mount[/data/tier1/oracle/oradata/PUTEST01/tempfiles] =>
Act::Util::Linux::Nfs_mount[PUTEST01_tempfiles] =>
Act::Util::Linux::Nfs_mount[PUTEST01_archive] =>
Mount[/data/tier2/oracle/archivelogs/PUTEST01] =>
Act::Util::Linux::Nfs_mount[PUTEST01_archive] =>
Act::Util::Linux::Nfs_mount[PUTEST01_diag] =>
Mount[/data/tier2/oracle/diag/PUTEST01] =>
Act::Util::Linux::Nfs_mount[PUTEST01_diag] =>
File[/data/tier1/oracle/oradata/PUTEST01] =>
File[/data/tier1/oracle/oradata/PUTEST01/redologs]

Be aware that order Puppet parses declarations in your manifests has
nothing to do with the order in which they are applied to the client node,
and resource relationships are concerned only with the latter. Physically
reordering your declarations will never break a dependency cycle.

On the other hand, if by "I've tried various [permutations]" you meant
that you had changed where your relationships point, then that further
supports the proposition that you are specifying relationships that you do
not need.

In particular, I'd guess that the problem is not restricted to the body of
the Act::Util::Linux::Nfs_mount definition, but rather that it also
involves something in the context where instances of that defined type are
themselves declared.


John
--
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+unsubscribe@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Search Discussions

Discussion Posts

Previous

Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 2 of 6 | next ›
Discussion Overview
grouppuppet-users @
categoriespuppet
postedFeb 6, '13 at 12:17p
activeFeb 9, '13 at 2:57a
posts6
users2
websitepuppetlabs.com

2 users in discussion

Fatmcgav: 4 posts Jcbollinger: 2 posts

People

Translate

site design / logo © 2021 Grokbase