Jira (PUP-9934) AIX user resource fails
Title: Message Title Vladimir Vassyukov updated an issue Puppet / PUP-9934 AIX user resource fails Change By: Vladimir Vassyukov Environment: root@nes-t1a-app6> [~]# oslevel -s7100-05-03-1846root@nes-t1a-app6> [~]# uname -aAIX nes-t1a-app6 1 7 00F7040C4C00 Debug: Executing: '/bin/chpasswd -e -c oracle'Error: undefined local variable or method `param' for User[oracle](provider=aix):Puppet::Type::User::ProviderAixError: /Stage[main]/Aix::Oracleuser/User[oracle]/password: change from [old password hash redacted] to [new password hash redacted] failed: undefined local variable or method `param' for User[oracle](provider=aix):Puppet::Type::User::ProviderAix An error occurs using parameter "password" module "users". I find the bug report PUP-8538, it describes the same issue, and it marked as fixed in version PUP 4.10.11, PUP 5.3.6, PUP 5.5.1, but i get the error in version 6.5.0 Debug: Executing: '/bin/chpasswd -e -c oracle' Error: undefined local variable or method `param' for User[oracle](provider=aix):Puppet::Type::User::ProviderAix Error: /Stage[main]/Aix::Oracleuser/User[oracle]/password: change from [old password hash redacted] to [new password hash redacted] failed: undefined local variable or method `param' for User[oracle](provider=aix):Puppet::Type::User::ProviderAix Add Comment This message was sent by
Jira (PDB-4468) Partitioning of resource_events: Migration test for initial creation of partitions
Title: Message Title Robert Roland created an issue PuppetDB / PDB-4468 Partitioning of resource_events: Migration test for initial creation of partitions Issue Type: Story Assignee: Unassigned Components: PuppetDB Created: 2019/08/01 2:36 PM Priority: Normal Reporter: Robert Roland A schema migration test for the partitioned tables should be created. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-4467) Partitioning of resource_events: Migrate existing events to partitioned tables
Title: Message Title Robert Roland created an issue PuppetDB / PDB-4467 Partitioning of resource_events: Migrate existing events to partitioned tables Issue Type: Story Assignee: Unassigned Components: PuppetDB Created: 2019/08/01 2:35 PM Priority: Normal Reporter: Robert Roland The existing entries in resource_events need to be migrated to the partitioned table. Caveat: the existing `resource_events` table will be renamed prior to the migration (ex. `resource_events_original`) due to the nature of creating the partitions. This ensures we don't have a lengthy set of renames on the partitions themselves. Add Comment
Jira (PDB-4466) Partitioning of resource_events: GC by dropping expired partitions
Title: Message Title Robert Roland created an issue PuppetDB / PDB-4466 Partitioning of resource_events: GC by dropping expired partitions Issue Type: Story Assignee: Unassigned Components: PuppetDB Created: 2019/08/01 2:34 PM Priority: Normal Reporter: Robert Roland GC of resource_events should drop any resource_events__Www tables that are older than the TTL. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1492) get_targets surfaces exception when used in apply block with inventory v2
Title: Message Title Chris Cowell updated an issue Puppet Task Runner / BOLT-1492 get_targets surfaces exception when used in apply block with inventory v2 Change By: Chris Cowell Labels: docs_reviewed 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.318475.1564443989000.40560.1564685400237%40Atlassian.JIRA.
Jira (BOLT-1329) Delete task wrapper script before running the task
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-1329 Delete task wrapper script before running the task Change By: Cas Donoghue Sprint: Bolt Kanban Ready for Grooming 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.309610.1558465731000.40425.1564683300135%40Atlassian.JIRA.
Jira (BOLT-1329) Delete task wrapper script before running the task
Title: Message Title Cas Donoghue assigned an issue to Unassigned Puppet Task Runner / BOLT-1329 Delete task wrapper script before running the task Change By: Cas Donoghue Assignee: Cas Donoghue 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.309610.1558465731000.40421.1564683240746%40Atlassian.JIRA.
Jira (BOLT-1502) Do not rely on wrapper script for run-as with stdin task input
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1502 Do not rely on wrapper script for run-as with stdin task input Issue Type: Improvement Assignee: Unassigned Created: 2019/08/01 11:09 AM Priority: Normal Reporter: Cas Donoghue Currently tasks run with the run-as option rely on laying down a wrapper script to direct task input data over stdin. There are several issues with this approach, the first is that the wrapper script can contain sensitive data in clear text. A ticket describing an idea to minimize the time the wrapper script lives on disk has been filed under https://tickets.puppetlabs.com/browse/BOLT-1329 The second issue described has to do with file permissions of the wrapper script when run on the local transport which is ticketed under https://tickets.puppetlabs.com/browse/BOLT-1283 Instead of relying on the wrapper script we should investigate a solution that does not involve one. The solution should be able to safely pass the input data (even if it is very large) to the task over stdin even if it is ambigious whether a sudo password is required. The solution should avoid problems with passing the data over the bash CLI such as Argument list too long and exposing the sensitive data in the process list or in the shell history. A commit with some discussion and potential pitfalls is https://github.com/puppetlabs/bolt/pull/1109 From Nlew on slack: The root issue is that there’s only one stdin, and both the password for sudo and the parameters of the task need to be on stdin. But the password should only be on stdin if sudo asks for it. But we don’t know how to conclusively determine that sudo doesn’t need the password. So we skirt around that by wrapping the task executable in a script that also passes its stdin, so in the case where sudo doesn’t need the password, it will just start executing the script, which will pass stdin to the task. Ansible’s solution is basically to instead run sudo 'echo "okay done with sudo, please pass stdin now"; /path/to/actual/task, and then it waits to see the “done with sudo” message before passing the task parameters on stdin
Jira (BOLT-1492) get_targets surfaces exception when used in apply block with inventory v2
Title: Message Title Chris Cowell updated an issue Puppet Task Runner / BOLT-1492 get_targets surfaces exception when used in apply block with inventory v2 Change By: Chris Cowell Labels: docs_reviewed 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.318475.1564443989000.40338.1564681801448%40Atlassian.JIRA.
Jira (BOLT-1492) get_targets surfaces exception when used in apply block with inventory v2
Title: Message Title Chris Cowell updated an issue Puppet Task Runner / BOLT-1492 get_targets surfaces exception when used in apply block with inventory v2 Change By: Chris Cowell Labels: docs_reviewed 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.318475.1564443989000.40307.1564681440512%40Atlassian.JIRA.
Jira (BOLT-1412) 'script run' CLI silently ignores arguments containing equal signs
Title: Message Title Chris Cowell updated an issue Puppet Task Runner / BOLT-1412 'script run' CLI silently ignores arguments containing equal signs Change By: Chris Cowell Labels: docs_reviewed 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.313316.1561037704000.40276.1564680360145%40Atlassian.JIRA.
Jira (PUP-7808) puppet resource <...> --to_yaml mishandles structured resource values
Title: Message Title
Steve Marlow commented on PUP-7808
Re: puppet resource <...> --to_yaml mishandles structured resource values
I have also been seeing this with a client. They're using `puppet resource pe_node_group` on PE which outputs:
pe_node_group:
PE Certificate Authority:
ensure : 'present'
classes : {
'puppet_enterprise::profile::certificate_authority' => {
}
}
The classes parameter is a Hash internally. YAML implementations can't parse the above output. As a workaround we found that a simple s/=>/:/g fixes the problem, but obviously that's not ideal. The --to_yaml option in Puppet::Application::Resource ends up invoking Puppet::Resource.to_hierayaml. This function outputs the YAML with the following code:
# In Puppet::Resource.to_hierayaml
...
attributes = attr.collect { |k|
Jira (PUP-9935) service_provider for debian wrong on buster
Title: Message Title
Tobias Wolter updated an issue
Puppet / PUP-9935
service_provider for debian wrong on buster
Change By:
Tobias Wolter
*Puppet Version:* 6.7.2*Puppet Server Version:* n/a*OS Name/Version:* Debian 10Services cannot be managed correctly on Debian buster because the `service_provider` code does not consider buster a systemd distribution.*Desired Behavior:*Puppet using systemd.*Actual Behavior:* ``` {code} Debug: Executing: '/usr/sbin/service puppet status'dpkg: error: --compare-versions takes three arguments: Type dpkg --help for help about installing and deinstalling packages [*];Use 'apt' or 'aptitude' for user-friendly package management;Type dpkg -Dhelp for a list of dpkg debug flag values;Type dpkg --force-help for a list of forcing options;Type dpkg-deb --help for help about manipulating *.deb files;Options marked [*] produce a lot of output - pipe it through 'less' or 'more' !Debug: Executing: '/usr/sbin/update-rc.d -f puppet remove'Debug: Executing: '/usr/sbin/update-rc.d puppet stop 00 1 2 3 4 5 6 .'Error: Execution of '/usr/sbin/update-rc.d puppet stop 00 1 2 3 4 5 6 .' returned 1: update-rc.d: error: unable to read /etc/init.d/puppetError: /Stage[main]/Profile::Base/Service[puppet]/enable: change from 'true' to 'false' failed: Execution of '/usr/sbin/update-rc.d puppet stop 00 1 2 3 4 5 6 .' returned 1: update-rc.d: error: unable to read /etc/init.d/puppet ``` {code} The cause is following code in `/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/service/systemd.rb`: defaultfor :operatingsystem => :debian, :operatingsystemmajrelease => ["8", "stretch/sid", "9", "buster/sid"]This should not be a whitelist anymore. IMHO, it should be set as the Debian default, especially as PE 2018.1, as the oldest still supported version, has a minimum OS requirement of Debian 8 ('jessie') for the agent, which is a systemd distribution.
Add Comment
Jira (PUP-9935) service_provider for debian wrong on buster
Title: Message Title
Tobias Wolter updated an issue
Puppet / PUP-9935
service_provider for debian wrong on buster
Change By:
Tobias Wolter
*Puppet Version:* 6.7.2*Puppet Server Version:* n/a*OS Name/Version:* Debian 10Services cannot be managed correctly on Debian buster because the `service_provider` code does not consider buster a systemd distribution.*Desired Behavior:*Puppet using systemd.*Actual Behavior:*{code}Debug: Executing: '/usr/sbin/service puppet status'dpkg: error: --compare-versions takes three arguments: Type dpkg --help for help about installing and deinstalling packages [*];Use 'apt' or 'aptitude' for user-friendly package management;Type dpkg -Dhelp for a list of dpkg debug flag values;Type dpkg --force-help for a list of forcing options;Type dpkg-deb --help for help about manipulating *.deb files;Options marked [*] produce a lot of output - pipe it through 'less' or 'more' !Debug: Executing: '/usr/sbin/update-rc.d -f puppet remove'Debug: Executing: '/usr/sbin/update-rc.d puppet stop 00 1 2 3 4 5 6 .'Error: Execution of '/usr/sbin/update-rc.d puppet stop 00 1 2 3 4 5 6 .' returned 1: update-rc.d: error: unable to read /etc/init.d/puppetError: /Stage[main]/Profile::Base/Service[puppet]/enable: change from 'true' to 'false' failed: Execution of '/usr/sbin/update-rc.d puppet stop 00 1 2 3 4 5 6 .' returned 1: update-rc.d: error: unable to read /etc/init.d/puppet{code}The cause is following code in ` * /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/service/systemd.rb ` * : {code} defaultfor :operatingsystem => :debian, :operatingsystemmajrelease => ["8", "stretch/sid", "9", "buster/sid"] {code} This should not be a whitelist anymore. IMHO, it should be set as the Debian default, especially as PE 2018.1, as the oldest still supported version, has a minimum OS requirement of Debian 8 ('jessie') for the agent, which is a systemd distribution.
Add Comment
Jira (PUP-9935) service_provider for debian wrong on buster
Title: Message Title Tobias Wolter created an issue Puppet / PUP-9935 service_provider for debian wrong on buster Issue Type: Bug Affects Versions: PUP 6.7.2 Assignee: Unassigned Components: Catalog Application Created: 2019/08/01 6:00 AM Labels: debian Priority: Major Reporter: Tobias Wolter Puppet Version: 6.7.2 Puppet Server Version: n/a OS Name/Version: Debian 10 Services cannot be managed correctly on Debian buster because the `service_provider` code does not consider buster a systemd distribution. Desired Behavior: Puppet using systemd. Actual Behavior: ``` Debug: Executing: '/usr/sbin/service puppet status' dpkg: error: --compare-versions takes three arguments:Type dpkg --help for help about installing and deinstalling packages [*]; Use 'apt' or 'aptitude' for user-friendly package management; Type dpkg -Dhelp for a list of dpkg debug flag values; Type dpkg --force-help for a list of forcing options; Type dpkg-deb --help for help about manipulating *.deb files; Options marked [*] produce a lot of output - pipe it through 'less' or 'more' ! Debug: Executing: '/usr/sbin/update-rc.d -f puppet remove' Debug: Executing: '/usr/sbin/update-rc.d puppet stop 00 1 2 3 4 5 6 .' Error: Execution of '/usr/sbin/update-rc.d puppet stop 00 1 2 3 4 5 6 .' returned 1: update-rc.d: error: unable to read /etc/init.d/puppet Error: /Stage[main]/Profile::Base/Service[puppet]/enable: change from 'true' to 'false' failed: Execution of '/usr/sbin/update-rc.d puppet stop 00 1 2 3 4 5 6 .' returned 1: update-rc.d: error: unable to read /etc/init.d/puppet ``` The cause is
Jira (FACT-1944) Investigate custom facts
Title: Message Title Oana Tanasoiu updated an issue Facter / FACT-1944 Investigate custom facts Change By: Oana Tanasoiu Release Notes: Not Needed 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.316808.1563365164000.39668.1564662960143%40Atlassian.JIRA.
Jira (FACT-1965) Create Gemfile and Travis for benchmark tool
Title: Message Title Oana Tanasoiu updated an issue Facter / FACT-1965 Create Gemfile and Travis for benchmark tool Change By: Oana Tanasoiu Release Notes: Not Needed 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.318067.1564041936000.39669.1564662960148%40Atlassian.JIRA.
Jira (FACT-1948) Investigate acceptance tests from C++ facter
Title: Message Title Oana Tanasoiu assigned an issue to Oana Tanasoiu Facter / FACT-1948 Investigate acceptance tests from C++ facter Change By: Oana Tanasoiu Assignee: Oana Tanasoiu 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.316812.1563365421000.39664.1564662900562%40Atlassian.JIRA.
Jira (FACT-1944) Investigate custom facts
Title: Message Title Oana Tanasoiu commented on FACT-1944 Re: Investigate custom facts https://puppet.com/docs/facter/3.11/custom_facts.html https://github.com/puppetlabs/docs-archive/blob/master/facter/3.0/custom_facts.md 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.316808.1563365164000.39661.1564662840102%40Atlassian.JIRA.
Jira (FACT-1979) Port existing integration (acceptance) tests to docker containers
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-1979 Port existing integration (acceptance) tests to docker containers Change By: Bogdan Irimie Requirements:- use the same acceptance tests, no changes- need two hosts (1 for beaker and the other for facter (and puppet agent))Beaker steps:- initialisation (no)- provisioning (no)- pre suite (yes)- execute (yes)OS support:- linux (different flavours, maybe different architectures e.g. x86, ARM)- windows- osx (? maybe this is not the case because there are no containers for osx) Examples of Dockerfiles and how to run tests can be found in:https://tickets.puppetlabs.com/browse/PA-2779https://tickets.puppetlabs.com/browse/PA-2773https://tickets.puppetlabs.com/browse/PA-2751 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
Jira (FACT-1979) Port existing integration (acceptance) tests to docker containers
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-1979 Port existing integration (acceptance) tests to docker containers Change By: Bogdan Irimie Steps Requirements: - use the same acceptance tests, no changes- need two hosts (1 for beaker and the other for facter (and puppet agent))Beaker steps:- initialisation (no) - provisioning (no) - pre suite (yes) - execute (yes)OS support:- linux (different flavours, maybe different architectures e.g. x86, ARM)- windows- osx (? maybe this is not the case because there are no containers for osx) 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.319138.1564647484000.39489.1564648020086%40Atlassian.JIRA.
Jira (FACT-1979) Port existing integration (acceptance) tests to docker containers
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-1979 Port existing integration (acceptance) tests to docker containers Change By: Bogdan Irimie Steps- initialisation- provisioning- pre suite- execute 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.319138.1564647484000.39487.1564647780057%40Atlassian.JIRA.
Jira (FACT-1979) Port existing integration (acceptance) tests to docker containers
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-1979 Port existing integration (acceptance) tests to docker containers Change By: Bogdan Irimie Attachment: facter-ng-ci.png 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.319138.1564647484000.39486.1564647660146%40Atlassian.JIRA.
Jira (FACT-1979) Port existing integration (acceptance) tests to docker containers
Title: Message Title Bogdan Irimie created an issue Facter / FACT-1979 Port existing integration (acceptance) tests to docker containers Issue Type: Task Assignee: Unassigned Created: 2019/08/01 1:18 AM Priority: Normal Reporter: Bogdan Irimie 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
