Jira (PDB-1223) Unexpected behavior in apply run mode with resource indirection

[Adrien Thebo (JIRA)]

Title: Message Title

Adrien Thebo commented on PDB-1223   Re: Unexpected behavior in apply run mode with resource indirection I tested this against PE 2016.5.1 and couldn't reproduce: [root@pe-201651-master puppet]# cat test.pp service { 'vboxadd-x11': ensure => 'running', enable => 'false', }   [root@pe-201651-master puppet]# puppet apply test.pp Notice: Compiled catalog for pe-201651-master.puppetdebug.vlan in environment production in 0.36 seconds Notice: Applied catalog in 0.36 seconds [root@pe-201651-master puppet]# puppet resource service | head puppet --versiservice { 'NetworkManager-dispatcher.service': ensure => 'stopped', enable => 'true', } service { 'NetworkManager-wait-online.service': ensure => 'stopped', enable => 'false', } service { 'NetworkManager.service': ensure => 'running', [root@pe-201651-master puppet]# puppet --version 4.8.1 [root@pe-201651-master puppet]# cat /etc/puppetlabs/puppet/routes.yaml --- apply: catalog: terminus: compiler cache: puppetdb resource: terminus: ral cache: puppetdb facts: terminus: facter cache: puppetdb_apply This used PE because it's a quick way to get up a full Puppet stack with PuppetDB, but it should work with pure open source components. If you're able to reproduce this failure locally, please include the output of the failing commands with the --trace flag. Add Comment   This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.