Jira (PUP-5537) nonproductive statement errors inconsistent between class and global scopes
Title: Message Title Dan Bode created an issue Puppet / PUP-5537 nonproductive statement errors inconsistent between class and global scopes Issue Type: Bug Affects Versions: PUP 4.3.0 Assignee: Unassigned Components: Language Created: 2015/11/20 3:47 PM Environment: with Puppet 4.3.0 Priority: Normal Reporter: Dan Bode I am seeing inconsistencies in how empty conditional blocks are treated between class vs. global scopes. the code: class foo (
Jira (PUP-4047) change wording of 'non productive expression' errors
Title: Message Title
Dan Bode commented on PUP-4047
Re: change wording of 'non productive _expression_' errors
Using Puppet version 4.3.0, I am seeing that this fix does not work if the conditional statement is inside the scope of a class:
the code:
class foo (
$var = true
) {
if $var {
# do some stuff...
}
}
include foo
results in the followi
Jira (PUP-3761) puppet agent --onetime not honored
Title: Message Title Dan Bode commented on PUP-3761 Re: puppet agent --onetime not honored I'm going to go ahead and close since it's not new behavior. Obviously, I'm doing something different on my end that caused me to start seeing it. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3761) puppet agent --onetime not honored
Title: Message Title Dan Bode commented on PUP-3761 Re: puppet agent --onetime not honored I had another look today, and by default puppet agent --test doesn't work (the main thing that I'm confused about) I remember this command always just working before, so it seems like a significant break in backwards compat. Also you mentioned race conditions related to running puppet from the foreground. What is the safe way to run it? service puppet stop puppet agent --enable puppet agent -t puppet agent --disable service puppet start Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3761) puppet agent --onetime not honored
Title: Message Title Dan Bode commented on PUP-3761 Re: puppet agent --onetime not honored I need to look into this more. After looking at the code I can tell this isn't something new. I was a little confused b/c this message is what I see after a fresh Puppet install (ie: things are disabled by default). I may need to recreate and try to understand why I'm seeing it (b/c I didn't see any recent commits merged into 3.x that would cause this to be the default behavior) Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3761) puppet agent --onetime not honored
Title: Message Title Dan Bode commented on PUP-3761 Re: puppet agent --onetime not honored maybe --enable should just be added to the --test alias? Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3761) puppet agent --onetime not honored
Title: Message Title Dan Bode commented on PUP-3761 Re: puppet agent --onetime not honored It appears that setting this flat to --enable means that the puppet agent will start running in the background (is that not true?) Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3761) puppet agent --onetime not honored
Title: Message Title Dan Bode created an issue Puppet / PUP-3761 puppet agent --onetime not honored Issue Type: Bug Assignee: Unassigned Created: 2014/12/11 2:38 PM Priority: Normal Reporter: Dan Bode when running the following command: puppet agent --noop puppet-master.service.consul --test --onetime (NOTE: --onetime added for clarify here, it is also part of the --test alias) I get the following error: Notice: Skipping run of Puppet configuration client; administratively disabled (Reason: 'Disabled by default on new installations'); Use 'puppet agent --enable' to re-enable. After reading about - enable, it looks like I would not want to enable this option ( -onetime means that I just want to run puppet once, and I don't necessarily want it to run in the background. It seems as if --test, --onetime, and --no-daemonize, have been rendered unsupported by this admin lock. Am I missing something, or are these options not going to be supported anymore? That would be a shame b/c they were really useful
Jira (PUP-3656) Prefetch eats all exceptions, there is no way to fail out.
Title: Message Title Dan Bode commented on PUP-3656 Re: Prefetch eats all exceptions, there is no way to fail out. +1 to fixing this. This is pretty much a huge issue for all of the openstack providers. It makes it way to easy to create duplicate resources in openstack when there is api unreliability (it actually makes it pretty difficult to use prefetch with anything that uses the network) Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1526) Package type should support environment variables
Title: Message Title Dan Bode commented on an issue Re: Package type should support environment variables I think I ran into this when trying to use eatmydata to speed up package installs for test systems. eatmydata need to set the LD_PRELOAD environment variable to work. Add Comment Puppet / PUP-1526 Package type should support environment variables ## Overview ## With the release of Debian Squeeze, a customer mentioned some Debian packages are beginning to use environment variables to override behavior. For example, the sudo-ldap package will not install if there is no password set on the root account. # This is needed for removing the sudo package since it won't uninstall # when the... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For
Jira (HI-183) Really need the ability to lookup hashes and arrays from other parts of Hiera.
Title: Message Title Dan Bode commented on an issue Re: Really need the ability to lookup hashes and arrays from other parts of Hiera. I took at stab at updating Michael's code and submitted it as: https://github.com/puppetlabs/hiera/pull/213 Add Comment Hiera / HI-183 Really need the ability to lookup hashes and arrays from other parts of Hiera. So, back in the old Redmine system, there was feature #23323 (http://projects.puppetlabs.com/issues/23323), which needed to be able to look up hashes and arrays from other parts of Hiera. I would like to reinstate that request here since the current solution only partially meets common data management consolidation needs. For instance, consider this... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d
Jira (PUP-3167) node namespaces override class namespaces if they happen to match
Title: Message Title
Dan Bode created an issue
Puppet / PUP-3167
node namespaces override class namespaces if they happen to match
Issue Type:
Bug
Affects Versions:
3.6.2
Assignee:
Andy Parker
Components:
DSL
Created:
02/Sep/14 3:33 AM
Priority:
Major
Reporter:
Dan Bode
if a node happens to match the name of a class, it will override its namespace with the node's namespace (which I didn't even know existed). I marked this as major b/c it potentially breaks any modules that rely on fully qualified namespace lookup (like apache)
The issue is probably better articulated with the following simple example:
class foo { $bar = 'one' }
node /foo/ { $bar = 'two' include foo notice("${::foo::bar}") }
Add Comment
Jira (PUP-1112) Puppet Packages should be built to support Ruby 1.9 from Software Collections.
Title: Message Title Dan Bode commented on an issue Re: Puppet Packages should be built to support Ruby 1.9 from Software Collections. One more reason this would be nice. Many Puppet modules depend on external gems for type and providers. As time goes by, the latest version of less of these gems will work with 1.8.7. Add Comment Puppet / PUP-1112 Puppet Packages should be built to support Ruby 1.9 from Software Collections. Many RHEL/CentOS users wish to move to Ruby 1.9 but without having to roll their own environment and repackage all Puppet packages. The Fedora Software Collections gives us this capability and I would like to request that a set of packages be rolled to support Ruby from SC. https://fedorahosted.org/SoftwareCollections/ This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http:/
