Jira (PUP-5109) Puppet::Resource::Catalog::Compiler#set_server_facts always produces a warning on ipv6 only systems
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5109 Puppet::Resource::Catalog::Compiler#set_server_facts always produces a warning on ipv6 only systems Change By: Josh Cooper Labels: IPv6 help_wanted 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.95553.144084808.10319.1558067041018%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9480) puppet unable to put ipv4+ipv6 dual stack hosts into /etc/hosts
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9480 puppet unable to put ipv4+ipv6 dual stack hosts into /etc/hosts Change By: Josh Cooper Labels: IPv6 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.295251.154953565.10313.1558066921156%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1298) manage_membership for unix groups provider
Title: Message Title Jarret Lavallee updated an issue Puppet / PUP-1298 manage_membership for unix groups provider Change By: Jarret Lavallee Team: Platform OS Puppet Romania 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.22682.1388437397000.10248.1558050841094%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1298) manage_membership for unix groups provider
Title: Message Title Jarret Lavallee updated an issue Puppet / PUP-1298 manage_membership for unix groups provider Change By: Jarret Lavallee CS Priority: Needs Priority 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.22682.1388437397000.10208.1558050480563%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9697) Solaris Crontabs -> puppet resource cron only returns root account
Title: Message Title Jarret Lavallee updated an issue Puppet / PUP-9697 Solaris Crontabs -> puppet resource cron only returns root account Change By: Jarret Lavallee CS Priority: Needs Priority 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308025.155742000.10170.1558049821284%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9697) Solaris Crontabs -> puppet resource cron only returns root account
Title: Message Title
Jarret Lavallee updated an issue
Puppet / PUP-9697
Solaris Crontabs -> puppet resource cron only returns root account
Change By:
Jarret Lavallee
*Puppet Version:2018.1.5* *Puppet Server Version:* *OS Name/Version: Oracle Linux 7 Solaris 11 *Unable to get a cron job from crontab for another user using `puppet resource cron` or `crontab -l` Solaris 11.This has been set with a .pp code through classification and it uses the `user` resource to set up the cron job. Example :crontab -l -> returns only jobs in the root crontab file.crontab -l username -> returns only cron jobs in the users crontab.Puppet Resource Cron will only return the root crontab. *Desired Behavior:*When running a puppet resource cron it should return all crontabs*Actual Behavior:*Only the root accounts crontab is returned on Solaris 11. Cron is created with pp code cron { 'my cron job': command => "my command", user => "someuser", }
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (FACT-1354) Facter ec2_userdata handles binary data incorrectly
Title: Message Title Jarret Lavallee updated an issue Facter / FACT-1354 Facter ec2_userdata handles binary data incorrectly Change By: Jarret Lavallee CS Priority: Needs Priority 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.119289.1456858282000.9984.1558047360485%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9689) String to integer conversion fails
Title: Message Title Jarret Lavallee updated an issue Puppet / PUP-9689 String to integer conversion fails Change By: Jarret Lavallee CS Priority: Needs Priority 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.306573.1556527664000.9975.1558047120458%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1925) fact pxe_boot => false after pxe-kexec
Title: Message Title Josh Cooper updated an issue Facter / FACT-1925 fact pxe_boot => false after pxe-kexec Change By: Josh Cooper Team: Puppet Romania 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308945.1558019544000.9940.1558045860155%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9706) Removing user on Solaris 11 with altered managehome
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9706 Removing user on Solaris 11 with altered managehome Change By: Josh Cooper Team: Puppet Romania 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308724.155793208.9929.1558044780398%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1166) Windows compatibility for orchestrator_client-ruby persistent http connections
Title: Message Title Thomas Kishel commented on BOLT-1166 Re: Windows compatibility for orchestrator_client-ruby persistent http connections Docs: https://puppet.com/docs/pe/2018.1/bolt_configure_orchestrator.html#adjust-the-orchestrator-configuration-files "Set up the orchestrator API for Bolt in the same configuration file that is used for PE client tools" is vague. 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.298616.1551895531000.9912.1558044480135%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9706) Removing user on Solaris 11 with altered managehome
Title: Message Title Robert August Vincent II commented on PUP-9706 Re: Removing user on Solaris 11 with altered managehome The problematic line is here. 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308724.155793208.9901.1558043580125%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4373) PDB has issues upgrading to versions later than 6.1 on centos6
Title: Message Title Zachary Kent created an issue PuppetDB / PDB-4373 PDB has issues upgrading to versions later than 6.1 on centos6 Issue Type: Bug Assignee: Unassigned Created: 2019/05/16 2:37 PM Priority: Normal Reporter: Zachary Kent During the PDB upgrade_oldest acceptance tests on centos6 for 6.3.x and master we try to upgrade the PDB package from 5.2.0 to the latest snapshot build 6.3.3-SNAPSHOT. This upgrade fails in our tests and results in PDB ending up in a state where running service puppetdb stop is unable to stop PDB and it must be killed by hand. This problem only appears to affect platforms which are running sysvinit and not systemd. It appears that due to changes with how PDB is invoked in later versions the main namespace provided via the -m argument has changed. In versions prior to PDB 6.1.0 the main namespace was puppetlabs.puppetdb.main in later versions it has changed to puppetlabs.puppetdb.cli.services. When testing upgrades from 5.2.0 -> 6.3.2 on a centos6 by hand I was able to see that the command service puppetdb stop was looking for the pid of PDB using the new main namespace when it was still running under the old name. One possibility is that the newer stop script is being run when trying to upgrade which is resulting in service not finding the old name and the right pid to kill. Repo: 1. install pdb 5.2.0 on centos6 2. grab a package version later than 6.1 3. yum install the package while pdb is running (this will put the upgrade in a broken state) 4. add a set -x to /opt/puppetlabs/server/apps/puppetdb/cli/apps/stop 5. run service puppetdb stop 6. compare the output from the pgrep call in the stop script to the main namespace pdb is being run under. We may need to make changes to lein-ezbake templates that create our stop/start scripts to account for the name change on platforms running sysvinit. see lein-ezbake templates Workaround in case anyone hits this issue before it is fixed: If you manually stop PDB before trying to install the upgraded package this issue can be avoided. If an upgrade was tried while PDB was running and you're in the state where service puppetdb stop can't find and stop PDB, finding th
Jira (BOLT-1316) The plan language should have a catch_errors functions
Title: Message Title
Alex Dreyer created an issue
Puppet Task Runner / BOLT-1316
The plan language should have a catch_errors functions
Issue Type:
New Feature
Assignee:
Unassigned
Created:
2019/05/16 2:22 PM
Priority:
Normal
Reporter:
Alex Dreyer
Sometimes a plan wants to execute a series of steps until one step fails then move on to some finalization or clean up actions. This can be handled by writing a subplan and calling run_plan with _catch_errors => true but sometimes this is less readable. Proposed solution: A catch_errors function that executes a block of code returning the final value or an Error if one was thrown.
$result_or_error = catch_errors([kind1, kind2]) ||{
run_task(task1)
run_task(task2)
run_task(task3)
}
Jira (BOLT-1315) Collect analytics about Boltdir usage
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-1315 Collect analytics about Boltdir usage Change By: Nick Lewis Sprint: Bolt 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309059.1558038203000.9695.1558038240509%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1315) Collect analytics about Boltdir usage
Title: Message Title Nick Lewis created an issue Puppet Task Runner / BOLT-1315 Collect analytics about Boltdir usage Issue Type: Improvement Assignee: Unassigned Created: 2019/05/16 1:23 PM Priority: Normal Reporter: Nick Lewis We should collect a data point about whether users are using a Boltdir, a local bolt.yaml, or ~/.puppetlabs/bolt. We should be able to include that as a custom dimension on the screen view that we send in the CLI. On the google analytics side, this can probably be tracked as a session-level metric, as a single user might have multiple projects potentially following different patterns, and we would like to know about that. Add Comment This message was sent by Atlassian JIRA
Jira (BOLT-1185) plan examples
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-1185 plan examples Change By: Cas Donoghue 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.300539.1552676543000.9641.1558037520393%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1297) Bolt should raise a nice error if the private key file doesn't exist
Title: Message Title Alex Dreyer assigned an issue to Alex Dreyer Puppet Task Runner / BOLT-1297 Bolt should raise a nice error if the private key file doesn't exist Change By: Alex Dreyer Assignee: Alex Dreyer 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.307991.1557409042000.9140.1558029060285%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9709) Puppet yum repo link broken
Title: Message Title Paul Hortiatis commented on PUP-9709 Re: Puppet yum repo link broken Looks like all of the PC1 repositories have been removed (yum and apt). There is an archive that may help for yum, but for apt the dist directory is not there, only the pool, which is a problem for mirroring it. http://release-archives.puppet.com/ 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308879.1558006404000.8890.1558024020270%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1265) target-lookup plugin to discover targets from a terraform state file.
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-1265 target-lookup plugin to discover targets from a terraform state file. Change By: Cas Donoghue Release Notes Summary: A new plugin was added to inventory v2 that can load terraform state and map resource properties to target parameters. This allows a terraform project to beused to dynamically determine the targets to use when running Bolt. Release Notes: New Feature 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.305931.1556035315000.8884.1558023780239%40Atlassian.JIRA. For more opt
Jira (BOLT-1265) target-lookup plugin to discover targets from a terraform state file.
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-1265 target-lookup plugin to discover targets from a terraform state file. Change By: Cas Donoghue Labels: docs 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.305931.1556035315000.8864.1558023540421%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1265) target-lookup plugin to discover targets from a terraform state file.
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-1265 target-lookup plugin to discover targets from a terraform state file. Change By: Cas Donoghue Fix Version/s: BOLT Next 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.305931.1556035315000.8867.1558023540561%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1314) tasks-hands-on-lab writing plan page improvements
Title: Message Title Randell Pelak created an issue Puppet Task Runner / BOLT-1314 tasks-hands-on-lab writing plan page improvements Issue Type: Improvement Assignee: Unassigned Created: 2019/05/16 9:08 AM Priority: Normal Reporter: Randell Pelak ON this page https://github.com/puppetlabs/tasks-hands-on-lab/tree/master/07-writing-plans This text: Use plans when you want to run several commands together across multiple nodes. For instance to remove a node from a load balancer before you deploy the new version of the application, or to clear a cache after you re-index a search engine. could use some improvement. When read it, my first thought was... tasks can already run several commands across multiple nodes. But I think what is trying to be communicated is that different sets of commands can be run on different nodes from one plan. Not sure how to make it say that though. Might need a docs person. Also, the other big win for plans is being able to apply puppet code, which should be mentioned in this section. And in the examples, the first thing I noticed is that the output of commands and tasks doesn't show up. This should be mentioned somewhere in text on this page because as a reader it was really obvious and I looked twice for something that explained why the output was missing (even though I already know roughly why, I thought I had missed a section). Probably mentioning that getting at the output is covered in advanced plans or something...
Jira (BOLT-836) Support Hiera lookup() in plans outside of apply blocks
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-836 Support Hiera lookup() in plans outside of apply blocks Change By: Alex Dreyer Summary: Support Hiera lookup() in plans outside of apply blocks 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.275693.1536882656000.8823.1558022280357%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1925) fact pxe_boot => false after pxe-kexec
Title: Message Title Andrew Sparrow commented on FACT-1925 Re: fact pxe_boot => false after pxe-kexec Bah; please ignore/close. This is a custom fact that hinges off of BOOT_IF (and only BOOT_IF). 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308945.1558019544000.8802.1558021140065%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1925) fact pxe_boot => false after pxe-kexec
Title: Message Title Andrew Sparrow created an issue Facter / FACT-1925 fact pxe_boot => false after pxe-kexec Issue Type: Bug Assignee: Unassigned Components: CLI, Community, DOCS Created: 2019/05/16 8:12 AM Environment: Debian 9.9 (Stretch) has facter 2.4.6 in the repos, Debian 8.11.0 ships facter 2.2.0. Happens with both/either. Labels: pxe facter debian Priority: Normal Reporter: Andrew Sparrow After running pxe-kexec to load initram/kernel and avoid lengthy BIOS wait, facter indicates "pxe_booted => false". Noticed this because a post-boot puppet one-shot attempted to install raid modules into initram. Haven't investigated, but this may be as simple as the presence of either BOOT_IMAGE or BOOTIF in /proc/cmdline being used as flags for a PXE booted host (these are not set after a initrd/kernel reload initiated by pxe-kexec and subsequent kexec)
Jira (BOLT-1306) Bolt 1.20.0 2019-05-16 Release
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1306 Bolt 1.20.0 2019-05-16 Release Issue Type: Task Assignee: Cas Donoghue Created: 2019/05/16 7:58 AM Priority: Normal Reporter: Cas Donoghue Bolt 1.20.0 2019-05-16 Release Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1308) Kick off release pipeline (Bolt 1.20.0)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1308 Kick off release pipeline (Bolt 1.20.0) Issue Type: Sub-task Assignee: Cas Donoghue Created: 2019/05/16 7:58 AM Due Date: 2019/05/16 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2019-05-16) With our shiny new automated builds pipeline, all you have to do is Go to https://jenkins-master-prod-1.delivery.puppetlabs.net/view/bolt/job/platform_bolt-vanagon_bolt-release-init_bolt-release/ Click "Build with Parameters" Check the PUBLIC checkbox Enter the version in the NEW_TAG box (x.y.z format) Click build! And make sure the pipeline is green! Add Comment
Jira (BOLT-1313) Send release announcements (Bolt 1.20.0)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1313 Send release announcements (Bolt 1.20.0) Issue Type: Sub-task Assignee: Melissa Amos Created: 2019/05/16 7:58 AM Due Date: 2019/05/16 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2019-05-16) Once docs have finished building (check that all links resolve appropriately) - Create an e-mail announcement with the subject "Bolt 1.20.0 now available". Include a summary of the release and links to the installation instructions and release notes. In the From: field, enter the Google account Puppet Product Updates (puppet-product-upda...@puppet.com). In the Bcc: field, enter the following addresses. Send a separate message to each: internal-puppet-product-upda...@puppet.com, puppet-us...@googlegroups.com, puppet-...@googlegroups.com, and puppet-annou...@googlegroups.com. If this release has security implications, also send to puppet-security-annou...@googlegroups.com. If you want, make a PSA on IRC and/or Slack, something along the lines of "PSA: Bolt 1.20.0 is now available".
Jira (BOLT-1312) Docs for bolt release (Bolt 1.20.0)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1312 Docs for bolt release (Bolt 1.20.0) Issue Type: Sub-task Assignee: Melissa Amos Created: 2019/05/16 7:58 AM Due Date: 2019/05/16 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2019-05-16) Release notes and docs changes for bolt 1.20.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1310) Update the release spreadsheet (Bolt 1.20.0)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1310 Update the release spreadsheet (Bolt 1.20.0) Issue Type: Sub-task Assignee: Cas Donoghue Created: 2019/05/16 7:58 AM Due Date: 2019/05/16 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2019-05-16) Update the release google spreadsheet for Bolt 1.20.0. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1307) Reconcile git commits, JIRA tickets, and versions (Bolt 1.20.0)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1307 Reconcile git commits, JIRA tickets, and versions (Bolt 1.20.0) Issue Type: Sub-task Assignee: Cas Donoghue Created: 2019/05/16 7:58 AM Due Date: 2019/05/16 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2019-05-16) Ensure all tickets referenced in the commit log have a bug targeted at the release, and ensure all tickets targeted at the release have a corresponding commit. You can do this manually by inspecting the git log and comparing against 'Project=Bolt and fixVersion="Bolt x.y.z"' in JIRA. Add Comment
Jira (BOLT-1309) Publish release artifacts (Bolt 1.20.0)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1309 Publish release artifacts (Bolt 1.20.0) Issue Type: Sub-task Assignee: Cas Donoghue Created: 2019/05/16 7:58 AM Due Date: 2019/05/16 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2019-05-16) Run the Bolt shipping pipeline. Set REF to 1.20.0. If you encounter any issues, ping the on-call person in the #release-new-new Slack channel. Add Comment This message was sent by Atlassian JIRA (v7.7.1#
Jira (BOLT-1311) Update homebrew-puppet (Bolt 1.20.0)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1311 Update homebrew-puppet (Bolt 1.20.0) Issue Type: Sub-task Assignee: Cas Donoghue Created: 2019/05/16 7:58 AM Due Date: 2019/05/16 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2019-05-16) Until we automate this, you'll also need to update the version and SHA hashes of https://github.com/puppetlabs/homebrew-puppet/blob/master/Casks/puppet-bolt.rb. To do this please Create a fork of the homebrew-puppet repo Create a new branch on that fork Run "rake 'brew:cask[puppet-bolt]'" Verify Casks/puppet-bolt.rb was updated to the correct version Put up a PR to homebrew-puppet and request review Add Comment
Jira (PUP-9711) Missing puppetlabs-release-el-6.noarch.rpm
Title: Message Title Enrico Vianello created an issue Puppet / PUP-9711 Missing puppetlabs-release-el-6.noarch.rpm Issue Type: Bug Assignee: Unassigned Created: 2019/05/16 6:56 AM Priority: Major Reporter: Enrico Vianello Got 404 on retrieving puppetlabs-release-el-6.noarch.rpm. Package seems disappeared. rpm -ivh http://yum.puppetlabs.com/puppetlabs-release-el-6.noarch.rpm Retrieving http://yum.puppetlabs.com/puppetlabs-release-el-6.noarch.rpm curl: (22) The requested URL returned error: 404 Not Found
Jira (FACT-1924) Investigate if FFI works on AIX/Solaris and Solaris-sparc
Title: Message Title Sebastian Miclea assigned an issue to Sebastian Miclea Facter / FACT-1924 Investigate if FFI works on AIX/Solaris and Solaris-sparc Change By: Sebastian Miclea Assignee: Sebastian Miclea 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308706.1557915892000.8675.1558014660295%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9710) Puppet yum repo unreachable
Title: Message Title Patrick Cardin created an issue Puppet / PUP-9710 Puppet yum repo unreachable Issue Type: Bug Assignee: Unassigned Created: 2019/05/16 6:47 AM Priority: Normal Reporter: Patrick Cardin Puppet Version: 3.7.3 Puppet Server Version: 3.7.3 OS Name/Version: Centos7/6 Since 2-3 days ago, we cant no longer access public yum repos from puppetlabs for 3.7.3 Desired Behavior: **we should be able to resolve: https://yum.puppetlabs.com/el/7/products/x86_64/ **Looks like the new puppet-release-el7 package that contains the the yum repo doest have puppet3.7.3... Actual Behavior: When we try to access the URL we get: 404 Not Found Code: NoSuchKey Message: The specified key does not exist. Key: el/7/products/x86_64/index_by_name.html RequestId: 364CE5CB0E471C7F HostId: upQmWVbqkUAGfgvYaPsbwsx03l/UGDCMGGX28CYU8c5Ad5Kui4fVdFjxClc/fFKIw2gRi94WeOo= Add Comment
Jira (PUP-9570) Catalog failure on first run due to pluginsync and environment switch
Title: Message Title
Josh Cooper commented on PUP-9570
Re: Catalog failure on first run due to pluginsync and environment switch
Ah sorry, my example was bad. You could get access to the current environment in the fact doing something like:
Facter.add(:pluginsync_environment) do
setcode do
env = Puppet.lookup(:current_environment) { nil }
env ? env.name.to_s : Puppet[:environment]
end
end
That said I think just adding a builtin pluginsync_environment fact is more direct. I'll put up a PR today.
Add Comment
Jira (FACT-1921) Facter java class incorrectly using "FACTERDIR" environment variable
Title: Message Title Thomas Montague commented on FACT-1921 Re: Facter java class incorrectly using "FACTERDIR" environment variable Yup, 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.307655.1557260973000.8529.1558008780180%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9709) Puppet yum repo link broken
Title: Message Title Valentyn Tymku created an issue Puppet / PUP-9709 Puppet yum repo link broken Issue Type: Bug Assignee: Unassigned Created: 2019/05/16 4:33 AM Priority: Critical Reporter: Valentyn Tymku https://yum.puppetlabs.com/puppetlabs-release-pc1-el-7.noarch.rpm http://yum.puppetlabs.com/el/7/PC1/x86_64/repodata/repomd.xml: are broken Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (FACT-1767) AIX processor facts return "mismatched processor frequencies found; facter will only report one of them" on every puppet run
Title: Message Title Jason Stewart updated an issue Facter / FACT-1767 AIX processor facts return "mismatched processor frequencies found; facter will only report one of them" on every puppet run Change By: Jason Stewart CS Priority: Normal Needs Priority 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.213798.1506692618000.8430.1557996360340%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1923) [SPIKE] investigate OS specific facts
Title: Message Title Oana Tanasoiu assigned an issue to Oana Tanasoiu Facter / FACT-1923 [SPIKE] investigate OS specific facts 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308667.1557907147000.8415.1557993960257%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
