Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Duplicate
-
PUP 3.5.1
-
None
-
None
-
Ubuntu 12.04 LTS, packages directly from puppetlabs repo
-
Major
Description
Having this manifest:
class foo::bar {
|
file { '/tmp/foobar':
|
content => 'foobar',
|
}
|
}
|
|
|
class foo::baz {
|
file { '/tmp/foobaz':
|
content => 'foobar',
|
}
|
}
|
|
|
include foo::bar
|
include foo::baz
|
and applying it with:
$ puppet apply --noop test.pp --tags foo::bar
or
$ puppet apply --noop test.pp --tags Foo::Bar
also applies the "Foo::Baz" class:
$ puppet apply --noop test.pp --tags Foo::Bar
|
Notice: Compiled catalog for puppet-test1.nureg.intra in environment production in 0.06 seconds
|
Notice: /Stage[main]/Foo::Baz/File[/tmp/foobaz]/ensure: current_value absent, should be file (noop)
|
Notice: Class[Foo::Baz]: Would have triggered 'refresh' from 1 events
|
Notice: /Stage[main]/Foo::Bar/File[/tmp/foobar]/ensure: current_value absent, should be file (noop)
|
Notice: Class[Foo::Bar]: Would have triggered 'refresh' from 1 events
|
Notice: Stage[main]: Would have triggered 'refresh' from 2 events
|
Notice: Finished catalog run in 0.02 seconds
|
giving the option --tags baz works, but would also fire another class ending in baz, i.e. test::baz
I think, this is a bug and was working some versions (3.x) ago.
Attachments
Issue Links
- duplicates
-
-
- Closed
-
