Jira (PUP-6671) Unable to start puppetserver after upgrade
Title: Message Title Ameya Agashe commented on PUP-6671 Re: Unable to start puppetserver after upgrade This is what I observed: [[root@puppet sysconfig]# diff puppetserver.rpmnew puppetserver 9c9 < JAVA_ARGS="-Xms2g -Xmx2g -XX:MaxPermSize=256m" — > JAVA_ARGS="-Xms1g -Xmx1g -XX:MaxPermSize=256m" 18c18 < BOOTSTRAP_CONFIG="/etc/puppetlabs/puppetserver/services.d/,/opt/puppetlabs/server/apps/puppetserver/config/services.d/" — > BOOTSTRAP_CONFIG="/etc/puppetlabs/puppetserver/bootstrap.cfg" 26,27d25 < < [root@puppet sysconfig]# pwd /etc/sysconfig [root@puppet sysconfig]# ] May I be allowed to ask why memory setting have been changed as part of upgrade ? and secondly why puppetserver.rpmnew is ready while doing puppetserver start and it reads old file puppetserver ? I'm not able to perform any deployments as a result of this. Please assist. Thanks 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.
Jira (PUP-6671) Unable to start puppetserver after upgrade
Title: Message Title Ameya Agashe created an issue Puppet / PUP-6671 Unable to start puppetserver after upgrade Issue Type: Bug Affects Versions: PUP 4.6.1 Assignee: Unassigned Components: Puppet Server Created: 2016/09/01 6:12 PM Priority: Blocker Reporter: Ameya Agashe Hi Guys, I had a good running puppetserver daemon but after sudo yum update -y It is not running, complaining Specified bootstrap config file does not exist: '/etc/puppetlabs/puppetserver/bootstrap.cfg'. detailed log output from puppetserver-daemon.log is as below: OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0 Exception in thread "main" java.lang.IllegalArgumentException: Specified bootstrap config file does not exist: '/etc/puppetlabs/puppetserver/bootstrap.cfg' at puppetlabs.trapperkeeper.bootstrap$eval14658$wrap_uri_error_14663$fn_14664.invoke(bootstrap.clj:131) at puppetlabs.trapperkeeper.bootstrap$eval14658$wrap_uri_error__14663.invoke(bootstrap.clj:127) at puppetlabs.trapperkeeper.bootstrap$eval14681$read_config_14686$fn_14687.invoke(bootstrap.clj:150) at
Jira (PUP-6670) Newlines break Puppet tag validation
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6670 Newlines break Puppet tag validation Change By: Henrik Lindberg Story Points: 1 Release Notes Summary: Tags containing newlines caused problems in Puppet DB as they were silently accepted when compiling a catalog. Now an error will be raised when compiling. Sprint: Language 2016-09-07 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.
Jira (PUP-5661) Stack level too deep issue
Title: Message Title Henrik Lindberg commented on PUP-5661 Re: Stack level too deep issue In older versions environment caching benefits are probably on par with the loss of memory and increased load on garbage collection - at least if looking at it over a longer stretch of time than a handful of compilations. It does however depend on how many environments you have, how many changes you have, and how different the code in the different environments are. You may see slower compilations but better overall throughput when turning off the cache (that is - it is not all bad . 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.
Jira (PUP-5971) Define evaluation should be evaluated depth-first, not breadth-first
Title: Message Title
Hunter Haugen commented on PUP-5971
Re: Define evaluation should be evaluated depth-first, not breadth-first
Ran into this again with the tomcat module. Here is a simple minimal case:
define foo {
foo::foo { $name: }
}
define foo::foo {
ensure_resource('user', 'tomcat8', { 'ensure' => 'present' })
file { '/test':
owner => 'tomcat8',
}
}
define bar {
ensure_resource('user', 'tomcat8', { 'ensure' => 'present' })
Jira (PUP-5661) Stack level too deep issue
Title: Message Title Clayton O'Neill commented on PUP-5661 Re: Stack level too deep issue Thanks for the quick reply. That was kind of the conclusion we had come to for now. We're close to upgrading to Puppet 4 now, so we'll be able to test again after we've upgraded. How much performance benefit do you think there is from environment caching that we'd be giving up? 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.
Jira (PUP-5661) Stack level too deep issue
Title: Message Title Henrik Lindberg commented on PUP-5661 Re: Stack level too deep issue We have found and plugged memory leaks in 4.x that were released in Puppet 4.6.1 that relate to environment caching. They fixes are however of general nature and they should not have an effect on stack depth which is another kind of problem. There has also been numerous changes in the networking / serailization / request handling on 4.x. The full set of changes cannot really be backported to 3.x and we are also close to EOL of 3.x. I think the general recommendation for any version before 4.6.1 is to turn off environment caching. 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.
Jira (PUP-5285) Systemd service provider only handles .service units, when others can be useful
Title: Message Title John Florian commented on PUP-5285 Re: Systemd service provider only handles .service units, when others can be useful There may still be an issue here. For example: Error: Could not start Service[tidy-conf.timer]: Execution of '/sbin/service tidy-conf.timer start' returned 6: Redirecting to /bin/systemctl start tidy-conf.timer.service Now if I modify my service resource to have provider=>systemd, all is good. However puppet-4.7.1 prefers /sbin/service over /bin/systemctl. So while Puppet does the right thing in not forcing a '.service' suffix, it does the wrong thing in preferring the /sbin/service, which is a systemd wrapper for backwards compatibility, which then sort of does the wrong thing in forcing this suffix. I think its wrong for Puppet to try /sbin/service first for this very reason. If systemctl is not present, then it would be okay to look for the legacy service command. 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.
Jira (PUP-6241) puppet agent ostensibly succeeds when environment directory has wrong permissions
Title: Message Title Chris Price commented on PUP-6241 Re: puppet agent ostensibly succeeds when environment directory has wrong permissions Henrik Lindberg oh - I was assuming that the patch to Puppet could be applied for just the check on the environment directory, specifically. If that's not possible, and it would have to go into some generic filesystem handling code, then I would probably agree that we shouldn't do that. I expect that when we open the issue with JRuby, if there's a good reproducer included, they'll merge it very quickly; it's just that their release cadence has slowed down significantly for the 1.7.x branch. They'd probably get the fix out in JRuby9k within a week or two, but we can't use that yet. 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.
Jira (PUP-6241) puppet agent ostensibly succeeds when environment directory has wrong permissions
Title: Message Title Henrik Lindberg commented on PUP-6241 Re: puppet agent ostensibly succeeds when environment directory has wrong permissions Was not considering how hard that could possibly be - seemed like the right thing to do as it fixes the actual problem rather that applying duct-tape. I don't like duct tape and puppet is filled with "ah shrug, this is horrible, let's... uh... add more duct tape?". Pardon the sarcasm - I understand we need to work around the problem if we don't have a pipeline to build and deliver JRuby (which it seems we should be prepared for given their long release schedule). I consider this a quite severe problem and if I were at the other end I would be happy to accept a fix and make a quick turn around - but maybe they do not reason that way. To do a work around we need to have a JRuby mode for the FileSystem providers. We have to comb all calls that does things with files to ensure that they do not hit the problem. In order to do that we need to understand the extent of the EXXX problems on JRuby. Is "open with no access permission" the only thing wrong there? Is it lying about other states of files? We also have IO reads that do not go via the FileSystem - are they ok? I fear that if we just wing it we probably end up with some other similar problem. While it may not seem like much overhead to add an exists? when a read fails with "not found" it is actually quite bad since we do a lot of searching for files (not sure if we have optimizations that read/test existence at the same time rather than first testing and then reading though). The 4.x loaders does not work that way (they do a Dir.glob and cache the result to avoid hitting disk), but other code may. 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.
Jira (PDB-3035) PDB should use gzip when replicating data
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-3035 PDB should use gzip when replicating data Issue Type: Improvement Assignee: Unassigned Created: 2016/09/01 3:25 PM Priority: Normal Reporter: Wyatt Alt It looks like we can do this by specifying the Accept-Encoding:gzip in the request headers when we ask for data from extensions, per https://github.com/puppetlabs/trapperkeeper-webserver-jetty9/blob/master/doc/jetty-config.md#gzip-enable. That should save a lot of bandwidth on replication if it's not already happening somehow. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-6241) puppet agent ostensibly succeeds when environment directory has wrong permissions
Title: Message Title Chris Price commented on PUP-6241 Re: puppet agent ostensibly succeeds when environment directory has wrong permissions We've laid some initial groundwork for shipping JRuby from a fork, but we've never actually done it before, because they did a release of the things we needed before we finished ironing out the process. I'd prefer to avoid that except for a last-resort kind of situation; the build process for JRuby is pretty hairy and it seems like it wouldn't be too hard for us to screw something up This one seems like it'd be reasonably easy to solve in Ruby code, so maybe not worth those risks... WDYT? 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.
Jira (PUP-5661) Stack level too deep issue
Title: Message Title Clayton O'Neill commented on PUP-5661 Re: Stack level too deep issue We've since updated to 3.8.7 and still have this issue with both Passenger and Puppet Server 1.1.3. We've recently realized that this problem only occurs in environments that have environment caching turned on. If we use the Puppet Server Admin API to delete the environment cache, then the problem goes away. 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.
Jira (PUP-6669) Puppet should return better errors for Enum mismatches
Title: Message Title Igor Galić commented on PUP-6669 Re: Puppet should return better errors for Enum mismatches Thomas Hallgren all i did was run bundle exec rake spec in the puppet code base 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.
Jira (PUP-6241) puppet agent ostensibly succeeds when environment directory has wrong permissions
Title: Message Title Henrik Lindberg commented on PUP-6241 Re: puppet agent ostensibly succeeds when environment directory has wrong permissions Chris Price sounds like a plan. OTOH - can we fix it and ship a patched version until it is accepted? 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.
Jira (PUP-6241) puppet agent ostensibly succeeds when environment directory has wrong permissions
Title: Message Title Chris Price commented on PUP-6241 Re: puppet agent ostensibly succeeds when environment directory has wrong permissions Thomas Hallgren I would say that it depends on the proposed solution. If we want to file a bug with upstream JRuby and wait for a release that contains that fix, then yes, our team should take it. But if we think this is too urgent to wait for (it will be several months before they do another release since they just did one last week), and we want to put a permissions check directory into the Puppet Ruby code in the interim, then maybe not? In fact, having thought about it for a second, it seems like perhaps the best thing to do would be to do both? So we could keep this ticket for a short-term fix in the Puppet codebase, and I will spin off a separate ticket about filing/tracking an upstream JRuby bug? 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.
Jira (PUP-6670) Newlines break Puppet tag validation
Title: Message Title Charlie Sharpsteen created an issue Puppet / PUP-6670 Newlines break Puppet tag validation Issue Type: Bug Affects Versions: PUP 4.6.1 Assignee: Unassigned Components: Language Created: 2016/09/01 9:03 AM Labels: compiler Priority: Major Reporter: Charlie Sharpsteen The Puppet compiler uses the following regex to determine whether or not a tag\ is valid: ^[0-9A-Za-z_][0-9A-Za-z_:.-]*$
Jira (FACT-1498) Custom and external search paths not loaded correctly from config file
Title: Message Title Maggie Dreyer assigned an issue to qa Facter / FACT-1498 Custom and external search paths not loaded correctly from config file Change By: Maggie Dreyer Status: Ready for CI Test Assignee: qa 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.
Jira (PUP-6669) Puppet should return better errors for Enum mismatches
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-6669 Puppet should return better errors for Enum mismatches Change By: Thomas Hallgren Story Points: 1 Sprint: Language 2016-09-07 Scrum Team: Language 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.
Jira (PUP-6668) Installation _options is not working on puppet 3.8.7
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6668 Installation _options is not working on puppet 3.8.7 Change By: Henrik Lindberg Scrum Team: Client Platform 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.
Jira (PUP-6668) Installation _options is not working on puppet 3.8.7
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-6668
Installation _options is not working on puppet 3.8.7
Change By:
Henrik Lindberg
Environment:
i'm Trying to install a package without sign package { 'rubygem-foreman_scap_client': ensure => 'installed', install_options => '--nogpgcheck', }but apparently the install options is not working at all checking the client on this /usr/share/ruby/vendor_ruby/puppet/provider/package/yum.rb and add in this part of the code def installwanted = @resource[:name]# If not allowing virtual packages, do a query to ensure a real package existsunless @resource.allow_virtual? yum *['-d', '0', '-e', '0', '-y', install_options, :list, wanted].compactend manually the --nogpgcheck def installwanted = @resource[:name]# If not allowing virtual packages, do a query to ensure a real package existsunless @resource.allow_virtual? yum *['-d', '0', '-e', '0', '-y', '--nogpgcheck', install_options, :list, wanted].compactendis working fine is looks like the install_options string is never catching by the install function and is looks like this could be a bugalso i can see thisno_debug = if Facter.value(:operatingsystemmajrelease).to_i > 5 then ["-d", "0"] else [] endcommand = [command(:cmd)] + no_debug + ["-e", error_level, "-y", install_options, operation, wanted].compactoutput = execute(command)if my logical is correct i understand if the OS is major of 5 just execute the command with -d and 0 but if not you include all i don't know if this part is missing all the parameter like a version in minor of 5
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-6669) Puppet should return better errors for Enum mismatches
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-6669 Puppet should return better errors for Enum mismatches Change By: Thomas Hallgren Assignee: Thomas Hallgren 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.
Jira (PUP-6668) Installation _options is not working on puppet 3.8.7
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-6668
Installation _options is not working on puppet 3.8.7
Change By:
Henrik Lindberg
i'm Trying to install a package without sign {code:puppet} package { 'rubygem-foreman_scap_client': ensure => 'installed', install_options => '--nogpgcheck', }{code}but apparently the install options is not working at all checking the client on this {code} /usr/share/ruby/vendor_ruby/puppet/provider/package/yum.rb {code}and add in this part of the code {code:ruby} def installwanted = @resource[:name]# If not allowing virtual packages, do a query to ensure a real package existsunless @resource.allow_virtual? yum *['-d', '0', '-e', '0', '-y', install_options, :list, wanted].compactend{code} manually the --nogpgcheck {code:ruby} def installwanted = @resource[:name]# If not allowing virtual packages, do a query to ensure a real package existsunless @resource.allow_virtual? yum *['-d', '0', '-e', '0', '-y', '--nogpgcheck', install_options, :list, wanted].compactend{code}is working fine is looks like the install_options string is never catching by the install function and is looks like this could be a bugalso i can see this {code:ruby} no_debug = if Facter.value(:operatingsystemmajrelease).to_i > 5 then ["-d", "0"] else [] endcommand = [command(:cmd)] + no_debug + ["-e", error_level, "-y", install_options, operation, wanted].compactoutput = execute(command){code}if my logical is correct i understand if the OS is major of 5 just execute the command with -d and 0 but if not you include all i don't know if this part is missing all the parameter like a version in minor of 5
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-6669) Puppet should return better errors for Enum mismatches
Title: Message Title Thomas Hallgren commented on PUP-6669 Re: Puppet should return better errors for Enum mismatches Yes, this is a regression. Igor Galić, do you have an example on how your patch breaks with the Sensitive, and/or other types? 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.
Jira (PUP-6667) yumrepo not idempotent when managing yum.conf
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6667 yumrepo not idempotent when managing yum.conf Change By: Henrik Lindberg Scrum Team: Client Platform 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.
Jira (PUP-1441) --show_diff causes crashes on files with UTF-8 content
Title: Message Title Henrik Lindberg commented on PUP-1441 Re: --show_diff causes crashes on files with UTF-8 content Ping Kylo Ginsberg - ticket needs priority to be decided 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.
Jira (PUP-6669) Puppet should return better errors for Enum mismatches
Title: Message Title Igor Galić commented on PUP-6669 Re: Puppet should return better errors for Enum mismatches This seems to be a regression compared to PUP-5964 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.
Jira (PUP-6669) Puppet should return better errors for Enum mismatches
Title: Message Title
Igor Galić created an issue
Puppet / PUP-6669
Puppet should return better errors for Enum mismatches
Issue Type:
Bug
Assignee:
Unassigned
Created:
2016/09/01 5:47 AM
Priority:
Normal
Reporter:
Igor Galić
given the following code:
define foo (
Optional[Enum['foo', 'bar']] $x
){
notify { $x: }
}
Jira (PUP-6669) Puppet should return better errors for Enum mismatches
Title: Message Title
Igor Galić updated an issue
Puppet / PUP-6669
Puppet should return better errors for Enum mismatches
Change By:
Igor Galić
given the following code:{code}define foo ( Optional[Enum['foo', 'bar']] $x){ notify { $x: }}foo { 'lolnope': x => 'baz',}{code}Puppet will return this Error:{code}Error: Evaluation Error: Error while evaluating a Resource Statement, Foo[lolnope]: parameter 'x' expects a match for Enum['bar', 'baz'], got String at /tmp/foo.pp:6 on node levix{code} (note the suspicious additional blank) my naïve patch:{code}diff --git a/lib/puppet/pops/types/type_mismatch_describer.rb b/lib/puppet/pops/types/type_mismatch_describer.rbindex 98763ad..3f11e96 100644--- a/lib/puppet/pops/types/type_mismatch_describer.rb+++ b/lib/puppet/pops/types/type_mismatch_describer.rb@@ -578,7 +578,7 @@ module Types value = param_hash[name] value_type = elem.value_type if param_hash.include?(name)- result << describe(value_type, TypeCalculator.singleton.infer_set(value).generalize, [ParameterPathElement.new(name)]) unless value_type.instance?(value)+ result << describe(value_type, TypeCalculator.singleton.infer_set(value), [ParameterPathElement.new(name)]) unless value_type.instance?(value) else result << MissingParameter.new(nil, name) unless elem.key_type.assignable?(PUndefType::DEFAULT) unless missing_ok end{code}works for this case :{code}Error: Evaluation Error: Error while evaluating a Resource Statement , Foo[lolnope]: parameter 'x' expects a match for Enum['bar', 'baz'], got String 'baz' at /tmp/foo.pp:6 on node levix{code} but breaks other types — in particular the new Sensitive type.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-6241) puppet agent ostensibly succeeds when environment directory has wrong permissions
Title: Message Title Thomas Hallgren assigned an issue to Chris Price Puppet / PUP-6241 puppet agent ostensibly succeeds when environment directory has wrong permissions Change By: Thomas Hallgren Assignee: Thomas Hallgren Chris Price 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.
Jira (PUP-6241) puppet agent ostensibly succeeds when environment directory has wrong permissions
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-6241 puppet agent ostensibly succeeds when environment directory has wrong permissions Change By: Thomas Hallgren Assignee: Thomas Hallgren 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.
Jira (PUP-6241) puppet agent ostensibly succeeds when environment directory has wrong permissions
Title: Message Title Thomas Hallgren commented on PUP-6241 Re: puppet agent ostensibly succeeds when environment directory has wrong permissions The problem stems from a not so subtle difference between the Ruby and JRuby implementation of Pathname. When calling #read on a file that resides under a directory with permissions that prevent access, Ruby correctly raises Errno::EACCES: Permission denied whereas the JRuby implementation raises Errno::ENOENT: No such file or directory. The latter, of course, results in an ostensibly empty environment when the directory in question is the environment root. Chris Price, given that your team are experts on JRuby, is it OK if we hand this over? 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.
Jira (PUP-6241) puppet agent ostensibly succeeds when environment directory has wrong permissions
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-6241 puppet agent ostensibly succeeds when environment directory has wrong permissions Change By: Thomas Hallgren Assignee: John Duarte 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.
Jira (PUP-6668) Installation _options is not working on puppet 3.8.7
Title: Message Title
Mario Gamboa updated an issue
Puppet / PUP-6668
Installation _options is not working on puppet 3.8.7
Change By:
Mario Gamboa
Environment:
i'm Trying to install a package without sign package { 'rubygem-foreman_scap_client': ensure => 'installed', install_options => '--nogpgcheck', }but apparently the install options is not working at all checking the client on this /usr/share/ruby/vendor_ruby/puppet/provider/package/yum.rb and add in this part of the code def installwanted = @resource[:name]# If not allowing virtual packages, do a query to ensure a real package existsunless @resource.allow_virtual? yum *['-d', '0', '-e', '0', '-y', install_options, :list, wanted].compactend manually the --nogpgcheck def installwanted = @resource[:name]# If not allowing virtual packages, do a query to ensure a real package existsunless @resource.allow_virtual? yum *['-d', '0', '-e', '0', '-y', '--nogpgcheck', install_options, :list, wanted].compactend is working fine is looks like the install_options string is never catching by the install function and is looks like this could be a bug also i can see thisno_debug = if Facter.value(:operatingsystemmajrelease).to_i > 5 then ["-d", "0"] else [] endcommand = [command(:cmd)] + no_debug + ["-e", error_level, "-y", install_options, operation, wanted].compactoutput = execute(command)if my logical is correct i understand if the OS is major of 5 just execute the command with -d and 0 but if not you include all i don't know if this part is missing all the parameter like a version in minor of 5
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-6668) Installation _options is not working on puppet 3.8.7
Title: Message Title
Mario Gamboa created an issue
Puppet / PUP-6668
Installation _options is not working on puppet 3.8.7
Issue Type:
Bug
Affects Versions:
PUP 3.8.8
Assignee:
Kylo Ginsberg
Components:
Types and Providers
Created:
2016/09/01 2:02 AM
Environment:
i'm Trying to install a package without sign
package { 'rubygem-foreman_scap_client': ensure => 'installed', install_options => '--nogpgcheck', }
but apparently the install options is not working at all checking the client on this
/usr/share/ruby/vendor_ruby/puppet/provider/package/yum.rb
and add in this part of the code
def install wanted = @resource[:name]
If not allowing virtual packages, do a query to ensure a real package exists unless @resource.allow_virtual? yum *['-d', '0', '-e', '0', '-y', install_options, :list, wanted].compact end
manually the --nogpgcheck
def install wanted = @resource[:name]
If not allowing virtual packages, do a query to ensure a real package exists unless @resource.allow_virtual? yum *['-d', '0', '-e', '0', '-y', '--nogpgcheck', install_options, :list, wanted].compact end
is working fine is looks like the install_options string is never catching by the install function
Jira (PUP-1441) --show_diff causes crashes on files with UTF-8 content
Title: Message Title Yadan Fan commented on PUP-1441 Re: --show_diff causes crashes on files with UTF-8 content Hi everyone, is there any progress for this bug? Thanks! 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.
