Jira (PUP-10677) Gem provider should install gems on the system ruby on Windows
Title: Message Title Nick Walker updated an issue Puppet / PUP-10677 Gem provider should install gems on the system ruby on Windows Change By: Nick Walker Summary: Gem provider should install gems on the system ruby on Windows 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.361146.1591175992000.91831.1607116560043%40Atlassian.JIRA.
Jira (PUP-10812) Remove CA dir deprecation warning from settings defaults
Title: Message Title Molly Waggett updated an issue Puppet / PUP-10812 Remove CA dir deprecation warning from settings defaults Change By: Molly Waggett We added a warning to the CA dir setting that logs when it is configured to be inside the SSL dir. This warning is way too noisy, and we are going to remove it, in favor of just warning on server startup [INSERT LINK TO CODE HERE] and from the CA CLI tool (this is already in place).Warning to remove: [https://github.com/puppetlabs/puppet/blob/main/lib/puppet/defaults.rb#L35-L47]Add similar warning that is logged in the server logs on startup. [INSERT LINK TO CODE HERE] 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/JIR
Jira (PUP-10812) Remove CA dir deprecation warning from settings defaults
Title: Message Title Cas Donoghue updated an issue Puppet / PUP-10812 Remove CA dir deprecation warning from settings defaults Change By: Cas Donoghue Story Points: 2 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.379969.1607106146000.91768.1607109540030%40Atlassian.JIRA.
Jira (PUP-10812) Remove CA dir deprecation warning from settings defaults
Title: Message Title Cas Donoghue updated an issue Puppet / PUP-10812 Remove CA dir deprecation warning from settings defaults Change By: Cas Donoghue We added a warning to the CA dir setting that logs when it is configured to be inside the SSL dir. This warning is way too noisy, and we are going to remove it, in favor of just warning on server startup (this might still need to be added) [INSERT LINK TO CODE HERE] and from the CA CLI tool (this is already in place).Warning to remove: [ https://github.com/puppetlabs/puppet/blob/main/lib/puppet/defaults.rb#L35-L47 ]Add similar warning that is logged in the server logs on startup. 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/puppe
Jira (PUP-10812) Remove CA dir deprecation warning from settings defaults
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10812 Remove CA dir deprecation warning from settings defaults Change By: Josh Cooper Labels: platform_7.1 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.379969.1607106146000.91757.1607108760028%40Atlassian.JIRA.
Jira (FACT-2882) Gem-based Facter 4.0.x does not return the complete FQDN
Title: Message Title Sanjay Tripathi commented on FACT-2882 Re: Gem-based Facter 4.0.x does not return the complete FQDN Okay, I will omit this template in future tickets. I also would like to mention that this problem of incorrect/incomplete FQDN occurs on Windows 2016 (because the domain fact returns empty string). I don't know if it works on other OS but I have only run my tests in Windows. 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.379598.1606874598000.91728.1607106960186%40Atlassian.JIRA.
Jira (PUP-10792) How to set token for https url when using puppet file resource
Title: Message Title Josh Cooper commented on PUP-10792 Re: How to set token for https url when using puppet file resource Does curl -vv 'https://test.blob.core.chinacloudapi.cn/test/key_password.txt?sv=2020-02-10&si=1&sr=c&sig=t9ZbB0tL3q8AtFATbw1HdF/zXhp0%3' work? Can you include the output? 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.379148.1606203494000.91708.1607106360178%40Atlassian.JIRA.
Jira (PUP-10812) Remove CA dir deprecation warning from settings defaults
Title: Message Title Maggie Dreyer created an issue Puppet / PUP-10812 Remove CA dir deprecation warning from settings defaults Issue Type: Task Assignee: Unassigned Created: 2020/12/04 10:22 AM Priority: Normal Reporter: Maggie Dreyer We added a warning to the CA dir setting that logs when it is configured to be inside the SSL dir. This warning is way too noisy, and we are going to remove it, in favor of just warning on server startup (this might still need to be added) and from the CA CLI tool (this is already in place). Warning to remove: https://github.com/puppetlabs/puppet/blob/main/lib/puppet/defaults.rb#L35-L47 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PDB-4971) PDB terminus generates a warning on ruby 2.7
Title: Message Title Josh Cooper updated an issue PuppetDB / PDB-4971 PDB terminus generates a warning on ruby 2.7 Change By: Josh Cooper Labels: platform_7.1 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.378969.1605830582000.91696.1607105280031%40Atlassian.JIRA.
Jira (PUP-10800) Add logonaccount and logonpassword to windows service provider example
Title: Message Title Claire Cadman assigned an issue to Claire Cadman Puppet / PUP-10800 Add logonaccount and logonpassword to windows service provider example Change By: Claire Cadman Assignee: Claire Cadman 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.379820.1607016894000.91583.1607098620028%40Atlassian.JIRA.
Jira (PUP-10800) Add logonaccount and logonpassword to windows service provider example
Title: Message Title
Claire Cadman commented on PUP-10800
Re: Add logonaccount and logonpassword to windows service provider example
I'll add an example to the end of here: https://puppet.com/docs/puppet/7.0/resources_service.html#service_windows Maybe something like the following?: Puppet 7 adds support for managing the logon user and password to the Windows service provider. For example:
service { 'name-of-service':
ensure => 'running',
enable => 'true',
logonaccount => 'domain\\user',
logonpassword => $password,
}
Add Comment
Jira (FACT-2081) Facter virtual and is_virtual are worng
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2081 Facter virtual and is_virtual are worng Change By: Mihai Buzgau Labels: help_wanted 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.331929.1571915917000.91568.1607097780209%40Atlassian.JIRA.
Jira (FACT-2081) Facter virtual and is_virtual are worng
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2081 Facter virtual and is_virtual are worng Change By: Mihai Buzgau Sprint: ready for 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.331929.1571915917000.91569.1607097780256%40Atlassian.JIRA.
Jira (PUP-10498) host resources don't support stock Linux configurations
Title: Message Title Josh Cooper commented on PUP-10498 Re: host resources don't support stock Linux configurations This is actually a dup of 9480, closing. 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.358196.1589201636000.91516.1607096100085%40Atlassian.JIRA.
Jira (PUP-10800) Add logonaccount and logonpassword to windows service provider example
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10800 Add logonaccount and logonpassword to windows service provider example Change By: Mihai Buzgau Sprint: Triaged tickets 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.379820.1607016894000.91509.1607095620104%40Atlassian.JIRA.
Jira (PUP-10800) Add logonaccount and logonpassword to windows service provider example
Title: Message Title Mihai Buzgau assigned an issue to Unassigned Puppet / PUP-10800 Add logonaccount and logonpassword to windows service provider example Change By: Mihai Buzgau Assignee: Claire Cadman 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.379820.1607016894000.91510.1607095620147%40Atlassian.JIRA.
Jira (PUP-10798) Unable to install rpm packages via provides of the package
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10798 Unable to install rpm packages via provides of the package Change By: Mihai Buzgau Sprint: Triaged tickets 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.379779.1606993694000.91502.1607095440048%40Atlassian.JIRA.
Jira (FACT-2882) Gem-based Facter 4.0.x does not return the complete FQDN
Title: Message Title Josh Cooper commented on FACT-2882 Re: Gem-based Facter 4.0.x does not return the complete FQDN Hi Sanjay Tripathi it looks like you're using the "New os support on traditional module" template to file new tickets. Can you omit the template for any new tickets you file? Thanks! 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.379598.1606874598000.91503.1607095440092%40Atlassian.JIRA.
Jira (FACT-2882) Gem-based Facter 4.0.x does not return the complete FQDN
Title: Message Title Josh Cooper updated an issue Facter / FACT-2882 Gem-based Facter 4.0.x does not return the complete FQDN Change By: Josh Cooper The gem-based facter 4.0.x does not return the correct fqdn – it returns the hostname with dot instead of returning hostname with the domain suffix.Example: facter fqdn Output:myhostname.The correct output: myhostname.mydomain.comThis breaks scripts which issue http request to the fqdn (like: [http://myhostname.:1234|http://myhostname.:1234/] is not reachable). Add new os support on litmus modules*Before to start, make sure the new platform is provided by vmpooler and it's fully equipped* *an image with the new os is available from puppet agent team*[Here|https://confluence.puppetlabs.com/display/ECO/How+to+add+support+for+new+platforms] you can find a list with all the converted modules to use litmusStep1: Using pdksync, check/update metadata.json, ci-job-configs/jenkii/platform/projects/modules-unified.yaml*metadata.json file* - check for section: operatingsystem_support - add new version under the intended operatingsystem and save*[ci-job-configs/jenkii/platform/projects/modules-unified.yaml|https://github.com/puppetlabs/ci-job-configs/blob/master/jenkii/platform/projects/modules-unified.yaml]* - check for the module and add new platform under smoke_platforms| pe_platforms (if this platform was released)Step2: Using pdksync, create PR with the changes on modules Step3: Create PR on [ci-job-configs|https://github.com/puppetlabs/ci-job-configs/blob/master/jenkii/platform/projects/modules-unified.yaml] Step4: Deploy experimental platform intended module Step5: Run ad-hoc tests using that experimental Step6: Check testing results Step7: If failures, fix them, re-execute all the testing part until they are green Step8: Ask for review/merge(-) check for vmpooler platform (-) pdksync: update metadata.json (-) pdksync: push changes, create commit (-) create PR on ci-job-configs (-) deploy experimental platform intended module (-) run tests through ad-hoc jenkins using that experimental (-) check testing report (-) if failures, fix them, re-execute ad-hoc until they are green (-) review/merge PR Add Comment
Jira (FACT-2883) Gem-based Facter 4.0.x does not log the facts in debug mode
Title: Message Title Josh Cooper updated an issue Facter / FACT-2883 Gem-based Facter 4.0.x does not log the facts in debug mode Change By: Josh Cooper In debug mode, native facter logs the fact and its value - as in the following example:Facter: fact "fqdn" has resolved to "mymachine.mydomain.com".This is very helpful in debugging.But the gem-based facter does not log the value in the debug mode – instead it logs the cryptic messages, like:Facter: User query is: ["fqdn"]Facter: Query is fqdnChecking query tokens fqdnFacter: List of resolvable facts: [#] 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.379599.1606874914000.91499.1607095320104%40Atlassian.JIRA.
Jira (FACT-2883) Gem-based Facter 4.0.x does not log the facts in debug mode
Title: Message Title Josh Cooper updated an issue Facter / FACT-2883 Gem-based Facter 4.0.x does not log the facts in debug mode Change By: Josh Cooper Add new os support on litmus modules*Before to start, make sure the new platform is provided by vmpooler and it's fully equipped* *an image with the new os is available from puppet agent team*[Here|https://confluence.puppetlabs.com/display/ECO/How+to+add+support+for+new+platforms] you can find a list with all the converted modules to use litmusStep1: Using pdksync, check/update metadata.json, ci-job-configs/jenkii/platform/projects/modules-unified.yaml*metadata.json file* - check for section: operatingsystem_support - add new version under the intended operatingsystem and save*[ci-job-configs/jenkii/platform/projects/modules-unified.yaml|https://github.com/puppetlabs/ci-job-configs/blob/master/jenkii/platform/projects/modules-unified.yaml]* - check for the module and add new platform under smoke_platforms| pe_platforms (if this platform was released)Step2: Using pdksync, create PR with the changes on modules Step3: Create PR on [ci-job-configs|https://github.com/puppetlabs/ci-job-configs/blob/master/jenkii/platform/projects/modules-unified.yaml] Step4: Deploy experimental platform intended module Step5: Run ad-hoc tests using that experimental Step6: Check testing results Step7: If failures, fix them, re-execute all the testing part until they are green Step8: Ask for review/merge(-) check for vmpooler platform (-) pdksync: update metadata.json (-) pdksync: push changes, create commit (-) create PR on ci-job-configs (-) deploy experimental platform intended module (-) run tests through ad-hoc jenkins using that experimental (-) check testing report (-) if failures, fix them, re-execute ad-hoc until they are green (-) review/merge PR Add Comment
Jira (FACT-2884) How to disable Querying Ec2 metadata
Title: Message Title Josh Cooper updated an issue Facter / FACT-2884 How to disable Querying Ec2 metadata Change By: Josh Cooper In non-cloud environment, issuing the request to [http://169.254.169.254/latest/meta-data] causes delay in execution:Facter: Querying Ec2 metadata Facter: Trying to connect to [http://169.254.169.254/latest/meta-data/] but got: execution expiredHow to disable this query (don't need it in a non-cloud environment)?Tried setting the environment variable FACTER_virtual=generic but that does not suppress this query in non-cloud environment. Add new os support on litmus modules*Before to start, make sure the new platform is provided by vmpooler and it's fully equipped* *an image with the new os is available from puppet agent team*[Here|https://confluence.puppetlabs.com/display/ECO/How+to+add+support+for+new+platforms] you can find a list with all the converted modules to use litmusStep1: Using pdksync, check/update metadata.json, ci-job-configs/jenkii/platform/projects/modules-unified.yaml*metadata.json file* - check for section: operatingsystem_support - add new version under the intended operatingsystem and save*[ci-job-configs/jenkii/platform/projects/modules-unified.yaml|https://github.com/puppetlabs/ci-job-configs/blob/master/jenkii/platform/projects/modules-unified.yaml]* - check for the module and add new platform under smoke_platforms| pe_platforms (if this platform was released)Step2: Using pdksync, create PR with the changes on modules Step3: Create PR on [ci-job-configs|https://github.com/puppetlabs/ci-job-configs/blob/master/jenkii/platform/projects/modules-unified.yaml] Step4: Deploy experimental platform intended module Step5: Run ad-hoc tests using that experimental Step6: Check testing results Step7: If failures, fix them, re-execute all the testing part until they are green Step8: Ask for review/merge(-) check for vmpooler platform (-) pdksync: update metadata.json (-) pdksync: push changes, create commit (-) create PR on ci-job-configs (-) deploy experimental platform intended module (-) run tests through ad-hoc jenkins using that experimental (-) check testing report (-) if failures, fix them, re-execute ad-hoc until they are green (-) review/merge PR Add Comment
Jira (PUP-10795) Accept multiple logdest locations in puppet.conf
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10795 Accept multiple logdest locations in puppet.conf Change By: Mihai Buzgau Sprint: Triaged tickets 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.379455.1606836974000.91494.1607095080099%40Atlassian.JIRA.
Jira (PUP-10794) Update certname description
Title: Message Title Claire Cadman updated an issue Puppet / PUP-10794 Update certname description Change By: Claire Cadman Labels: generated-docs puppet 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.379406.1606764882000.91419.1607079060095%40Atlassian.JIRA.
Jira (FACT-2886) networking.interfaces fact not appearing
Title: Message Title Sebastian Miclea assigned an issue to Sebastian Miclea Facter / FACT-2886 networking.interfaces fact not appearing Change By: Sebastian Miclea Assignee: Sebastian Miclea 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.379783.1606999223000.91378.1607070420044%40Atlassian.JIRA.
