Jira (PUP-2608) An error is logged during an agent run if the puppetmaster does not have at least one /lib dir in its modules directory.
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-2608
An error is logged during an agent run if the puppetmaster does not have at least one /lib dir in its modules directory.
Change By:
Josh Cooper
To reproduce:(Make sure you have a '127.0.0.1 localhost puppetmaster' entry in /etc/hosts for the below)In one terminal setup the master: {noformat} jpartlow@percival:~/work/puppet$ rm -rf ~/test/master/bug-testjpartlow@percival:~/work/puppet$ mkdir -p ~/test/master/bug-testjpartlow@percival:~/work/puppet$ bundle exec puppet master --no-daemonize --trace --autosign=true --debug --confdir=~/test/master/bug-test --vardir=~/test/master/bug-test --certname puppetmaster {noformat} In another terminal, run the agent: {noformat} jpartlow@percival:~/work/puppet$ be puppet agent -t --server puppetmasterInfo: Creating a new SSL key for percival.corp.puppetlabs.netInfo: Caching certificate for caInfo: Creating a new SSL certificate request for percival.corp.puppetlabs.netInfo: Certificate Request fingerprint (SHA256): 20:18:5A:F0:3B:A0:BE:76:6B:03:71:ED:BD:EF:47:04:F1:49:3F:BD:63:AC:42:3D:7E:0F:66:3F:08:F9:70:C9Info: Caching certificate for percival.corp.puppetlabs.netInfo: Caching certificate_revocation_list for caInfo: Retrieving pluginError: /File[/home/jpartlow/.puppet/var/lib]: Could not evaluate: Could not retrieve information from environment production source(s) puppet://puppetmaster/pluginsInfo: Caching catalog for percival.corp.puppetlabs.netInfo: Applying configuration version '1374537817'Info: Creating state file /home/jpartlow/.puppet/var/state/state.yaml {noformat}
Add Comment
Jira (PUP-2608) An error is logged during an agent run if the puppetmaster does not have at least one /lib dir in its modules directory.
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2608 An error is logged during an agent run if the puppetmaster does not have at least one /lib dir in its modules directory. Change By: Josh Cooper Attachment: Undeliverable_ Jira (PUP-2608) An error is logged during an agent run if the puppetmaster does not have at least one _module__lib dir in its modules directory. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.35962.1400279607000.81906.1591671480702%40Atlassian.JIRA.
Jira (PUP-2608) An error is logged during an agent run if the puppetmaster does not have at least one /lib dir in its modules directory.
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2608 An error is logged during an agent run if the puppetmaster does not have at least one /lib dir in its modules directory. Change By: Josh Cooper Comment: Renamed attached file: 'Undeliverable: Jira (PUP-2608) An error is logged during an agent run if the puppetmaster does not have at least one /lib dir in its modules directory.' to 'Undeliverable_ Jira (PUP-2608) An error is logged during an agent run if the puppetmaster does not have at least one _module__lib dir in its modules directory.' because it contained invalid character(s). Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.35962.1400279607000.81905.1591671480659%40Atlassian.JIRA.
Jira (PUP-2608) An error is logged during an agent run if the puppetmaster does not have at least one /lib dir in its modules directory.
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2608 An error is logged during an agent run if the puppetmaster does not have at least one /lib dir in its modules directory. Change By: Josh Cooper Comment: DisclaimerDit bericht met eventuele bijlagen is vertrouwelijk en uitsluitend bestemd voor de geadresseerde. Indien u niet de bedoelde ontvanger bent, wordt u verzocht de afzender te waarschuwen en dit bericht met eventuele bijlagen direct te verwijderen en/of te vernietigen. Het is niet toegestaan dit bericht en eventuele bijlagen te vermenigvuldigen, door te sturen, openbaar te maken, op te slaan of op andere wijze te gebruiken. Ordina N.V. en/of haar groepsmaatschappijen accepteren geen verantwoordelijkheid of aansprakelijkheid voor schade die voortvloeit uit de inhoud en/of de verzending van dit bericht.This e-mail and any attachments are confidential and are solely intended for the addressee. If you are not the intended recipient, please notify the sender and delete and/or destroy this message and any attachments immediately. It is prohibited to copy, to distribute, to disclose or to use this e-mail and any attachments in any other way. Ordina N.V. and/or its group companies do not accept any responsibility nor liability for any damage resulting from the content of and/or the transmission of this message.Delivery has failed to these recipients or groups:sebastian.hendri...@ordina.nlThe email address you entered couldn't be found. Please check the recipient's email address and try to resend the message. If the problem continues, please contact your helpdesk.Diagnostic information for administrators:Generating server: BA14-0165.work.localsebastian.hendri...@ordina.nlRemote Server returned '550 5.1.1 RESOLVER.ADR.RecipNotFound; not found'Original message headers:Received: from EUR01-HE1-obe.outbound.protection.outlook.com (213.199.154.208) by BA14-0165.work.local (172.16.0.163) with Microsoft SMTP Server (TLS) id 15.0.1236.3; Thu, 18 May 2017 19:45:31 +0200Received: from HE1PR0601CA0018.eurprd06.prod.outlook.com (2a01:111:e400:c513::28) by DB5PR06MB1703.eurprd06.prod.outlook.com (2a01:111:e400:7904::13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1084.16; Thu, 18 May 2017 17:45:29 +Received: from AM5EUR02FT061.eop-EUR02.prod.protection.outlook.com (2a01:111:f400:7e1e::203) by HE1PR0601CA0018.outlook.office365.com (2a01:111:e400:c513::28) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1101.14 via Frontend Transport; Thu, 18 May 2017 17:45:29 +Authentication-Results: spf=pass (sender IP is 50.31.32.210) smtp.mailfrom=sendgrid.puppet.com; ordina.nl; dkim=pass (signature was verified) header.d=puppet.com;ordina.nl; dmarc=pass action=""> header.from=puppet.com;Received-SPF: Pass (protection.outlook.com: domain of sendgrid.puppet.com designates 50.31.32.210 as permitted sender) receiver=protection.outlook.com; client-ip=50.31.32.210; helo=o1.em.puppetlabs.com;Received: from o1.em.puppetlabs.com (50.31.32.210) by AM5EUR02FT061.mail.protection.outlook.com (10.152.9.198) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.1075.5 via
Jira (PUP-2608) An error is logged during an agent run if the puppetmaster does not have at least one /lib dir in its modules directory.
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2608 An error is logged during an agent run if the puppetmaster does not have at least one /lib dir in its modules directory. Change By: Josh Cooper Comment: Renamed attached file: 'Undeliverable: Jira (PUP-2608) An error is logged during an agent run if the puppetmaster does not have at least one /lib dir in its modules directory.' to 'Undeliverable_ Jira (PUP-2608) An error is logged during an agent run if the puppetmaster does not have at least one _module__lib dir in its modules directory.' because it contained invalid character(s). Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.35962.1400279607000.81903.1591671480571%40Atlassian.JIRA.
Jira (PUP-2608) An error is logged during an agent run if the puppetmaster does not have at least one /lib dir in its modules directory.
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2608 An error is logged during an agent run if the puppetmaster does not have at least one /lib dir in its modules directory. Change By: Josh Cooper Attachment: Undeliverable_ Jira (PUP-2608) An error is logged during an agent run if the puppetmaster does not have at least one _module__lib dir in its modules directory. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.35962.1400279607000.81908.1591671480790%40Atlassian.JIRA.
Jira (PUP-2608) An error is logged during an agent run if the puppetmaster does not have at least one /lib dir in its modules directory.
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2608 An error is logged during an agent run if the puppetmaster does not have at least one /lib dir in its modules directory. Change By: Josh Cooper Comment: DisclaimerDit bericht met eventuele bijlagen is vertrouwelijk en uitsluitend bestemd voor de geadresseerde. Indien u niet de bedoelde ontvanger bent, wordt u verzocht de afzender te waarschuwen en dit bericht met eventuele bijlagen direct te verwijderen en/of te vernietigen. Het is niet toegestaan dit bericht en eventuele bijlagen te vermenigvuldigen, door te sturen, openbaar te maken, op te slaan of op andere wijze te gebruiken. Ordina N.V. en/of haar groepsmaatschappijen accepteren geen verantwoordelijkheid of aansprakelijkheid voor schade die voortvloeit uit de inhoud en/of de verzending van dit bericht.This e-mail and any attachments are confidential and are solely intended for the addressee. If you are not the intended recipient, please notify the sender and delete and/or destroy this message and any attachments immediately. It is prohibited to copy, to distribute, to disclose or to use this e-mail and any attachments in any other way. Ordina N.V. and/or its group companies do not accept any responsibility nor liability for any damage resulting from the content of and/or the transmission of this message.Delivery has failed to these recipients or groups:sebastian.hendri...@ordina.nlThe email address you entered couldn't be found. Please check the recipient's email address and try to resend the message. If the problem continues, please contact your helpdesk.Diagnostic information for administrators:Generating server: BA14-0165.work.localsebastian.hendri...@ordina.nlRemote Server returned '550 5.1.1 RESOLVER.ADR.RecipNotFound; not found'Original message headers:Received: from EUR01-HE1-obe.outbound.protection.outlook.com (213.199.154.210) by BA14-0165.work.local (172.16.0.163) with Microsoft SMTP Server (TLS) id 15.0.1236.3; Tue, 16 May 2017 00:18:09 +0200Received: from DB6PR0601CA0022.eurprd06.prod.outlook.com (2603:10a6:4:7b::32) by HE1PR06MB1705.eurprd06.prod.outlook.com (2a01:111:e400:7a29::15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1084.16; Mon, 15 May 2017 22:18:07 +Received: from AM5EUR02FT008.eop-EUR02.prod.protection.outlook.com (2a01:111:f400:7e1e::209) by DB6PR0601CA0022.outlook.office365.com (2603:10a6:4:7b::32) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1084.16 via Frontend Transport; Mon, 15 May 2017 22:18:06 +Authentication-Results: spf=pass (sender IP is 50.31.32.210) smtp.mailfrom=sendgrid.puppet.com; ordina.nl; dkim=pass (signature was verified) header.d=puppet.com;ordina.nl; dmarc=pass action=""> header.from=puppet.com;Received-SPF: Pass (protection.outlook.com: domain of sendgrid.puppet.com designates 50.31.32.210 as permitted sender) receiver=protection.outlook.com; client-ip=50.31.32.210; helo=o1.em.puppetlabs.com;Received: from o1.em.puppetlabs.com (50.31.32.210) by AM5EUR02FT008.mail.protection.outlook.com (10.152.8.69) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.1075.5 via Frontend
Jira (PUP-2608) An error is logged during an agent run if the puppetmaster does not have at least one /lib dir in its modules directory.
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2608 An error is logged during an agent run if the puppetmaster does not have at least one /lib dir in its modules directory. Change By: Josh Cooper Comment: DisclaimerDit bericht met eventuele bijlagen is vertrouwelijk en uitsluitend bestemd voor de geadresseerde. Indien u niet de bedoelde ontvanger bent, wordt u verzocht de afzender te waarschuwen en dit bericht met eventuele bijlagen direct te verwijderen en/of te vernietigen. Het is niet toegestaan dit bericht en eventuele bijlagen te vermenigvuldigen, door te sturen, openbaar te maken, op te slaan of op andere wijze te gebruiken. Ordina N.V. en/of haar groepsmaatschappijen accepteren geen verantwoordelijkheid of aansprakelijkheid voor schade die voortvloeit uit de inhoud en/of de verzending van dit bericht.This e-mail and any attachments are confidential and are solely intended for the addressee. If you are not the intended recipient, please notify the sender and delete and/or destroy this message and any attachments immediately. It is prohibited to copy, to distribute, to disclose or to use this e-mail and any attachments in any other way. Ordina N.V. and/or its group companies do not accept any responsibility nor liability for any damage resulting from the content of and/or the transmission of this message.Delivery has failed to these recipients or groups:sebastian.hendri...@ordina.nlThe email address you entered couldn't be found. Please check the recipient's email address and try to resend the message. If the problem continues, please contact your helpdesk.Diagnostic information for administrators:Generating server: BA14-0165.work.localsebastian.hendri...@ordina.nlRemote Server returned '550 5.1.1 RESOLVER.ADR.RecipNotFound; not found'Original message headers:Received: from EUR01-HE1-obe.outbound.protection.outlook.com (213.199.154.211) by BA14-0165.work.local (172.16.0.163) with Microsoft SMTP Server (TLS) id 15.0.1236.3; Tue, 16 May 2017 00:18:09 +0200Received: from HE1PR0601CA0015.eurprd06.prod.outlook.com (10.166.117.25) by VI1PR06MB1840.eurprd06.prod.outlook.com (10.165.237.158) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1084.16; Mon, 15 May 2017 22:18:07 +Received: from HE1EUR02FT063.eop-EUR02.prod.protection.outlook.com (2a01:111:f400:7e05::208) by HE1PR0601CA0015.outlook.office365.com (2a01:111:e400:c513::25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1084.16 via Frontend Transport; Mon, 15 May 2017 22:18:07 +Authentication-Results: spf=pass (sender IP is 50.31.32.210) smtp.mailfrom=sendgrid.puppet.com; ordina.nl; dkim=pass (signature was verified) header.d=puppet.com;ordina.nl; dmarc=pass action=""> header.from=puppet.com;Received-SPF: Pass (protection.outlook.com: domain of sendgrid.puppet.com designates 50.31.32.210 as permitted sender) receiver=protection.outlook.com; client-ip=50.31.32.210; helo=o1.em.puppetlabs.com;Received: from o1.em.puppetlabs.com (50.31.32.210) by HE1EUR02FT063.mail.protection.outlook.com (10.152.11.211) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.1075.5 via Frontend
Jira (PUP-2608) An error is logged during an agent run if the puppetmaster does not have at least one /lib dir in its modules directory.
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2608 An error is logged during an agent run if the puppetmaster does not have at least one /lib dir in its modules directory. Change By: Josh Cooper Comment: Renamed attached file: 'Undeliverable: Jira (PUP-2608) An error is logged during an agent run if the puppetmaster does not have at least one /lib dir in its modules directory.' to 'Undeliverable_ Jira (PUP-2608) An error is logged during an agent run if the puppetmaster does not have at least one _module__lib dir in its modules directory.' because it contained invalid character(s). Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.35962.1400279607000.81901.1591671480479%40Atlassian.JIRA.
Jira (PUP-2608) An error is logged during an agent run if the puppetmaster does not have at least one /lib dir in its modules directory.
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2608 An error is logged during an agent run if the puppetmaster does not have at least one /lib dir in its modules directory. Change By: Josh Cooper Attachment: Undeliverable_ Jira (PUP-2608) An error is logged during an agent run if the puppetmaster does not have at least one _module__lib dir in its modules directory. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.35962.1400279607000.81907.1591671480747%40Atlassian.JIRA.
Jira (PUP-10528) Extend the trusted_external_command setting to support specifying directories
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10528 Extend the trusted_external_command setting to support specifying directories Change By: Josh Cooper Fix Version/s: PUP 6.17.0 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.359569.159008843.81894.1591670940044%40Atlassian.JIRA.
Jira (PUP-10528) Extend the trusted_external_command setting to support specifying directories
Title: Message Title Josh Cooper commented on PUP-10528 Re: Extend the trusted_external_command setting to support specifying directories Merged to master in https://github.com/puppetlabs/puppet/commit/732ae5f07d4e2ef5dcadbb0bd36c30c0f677dc8a Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.359569.159008843.81895.1591670940100%40Atlassian.JIRA.
Jira (PUP-7141) Refactor required string dup in 3x runtime converter
Title: Message Title Josh Cooper commented on PUP-7141 Re: Refactor required string dup in 3x runtime converter A follow-up PR was merged in bd870bf21bac6979b8adc550c85d446f1e8c8aff Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.172448.1485535001000.81645.1591653240028%40Atlassian.JIRA.
Jira (PUP-9251) Deprecate 'application orchestration' features
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-9251 Deprecate 'application orchestration' features Change By: Josh Cooper Assignee: Josh Cooper Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.281366.1539943536000.81421.1591643460099%40Atlassian.JIRA.
Jira (PUP-9251) Deprecate 'application orchestration' features
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9251 Deprecate 'application orchestration' features Change By: Josh Cooper Sprint: Coremunity Hopper Platform Core KANBAN Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.281366.1539943536000.81420.1591643460055%40Atlassian.JIRA.
Jira (PUP-6645) Remove the hiera_xxx functions
Title: Message Title Lee Lowder commented on PUP-6645 Re: Remove the hiera_xxx functions One feature present in the hiera functions that are missing from lookup() is hiera's little known third argument - an alternate lookup path to used that overrides the lookup path defined in hiera.yaml. This allowed us to, for example, override the lookup path on our pgpool nodes to pull some data specified in a yaml file specific to a given postgresql cluster. With the new method, we were told this is not possible, we have to restructure our hierarchy and use some sort of shared file. This, however, requires considerable effort to execute properly as have have to find a way to have a file that is shared across two different roles, but still confined to a given group, lifecyle, and cluster (these are fact based layers or pieces to our current hierarchy) so that we can not have to enter the same data over and over but also not have the data leak into places it shouldn't be (i.e. a different PG cluster). We face a similar issue with keepalived/haproxy/apache/tomcat type application stacks with pieces of configuration that need to be shared between them in a DRY manner. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.148538.1471963467000.81410.1591643220025%40Atlassian.JIRA.
Jira (PUP-10525) puppet apply should set trusted['external']
Title: Message Title Josh Cooper commented on PUP-10525 Re: puppet apply should set trusted['external'] Moving to main means the command will be executed for all other puppet applications that try to load a Node object. I'd expect that to affect puppet device and maybe puppet resource. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.359456.1590012226000.81383.1591642200041%40Atlassian.JIRA.
Jira (PUP-8650) Repository error message uri is missing part of the path
Title: Message Title Josh Cooper commented on PUP-8650 Re: Repository error message uri is missing part of the path As of 6.16.0 the puppet module search action is deprecated, but the same problem exists when trying to install a module: bx puppet module --debug --module_repository https://artifactory.domain.com/bogus_test/puppet/ install nope/test Debug: Runtime environment: puppet_version=6.17.0, ruby_version=2.5.7, run_mode=user, default_encoding=UTF-8 Notice: Preparing to install into /Users/josh/.puppetlabs/etc/code/environments/production/modules ... Notice: Downloading from https://artifactory.domain.com/bogus_test/puppet/ ... Debug: HTTP GET https://artifactory.domain.com/bogus_test/puppet/v3/releases?module=nope-test_by=version_fields=readme%2Cchangelog%2Clicense%2Curi%2Cmodule%2Ctags%2Csupported%2Cfile_size%2Cdownloads%2Ccreated_at%2Cupdated_at%2Cdeleted_at returned 404 Not Found Debug: Caching connection for https://artifactory.domain.com:443 Error: Request to Puppet Forge failed. The server being queried was https://artifactory.domain.com/v3/releases?module=nope-test_by=version_fields=readme,changelog,license,uri,module,tags,supported,file_size,downloads,created_at,updated_at,deleted_at The HTTP response we received was '404 Not Found' The double // issue mentioned above is fixed, but not the "The server being queried" error message. That
Jira (PUP-7197) make type aliases from modules available on the agent
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7197 make type aliases from modules available on the agent Change By: Josh Cooper Issue Type: Story New Feature Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.174775.1486632721000.81346.159164166%40Atlassian.JIRA.
Jira (PUP-8200) No docs to run Puppet 4, 5, or 6 from source
Title: Message Title Josh Cooper commented on PUP-8200 Re: No docs to run Puppet 4, 5, or 6 from source Passed CI in f6e4dab7be83540dcca07f87398a7127a221d83b Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.223720.1511376216000.81341.1591640640090%40Atlassian.JIRA.
Jira (PUP-5823) Puppet agent with splay on windows begets random interval between runs
Title: Message Title Kevin Reeuwijk commented on PUP-5823 Re: Puppet agent with splay on windows begets random interval between runs This issue causes runtimes to get reported as abnormal for Windows runs, see attached screenshot. When looker deeper at the metrics, the "Agent startup time (sec)" erroneously includes the splay wait time. The actual puppet run took a normal amount of seconds, but in the higher level reporting this is no longer visible. Especially on Windows, long agent runs are important to spot. Windows patching can cause a long puppet run, so when I first saw these long runtimes, I was worried all my nodes were continuously re-applying patches or something. With the current state, the agent runtime metric becomes completely useless, and will admins to disable splay. Please look at fixing this issue as we get more Windows customers. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.115341.1454671876000.81284.1591639080089%40Atlassian.JIRA.
Jira (PUP-8600) plugin-sync the data-types from all modules
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8600 plugin-sync the data-types from all modules Change By: Josh Cooper Currently deferred functions can only use types that are built into puppet such as String, etc, but it can't use types from modules such as stdlib, because puppet does not pluginsync those types to the agent. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.242740.1521815941000.81282.1591639020048%40Atlassian.JIRA.
Jira (PUP-5823) Puppet agent with splay on windows begets random interval between runs
Title: Message Title Kevin Reeuwijk updated an issue Puppet / PUP-5823 Puppet agent with splay on windows begets random interval between runs Change By: Kevin Reeuwijk Attachment: agent_startup_time.png Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.115341.1454671876000.81278.1591638840200%40Atlassian.JIRA.
Jira (PUP-5823) Puppet agent with splay on windows begets random interval between runs
Title: Message Title Kevin Reeuwijk updated an issue Puppet / PUP-5823 Puppet agent with splay on windows begets random interval between runs Change By: Kevin Reeuwijk Attachment: runtimes_windows.png Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.115341.1454671876000.81277.1591638840146%40Atlassian.JIRA.
Jira (PUP-10540) Performance of puppet grows worse as the size of /proc/mounts increases
Title: Message Title
Michele Baldessari updated an issue
Puppet / PUP-10540
Performance of puppet grows worse as the size of /proc/mounts increases
Change By:
Michele Baldessari
*Puppet Version: puppet-5.5.10-5.el8ost**Puppet Server Version: N/A**OS Name/Version: Centos 8*A system that has many containers (~1000) will make /proc/mounts rather large (700-900 kbytes). Running any trivial puppet command will take a very long time there due to the following line:https://github.com/puppetlabs/puppet/blob/master/lib/puppet/util/selinux.rb#L210In there we're reading /proc/mounts 1024 bytes at the time, which is clearly suboptimal in this case (but also in most default cases as /proc/mounts is rarely < 1024 bytes these days on most modern linux systems).On such an environment we will observe:[root@database-0 ~]# time puppet apply --noop --detailed-exitcodes --color=false -e 'file {"/tmp/foobar": content => "baz" }'Notice: Compiled catalog for database-0.redhat.local in environment production in 0.16 secondsNotice: /Stage[main]/Main/File[/tmp/foobar]/ensure: current_value absent, should be file (noop)Notice: Class[Main]: Would have triggered 'refresh' from 1 eventsNotice: Stage[main]: Would have triggered 'refresh' from 1 eventsNotice: Applied catalog in 0.05 secondsreal5m43.258suser5m7.929ssys 0m5.603sIncreasing the read size to 1024 ** 2 provides immediate benefits:[root@database-0 ~]# time puppet apply --noop --detailed-exitcodes --color=false -e 'file {"/tmp/foobar": content => "baz" }'Notice: Compiled catalog for database-0.redhat.local in environment production in 0.11 secondsNotice: /Stage[main]/Main/File[/tmp/foobar]/ensure: current_value absent, should be file (noop)Notice: Class[Main]: Would have triggered 'refresh' from 1 eventsNotice: Stage[main]: Would have triggered 'refresh' from 1 eventsNotice: Applied catalog in 0.13 secondsreal1m22.954suser0m50.423ssys 0m5.115sIn such an environment strace confirms that the number of small read() calls goes from:[root@database-0 ~]# grep -ir -e 'read(7.*1024' /tmp/strace-puppet.txt |wc -l231381To:[root@database-0 ~]# grep -ir -e 'read(7.*1024' /tmp/strace-puppet-after.txt |wc -l810
Add Comment
Jira (PUP-7791) No useful debug output for yum/rpm provider success/failure/version information
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-7791 No useful debug output for yum/rpm provider success/failure/version information Change By: Mihai Buzgau Sprint: PR - Triage Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.201571.150057424.81172.1591635360041%40Atlassian.JIRA.
Jira (PUP-10540) Performance of puppet grows worse as the size of /proc/mounts increases
Title: Message Title
Michele Baldessari created an issue
Puppet / PUP-10540
Performance of puppet grows worse as the size of /proc/mounts increases
Issue Type:
Bug
Assignee:
Unassigned
Created:
2020/06/08 9:40 AM
Priority:
Normal
Reporter:
Michele Baldessari
Puppet Version: puppet-5.5.10-5.el8ost Puppet Server Version: N/A OS Name/Version: Centos 8 A system that has many containers (~1000) will make /proc/mounts rather large (700-900 kbytes). Running any trivial puppet command will take a very long time there due to the following line: https://github.com/puppetlabs/puppet/blob/master/lib/puppet/util/selinux.rb#L210 In there we're reading /proc/mounts 1024 bytes at the time, which is clearly suboptimal in this case (but also in most default cases as /proc/mounts is rarely < 1024 bytes these days on most modern linux systems). On such an environment we will observe: [root@database-0 ~]# time puppet apply --noop --detailed-exitcodes --color=false -e 'file {"/tmp/foobar": content => "baz" } ' Notice: Compiled catalog for database-0.redhat.local in environment production in 0.16 seconds Notice: /Stage[main]/Main/File[/tmp/foobar]/ensure: current_value absent, should be file (noop) Notice: Class[Main]: Would have triggered 'refresh' from 1 events Notice: Stage[main]: Would have triggered 'refresh' from 1 events Notice: Applied catalog in 0.05 seconds real 5m43.258s user 5m7.929s sys 0m5.603s Increasing the read size to 1024 ** 2 provides immediate benefits: [root@database-0 ~]# time puppet apply --noop --detailed-exitcodes --color=false -e 'file {"/tmp/foobar": content => "baz" } ' Notice: Compiled catalog for database-0.redhat.local in environment production in 0.11 seconds Notice: /Stage[main]/Main/File[/tmp/foobar]/ensure: current_value absent, should be file (noop) Notice: Class[Main]: Would have triggered 'refresh' from 1 events Notice: Stage[main]: Would have triggered 'refresh' from 1 events Notice: Applied catalog in 0.13 seconds real 1m22.954s user 0m50.423s sys 0m5.115s In such an environment strace confirms that the number of small read() calls goes from: [root@database-0 ~]# grep -ir -e 'read(7.*1024' /tmp/strace-puppet.txt |wc -l 231381 To: [root@database-0 ~]#
Jira (PUP-8014) Create an environment_ttl setting to clear short-lived puppet environments from memory
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8014 Create an environment_ttl setting to clear short-lived puppet environments from memory Change By: Josh Cooper Epic Link: PUP-7563 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.214193.1506980344000.81150.1591634220324%40Atlassian.JIRA.
Jira (PDB-4781) PuppetDB deb should depend on Java 11 or Java 8
Title: Message Title
Simon Deziel updated an issue
PuppetDB / PDB-4781
PuppetDB deb should depend on Java 11 or Java 8
Change By:
Simon Deziel
According to the [release notes|https://puppet.com/docs/puppetdb/latest/release_notes.html#puppetdb-6110], Java 11 is the preferred version and Java 8 is considered deprecated. Yet, the deb package still tries to pull Java 8: {code:shell} # apt-cache show puppetdb | head | grep -E '^(Package|Version|Depends):' Package: puppetdb Version: 6.11.0-1bionic Depends: openjdk-8-jre-headless, bash, net-tools, adduser, procps, puppet-agent (>= 5.99.0){code} Ideally, the Depends should have "openjdk-11-jre-headless| openjdk-8-jre-headless".
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
--
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
Jira (PDB-4781) PuppetDB deb should depend on Java 11 or Java 8
Title: Message Title Simon Deziel created an issue PuppetDB / PDB-4781 PuppetDB deb should depend on Java 11 or Java 8 Issue Type: Bug Affects Versions: PDB 6.11.0 Assignee: Unassigned Created: 2020/06/08 8:03 AM Environment: Ubuntu 18.04 LTS 64 bit # apt-cache policy puppetdb | head puppetdb: Installed: 6.11.0-1bionic Candidate: 6.11.0-1bionic Version table: *** 6.11.0-1bionic 500 500 http://apt.puppetlabs.com bionic/puppet6 amd64 Packages 500 http://apt.puppetlabs.com bionic/puppet6 all Packages 100 /var/lib/dpkg/status
