Jira (PUP-7486) useradd provider silently does not set password
Title: Message Title Moses Mendoza assigned an issue to Josh Cooper Puppet / PUP-7486 useradd provider silently does not set password Change By: Moses Mendoza Assignee: Josh Cooper 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-7745) package latest method does not refresh metadata on Solaris
Title: Message Title Moses Mendoza commented on PUP-7745 Re: package latest method does not refresh metadata on Solaris merged to master at https://github.com/puppetlabs/puppet/commit/c72a654e20110da444d5d5247a4accdeb410890c 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-7745) package latest method does not refresh metadata on Solaris
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7745 package latest method does not refresh metadata on Solaris Change By: Moses Mendoza Fix Version/s: PUP 5.4.0 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-7745) package latest method does not refresh metadata on Solaris
Title: Message Title Moses Mendoza assigned an issue to Unassigned Puppet / PUP-7745 package latest method does not refresh metadata on Solaris Change By: Moses Mendoza Assignee: Shawn Ferry 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-7982) pip provider package install loop
Title: Message Title Moses Mendoza commented on PUP-7982 Re: pip provider package install loop Closed associated PR, and closing this as won't fix based on this info (also left in PR): I think after reviewing the info online about this, it seems like packages generally are discouraged from having an underscore (`_`) in the name, and the system treats these as dashes (`-`). For example, note for int-date: ☂ : pip install int_date Collecting int_date Using cached int_date-0.1.8-py2.py3-none-any.whl Requirement already satisfied: six>=1.9.0 in /usr/local/lib/python2.7/site-packages (from int_date) Requirement already satisfied: python-dateutil>=2.4.2 in /usr/local/lib/python2.7/site-packages (from int_date) Installing collected packages: int-date Successfully installed int-date-0.1.8 ☂ : pip list
Jira (PDB-3717) Merge stable to master
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3717 Merge stable to master Issue Type: Bug Assignee: Unassigned Created: 2017/10/16 3:25 PM Priority: Normal Reporter: gepetto-bot 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 (PDB-3716) Merge lts to stable
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3716 Merge lts to stable Issue Type: Bug Assignee: Unassigned Created: 2017/10/16 3:18 PM Priority: Normal Reporter: gepetto-bot 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 (FACT-1765) Facter should not output a warning for a missing dmidecode component on Power Linux machines
Title: Message Title Casey Williams commented on FACT-1765 Re: Facter should not output a warning for a missing dmidecode component on Power Linux machines Adding a little more context to this closed ticket: I tried updating the version of dmidecode (2.x -> 3.x) used on power8 this morning to see if it would solve our problems like it did for aarch64, but it seems that power8 lacks a DMI table at all, and the alternative is to use the /proc/device-tree filesystem to gather similar information (this is something we could add to facter if necessary). 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 (PDB-3715) PuppetDB doesn't complete shutdown after migration fails
Title: Message Title
Charlie Sharpsteen updated an issue
PuppetDB / PDB-3715
PuppetDB doesn't complete shutdown after migration fails
Change By:
Charlie Sharpsteen
The PuppetDB service doesn't shut down after a failed migration, despite log messages indicating that the shutdown cycle has been started. This causes the init service to wait for the full START_TIMEOUT before declaring startup as failed and killing the process. Given we've bumped START_TIMEOUT to 4 hours to allow for migration of large databases, this significantly delays detection of failed upgrades due to migration issues. ## h2. Reproduction CaseInstall PuppetDB 5.0.1 on a CentOS 7 VM using the puppetlabs/puppetdb module: - Add package repos for version 5 of the Puppet Platform and install the puppet agent:{code:bash}rpm -Uvh http://yum.puppetlabs.com/puppet5/puppet-release-el-7.noarch.rpmyum install -y puppet agent{code} - Instal the PuppetDB module{code:bash}/opt/puppetlabs/bin/puppet module install puppetlabs-puppetdb --version 6.0.1{code} - Apply the following manifest to install Postgres and PuppetDB. Two applications may be necessary due to a race condition where Puppet resources attempt to enforce state on the database while Postgres is still starting up.{code:bash}/opt/puppetlabs/puppet/bin/puppet apply << EOFclass {'puppetdb::globals': version => '5.0.1'}class {'puppetdb': disable_ssl => true}EOF{code}Add some test data to PuppetDB that will trigger the migration failure described in PDB-3692:{code:bash}/opt/puppetlabs/puppet/bin/curl -X POST \ -H 'Content-Type:application/json' \ -H 'Accept:application/json' \ -d '{"certname":"test1","environment":"DEV","values":{"myfact": null},"producer_timestamp":"2015-01-01", "producer":"master1"}' \ "http://localhost:8080/pdb/cmd/v1?command=replace_facts=5=test1"/opt/puppetlabs/puppet/bin/curl -X POST \ -H 'Content-Type:application/json' \ -H 'Accept:application/json' \ -d '{"certname":"test2","environment":"DEV","values":{"myfact": null},"producer_timestamp":"2015-01-01", "producer":"master1"}' \ "http://localhost:8080/pdb/cmd/v1?command=replace_facts=5=test2"# Alter the facts table to trigger PDB-3692 on upgradesudo -u postgres /usr/bin/psql -d puppetdb -c "UPDATE facts SET value='null' WHERE factset_id=2 AND value_type_id=4"{code}Decrease the timeout for PuppetDB startup and then upgrade PuppetDB to 5.1.1:{code:bash}echo 'START_TIMEOUT=60' >> /etc/sysconfig/puppetdb/opt/puppetlabs/bin/puppet resource --evaltrace package puppetdb ensure=5.1.1{code} ### h3. Outcome/var/log/puppetlabs/puppetdb/puppetdb.log shows the migration fails and the service enters shutdown within seconds after starting:{noformat}2017-10-16 20:03:52,350 INFO [p.p.c.services] PuppetDB version 5.1.12017-10-16 20:03:52,351 INFO [c.z.h.HikariDataSource] PDBMigrationsPool - Starting...2017-10-16 20:03:52,353 INFO [c.z.h.HikariDataSource] PDBMigrationsPool - Start completed.2017-10-16 20:03:52,517 INFO [p.p.s.migrate] Applying database migration version 642017-10-16 20:03:52,518 INFO [p.p.s.migrate] [1/8] Cleaning up unreferenced facts...2017-10-16 20:03:52,527 INFO [p.p.s.migrate] [2/8] Creating new fact storage tables...2017-10-16 20:03:52,543 INFO [p.p.s.migrate] [3/8] Copying unique fact values into fact_values2017-10-16 20:03:52,555 INFO
Jira (PDB-3715) PuppetDB doesn't complete shutdown after migration fails
Title: Message Title Charlie Sharpsteen created an issue PuppetDB / PDB-3715 PuppetDB doesn't complete shutdown after migration fails Issue Type: Bug Affects Versions: PDB 5.1.1 Assignee: Unassigned Created: 2017/10/16 1:42 PM Priority: Major Reporter: Charlie Sharpsteen The PuppetDB service doesn't shut down after a failed migration, despite log messages indicating that the shutdown cycle has been started. This causes the init service to wait for the full START_TIMEOUT before declaring startup as failed and killing the process. Given we've bumped START_TIMEOUT to 4 hours to allow for migration of large databases, this significantly delays detection of failed upgrades due to migration issues. Reproduction Case Install PuppetDB 5.0.1 on a CentOS 7 VM using the puppetlabs/puppetdb module: Add package repos for version 5 of the Puppet Platform and install the puppet agent:
Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title Thomas Kishel updated an issue Puppet / PUP-6134 Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows Change By: Thomas Kishel Comment: That PR is rather old, it may need to be rebased. I’m on PTO today. I couldlook at it on Monday. 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-8056) Error type docs show new from hash - does not work as intended
Title: Message Title John Duarte commented on PUP-8056 Re: Error type docs show new from hash - does not work as intended PR opened to update Bolt to puppet at 088f1d4 https://github.com/puppetlabs/bolt/pull/113 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-8056) Error type docs show new from hash - does not work as intended
Title: Message Title
John Duarte commented on PUP-8056
Re: Error type docs show new from hash - does not work as intended
Confirmed that this change allows the Error type to be supported within a task plan using bolt at d0ae504 with the puppet submodule updated to 088f1d4 from the feature_puppet-tasks branch.
$ cat /tmp/modules/mymodule/plans/myplan.pp
plan mymodule::myplan {
Error(
message=> "Sorry, this plan does not work yet.",
kind => 'mymodule/error',
issue_code => 'NOT_IMPLEMENTED'
)
}
$ bundle exec bolt plan run mymodule::myplan --modules /tmp/modules
Jira (PUP-8056) Error type docs show new from hash - does not work as intended
Title: Message Title John Duarte updated an issue Puppet / PUP-8056 Error type docs show new from hash - does not work as intended Change By: John Duarte QA Risk Assessment: Needs Assessment Manual 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 (PDB-3692) PDB migration error due to facts deduplication and null values
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3692 PDB migration error due to facts deduplication and null values Change By: Russell Mull Fix Version/s: PDB 5.1.1 Fix Version/s: PDB 5.1.2 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 (PDB-3692) PDB migration error due to facts deduplication and null values
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3692 PDB migration error due to facts deduplication and null values Change By: Russell Mull Sprint: Data Platform 2017-10-04 , Data Platform 2017-10-18 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 (PDB-3692) PDB migration error due to facts deduplication and null values
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3692 PDB migration error due to facts deduplication and null values Change By: Russell Mull Affects Version/s: PDB 5.1.1 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-6986) Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-6986 Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars Change By: Adrien Thebo Sprint: AP 2017-01-11, AP 2017-03-08, Agent 2017-03-22, Platform Core KANBAN Hopper 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 (PDB-3714) (maint) Update beaker gems for testing
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3714 (maint) Update beaker gems for testing Issue Type: Bug Assignee: Unassigned Created: 2017/10/16 11:38 AM Priority: Normal Reporter: gepetto-bot Updates beaker gems to support setting in CI config. Needed to support testing macOS 10.12. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-8006) Wrong PID dir
Title: Message Title Josh Cooper assigned an issue to steclest Puppet / PUP-8006 Wrong PID dir Change By: Josh Cooper Assignee: Laura Raney steclest 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-7807) AIX mount resource remounts without options
Title: Message Title Jarret Lavallee commented on PUP-7807 Re: AIX mount resource remounts without options Thank you Moses Mendoza! 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-7672) The ZFS zoned property is not portable
Title: Message Title Moses Mendoza commented on PUP-7672 Re: The ZFS zoned property is not portable merged to master at https://github.com/puppetlabs/puppet/commit/756eff0f059d0a8f986a8cfe0608387dbf5f6b4e 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-7672) The ZFS zoned property is not portable
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7672 The ZFS zoned property is not portable Change By: Moses Mendoza Fix Version/s: PUP 5.4.0 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-7807) AIX mount resource remounts without options
Title: Message Title Moses Mendoza commented on PUP-7807 Re: AIX mount resource remounts without options merged to master at https://github.com/puppetlabs/puppet/commit/f74eb05897560c0a3bc7ef2ec3ea0083f96f34a5 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-7807) AIX mount resource remounts without options
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7807 AIX mount resource remounts without options Change By: Moses Mendoza Fix Version/s: PUP 5.4.0 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 (FACT-1759) facter should compute the correct logical and physical cpu count on Power for the processors.count and processors.physicalcount facts
Title: Message Title Enis Inan updated an issue Facter / FACT-1759 facter should compute the correct logical and physical cpu count on Power for the processors.count and processors.physicalcount facts Change By: Enis Inan Release Notes Summary: It was decided that the /sys/devices/system/cpu directory will compute only the physical CPU count, while the logical count is computed by incrementing the # of processor entries in /proc/cpuinfo 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 (PDB-3630) Configurable facts blacklist
Title: Message Title Zachary Kent assigned an issue to Zachary Kent PuppetDB / PDB-3630 Configurable facts blacklist Change By: Zachary Kent Assignee: Zachary Kent 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-8059) rake validate fails on modules with plans
Title: Message Title Gene Liverman created an issue Puppet / PUP-8059 rake validate fails on modules with plans Issue Type: Bug Affects Versions: PUP 5.3.2 Assignee: Unassigned Created: 2017/10/16 9:55 AM Environment: Bunder-based environment used by Travis CI Priority: Normal Reporter: Gene Liverman puppetlabs_spec_helper provides a task named validate that now fails on modules containing plans. I have traced the calls this makes down and it seems that, in the end, each .pp file in a project that is not excluded manually via PuppetSyntax.exclude_paths is passed to puppet parser validate via the code below: def validate_manifest(file) Puppet[:parser] = 'future' if
Jira (PUP-7987) Add support to defined top scope variables to the Pal API
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-7987 Add support to defined top scope variables to the Pal API Change By: Henrik Lindberg Assignee: Henrik Lindberg 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-8058) filebucket has a lack of authorization on puppet server side (extern)
Title: Message Title Andreas Papst created an issue Puppet / PUP-8058 filebucket has a lack of authorization on puppet server side (extern) Issue Type: Bug Affects Versions: PUP 4.10.8 Assignee: Unassigned Components: filebucket Created: 2017/10/16 8:23 AM Environment: all Priority: Minor Reporter: Andreas Papst Hello, I'd asked you for providing `puppet filebucket list` of external data (on puppet-server) too and digged into this issue to provide some ideas or maybe a draft. But for very good reasons it is not allowed to query an external filebucket list at the moment and more basic work is needed to accomplish this task. The crucial point is no limitation exists on accessing filebucket data. It has only "security through obscurity" and if a root user guesses the MD5 hash reading all files from all servers using filebucket is possible. An iteration attack is simple thus credentials and other confidential information could
Jira (FACT-1759) facter should compute the correct logical and physical cpu count on Power for the processors.count and processors.physicalcount facts
Title: Message Title John Duarte commented on FACT-1759 Re: facter should compute the correct logical and physical cpu count on Power for the processors.count and processors.physicalcount facts Enis Inan could you add a release note for this ticket. 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 (FACT-1759) facter should compute the correct logical and physical cpu count on Power for the processors.count and processors.physicalcount facts
Title: Message Title
John Duarte commented on FACT-1759
Re: facter should compute the correct logical and physical cpu count on Power for the processors.count and processors.physicalcount facts
Using puppet-agent at SHA 8b59b88 containing facter at SHA 4f136bc, the processors.count fact now matches the cpu count found in /proc/cpuinfo.
[root@power8-rhel73-3 ~]# facter processors.count
4
[root@power8-rhel73-3 ~]# facter processors
{
count => 4,
isa => "ppc64le",
models => [
"POWER8 (raw), altivec supported",
"POWER8 (raw), altivec supported",
Jira (FACT-1642) facter should understand cpu model on Power for the processors.model fact
Title: Message Title John Duarte commented on FACT-1642 Re: facter should understand cpu model on Power for the processors.model fact Enis Inan could you add a release note to this ticket. 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 (FACT-1642) facter should understand cpu model on Power for the processors.model fact
Title: Message Title
John Duarte commented on FACT-1642
Re: facter should understand cpu model on Power for the processors.model fact
Using puppet-agent at SHA 8b59b88 containing facter at SHA 4f136bc, the processors.count fact now matches the cpu count found in /proc/cpuinfo.
[root@power8-rhel73-3 ~]# facter processors.count
4
[root@power8-rhel73-3 ~]# facter processors
{
count => 4,
isa => "ppc64le",
models => [
"POWER8 (raw), altivec supported",
"POWER8 (raw), altivec supported",
Jira (FACT-1642) facter should understand cpu model on Power for the processors.model fact
Title: Message Title John Duarte updated an issue Facter / FACT-1642 facter should understand cpu model on Power for the processors.model fact Change By: John Duarte QA Risk Assessment: Automate Manual 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-8020) Add data types Nodes and Node to puppet for tasks/plans
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-8020 Add data types Nodes and Node to puppet for tasks/plans Change By: Thomas Hallgren Assignee: Henrik Lindberg 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 (HI-587) Enable testing hiera acceptance tests on platforms in FIPS mode
Title: Message Title Jayant Sane commented on HI-587 Re: Enable testing hiera acceptance tests on platforms in FIPS mode Valid question but it was indicated to me that there be a clean run through all PA CI pipeline tests (that happen to also include hiera tests) with agent hosts configured in FIPS mode for whoever to be able to accept the other FIPS related changes in all other affected repos plus I guess it is good to have our CI enabled to be able to test PA for FIPS on demand. All hiera changes would hopefully be confined to the acceptance test scripts - mainly the install step as against actual code. FIPS compliant PA is very desirable to some (potential) customers if it does not get mandated sometime in future, at least so am told, and it is an important deliverable on my plate. So the short answer is - Am doing it since PA 5.x uses whatever version(s) of hiera and has its own set of acceptance tests that are exercised in current CI which now need to run in FIPS mode. 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-8057) Ruby Rational data type matches RichData when it should not
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-8057 Ruby Rational data type matches RichData when it should not Change By: Henrik Lindberg Release Notes: Bug Fix 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-8057) Ruby Rational data type matches RichData when it should not
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-8057 Ruby Rational data type matches RichData when it should not Change By: Henrik Lindberg 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-8057) Ruby Rational data type matches RichData when it should not
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-8057 Ruby Rational data type matches RichData when it should not Issue Type: Bug Assignee: Unassigned Created: 2017/10/16 6:52 AM Fix Versions: PUP 4.10.z Priority: Normal Reporter: Henrik Lindberg The RichData type returns true for a ruby Rational value when it should return false. This is probably because it blindly accepts subtypes of ruby numeric. Add Comment
Jira (PUP-8056) Error type docs show new from hash - does not work as intended
Title: Message Title Henrik Lindberg commented on PUP-8056 Re: Error type docs show new from hash - does not work as intended merged to master and feature branch for task/plans 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-8050) puppet agent -e environment
Title: Message Title R.I.Pienaar commented on PUP-8050 Re: puppet agent -e environment yes, puppet apply has -e, clash would be bad -E perhaps but seems like a pit of dsispair 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-8056) Error type docs show new from hash - does not work as intended
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-8056 Error type docs show new from hash - does not work as intended Change By: Henrik Lindberg Method Found: Needs Assessment Customer Feedback 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-8050) puppet agent -e environment
Title: Message Title Henrik Lindberg commented on PUP-8050 Re: puppet agent -e environment There may be a risk of clashing with -e in other commands where e stands for evaluate. I think --environment is in long form for the sake of consistency. 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-3732) type validation should not run for `puppet resource`
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3732 type validation should not run for `puppet resource` Change By: Henrik Lindberg Component/s: Types and Providers 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-8056) Error type docs show new from hash - does not work as intended
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-8056 Error type docs show new from hash - does not work as intended Change By: Henrik Lindberg Assignee: Henrik Lindberg 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-8056) Error type docs show new from hash - does not work as intended
Title: Message Title Thomas Hallgren assigned an issue to Henrik Lindberg Puppet / PUP-8056 Error type docs show new from hash - does not work as intended Change By: Thomas Hallgren Assignee: Thomas Hallgren Henrik Lindberg 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-8056) Error type docs show new from hash - does not work as intended
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-8056 Error type docs show new from hash - does not work as intended Change By: Thomas Hallgren Fix Version/s: PUP 5.3.3 Fix Version/s: PUP 5.4.0 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 (HI-587) Enable testing hiera acceptance tests on platforms in FIPS mode
Title: Message Title Henrik Lindberg commented on HI-587 Re: Enable testing hiera acceptance tests on platforms in FIPS mode How important is this given that hiera 3 (the HI project) is deprecated? 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-8056) Error type docs show new from hash - does not work as intended
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-8056
Error type docs show new from hash - does not work as intended
Change By:
Henrik Lindberg
The plan error docs https://puppet.com/docs/bolt/0.5/writing_plans.html#returning-errors-in-plans suggest this would work:{code}plan mymodule::myplan { Error(message=> "Sorry, this plan does not work yet.",kind => 'mymodule/error',issue_code => 'NOT_IMPLEMENTED') }{code}This gives:{code}Error: Evaluation Error: Error while evaluating a Function Call, 'new_error' parameter 'message' expects a String value, got Struct at /home/rip/temp/bolts/mymod/plans/discover.pp:2:3 on node dev2.devco.net{code}Appears the code does not support that syntax it wants params of strings https://github.com/puppetlabs/puppet/blob/7fce55c2395df4c9547220169f82c97bb92b4574/lib/puppet/pops/types/p_error_type.rb#L59Henrik points out and I seem to recall that there's something that should allow a hash to be passed in and mapped to param names - this might be the actual thing thats broken (Henrik: yes this is an implementation 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
Jira (PUP-8056) Error type docs show new from hash - does not work as intended
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-8056 Error type docs show new from hash - does not work as intended Change By: Henrik Lindberg Release Notes Summary: The Error object did not support being initialized from a hash with arguments for the error object. It was only possible to give it the error message as a string. Sprint: Tasks Kanban Release Notes: Bug Fix 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-8056) Error type docs show new from hash - does not work as intended
Title: Message Title Henrik Lindberg commented on PUP-8056 Re: Error type docs show new from hash - does not work as intended The docs are correct, the implementation is wrong (and there is no test for the desired behaviour). 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-8056) Error type docs show new from hash - does not work as intended
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-8056 Error type docs show new from hash - does not work as intended Change By: Henrik Lindberg Fix Version/s: PUP 5.3.3 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-8056) Error type docs show new from hash - does not work as intended
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-8056 Error type docs show new from hash - does not work as intended Change By: Henrik Lindberg 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-8056) Error type docs show new from hash - does not work as intended
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-8056 Error type docs show new from hash - does not work as intended Change By: Henrik Lindberg Summary: Error type docs wrong show new from hash - does not work as intended 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-8056) Error type docs wrong
Title: Message Title
R.I.Pienaar updated an issue
Puppet / PUP-8056
Error type docs wrong
Change By:
R.I.Pienaar
The plan error docs https://puppet.com/docs/bolt/0.5/writing_plans.html#returning-errors-in-plans suggest this would work:{code}plan mymodule::myplan { Error(message=> "Sorry, this plan does not work yet.",kind => 'mymodule/error',issue_code => 'NOT_IMPLEMENTED') }{code} This gives:{code}Error: Evaluation Error: Error while evaluating a Function Call, 'new_error' parameter 'message' expects a String value, got Struct at /home/rip/temp/bolts/mymod/plans/discover.pp:2:3 on node dev2.devco.net{code} Appears the code does not support that syntax it wants params of strings https://github.com/puppetlabs/puppet/blob/7fce55c2395df4c9547220169f82c97bb92b4574/lib/puppet/pops/types/p_error_type.rb#L59 Henrik points out and I seem to recall that there's something that should allow a hash to be passed in and mapped to param names - this might be the actual thing thats broken
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-8056) Error type docs wrong
Title: Message Title
R.I.Pienaar created an issue
Puppet / PUP-8056
Error type docs wrong
Issue Type:
Bug
Assignee:
Unassigned
Created:
2017/10/16 4:41 AM
Priority:
Normal
Reporter:
R.I.Pienaar
The plan error docs https://puppet.com/docs/bolt/0.5/writing_plans.html#returning-errors-in-plans suggest this would work:
plan mymodule::myplan {
Error(
message=> "Sorry, this plan does not work yet.",
kind => 'mymodule/error',
