Jira (PUP-7526) no pip2 package provider when pip3 is system default
Title: Message Title James Glenn commented on PUP-7526 Re: no pip2 package provider when pip3 is system default Created fresh PR with different base branch. https://github.com/puppetlabs/puppet/pull/8311 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.190780.1494614925000.29849.1599121020025%40Atlassian.JIRA.
Jira (PUP-7526) no pip2 package provider when pip3 is system default
Title: Message Title James Glenn commented on PUP-7526 Re: no pip2 package provider when pip3 is system default MR https://github.com/puppetlabs/puppet/pull/8300. Please review. 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.190780.1494614925000.26171.1598637960156%40Atlassian.JIRA.
Jira (PDB-1880) org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint "reports_pkey"
Title: Message Title James Glenn assigned an issue to James Glenn I have not been able to reproduce since upgrading versions. PuppetDB / PDB-1880 org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint "reports_pkey" Change By: James Glenn Resolution: Cannot Reproduce Assignee: James Glenn Status: Open Closed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-1880) org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint "reports_pkey"
Title: Message Title James Glenn commented on PDB-1880 Re: org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint "reports_pkey" Have not had this issue since moving to puppetdb 2.3.8. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1880) org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint reports_pkey
Title: Message Title
James Glenn commented on PDB-1880
Re: org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint reports_pkey
does your setup contain a single PuppetDB instance or multiple? Same question for Puppet masters.
Single puppetdb server and single puppet master server.
have you recently used the import tool (or other bulk loading tool) to get data into PuppetDB?
No.
is this an isolated occurrence or do you have similar conflicts for other reports?
Seems to be limited to Key (hash)=(6cb10ac4b4be82870db2a709a346fb4a132325cb)
[root@plvmlinfra01 ~]# curl -X GET http://localhost:8080/v4/reports -d 'query=[=,hash,6cb10ac4b4be82870db2a709a346fb4a132325cb]'
[ {
hash : 6cb10ac4b4be82870db2a709a346fb4a132325cb,
puppet-version : 3.8.1,
receive-time : 2015-08-06T05:08:55.507Z,
report-format : 4,
start-time : 2015-08-06T04:34:51.035Z,
end-time : 2015-08-06T04:35:06.526Z,
Jira (PDB-1880) org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint reports_pkey
Title: Message Title James Glenn commented on PDB-1880 Re: org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint reports_pkey No clue. Nothing about the environment should cause that. puppetdb configs: [global] # Store mq/db data in a custom directory vardir = /var/lib/puppetdb # Use an external logback config file logging-config = /etc/puppetdb/logback.xml [command-processing] # How many command-processing threads to use, defaults to (CPUs / 2) # threads = 4
Jira (PDB-1880) org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint reports_pkey
Title: Message Title
James Glenn created an issue
PuppetDB / PDB-1880
org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint reports_pkey
Issue Type:
Bug
Affects Versions:
PDB 2.3.6
Assignee:
Unassigned
Created:
2015/08/06 12:12 PM
Environment:
CentOS 7.1.1503
puppet-3.8.1-1.el7.noarch puppetlabs-release-7-11.noarch puppetdb-2.3.6-1.el7.noarch puppet-server-3.8.1-1.el7.noarch puppetdb-terminus-2.3.6-1.el7.noarch
postgresql-server-9.2.13-1.el7_1.x86_64 postgresql-contrib-9.2.13-1.el7_1.x86_64 postgresql-9.2.13-1.el7_1.x86_64 postgresql-libs-9.2.13-1.el7_1.x86_64
Priority:
Minor
Reporter:
James Glenn
{{2015-08-06 14:05:37,551 INFO [o.e.j.u.log] Logging initialized @38444ms 2015-08-06 14:05:40,472 INFO [p.t.s.w.jetty9-service] Initializing web server(s). 2015-08-06 14:05:40,485 INFO [p.t.s.w.jetty9-service] Starting web server(s). 2015-08-06 14:05:40,734 INFO [p.t.s.w.jetty9-core] Starting web server. 2015-08-06 14:05:40,739 INFO [o.e.j.s.Server] jetty-9.2.z-SNAPSHOT 2015-08-06 14:05:40,822 INFO [o.e.j.s.ServerConnector] Started ServerConnector@64127516 {HTTP/1.1} {localhost:8080}
2015-08-06 14:05:40,938 INFO [o.e.j.s.ServerConnector] Started ServerConnector@2c46492b
Jira (PDB-1880) org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint reports_pkey
Title: Message Title James Glenn commented on PDB-1880 Re: org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint reports_pkey Please let me know if anyone needs more info. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-236) Facter RPM should not require virt-what
Title: Message Title Glenn commented on an issue Re: Facter RPM should not require virt-what The issue is that facter is not correctly identifying the instance as an ec2 instance. This is because it's not resolving the virtual fact correctly (see the bugs that I linked). Because it's not identifying the instance as an ec2 instance, it is also not resolving the ec2_* facts. FACT-185 is a duplicate of this issue. Does that help? Add Comment Facter / FACT-236 Facter RPM should not require virt-what There is a bug in virt-what that causes facter to behave incorrectly. https://bugzilla.redhat.com/show_bug.cgi?id=973663 http://projects.puppetlabs.com/issues/7559#note-71 I'm currently in the process of updating my automation to install facter (and thus puppet) as gems instead of RPM's due to the fact that the RPM (after v1.6.10) requires the virt-w... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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,
Jira (FACT-185) No EC2 facts shown on newly-built Amazon Linux host
Title: Message Title Glenn commented on an issue Re: No EC2 facts shown on newly-built Amazon Linux host Adrien, is the output in this comment (https://tickets.puppetlabs.com/browse/FACT-185?focusedCommentId=52961page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-52961) from an instance that is inside a VPC? Add Comment Facter / FACT-185 No EC2 facts shown on newly-built Amazon Linux host `facter|grep ec2` yields only the 'domain' and 'fqdn' facts for me, not a gaggle of them including stuff like 'ec2_profile'. The same versions on another host are working fine. Any tips on troubleshooting? An strace isn't showing anything promising to me, although it confirms that it's firing up the ec2.rb library. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit
Jira (FACT-236) Facter RPM should not require virt-what
Title: Message Title Glenn commented on an issue Re: Facter RPM should not require virt-what I understand the reluctance to remove the virt-what dependency. Perhaps adding code to work around this particular issue with ec2 instances inside AWS VPC's. Perhaps, FACT-185 does just that. I posted a comment in that ticket trying to determine if this particular case was tested (an ec2 instance inside a VPC with virt-what installed on it). Add Comment Facter / FACT-236 Facter RPM should not require virt-what There is a bug in virt-what that causes facter to behave incorrectly. https://bugzilla.redhat.com/show_bug.cgi?id=973663 http://projects.puppetlabs.com/issues/7559#note-71 I'm currently in the process of updating my automation to install facter (and thus puppet) as gems instead of RPM's due to the fact that the RPM (after v1.6.10) requires the virt-w... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group,
Jira (FACT-236) Facter RPM should not require virt-what
Title: Message Title Glenn created an issue Facter / FACT-236 Facter RPM should not require virt-what Issue Type: Bug Assignee: Eric Sorenson Created: 21/Jan/14 6:16 AM Fix Versions: 1.7.4 Priority: Normal Reporter: Glenn There is a bug in virt-what that causes facter to behave incorrectly. https://bugzilla.redhat.com/show_bug.cgi?id=973663 http://projects.puppetlabs.com/issues/7559#note-71 I'm currently in the process of updating my automation to install facter (and thus puppet) as gems instead of RPM's due to the fact that the RPM (after v1.6.10) requires the virt-what package which causes the bug mentioned here to manifest. When this bug manifests, facter does not resolve ec2 facts. http://projects.puppetlabs.com/issues/7559#note-70 It appears that there is no 'hard' requirement on the virt-what package as facter appears (to me) to behave correctly without this package installed. Please remove the dependency so that we can continue to use RPM's for package installation. Add Comment
