Jira (FACT-3188) Error on on Solaris non-global zone after upgrading to PE2021.7.2
Title: Message Title Selvakumar Azhagarsami updated an issue Facter / FACT-3188 Error on on Solaris non-global zone after upgrading to PE2021.7.2 Change By: Selvakumar Azhagarsami Attachment: ipmp_config.txt Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.481890.1677480699000.7340.1682061900029%40Atlassian.JIRA.
Jira (FACT-3188) Error on on Solaris non-global zone after upgrading to PE2021.7.2
Title: Message Title Selvakumar Azhagarsami updated an issue Facter / FACT-3188 Error on on Solaris non-global zone after upgrading to PE2021.7.2 Change By: Selvakumar Azhagarsami Component/s: Facter 4 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.481890.1677480699000.1106.1677480780181%40Atlassian.JIRA.
Jira (FACT-3188) Error on on Solaris non-global zone after upgrading to PE2021.7.2
Title: Message Title Selvakumar Azhagarsami updated an issue Facter / FACT-3188 Error on on Solaris non-global zone after upgrading to PE2021.7.2 Change By: Selvakumar Azhagarsami Labels: jira_escalated regression Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.481890.1677480699000.1105.1677480780136%40Atlassian.JIRA.
Jira (FACT-3188) Error on on Solaris non-global zone after upgrading to PE2021.7.2
Title: Message Title Selvakumar Azhagarsami updated an issue Facter / FACT-3188 Error on on Solaris non-global zone after upgrading to PE2021.7.2 Change By: Selvakumar Azhagarsami Labels: jira_escalated regression Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.481890.1677480699000.1104.1677480780090%40Atlassian.JIRA.
Jira (FACT-3188) Error on on Solaris non-global zone after upgrading to PE2021.7.2
Title: Message Title Selvakumar Azhagarsami created an issue Facter / FACT-3188 Error on on Solaris non-global zone after upgrading to PE2021.7.2 Issue Type: Bug Assignee: Unassigned Created: 2023/02/26 10:51 PM Priority: Normal Reporter: Selvakumar Azhagarsami Puppet Version: 2021.7.2 Agent OS: Solaris 11 After the agent upgrades a non-global zone, I get the following during a puppet agent run: puppet agent -vt Info: Using environment 'production' Info: Retrieving pluginfacts Info: Retrieving plugin Info: Loading facts Error: Facter: undefined method `each' for nil:NilClass Error: Fac
Jira (FACT-3187) Facter fails on mountpoints fact on Solaris 10 with non-global zones which have NFS mounts
Title: Message Title Selvakumar Azhagarsami updated an issue Facter / FACT-3187 Facter fails on mountpoints fact on Solaris 10 with non-global zones which have NFS mounts Change By: Selvakumar Azhagarsami Priority: Normal Major Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.481548.1676518094000.10882.1676519460023%40Atlassian.JIRA.
Jira (FACT-3187) Facter fails on mountpoints fact on Solaris 10 with non-global zones which have NFS mounts
Title: Message Title Selvakumar Azhagarsami updated an issue Facter / FACT-3187 Facter fails on mountpoints fact on Solaris 10 with non-global zones which have NFS mounts Change By: Selvakumar Azhagarsami Component/s: Facter 4 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.481548.1676518094000.10881.1676518680026%40Atlassian.JIRA.
Jira (FACT-3187) Facter fails on mountpoints fact on Solaris 10 with non-global zones which have NFS mounts
Title: Message Title
Selvakumar Azhagarsami updated an issue
Facter / FACT-3187
Facter fails on mountpoints fact on Solaris 10 with non-global zones which have NFS mounts
Change By:
Selvakumar Azhagarsami
Puppet Version: 2021.7.2Agent OS: Solaris 10 u1Our infrastructure and agents have been upgraded to 2021.7.2. (from 2019.8.10). In this specific case, it appears that facter in the new version has a problem: * Solaris 10 agent * Running on global zone of a system that has at least one non-global zone * At least one non-global zone has an NFS mount pointIn this combination, the root user on the global zone does not have the ability to run statvfs on the NFS filesystems:{code:java} # df -h -ZFilesystem size used avail capacity Mounted on/zones/X/root/export/disk01/app/axentsu 27G 13G 15G 47% /zones/X/root/app/axentsudf: cannot statvfs /zones/X/root/cmntsu: Not owner{code} The previous version of facter seemed to handle this well, but the new version does not:{code:java} # facter -p mountpoints [2023-02-16 09:22:00.944124 ] ERROR Facter::InternalFactManager - statvfs() function failed: Not owner{code} I think facter should just ignore such errors, as it apparently used to do
Add Comment
This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
Jira (FACT-3187) Facter fails on mountpoints fact on Solaris 10 with non-global zones which have NFS mounts
Title: Message Title
Selvakumar Azhagarsami updated an issue
Facter / FACT-3187
Facter fails on mountpoints fact on Solaris 10 with non-global zones which have NFS mounts
Change By:
Selvakumar Azhagarsami
Puppet Version: 2021.7.2Agent OS: Solaris 10 u1Our infrastructure and agents have been upgraded to 2021.7.2. (from 2019.8.10). In this specific case, it appears that facter in the new version has a problem: * Solaris 10 agent * Running on global zone of a system that has at least one non-global zone * At least one non-global zone has an NFS mount pointIn this combination, the root user on the global zone does not have the ability to run statvfs on the NFS filesystems: {code:java} ``` # df -h -ZFilesystem size used avail capacity Mounted on /zones/X/root/export/disk01/app/axentsu 27G 13G 15G 47% /zones/X/root/app/axentsudf: cannot statvfs /zones/X/root/cmntsu: Not owner {code} ``` The previous version of facter seemed to handle this well, but the new version does not: {code:java} ``` # facter -p mountpoints[2023-02-16 09:22:00.944124 ] ERROR Facter::InternalFactManager - statvfs() function failed: Not owner {code} #```
Add Comment
This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
Jira (FACT-3187) Facter fails on mountpoints fact on Solaris 10 with non-global zones which have NFS mounts
Title: Message Title Selvakumar Azhagarsami created an issue Facter / FACT-3187 Facter fails on mountpoints fact on Solaris 10 with non-global zones which have NFS mounts Issue Type: Bug Assignee: Unassigned Created: 2023/02/15 7:28 PM Priority: Normal Reporter: Selvakumar Azhagarsami Puppet Version: 2021.7.2 Agent OS: Solaris 10 u1 Our infrastructure and agents have been upgraded to 2021.7.2. (from 2019.8.10). In this specific case, it appears that facter in the new version has a problem: Solaris 10 agent Running on global zone of a system that has at least one non-global zone At least one non-global zone has an NFS mount point In this combination, the root user on the global zone does not have the ability to run statvfs on the NFS filesystems: ``` df -h -Z Filesystem size used avail capacity Mounted on /zones/X/root/export/disk01/app/axentsu 27G 13G 15G 47% /zones/X/root/app/axentsu df: cannot statvfs /zones/X/root/cmntsu: Not owner ``` The previous version of facter seemed to handle this well, but the new version does not: ``` facter -p mountpoints [2023-02-16 09:22:00.944124 ] ERROR Facter::InternalFactManager - statvfs() function failed: Not owner # ```
Jira (PUP-11712) Resource type TIDY is not honouring the parameter value from age
Title: Message Title
Selvakumar Azhagarsami updated an issue
Puppet / PUP-11712
Resource type TIDY is not honouring the parameter value from age
Change By:
Selvakumar Azhagarsami
*Puppet Version:* 6.26.0{*}{ { *} } {*}Puppet Server Version:{*} 2019.8.10{*}{ { *} } {*}OS Name/Version:{*} RHEL 7The documentation for the {{age}} parameter for the {{tidy}} type states:{quote}Tidy files whose age is *equal to or greater* than the specified time. You can choose seconds, minutes, hours, days, or weeks by specifying the first letter of any of those words (for example, ‘1w’ represents one week).Docs: [https://puppet.com/docs/puppet/7.7/types/tidy.html#tidy-attribute-age]{*}Specifying 0 will remove all files{*}.{quote}*Desired Behavior:* Setting *age=1w* removes all files more than 1 week old*Actual Behavior:* It's not removing any files, details of the testing below {code:java} [root@pepm reports]# pwd/tmp/comply/assessors/4.19.0/Assessor-CLI/reports[root@pepm reports]# ls -lrttotal 3904-rw-r--r-- 1 root root 995383 Dec 1 07:23 agentdebugoutput.txt-rw-r--r-- 1 root root 995383 Dec 1 07:23 agentdebugoutput4.txt-rw-r--r-- 1 root root 995383 Dec 1 07:23 agentdebugoutput3.txt-rw-r--r-- 1 root root 995383 Dec 1 07:23 agentdebugoutput2.txt {code} {code:java} [root@pepm reports]# cat ~/code/newtidy.ppclass basic_tidy { tidy { 'delete-assessors': path => '/tmp/comply/assessors', age => ' 0 1w ', recurse => true, matches => [ 'agentdebugoutput*.txt' ], }}include basic_tidy {code} {code:java} [root@pepm reports]# puppet apply ~/code/newtidy.ppNotice: Compiled catalog for pepm.puppetdebug.vlan in environment production in 0.14 secondsNotice: Applied catalog in 0.30 seconds {code}
Add Comment
Jira (PUP-11712) Resource type TIDY is not honouring the parameter value from age
Title: Message Title Selvakumar Azhagarsami updated an issue Puppet / PUP-11712 Resource type TIDY is not honouring the parameter value from age Change By: Selvakumar Azhagarsami Component/s: Types and Providers Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.478600.1673515682000.1278.1673929620024%40Atlassian.JIRA.
Jira (PUP-11712) Resource type TIDY is not honouring the parameter value from age
Title: Message Title
Selvakumar Azhagarsami created an issue
Puppet / PUP-11712
Resource type TIDY is not honouring the parameter value from age
Issue Type:
Bug
Assignee:
Unassigned
Created:
2023/01/12 1:28 AM
Priority:
Normal
Reporter:
Selvakumar Azhagarsami
Puppet Version: 6.26.0 {}Puppet Server Version: 2019.8.10 {}OS Name/Version: RHEL 7 The documentation for the age parameter for the tidy type states:
Tidy files whose age is equal to or greater than the specified time. You can choose seconds, minutes, hours, days, or weeks by specifying the first letter of any of those words (for example, ‘1w’ represents one week).
Docs: https://puppet.com/docs/puppet/7.7/types/tidy.html#tidy-attribute-age
Specifying 0 will remove all files.
Desired Behavior: Setting age=1w removes all files more than 1 week old Actual Behavior: It's not removing any files, details of the testing below
[root@pepm reports]# pwd
/tmp/comply/assessors/4.19.0/Assessor-CLI/reports
Jira (FACT-3170) Debug output on Windows nodes shows the same Facter logs repeated
Title: Message Title Selvakumar Azhagarsami updated an issue Facter / FACT-3170 Debug output on Windows nodes shows the same Facter logs repeated Change By: Selvakumar Azhagarsami Attachment: agent720.log Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.477181.1671137416000.69148.1672282920078%40Atlassian.JIRA.
Jira (FACT-3170) Debug output on Windows nodes shows the same Facter logs repeated
Title: Message Title Selvakumar Azhagarsami updated an issue Facter / FACT-3170 Debug output on Windows nodes shows the same Facter logs repeated Change By: Selvakumar Azhagarsami Attachment: agent720.log Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.477181.1671137416000.69147.1672282860074%40Atlassian.JIRA.
Jira (FACT-3133) Facter 4 Does Not Support Built-In Windows Commands
Title: Message Title Selvakumar Azhagarsami commented on FACT-3133 Re: Facter 4 Does Not Support Built-In Windows Commands Tony Vu for the benefit of this ticket, please fix it specifically the echo command but if you think fixing other windows command is feasible please proceed I will leave it up to you. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.453891.1656569785000.27005.166207872%40Atlassian.JIRA.
Jira (FACT-3133) Facter 4 Does Not Support Built-In Windows Commands
Title: Message Title Selvakumar Azhagarsami updated an issue Facter / FACT-3133 Facter 4 Does Not Support Built-In Windows Commands Change By: Selvakumar Azhagarsami Labels: jira_escalated support Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.453891.1656569785000.56360.165657088%40Atlassian.JIRA.
Jira (FACT-3133) Facter 4 Does Not Support Built-In Windows Commands
Title: Message Title Selvakumar Azhagarsami updated an issue Facter / FACT-3133 Facter 4 Does Not Support Built-In Windows Commands Change By: Selvakumar Azhagarsami Team: Night's Watch Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.453891.1656569785000.56359.165657041%40Atlassian.JIRA.
Jira (FACT-3133) Facter 4 Does Not Support Built-In Windows Commands
Title: Message Title
Selvakumar Azhagarsami updated an issue
Facter / FACT-3133
Facter 4 Does Not Support Built-In Windows Commands
Change By:
Selvakumar Azhagarsami
When executing the custom fact, Facter version 4.2.x fails with the "{*}command not found{*}" error. Created *custom facts* to test the scenario as shown below.{code:java} Facter.add(:factertestingwindows) do confine :kernel => 'windows' setcode doFacter::Core::Execution.execute('echo Hello', :timeout => 10) endend {code} It is *working* as expected in _{{Facter version 3.14.x}}_ _ { {}}_{ code:java} PS C:\Users\Administrator> facter --version3.14.22 (commit 4d4afa91b226dfa8d2f92c495b7070377134386f) {code} _ { {}}_{ code:java} PS C:\Users\Administrator> facter -p factertestingwindowsHelloPS C:\Users\Administrator> {code}{{and }}{{ *Not working*}} _ {{ }}_ {{ in}} _{{ }}{{ Facter version 4.2.x}}_ _ { {}}_{ code:java} PS C:\Users\Administrator> facter --version4.2.2 {code} _ { {}}_{ code:java} PS C:\Users\Administrator> puppet agent -tInfo: Using configured environment 'production'Info: Retrieving pluginfactsInfo: Retrieving pluginInfo: Loading factsError: Facter: Error while resolving custom fact fact='factertestingwindows', resolution='': Could not execute 'echo Hello': command not foundInfo: Caching catalog for baroque-fort.delivery.puppetlabs.netInfo: Applying configuration version 'pe-202130-master-production-67440e89804'Notice: Applied catalog in 0.42 seconds {code} _{{}}_
Add Comment
This message was sent by Atlassian Jira (v8.20.2#
Jira (FACT-3133) Facter 4 Does Not Support Built-In Windows Commands
Title: Message Title
Selvakumar Azhagarsami created an issue
Facter / FACT-3133
Facter 4 Does Not Support Built-In Windows Commands
Issue Type:
Bug
Assignee:
Unassigned
Created:
2022/06/29 11:16 PM
Priority:
Normal
Reporter:
Selvakumar Azhagarsami
When executing the custom fact, Facter version 4.2.x fails with the "command not found" error. Created custom facts to test the scenario as shown below.
Facter.add(:factertestingwindows) do
confine :kernel => 'windows'
setcode do
Facter::Core::Execution.execute('echo Hello', :timeout => 10)
end
end
Jira (PDB-5469) PuppetDB services shutting down due to query performance
Title: Message Title
Selvakumar Azhagarsami updated an issue
PuppetDB / PDB-5469
PuppetDB services shutting down due to query performance
Change By:
Selvakumar Azhagarsami
h3. Summary:The issue reported on running the node query with 50 nodes, it got failed with the console error "Error resolving pql query" The query used was an arbitrary selection of 50 nodes using the OR condition.h5. Did it ever work?It worked for 20 nodes and in the case of 50 nodes, it got failed with the PQL error.h5. When did the issue first occur?Not sure. The customer reported this issue as a possible bug.h5. If applicable, did you do a run with --debug --trace?N/Ah4. OS & Version: Ubuntu- 18.04.6 LTS (Bionic Beaver) h4. PE Version on the affected machine:2021.5h4. Master Or Agent Affected:Masterh4. All In One Or Split Install:Split installh4. Steps Taken To Reproduce:The customer has provided the below steps to reproduce this error1. Perform an expensive PQL query from the console. In our case, we were able to reproduce the problem with 30+ OR statements in a query: {code:java} inventory[certname] \ { certname ~ "bastion-i-0df61833aa00e6acc" or certname ~ "compile-master-i-05d0fd872d2b1964f" or certname ~ "compile-master-i-061f9a63122235787"} {code} (and so on, of course, with 30+ nodes)2. There is no step 2! When running this query, I get the error in the console "Error resolving pql query: Server Error". It appears that the UI timeout occurs after 60 seconds, and the user would have no idea they caused a problem.On the backend, PuppetDB queries start getting slower and slower, and the load on the server in question climbs. In at least one test, if left unchecked, the load runs away and `apport` runs to try to gather a crash dump. {code:java}// 2022-03-10T17:26:59.813Z WARN [p.p.h.query] Parsing PQL took 3,705.52 ms: "nodes[certname] { report_timestamp > \"2022-03-01T00:00:00Z\" }" 2022-03-10T17:27:05.470Z WARN [p.p.h.query] Parsing PQL took 9,362.058 ms: "resources[certname] {\n type = 'Class' and\n title = 'Puppet_enterprise::Profile::Master' and\n nodes{ deactivated is null and expired is null }\n order by certname\n }" {code} Files Acquired:Support Bundle from Primary master and external puppet database h4. Relevant Error Messages:We can see the following error in the puppetdb logs which is matching with the customer who has tried to execute the query. {code:java}// error from the puppetdb Log at java.base/java.lang.Thread.run(Thread.java:829)2022-03-10T17:42:47.401Z INFO [p.p.c.services] Periodic activities halted2022-03-10T17:42:47.402Z INFO [c.z.h.HikariDataSource] PDBWritePool - Shutdown initiated...2022-03-10T17:43:03.587Z ERROR [p.p.threadpool] Reporting unexpected error from thread cmd-proc-thread-392 to stderr and logjava.util.concurrent.RejectedExecutionException: Task java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@7294c26[Not completed, task = java.util.concurrent.Executors$RunnableAdapter@22c31f38[Wrapped task = puppetlabs.puppetdb.command$schedule_delayed_message
Jira (PUP-11473) Error: Failed to apply catalog: undefined method `bytesize' for nil:NilClass on WinServer 2016
Title: Message Title Selvakumar Azhagarsami updated an issue Puppet / PUP-11473 Error: Failed to apply catalog: undefined method `bytesize' for nil:NilClass on WinServer 2016 Change By: Selvakumar Azhagarsami Attachment: puppetagent_trace_debug_47445-01-03-22.log Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.437686.1646195359000.26944.1646197800083%40Atlassian.JIRA.
Jira (PUP-11473) Error: Failed to apply catalog: undefined method `bytesize' for nil:NilClass on WinServer 2016
Title: Message Title Selvakumar Azhagarsami updated an issue Puppet / PUP-11473 Error: Failed to apply catalog: undefined method `bytesize' for nil:NilClass on WinServer 2016 Change By: Selvakumar Azhagarsami Affects Version/s: PUP 6.22.0 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.437686.1646195359000.26946.1646197800184%40Atlassian.JIRA.
Jira (PUP-11473) Error: Failed to apply catalog: undefined method `bytesize' for nil:NilClass on WinServer 2016
Title: Message Title
Selvakumar Azhagarsami updated an issue
Puppet / PUP-11473
Error: Failed to apply catalog: undefined method `bytesize' for nil:NilClass on WinServer 2016
Change By:
Selvakumar Azhagarsami
This is a follow-up ticket from https://tickets.puppetlabs.com/browse/PUP-10898*Puppet Version: 6.22.1**Puppet Server Version: PE 2019.8.5**OS Name/Version: Windows Server 2016*Windows Server 2016 failed to apply catalog, please refer to the error message below for details.attached is trace debug output from affected agent node the [^puppetagent_trace_debug_47445-01-03-22.log] affected agent node {code:java} [0;36mDebug: Could not retrieve raw SID bytes from 'Administrator': Failed to convert string SID: Administrator: The security ID structure is invalid. [0m [0;36mDebug: Failed to call LookupAccountNameW with account: Administrator: No mapping between account names and security IDs was done. [0m [0;36mDebug: Could not retrieve raw SID bytes from 'EC2AMAZ-NAUKKA2\Administrator': Failed to convert string SID: EC2AMAZ-NAUKKA2\Administrator: The security ID structure is invalid. [0m [0;36mDebug: Failed to call LookupAccountNameW with account: EC2AMAZ-NAUKKA2\Administrator: No mapping between account names and security IDs was done. [0m [1;31mError: Could not send report: undefined method `bytesize' for nil:NilClassC:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/api_types.rb:125:in `from_wide_string'C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/api_types.rb:26:in `from_string_to_wide_string'C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/sid.rb:184:in `string_to_sid_ptr'C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/security.rb:431:in `add_access_allowed_ace'C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/security.rb:659:in `block (7 levels) in set_security_descriptor'C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/access_control_list.rb:28:in `block in each'C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/access_control_list.rb:28:in `each'C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/access_control_list.rb:28:in `each'C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/security.rb:655:in `block (6 levels) in set_security_descriptor'C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/sid.rb:192:in `block (3 levels) in string_to_sid_ptr'C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/api_types.rb:94:in `read_win32_local_pointer'C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/sid.rb:191:in `block (2 levels) in string_to_sid_ptr'C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/sid.rb:185:in `initialize'C:/Program Files/Puppet
Jira (PUP-11473) Error: Failed to apply catalog: undefined method `bytesize' for nil:NilClass on WinServer 2016
Title: Message Title Selvakumar Azhagarsami updated an issue Puppet / PUP-11473 Error: Failed to apply catalog: undefined method `bytesize' for nil:NilClass on WinServer 2016 Change By: Selvakumar Azhagarsami Attachment: puppetagent_trace_debug_47445-01-03-22.log Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.437686.1646195359000.26943.1646197680118%40Atlassian.JIRA.
Jira (PUP-11473) Error: Failed to apply catalog: undefined method `bytesize' for nil:NilClass on WinServer 2016
Title: Message Title
Selvakumar Azhagarsami updated an issue
Puppet / PUP-11473
Error: Failed to apply catalog: undefined method `bytesize' for nil:NilClass on WinServer 2016
Change By:
Selvakumar Azhagarsami
This is a follow-up ticket from https://tickets.puppetlabs.com/browse/PUP-10898*Puppet Version: 6.22.1**Puppet Server Version: PE 2019.8.5**OS Name/Version: Windows Server 2016*Windows Server 2016 failed to apply catalog, please refer to the error message below for details.attached is trace debug output from affected agent node [^puppetagent_trace_debug_47445-01-03-22.log]{code:java} [0;36mDebug: Could not retrieve raw SID bytes from 'Administrator': Failed to convert string SID: Administrator: The security ID structure is invalid. [0m [0;36mDebug: Failed to call LookupAccountNameW with account: Administrator: No mapping between account names and security IDs was done. [0m [0;36mDebug: Could not retrieve raw SID bytes from 'EC2AMAZ-NAUKKA2\Administrator': Failed to convert string SID: EC2AMAZ-NAUKKA2\Administrator: The security ID structure is invalid. [0m [0;36mDebug: Failed to call LookupAccountNameW with account: EC2AMAZ-NAUKKA2\Administrator: No mapping between account names and security IDs was done. [0m [1;31mError: Could not send report: undefined method `bytesize' for nil:NilClassC:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/api_types.rb:125:in `from_wide_string'C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/api_types.rb:26:in `from_string_to_wide_string'C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/sid.rb:184:in `string_to_sid_ptr'C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/security.rb:431:in `add_access_allowed_ace'C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/security.rb:659:in `block (7 levels) in set_security_descriptor'C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/access_control_list.rb:28:in `block in each'C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/access_control_list.rb:28:in `each'C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/access_control_list.rb:28:in `each'C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/security.rb:655:in `block (6 levels) in set_security_descriptor'C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/sid.rb:192:in `block (3 levels) in string_to_sid_ptr'C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/api_types.rb:94:in `read_win32_local_pointer'C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/sid.rb:191:in `block (2 levels) in string_to_sid_ptr'C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/sid.rb:185:in `initialize'C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby
Jira (PUP-11473) Error: Failed to apply catalog: undefined method `bytesize' for nil:NilClass on WinServer 2016
Title: Message Title
Selvakumar Azhagarsami updated an issue
Puppet / PUP-11473
Error: Failed to apply catalog: undefined method `bytesize' for nil:NilClass on WinServer 2016
Change By:
Selvakumar Azhagarsami
This is a follow-up ticket from https://tickets.puppetlabs.com/browse/PUP-10898 *Puppet Version: 6.22.1**Puppet Server Version: PE 2019.8.5**OS Name/Version: Windows Server 2016* Describe your issue in as much detail as possible…Describe steps Windows Server 2016 failed to reproduce…*Desired Behavior:**Actual Behavior:*Actual apply catalog, please refer to the error message : below for details. attached trace debug output from affected agent node [^puppetagent_trace_debug_47445-01-03-22.log] {code:java} [0;36mDebug: Could not retrieve raw SID bytes from 'Administrator': Failed to convert string SID: Administrator: The security ID structure is invalid. [0m [0;36mDebug: Failed to call LookupAccountNameW with account: Administrator: No mapping between account names and security IDs was done. [0m [0;36mDebug: Could not retrieve raw SID bytes from 'EC2AMAZ-NAUKKA2\Administrator': Failed to convert string SID: EC2AMAZ-NAUKKA2\Administrator: The security ID structure is invalid. [0m [0;36mDebug: Failed to call LookupAccountNameW with account: EC2AMAZ-NAUKKA2\Administrator: No mapping between account names and security IDs was done. [0m [1;31mError: Could not send report: undefined method `bytesize' for nil:NilClassC:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/api_types.rb:125:in `from_wide_string'C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/api_types.rb:26:in `from_string_to_wide_string'C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/sid.rb:184:in `string_to_sid_ptr'C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/security.rb:431:in `add_access_allowed_ace'C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/security.rb:659:in `block (7 levels) in set_security_descriptor'C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/access_control_list.rb:28:in `block in each'C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/access_control_list.rb:28:in `each'C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/access_control_list.rb:28:in `each'C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/security.rb:655:in `block (6 levels) in set_security_descriptor'C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/sid.rb:192:in `block (3 levels) in string_to_sid_ptr'C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/api_types.rb:94:in `read_win32_local_pointer'C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/sid.rb:191:in `block (2 levels) in string_to_sid_ptr'C:/Program Files/Puppet Labs/Pupp
Jira (PUP-11473) Error: Failed to apply catalog: undefined method `bytesize' for nil:NilClass on WinServer 2016
Title: Message Title Selvakumar Azhagarsami updated an issue Puppet / PUP-11473 Error: Failed to apply catalog: undefined method `bytesize' for nil:NilClass on WinServer 2016 Change By: Selvakumar Azhagarsami Attachment: puppetagent_trace_debug_47445-01-03-22.log Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.437686.1646195359000.26940.1646197560053%40Atlassian.JIRA.
Jira (PUP-11473) Error: Failed to apply catalog: undefined method `bytesize' for nil:NilClass on WinServer 2016
Title: Message Title
Selvakumar Azhagarsami updated an issue
Puppet / PUP-11473
Error: Failed to apply catalog: undefined method `bytesize' for nil:NilClass on WinServer 2016
Change By:
Selvakumar Azhagarsami
*Puppet Version: 6.22.1**Puppet Server Version: PE 2019.8.5**OS Name/Version: Windows Server 2016 *Describe your issue in as much detail as possible… Describe steps to reproduce…*Desired Behavior:**Actual Behavior:* Please take a moment Actual error message:{code:java} [0;36mDebug: Could not retrieve raw SID bytes from 'Administrator': Failed to convert string SID: Administrator: The security ID structure is invalid. [0m [0;36mDebug: Failed to call LookupAccountNameW with account: Administrator: No mapping between account names and attach any relevant log output security IDs was done. [0m [0;36mDebug: Could not retrieve raw SID bytes from 'EC2AMAZ-NAUKKA2\Administrator': Failed to convert string SID: EC2AMAZ-NAUKKA2\Administrator: The security ID structure is invalid. [0m [0;36mDebug: Failed to call LookupAccountNameW with account: EC2AMAZ-NAUKKA2\Administrator: No mapping between account names and security IDs was done. [0m [1;31mError: Could not send report: undefined method `bytesize' for nil:NilClassC: / or manifests Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/api_types . This will help us immensely when troubleshooting the issue rb:125:in `from_wide_string'C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/api_types . rb:26:in `from_string_to_wide_string' C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/sid.rb:184:in `string_to_sid_ptr' Examples C : /Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/security.rb:431:in `add_access_allowed_ace' Run C:/Program Files/Puppet Labs/Puppet/ puppet agent with --test --trace --debug /lib/ruby/vendor_ruby/puppet/util/windows/security.rb:659:in `block (7 levels) in set_security_descriptor' C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/access_control_list.rb:28:in `block in each' Relevant sections of {{ C: / var Program Files / log Puppet Labs / puppetlabs Puppet / puppetserver puppet / puppetserver lib/ruby/vendor_ruby/puppet/util/windows/access_control_list . log}} or any applicable logs from the same directory rb:28:in `each'C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/access_control_list . rb:28:in `each' C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/security.rb:655:in `block (6 levels) in set_security_descriptor' For more detailed information turn up the server logs by upping the log level C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/sid.rb:192: in the server `block (3 levels) in string_to_sid_ptr ' s logback C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/api_types . xml rb:94:in `read_win32_
Jira (PUP-11473) Error: Failed to apply catalog: undefined method `bytesize' for nil:NilClass on WinServer 2016
Title: Message Title Selvakumar Azhagarsami created an issue Puppet / PUP-11473 Error: Failed to apply catalog: undefined method `bytesize' for nil:NilClass on WinServer 2016 Issue Type: Bug Assignee: Unassigned Created: 2022/03/01 8:29 PM Priority: Normal Reporter: Selvakumar Azhagarsami Puppet Version: 6.22.1 Puppet Server Version: PE 2019.8.5 OS Name/Version: Describe your issue in as much detail as possible… Describe steps to reproduce… Desired Behavior: Actual Behavior: Please take a moment and attach any relevant log output and/or manifests. This will help us immensely when troubleshooting the issue. Examples: Run puppet agent with --test --trace --debug Relevant sections of /var/log/puppetlabs/puppetserver/puppetserver.log or any applicable logs from the same directory. For more detailed information turn up the server logs by upping the log level in the server's logback.xml Relevant sections of configurations files (puppet.conf, hiera.conf, Server's conf.d, defaults/sysconfig) For memory issues with server heap dumps are also helpful. Add Comment
Jira (PUP-10898) Retrieve current user by using the fully-qualified username and domain on Windows
Title: Message Title Selvakumar Azhagarsami commented on PUP-10898 Re: Retrieve current user by using the fully-qualified username and domain on Windows luchian.nemes / josh DBS bank reported the same issue https://puppetlabs.zendesk.com/agent/tickets/47445, we have tried to upgrade the agent to the 6.22 version and still facing the same error. [0;36mDebug: Facter: fact "facterversion" has resolved to "3.14.17". [0m [0;36mDebug: Facter: fact "aio_agent_version" has resolved to "6.22.1". [0m attaching the puppet debug trace output here for more details puppetagent_trace_debug_47445-01-03-22.log [0;36mDebug: Could not retrieve raw SID bytes from 'Administrator': Failed to convert string SID: Administrator: The security ID structure is invalid. [0m [0;36mDebug: Failed to call LookupAccountNameW with account: Administrator: No mapping between account names and security IDs was done. [0m [0;36mDebug: Could not retrieve raw SID bytes from 'EC2AMAZ-NAUKKA2\Administrator': Failed to convert string SID: EC2AMAZ-NAUKKA2\Administrator: The security ID structure is invalid. [0m [0;36mDebug: Failed to call LookupAccountNameW with account: EC2AMAZ-NAUKKA2\Administrator: No mapping between account names and security IDs was done. [0m [1;31mError: Failed to apply catalog: undefined method `bytesize' for nil:NilClassC:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/api_types.rb:125:in `from_wide_string'C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/api_types.rb:26:in `from_string_to_wide_string'C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/sid.rb:184:in `string_to_sid_ptr'C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/security.rb:431:in `add_access_allowed_ace'C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/security.rb:659:in `block (7 levels) in set_security_descriptor'C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/access_control_list.rb:28:in `block in each' Please check and let me know if we have any workaround to recommend to customer.
Jira (PUP-10898) Retrieve current user by using the fully-qualified username and domain on Windows
Title: Message Title Selvakumar Azhagarsami updated an issue Puppet / PUP-10898 Retrieve current user by using the fully-qualified username and domain on Windows Change By: Selvakumar Azhagarsami Attachment: puppetagent_trace_debug_47445-01-03-22.log Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.387116.1613055296000.25412.1646126520075%40Atlassian.JIRA.
Jira (FACT-3077) Inconsistent values coming from facter-ng output
Title: Message Title Selvakumar Azhagarsami commented on FACT-3077 Re: Inconsistent values coming from facter-ng output Jeremy Mozes I just did a quick test in my lab PE 2021.3.0 machine. [root@pe-server-262baf-0 facts.d]# facter -p pe_build 2021.3.0 [root@pe-server-262baf-0 facts.d]# /opt/puppetlabs/puppet/bin/facter --version 4.2.2 [root@pe-server-262baf-0 facts.d]# /opt/puppetlabs/puppet/bin/facter-ng --version -bash: /opt/puppetlabs/puppet/bin/facter-ng: No such file or directory [root@pe-server-262baf-0 facts.d]# puppet facts show --facterng key1 key2 Error: Could not parse application options: inval
Jira (FACT-3077) Inconsistent values coming from facter-ng output
Title: Message Title
Selvakumar Azhagarsami updated an issue
Facter / FACT-3077
Inconsistent values coming from facter-ng output
Change By:
Selvakumar Azhagarsami
Facter & Facter-ng version:{code:java} [root@pepm facts.d]# /opt/puppetlabs/puppet/bin/facter --version3.14.18 (commit 92e6f64d36589c8a537d4a4d5c574c872c3aa329) {code}{code:java} [root@pepm facts.d]# /opt/puppetlabs/puppet/bin/facter-ng --version4.2.1 {code} The output of the ` * Puppet ` * command shows the inconsistent value and the result for the boolean value `false` the result is showing as empty string . Below are the steps to reproduce and the output: 1) Created an external fact: {code:java} [root@pepm facts.d]# cat /etc/facter/facts.d/build_information.yaml---key1: truekey2: false {code} 2) Output of the *Puppet* command shows the empty result boolean value `false` {code:java} [root@pepm facts.d]# puppet facts show --facterng key1 key22021-10-05 05:45:07.491417 WARN puppetlabs.facter - locale environment variables were bad; continuing with LANG=C LC_ALL=C{ "key1": true, "key2": ""}[root@pepm facts.d]# puppet facts show key1 key22021-10-05 05:45:24.325235 WARN puppetlabs.facter - locale environment variables were bad; continuing with LANG=C LC_ALL=C{ "key1": true, "key2": false}{code}
Add Comment
This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
Jira (FACT-3077) Inconsistent values coming from facter-ng output
Title: Message Title
Selvakumar Azhagarsami updated an issue
Facter / FACT-3077
Inconsistent values coming from facter-ng output
Change By:
Selvakumar Azhagarsami
Facter & Facter-ng version:{code:java}[root@pepm facts.d]# /opt/puppetlabs/puppet/bin/facter --version3.14.18 (commit 92e6f64d36589c8a537d4a4d5c574c872c3aa329) {code}{code:java}[root@pepm facts.d]# /opt/puppetlabs/puppet/bin/facter-ng --version4.2.1 {code} The output of the `Puppet` command shows the inconsistent value and for boolean value `false` the result is showing as empty.
Add Comment
This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
--
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.418363.1633415924000.146849.1633416240030%40Atlassian.JIRA.
Jira (FACT-3077) Inconsistent values coming from facter-ng output
Title: Message Title Selvakumar Azhagarsami updated an issue Facter / FACT-3077 Inconsistent values coming from facter-ng output Change By: Selvakumar Azhagarsami Labels: Support Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.418363.1633415924000.146848.1633415940088%40Atlassian.JIRA.
Jira (FACT-3077) Inconsistent values coming from facter-ng output
Title: Message Title Selvakumar Azhagarsami created an issue Facter / FACT-3077 Inconsistent values coming from facter-ng output Issue Type: Bug Assignee: Unassigned Created: 2021/10/04 11:38 PM Priority: Normal Reporter: Selvakumar Azhagarsami Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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/pupp
Jira (FACT-3049) Reading the `/etc/resolv.conf` file for the domain value
Title: Message Title Selvakumar Azhagarsami created an issue Facter / FACT-3049 Reading the `/etc/resolv.conf` file for the domain value Issue Type: Improvement Affects Versions: FACT 3.14.1 Assignee: Unassigned Created: 2021/05/31 1:46 AM Priority: Normal Reporter: Selvakumar Azhagarsami Per our environment settings, it is unable to get the FQDN from hostname -f. So, we have to read the /etc/resolve.conf for the domain value. But, it is not a must to set the 1st search domain as the server domain name in the /etc/resolve.conf file. So, do U think we have to review this mechanism to get the domain info? Add Comment
Jira (PDB-4642) Puppet 2019.3 upgrade failure from 2019.2.2
Title: Message Title
Selvakumar Azhagarsami updated an issue
PuppetDB / PDB-4642
Puppet 2019.3 upgrade failure from 2019.2.2
Change By:
Selvakumar Azhagarsami
During the upgrade from 2019.2.2 to 2019.3, pe-puppetdb service is failed to start with the error message "resource_events_20200123z" does not exist. Please refer to the attached log file for more details.{code:java}[m2020-01-31T12:43:01.508+11:00 - [Notice]: /Stage[main]/Puppet_enterprise::Puppetdb::Service/Puppet_enterprise::Trapperkeeper::Pe_service[puppetdb]/Exec[pe-puppetdb service full restart]: Triggered 'refresh' from 1 event [0m [1;31m2020-01-31T12:44:13.543+11:00 - [Error]: Systemd start for pe-puppetdb failed!journalctl log for pe-puppetdb:-- Logs begin at Mon 2019-12-23 23:25:01 AEDT, end at Fri 2020-01-31 12:44:13 AEDT. --Jan 31 12:43:02 harmony3-d1 puppetlabs . anu.edu.au com systemd[1]: Starting pe-puppetdb Service...Jan 31 12:43:37 harmony3-d1 puppetlabs . anu.edu.au com puppetdb[124158]: WARNING: An illegal reflective access operation has occurredJan 31 12:43:37 harmony3-d1 puppetlabs . anu.edu.au com puppetdb[124158]: WARNING: Illegal reflective access by dynapath.defaults$eval24067$fn__24068 to method java.net.URLClassLoader.addURL(java.net.URL)Jan 31 12:43:37 harmony3-d1 puppetlabs . anu.edu.au com puppetdb[124158]: WARNING: Please consider reporting this to the maintainers of dynapath.defaults$eval24067$fn__24068Jan 31 12:43:37 harmony3-d1 puppetlabs . anu.edu.au com puppetdb[124158]: WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operationsJan 31 12:43:37 harmony3-d1 puppetlabs . anu.edu.au com puppetdb[124158]: WARNING: All illegal access operations will be denied in a future releaseJan 31 12:43:52 harmony3-d1 puppetlabs . anu.edu.au com puppetdb[124158]: The [database] classname config option has been retired and will be ignored.Jan 31 12:43:52 harmony3-d1 puppetlabs . anu.edu.au com puppetdb[124158]: The [database] log-slow-statements config option has been retired and will be ignored.Jan 31 12:43:52 harmony3-d1 puppetlabs . anu.edu.au com puppetdb[124158]: The [database] subprotocol config option has been retired and will be ignored.Jan 31 12:44:04 harmony3-d1 puppetlabs . anu.edu.au com puppetdb[124158]: The [database] classname config option has been retired and will be ignored.Jan 31 12:44:04 harmony3-d1 puppetlabs . anu.edu.au com puppetdb[124158]: The [database] log-slow-statements config option has been retired and will be ignored.Jan 31 12:44:04 harmony3-d1 puppetlabs . anu.edu.au com puppetdb[124158]: The [database] subprotocol config option has been retired and will be ignored.Jan 31 12:44:13 harmony3-d1 puppetlabs . anu.edu.au com puppetdb[124158]: Execution error (PSQLException) at org.postgresql.core.v3.QueryExecutorImpl/receiveErrorResponse (QueryExecutorImpl.java:2497).Jan 31 12:44:13 harmony3-d1 puppetlabs . anu.edu.au com puppetdb[124158]: ERROR: relation "resource_events_20200123z" does not existJan 31 12:44:1
Jira (PDB-4642) Puppet 2019.3 upgrade failure from 2019.2.2
Title: Message Title Selvakumar Azhagarsami updated an issue PuppetDB / PDB-4642 Puppet 2019.3 upgrade failure from 2019.2.2 Change By: Selvakumar Azhagarsami Attachment: 2020-01-31T12.33.25 1100.install.log Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.344931.1580780081000.12439.1580780700367%40Atlassian.JIRA.
Jira (PDB-4642) Puppet 2019.3 upgrade failure from 2019.2.2
Title: Message Title
Selvakumar Azhagarsami updated an issue
PuppetDB / PDB-4642
Puppet 2019.3 upgrade failure from 2019.2.2
Change By:
Selvakumar Azhagarsami
During the upgrade from 2019.2.2 to 2019.3, pe-puppetdb service is failed to start with the error message "resource_events_20200123z" does not exist. Please refer to the attached log file for more details.{code:java}[m2020-01-31T12:43:01.508+11:00 - [Notice]: /Stage[main]/Puppet_enterprise::Puppetdb::Service/Puppet_enterprise::Trapperkeeper::Pe_service[puppetdb]/Exec[pe-puppetdb service full restart]: Triggered 'refresh' from 1 event [0m [1;31m2020-01-31T12:44:13.543+11:00 - [Error]: Systemd start for pe-puppetdb failed!journalctl log for pe-puppetdb:-- Logs begin at Mon 2019-12-23 23:25:01 AEDT, end at Fri 2020-01-31 12:44:13 AEDT. --Jan 31 12:43:02 harmony3-d1.anu.edu.au systemd[1]: Starting pe-puppetdb Service...Jan 31 12:43:37 harmony3-d1.anu.edu.au puppetdb[124158]: WARNING: An illegal reflective access operation has occurredJan 31 12:43:37 harmony3-d1.anu.edu.au puppetdb[124158]: WARNING: Illegal reflective access by dynapath.defaults$eval24067$fn__24068 to method java.net.URLClassLoader.addURL(java.net.URL)Jan 31 12:43:37 harmony3-d1.anu.edu.au puppetdb[124158]: WARNING: Please consider reporting this to the maintainers of dynapath.defaults$eval24067$fn__24068Jan 31 12:43:37 harmony3-d1.anu.edu.au puppetdb[124158]: WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operationsJan 31 12:43:37 harmony3-d1.anu.edu.au puppetdb[124158]: WARNING: All illegal access operations will be denied in a future releaseJan 31 12:43:52 harmony3-d1.anu.edu.au puppetdb[124158]: The [database] classname config option has been retired and will be ignored.Jan 31 12:43:52 harmony3-d1.anu.edu.au puppetdb[124158]: The [database] log-slow-statements config option has been retired and will be ignored.Jan 31 12:43:52 harmony3-d1.anu.edu.au puppetdb[124158]: The [database] subprotocol config option has been retired and will be ignored.Jan 31 12:44:04 harmony3-d1.anu.edu.au puppetdb[124158]: The [database] classname config option has been retired and will be ignored.Jan 31 12:44:04 harmony3-d1.anu.edu.au puppetdb[124158]: The [database] log-slow-statements config option has been retired and will be ignored.Jan 31 12:44:04 harmony3-d1.anu.edu.au puppetdb[124158]: The [database] subprotocol config option has been retired and will be ignored.Jan 31 12:44:13 harmony3-d1.anu.edu.au puppetdb[124158]: Execution error (PSQLException) at org.postgresql.core.v3.QueryExecutorImpl/receiveErrorResponse (QueryExecutorImpl.java:2497).Jan 31 12:44:13 harmony3-d1.anu.edu.au puppetdb[124158]: ERROR: relation "resource_events_20200123z" does not existJan 31 12:44:13 harmony3-d1.anu.edu.au puppetdb[124158]: Position: 13Jan 31 12:44:13 harmony3-d1.anu.edu.au puppetdb[124158]: Full report at:Jan 31 12:44:13 harmony3-d1.anu.edu.au puppetdb[124158]: /tmp/clojure-986115849128723.ednJan 31 12:44:13 harmony3-d1.anu.edu.au systemd[1]: pe-puppet
Jira (PDB-4642) Puppet 2019.3 upgrade failure from 2019.2.2
Title: Message Title Selvakumar Azhagarsami commented on PDB-4642 Re: Puppet 2019.3 upgrade failure from 2019.2.2 PE standard customer reported this issue. https://puppetlabs.zendesk.com/agent/tickets/37911 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.344931.1580780081000.12425.1580780460115%40Atlassian.JIRA.
Jira (PDB-4642) Puppet 2019.3 upgrade failure from 2019.2.2
Title: Message Title
Selvakumar Azhagarsami updated an issue
PuppetDB / PDB-4642
Puppet 2019.3 upgrade failure from 2019.2.2
Change By:
Selvakumar Azhagarsami
During the upgrade from 2019.2.2 to 2019.3, pe-puppetdb service is failed to start with the error message "resource_events_20200123z" does not exist. Please refer to the attached log file for more details.{code:java}[m2020-01-31T12:43:01.508+11:00 - [Notice]: /Stage[main]/Puppet_enterprise::Puppetdb::Service/Puppet_enterprise::Trapperkeeper::Pe_service[puppetdb]/Exec[pe-puppetdb service full restart]: Triggered 'refresh' from 1 event [0m [1;31m2020-01-31T12:44:13.543+11:00 - [Error]: Systemd start for pe-puppetdb failed!journalctl log for pe-puppetdb:-- Logs begin at Mon 2019-12-23 23:25:01 AEDT, end at Fri 2020-01-31 12:44:13 AEDT. --Jan 31 12:43:02 harmony3-d1.anu.edu.au systemd[1]: Starting pe-puppetdb Service...Jan 31 12:43:37 harmony3-d1.anu.edu.au puppetdb[124158]: WARNING: An illegal reflective access operation has occurredJan 31 12:43:37 harmony3-d1.anu.edu.au puppetdb[124158]: WARNING: Illegal reflective access by dynapath.defaults$eval24067$fn__24068 to method java.net.URLClassLoader.addURL(java.net.URL)Jan 31 12:43:37 harmony3-d1.anu.edu.au puppetdb[124158]: WARNING: Please consider reporting this to the maintainers of dynapath.defaults$eval24067$fn__24068Jan 31 12:43:37 harmony3-d1.anu.edu.au puppetdb[124158]: WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operationsJan 31 12:43:37 harmony3-d1.anu.edu.au puppetdb[124158]: WARNING: All illegal access operations will be denied in a future releaseJan 31 12:43:52 harmony3-d1.anu.edu.au puppetdb[124158]: The [database] classname config option has been retired and will be ignored.Jan 31 12:43:52 harmony3-d1.anu.edu.au puppetdb[124158]: The [database] log-slow-statements config option has been retired and will be ignored.Jan 31 12:43:52 harmony3-d1.anu.edu.au puppetdb[124158]: The [database] subprotocol config option has been retired and will be ignored.Jan 31 12:44:04 harmony3-d1.anu.edu.au puppetdb[124158]: The [database] classname config option has been retired and will be ignored.Jan 31 12:44:04 harmony3-d1.anu.edu.au puppetdb[124158]: The [database] log-slow-statements config option has been retired and will be ignored.Jan 31 12:44:04 harmony3-d1.anu.edu.au puppetdb[124158]: The [database] subprotocol config option has been retired and will be ignored.Jan 31 12:44:13 harmony3-d1.anu.edu.au puppetdb[124158]: Execution error (PSQLException) at org.postgresql.core.v3.QueryExecutorImpl/receiveErrorResponse (QueryExecutorImpl.java:2497).Jan 31 12:44:13 harmony3-d1.anu.edu.au puppetdb[124158]: ERROR: relation "resource_events_20200123z" does not existJan 31 12:44:13 harmony3-d1.anu.edu.au puppetdb[124158]: Position: 13Jan 31 12:44:13 harmony3-d1.anu.edu.au puppetdb[124158]: Full report at:Jan 31 12:44:13 harmony3-d1.anu.edu.au puppetdb[124158]: /tmp/clojure-986115849128723.ednJan 31 12:44:13 harmony3-d1.anu.edu.au systemd[1]: pe-puppet
Jira (PDB-4642) Puppet 2019.3 upgrade failure from 2019.2.2
Title: Message Title
Selvakumar Azhagarsami updated an issue
PuppetDB / PDB-4642
Puppet 2019.3 upgrade failure from 2019.2.2
Change By:
Selvakumar Azhagarsami
During the upgrade from 2019.2.2 to 2019.3, pe-puppetdb service is failed to start with the error message "resource_events_20200123z" does not exist. Please refer to the attached log file for more details.{code:java}[m2020-01-31T12:43:01.508+11:00 - [Notice]: /Stage[main]/Puppet_enterprise::Puppetdb::Service/Puppet_enterprise::Trapperkeeper::Pe_service[puppetdb]/Exec[pe-puppetdb service full restart]: Triggered 'refresh' from 1 event [0m [1;31m2020-01-31T12:44:13.543+11:00 - [Error]: Systemd start for pe-puppetdb failed!journalctl log for pe-puppetdb:-- Logs begin at Mon 2019-12-23 23:25:01 AEDT, end at Fri 2020-01-31 12:44:13 AEDT. --Jan 31 12:43:02 harmony3-d1.anu.edu.au systemd[1]: Starting pe-puppetdb Service...Jan 31 12:43:37 harmony3-d1.anu.edu.au puppetdb[124158]: WARNING: An illegal reflective access operation has occurredJan 31 12:43:37 harmony3-d1.anu.edu.au puppetdb[124158]: WARNING: Illegal reflective access by dynapath.defaults$eval24067$fn__24068 to method java.net.URLClassLoader.addURL(java.net.URL)Jan 31 12:43:37 harmony3-d1.anu.edu.au puppetdb[124158]: WARNING: Please consider reporting this to the maintainers of dynapath.defaults$eval24067$fn__24068Jan 31 12:43:37 harmony3-d1.anu.edu.au puppetdb[124158]: WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operationsJan 31 12:43:37 harmony3-d1.anu.edu.au puppetdb[124158]: WARNING: All illegal access operations will be denied in a future releaseJan 31 12:43:52 harmony3-d1.anu.edu.au puppetdb[124158]: The [database] classname config option has been retired and will be ignored.Jan 31 12:43:52 harmony3-d1.anu.edu.au puppetdb[124158]: The [database] log-slow-statements config option has been retired and will be ignored.Jan 31 12:43:52 harmony3-d1.anu.edu.au puppetdb[124158]: The [database] subprotocol config option has been retired and will be ignored.Jan 31 12:44:04 harmony3-d1.anu.edu.au puppetdb[124158]: The [database] classname config option has been retired and will be ignored.Jan 31 12:44:04 harmony3-d1.anu.edu.au puppetdb[124158]: The [database] log-slow-statements config option has been retired and will be ignored.Jan 31 12:44:04 harmony3-d1.anu.edu.au puppetdb[124158]: The [database] subprotocol config option has been retired and will be ignored.Jan 31 12:44:13 harmony3-d1.anu.edu.au puppetdb[124158]: Execution error (PSQLException) at org.postgresql.core.v3.QueryExecutorImpl/receiveErrorResponse (QueryExecutorImpl.java:2497).Jan 31 12:44:13 harmony3-d1.anu.edu.au puppetdb[124158]: ERROR: relation "resource_events_20200123z" does not existJan 31 12:44:13 harmony3-d1.anu.edu.au puppetdb[124158]: Position: 13Jan 31 12:44:13 harmony3-d1.anu.edu.au puppetdb[124158]: Full report at:Jan 31 12:44:13 harmony3-d1.anu.edu.au puppetdb[124158]: /tmp/clojure-986115849128723.ednJan 31 12:44:13 harmony3-d1.anu.edu.au systemd[1]: pe-puppet
Jira (PDB-4642) Puppet 2019.3 upgrade failure from 2019.2.2
Title: Message Title
Selvakumar Azhagarsami updated an issue
PuppetDB / PDB-4642
Puppet 2019.3 upgrade failure from 2019.2.2
Change By:
Selvakumar Azhagarsami
During the upgrade from 2019.2.2 to 2019.3, pe-puppetdb service is failed to start with the error message "resource_events_20200123z" does not exist.{code:java} [m2020-01-31T12:43:01.508+11:00 - [Notice]: /Stage[main]/Puppet_enterprise::Puppetdb::Service/Puppet_enterprise::Trapperkeeper::Pe_service[puppetdb]/Exec[pe-puppetdb service full restart]: Triggered 'refresh' from 1 event [0m [1;31m2020-01-31T12:44:13.543+11:00 - [Error]: Systemd start for pe-puppetdb failed!journalctl log for pe-puppetdb:-- Logs begin at Mon 2019-12-23 23:25:01 AEDT, end at Fri 2020-01-31 12:44:13 AEDT. --Jan 31 12:43:02 harmony3-d1.anu.edu.au systemd[1]: Starting pe-puppetdb Service...Jan 31 12:43:37 harmony3-d1.anu.edu.au puppetdb[124158]: WARNING: An illegal reflective access operation has occurredJan 31 12:43:37 harmony3-d1.anu.edu.au puppetdb[124158]: WARNING: Illegal reflective access by dynapath.defaults$eval24067$fn__24068 to method java.net.URLClassLoader.addURL(java.net.URL)Jan 31 12:43:37 harmony3-d1.anu.edu.au puppetdb[124158]: WARNING: Please consider reporting this to the maintainers of dynapath.defaults$eval24067$fn__24068Jan 31 12:43:37 harmony3-d1.anu.edu.au puppetdb[124158]: WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operationsJan 31 12:43:37 harmony3-d1.anu.edu.au puppetdb[124158]: WARNING: All illegal access operations will be denied in a future releaseJan 31 12:43:52 harmony3-d1.anu.edu.au puppetdb[124158]: The [database] classname config option has been retired and will be ignored.Jan 31 12:43:52 harmony3-d1.anu.edu.au puppetdb[124158]: The [database] log-slow-statements config option has been retired and will be ignored.Jan 31 12:43:52 harmony3-d1.anu.edu.au puppetdb[124158]: The [database] subprotocol config option has been retired and will be ignored.Jan 31 12:44:04 harmony3-d1.anu.edu.au puppetdb[124158]: The [database] classname config option has been retired and will be ignored.Jan 31 12:44:04 harmony3-d1.anu.edu.au puppetdb[124158]: The [database] log-slow-statements config option has been retired and will be ignored.Jan 31 12:44:04 harmony3-d1.anu.edu.au puppetdb[124158]: The [database] subprotocol config option has been retired and will be ignored.Jan 31 12:44:13 harmony3-d1.anu.edu.au puppetdb[124158]: Execution error (PSQLException) at org.postgresql.core.v3.QueryExecutorImpl/receiveErrorResponse (QueryExecutorImpl.java:2497).Jan 31 12:44:13 harmony3-d1.anu.edu.au puppetdb[124158]: ERROR: relation "resource_events_20200123z" does not existJan 31 12:44:13 harmony3-d1.anu.edu.au puppetdb[124158]: Position: 13Jan 31 12:44:13 harmony3-d1.anu.edu.au puppetdb[124158]: Full report at:Jan 31 12:44:13 harmony3-d1.anu.edu.au puppetdb[124158]: /tmp/clojure-986115849128723.ednJan 31 12:44:13 harmony3-d1.anu.edu.au systemd[1]: pe-puppetdb.service: control process exited, code=exited status
Jira (PDB-4642) Puppet 2019.3 upgrade failure from 2019.2.2
Title: Message Title
Selvakumar Azhagarsami updated an issue
PuppetDB / PDB-4642
Puppet 2019.3 upgrade failure from 2019.2.2
Change By:
Selvakumar Azhagarsami
During the upgrade from 2019.2.2 to 2019.3, pe-puppetdb service is failed to start with the error message "resource_events_20200123z" does not exist. Please refer to the attached log file for more details. {code:java}[m2020-01-31T12:43:01.508+11:00 - [Notice]: /Stage[main]/Puppet_enterprise::Puppetdb::Service/Puppet_enterprise::Trapperkeeper::Pe_service[puppetdb]/Exec[pe-puppetdb service full restart]: Triggered 'refresh' from 1 event [0m [1;31m2020-01-31T12:44:13.543+11:00 - [Error]: Systemd start for pe-puppetdb failed!journalctl log for pe-puppetdb:-- Logs begin at Mon 2019-12-23 23:25:01 AEDT, end at Fri 2020-01-31 12:44:13 AEDT. --Jan 31 12:43:02 harmony3-d1.anu.edu.au systemd[1]: Starting pe-puppetdb Service...Jan 31 12:43:37 harmony3-d1.anu.edu.au puppetdb[124158]: WARNING: An illegal reflective access operation has occurredJan 31 12:43:37 harmony3-d1.anu.edu.au puppetdb[124158]: WARNING: Illegal reflective access by dynapath.defaults$eval24067$fn__24068 to method java.net.URLClassLoader.addURL(java.net.URL)Jan 31 12:43:37 harmony3-d1.anu.edu.au puppetdb[124158]: WARNING: Please consider reporting this to the maintainers of dynapath.defaults$eval24067$fn__24068Jan 31 12:43:37 harmony3-d1.anu.edu.au puppetdb[124158]: WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operationsJan 31 12:43:37 harmony3-d1.anu.edu.au puppetdb[124158]: WARNING: All illegal access operations will be denied in a future releaseJan 31 12:43:52 harmony3-d1.anu.edu.au puppetdb[124158]: The [database] classname config option has been retired and will be ignored.Jan 31 12:43:52 harmony3-d1.anu.edu.au puppetdb[124158]: The [database] log-slow-statements config option has been retired and will be ignored.Jan 31 12:43:52 harmony3-d1.anu.edu.au puppetdb[124158]: The [database] subprotocol config option has been retired and will be ignored.Jan 31 12:44:04 harmony3-d1.anu.edu.au puppetdb[124158]: The [database] classname config option has been retired and will be ignored.Jan 31 12:44:04 harmony3-d1.anu.edu.au puppetdb[124158]: The [database] log-slow-statements config option has been retired and will be ignored.Jan 31 12:44:04 harmony3-d1.anu.edu.au puppetdb[124158]: The [database] subprotocol config option has been retired and will be ignored.Jan 31 12:44:13 harmony3-d1.anu.edu.au puppetdb[124158]: Execution error (PSQLException) at org.postgresql.core.v3.QueryExecutorImpl/receiveErrorResponse (QueryExecutorImpl.java:2497).Jan 31 12:44:13 harmony3-d1.anu.edu.au puppetdb[124158]: ERROR: relation "resource_events_20200123z" does not existJan 31 12:44:13 harmony3-d1.anu.edu.au puppetdb[124158]: Position: 13Jan 31 12:44:13 harmony3-d1.anu.edu.au puppetdb[124158]: Full report at:Jan 31 12:44:13 harmony3-d1.anu.edu.au puppetdb[124158]: /tmp/clojure-986115849128723.ednJan 31 12:44:13 harmony3-d1.anu.edu.au systemd[1]: pe-pupp
Jira (PDB-4642) Puppet 2019.3 upgrade failure from 2019.2.2
Title: Message Title Selvakumar Azhagarsami created an issue PuppetDB / PDB-4642 Puppet 2019.3 upgrade failure from 2019.2.2 Issue Type: Bug Assignee: Unassigned Attachments: 2020-01-31T12.33.25 1100.install.log Components: PuppetDB Created: 2020/02/03 5:34 PM Priority: Normal Reporter: Selvakumar Azhagarsami During the upgrade from 2019.2.2 to 2019.3, pe-puppetdb service is failed to start with the error message "resource_events_20200123z" does not exist. [m2020-01-31T12:43:01.508+11:00 - [Notice]: /Stage[main]/Puppet_enterprise::Puppetdb::Service/Puppet_enterprise::Trapperkeeper::Pe_service[puppetdb]/Exec[pe-puppetdb service full restart]: Triggered 'refresh' from 1 event [0m [1;31m2020-01-31T12:44:13.543+11:00 - [Error]: Systemd start for pe-puppetdb failed! journalctl log for pe-puppetdb: -- Logs begin at
