Jira (PUP-7312) Confine systemd provider to init system matching systemd
Title: Message Title Josh Cooper commented on PUP-7312 Re: Confine systemd provider to init system matching systemd Thanks Andreas Ntaflos, can you file a new PUP ticket and link to this one? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.178941.1488893881000.91387.1568073540424%40Atlassian.JIRA.
Jira (PUP-7312) Confine systemd provider to init system matching systemd
Title: Message Title
Andreas Ntaflos commented on PUP-7312
Re: Confine systemd provider to init system matching systemd
It seems that this change breaks a few things when Puppet is not being run as root, for example during spec tests (i.e. pdk test unit). At least under Ubuntu 16.04 and 18.04 the file /proc/1/exe is not accessible by regular users, so Puppet::FileSystem.exist?('/proc/1/exe') returns false and Puppet::FileSystem.readlink('/proc/1/exe').include?('systemd') fails with Errno::EACCES. ls also fails, obviously:
$ ls /proc/1/exe
ls: cannot read symbolic link '/proc/1/exe': Permission denied
lrwxrwxrwx 1 root root 0 Sep 7 00:13 /proc/1/exe
This has interesting implications in that now Puppet no longer recognizes that systemd is the correct service provider for recent Debian and Ubuntu releases. Thus spec tests for services fail with cryptic error messages like this:
$ pdk test unit
...
failed: rspec: ./spec/classes/service_spec.rb:9: Could not find the daemon directory (tested [/etc/sv,/var/lib/service])
Jira (PUP-10015) pip provider doesn't handle arbitrary equality
Title: Message Title Nathan Butler commented on PUP-10015 Re: pip provider doesn't handle arbitrary equality https://github.com/puppetlabs/puppet/pull/7703 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.324095.1568065161000.91157.1568065560546%40Atlassian.JIRA.
Jira (PUP-10015) pip provider doesn't handle arbitrary equality
Title: Message Title Nathan Butler created an issue Puppet / PUP-10015 pip provider doesn't handle arbitrary equality Issue Type: Bug Affects Versions: PUP 5.5.7 Assignee: Unassigned Components: Types and Providers Created: 2019/09/09 2:39 PM Priority: Normal Reporter: Nathan Butler Puppet Version: 5.5.6 Puppet Server Version: 5.3.5 OS Name/Version: Ubuntu 18.04 The current pip provider doesn't support Python's arbitrary equality https://www.python.org/dev/peps/pep-0440/#arbitrary-equality When encountering a python package specified with arbitrary equality via pip freeze, it fails to parse the package and keeps trying to install it e.g. $ pip freeze | grep pytz pytz===2012f Desired Behavior: Pip Provider correctly handles arbitrary equality Actual Behavior: Pip Provider incorrectly handles arbitrary equality Add Comment
Jira (PUP-10014) Unvendor deep_merge
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10014 Unvendor deep_merge Change By: Josh Cooper Puppet vendors the deep_merge gem version 1.0.1. Puppet also implements deep_merge logic (https://github.com/puppetlabs/puppet/blob/ca796215b95825f22b0ea30f56a27af181eda53a/lib/puppet/parser/scope.rb#L821-L838). And there are other places where we should deeply merging objects.This ticket is to update calls sites to use the deep_merge gem, and unvendor the gem. It will need to be added as a runtime dependency to .gemspec and ext/project_data.yaml. Also add to puppet- agent runtime as a shared gem (so it's useable by puppet-agent and puppetserver). < /td> Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit
Jira (PUP-10014) Unvendor deep_merge
Title: Message Title Josh Cooper created an issue Puppet / PUP-10014 Unvendor deep_merge Issue Type: Task Assignee: Unassigned Created: 2019/09/09 11:50 AM Priority: Normal Reporter: Josh Cooper Puppet vendors the deep_merge gem version 1.0.1. Puppet also implements deep_merge logic (https://github.com/puppetlabs/puppet/blob/ca796215b95825f22b0ea30f56a27af181eda53a/lib/puppet/parser/scope.rb#L821-L838). And there are other places where we should deeply merging objects. This ticket is to update calls sites to use the deep_merge gem, and unvendor the gem. It will need to be added as a runtime dependency to .gemspec and ext/project_data.yaml. Also add to puppet-agent as a shared gem (so it's useable by puppet-agent and puppetserver). Add Comment
Jira (PUP-9997) Puppet must not call Dir.chdir() except in a child process
Title: Message Title Jorie Tappa commented on PUP-9997 Re: Puppet must not call Dir.chdir() except in a child process Thanks for all the investigative work you've done on this James Ralston! If you want you are welcome to also file a PR to the puppet repo, otherwise, we'll pick this up as we are able. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.323575.156763800.90284.1568047920363%40Atlassian.JIRA.
Jira (PUP-9997) Puppet must not call Dir.chdir() except in a child process
Title: Message Title Jorie Tappa updated an issue Puppet / PUP-9997 Puppet must not call Dir.chdir() except in a child process Change By: Jorie Tappa Team: Coremunity Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.323575.156763800.90280.1568047860156%40Atlassian.JIRA.
Jira (PUP-9999) Puppet::Type.type('yumrepo') wrongly reports enabled repo
Title: Message Title
Jorie Tappa updated an issue
Puppet / PUP-
Puppet::Type.type('yumrepo') wrongly reports enabled repo
Change By:
Jorie Tappa
Team:
Night's Watch
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.323658.1567695504000.90278.1568047740156%40Atlassian.JIRA.
Jira (PDB-4502) PuppetDB command size metrics are missing
Title: Message Title Nick Walker assigned an issue to Rob Browning PuppetDB / PDB-4502 PuppetDB command size metrics are missing Change By: Nick Walker Assignee: Rob Browning Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.323996.156781861.90117.1568042400376%40Atlassian.JIRA.
Jira (PUP-9934) AIX user resource fails
Title: Message Title Gabriel Nagy commented on PUP-9934 Re: AIX user resource fails Great to know, we'll close this then! Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.319111.1564634229000.89994.1568023680144%40Atlassian.JIRA.
Jira (PUP-9934) AIX user resource fails
Title: Message Title Vladimir Vassyukov commented on PUP-9934 Re: AIX user resource fails Hi! I ran my manifest and it succeeds. Since opening ticket we installed some updates, maybe the error I encountered was fixed in them. Thanks for the help! The ticket can be closed. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.319111.1564634229000.89973.1568023020136%40Atlassian.JIRA.
Jira (PUP-9934) AIX user resource fails
Title: Message Title Gabriel Nagy commented on PUP-9934 Re: AIX user resource fails Hi, I understand your concerns, however you have not addressed my questions. The change in the chpasswd command was merged into Puppet 4.10: https://github.com/puppetlabs/puppet/commit/ee982cf532f1a253426b7e76f2352f9ce77af61e, so it's technically impossible to have Puppet 6.5.0 executing the chpasswd command with the user parameter, since the code is not there anymore. The AIX version is irrelevant here, as we do not differentiate our code based on that. That's why I requested more information, such as the contents of the /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/user/aix.rb file. I'm guessing what's happening here is either: the agent version on the affected systems does not include the previously mentioned fix (puppet version is not 6.5.0) an upgrade was done on the affected systems, from a version without the fix to a version with the fix, which ended badly, so puppet --version reports 6.5.0 but the behavior does not reflect this; in which case, please reinstall puppet-agent on the target systems the puppet/provider/user/aix.rb file has been manually tampered with (this is extremely unlikely, but still a possibility) I'm afraid that without more information I don't know how to help with this. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (FACT-2014) Implement Os fact for Aix
Title: Message Title Sebastian Miclea created an issue Facter / FACT-2014 Implement Os fact for Aix Issue Type: Task Assignee: Sebastian Miclea Created: 2019/09/09 12:58 AM Priority: Normal Reporter: Sebastian Miclea Implement the OS fact for Aix. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
