Jira (PUP-2782) Yumrepo target attribute does not work
Title: Message Title Fabrice Bacchella commented on PUP-2782 Re: Yumrepo target attribute does not work If target don't work, please don't put it on the documentation. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (PUP-7452) puppet certificate is missing a real destroy
Title: Message Title Fabrice Bacchella created an issue Puppet / PUP-7452 puppet certificate is missing a real destroy Issue Type: Improvement Affects Versions: PUP 4.10.0 Assignee: Unassigned Created: 2017/04/18 6:13 AM Priority: Normal Reporter: Fabrice Bacchella Puppet provides a 'certificate' command to allows remote CA management. But the option 'destroy' only operate on the local CA. It break one of the main purpose of that command, to allows remote administration of puppet CA. Wihout a remote destroy, generate and sign are not very useful, as they can only works on brand new hosts, not re-installed one. Add Comment
Jira (FACT-1165) facter partitions don't manage old HP SA
Title: Message Title Fabrice Bacchella commented on FACT-1165 Re: facter partitions don't manage old HP SA Any new for this ticket ? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-1166) bug in RHEL's latest libblkid and facter partitions
Title: Message Title Fabrice Bacchella commented on FACT-1166 Re: bug in RHEL's latest libblkid and facter partitions 2015-10-29 17:07:16.413489 INFO puppetlabs.facter - executed with command line: -d partitions. 2015-10-29 17:07:16.414570 INFO leatherman.ruby:124 - ruby loaded from "/opt/puppetlabs/puppet/lib/libruby.so.2.1.0". 2015-10-29 17:07:16.421175 INFO leatherman.ruby:145 - using ruby version 2.1.6 2015-10-29 17:07:16.458663 INFO puppetlabs.facter - requested queries: partitions. 2015-10-29 17:07:16.458890 DEBUG puppetlabs.facter - fact "facterversion" has resolved to "3.1.0". 2015-10-29 17:07:16.459585 DEBUG puppetlabs.facter - searching "/opt/puppetlabs/facter/facts.d" for external facts. 2015-10-29 17:07:16.459788 DEBUG puppetlabs.facter - skipping external facts for "/etc/facter/facts.d": No such file or directory 2015-10-29 17:07:16.459923 DEBUG puppetlabs.facter - skipping external facts for "/etc/puppetlabs/facter/facts.d": No such file or directory 2015-10-29 17:07:16.460050 DEBUG puppetlabs.facter - no external facts were found.
Jira (FACT-1166) bug in RHEL's latest libblkid and facter partitions
Title: Message Title Fabrice Bacchella commented on FACT-1166 Re: bug in RHEL's latest libblkid and facter partitions What is missing ? Everything, only the raw device size and the mount point is given. It used to be the file system type, the file system uuid, the label. All are gone. But everything is still here on a RHEL6. Of course, all tests are done as root, after a reboot. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 (PUP-4970) puppetlabs-release and puppetlabs-release-pc1 both needed but fails on RHEL6
Title: Message Title Fabrice Bacchella commented on PUP-4970 Re: puppetlabs-release and puppetlabs-release-pc1 both needed but fails on RHEL6 Nice try, but failed: ~# yum update puppetlabs-release-pc1 ... ---> Package puppetlabs-release-pc1.noarch 0:0.9.2-1.el6 will be updated ---> Package puppetlabs-release-pc1.noarch 0:1.0.0-1.el6 will be an update ... Package puppetlabs-release-pc1-1.0.0-1.el6.noarch.rpm is not signed Add Comment
Jira (PUP-4970) puppetlabs-release and puppetlabs-release-pc1 both needed but fails on RHEL6
Title: Message Title Fabrice Bacchella commented on PUP-4970 Re: puppetlabs-release and puppetlabs-release-pc1 both needed but fails on RHEL6 PC1 and product can be installed side by side. The only conflict is in puppetlabs-release and puppetlabs-release-pc1 rpm, because of a shared pgp key file. I rebuild my own puppetlabs-release rpm for RHEL 6 without the key and so have been able to install puppet-agent from pc1 and the the mcollective components from product. I have done that on the puppet server that run both puppet server and activemq. And it works very well, I haven't met a single problem. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-1165) facter partitions don't manage old HP SA
Title: Message Title Fabrice Bacchella commented on FACT-1165 Re: facter partitions don't manage old HP SA It works for me now. But the name for the partitions changed from /dev/cciss/c0d0p1 to /dev/cciss!c0d0p1 and this block device don't exist. It should be /dev/cciss/c0d0p1. $ ls -l '/dev/cciss!c0d0p1' '/dev/cciss/c0d0p1' ls: cannot access /dev/cciss!c0d0p1: No such file or directory brw-rw 1 root disk 104, 1 Aug 31 16:21 /dev/cciss/c0d0p1 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-1166) bug in RHEL's latest libblkid and facter partitions
Title: Message Title
Fabrice Bacchella commented on FACT-1166
Re: bug in RHEL's latest libblkid and facter partitions
Better but I'm still getting incomplete results:
{
/dev/sda1 => {
size => "1.00 MiB",
size_bytes => 1048576
},
/dev/sda2 => {
mount => "/",
size => "16.00 GiB",
size_bytes => 17179869184
},
/dev/sda3 => {
Jira (PUP-4970) puppetlabs-release and puppetlabs-release-pc1 both needed but fails on RHEL6
Title: Message Title Fabrice Bacchella commented on PUP-4970 Re: puppetlabs-release and puppetlabs-release-pc1 both needed but fails on RHEL6 Did someone look at this issue ? 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-1165) facter partitions don't manage old HP SA
Title: Message Title
Fabrice Bacchella created an issue
Facter / FACT-1165
facter partitions don't manage old HP SA
Issue Type:
Bug
Assignee:
Unassigned
Created:
2015/08/19 3:08 AM
Environment:
Redhat 7, with HP Smart Array P400
Priority:
Normal
Reporter:
Fabrice Bacchella
HP Smart Array P400 are hardware RAID SAS controler. They don't expose logical drives as scsi device but custom block device in /dev/cciss. Facter partitions don't know how to handle them:
# facter partitions
{
/dev/cciss/c0d0 = {
Jira (FACT-1166) bug in RHEL's latest libblkid and facter partitions
Title: Message Title Fabrice Bacchella created an issue Facter / FACT-1166 bug in RHEL's latest libblkid and facter partitions Issue Type: Bug Affects Versions: FACT 3.0.2 Assignee: Unassigned Components: UX Created: 2015/08/19 3:12 AM Environment: Centos 7, recently upgraded Priority: Normal Reporter: Fabrice Bacchella A bug in the latest libblkid for RHEL 7 broke facter partitions For example, on two servers, with different version of this package: Before (libblkid-2.23.2-22.el7_1.x86_64.): ~# facter partitions
Jira (PUP-4970) puppetlabs-release and puppetlabs-release-pc1 both needed but fails on RHEL6
Title: Message Title Fabrice Bacchella created an issue Puppet / PUP-4970 puppetlabs-release and puppetlabs-release-pc1 both needed but fails on RHEL6 Issue Type: Bug Affects Versions: PUP 4.2.1 Assignee: Unassigned Created: 2015/07/31 6:30 AM Environment: Centos 6 Priority: Normal Reporter: Fabrice Bacchella I want to both install puppet 4 and some mcollective plugins on a CentOS 6 As the the mcollective plugins are not in the PC1 repository, I need the products repository. But then : yum install https://yum.puppetlabs.com/el/6/products/x86_64/puppetlabs-release-6-11.noarch.rpm https://yum.puppetlabs.com/el/6/PC1/x86_64/puppetlabs-release-pc1-0.9.2-1.el6.noarch.rpm
Jira (FACT-1152) facter partitions don't work on Centos 5
Title: Message Title Fabrice Bacchella created an issue Facter / FACT-1152 facter partitions don't work on Centos 5 Issue Type: Bug Affects Versions: FACT 3.0.2 Assignee: Unassigned Created: 2015/07/30 9:15 AM Environment: # facter --version 3.0.2 (commit 5dc120fa9db4c19150466b1bbd1d0cf42c87c6bd) # lsb_release -a LSB Version::core-4.0-amd64:core-4.0-ia32:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-ia32:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-ia32:printing-4.0-noarch Distributor ID: CentOS
Jira (FACT-1152) facter partitions don't work on Centos 5
Title: Message Title Fabrice Bacchella commented on FACT-1152 Re: facter partitions don't work on Centos 5 Options 3 would be a very bad solution. RHEL5 is still supported by Redhat, and the purpose of facts and puppet is to manage old or strange installation, so sysadmin don't have to fight with each corner case and expect consistent results in an heterogenous datacenter. 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-1137) facter productname fails on CentOS
Title: Message Title
Fabrice Bacchella updated an issue
Facter / FACT-1137
facter productname fails on CentOS
Change By:
Fabrice Bacchella
Environment:
{code}~#lsb_release-aLSBVersion: :core-4.0-amd64:core-4.0-ia32:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-ia32:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-ia32:printing-4.0-noarchDistributorID: CentOSDescription: CentOSrelease5.11(Final)Release: 5.11Codename: Final{code}
Idon'tgettheproductnameonaallmyCentos5:{code}~#dmidecode-ssystem-product-nameSUNFIREX4150~# echo$( /opt/puppetlabs/bin/facterproductname ) {code}or:{code}~#dmidecode-ssystem-product-nameProLiantDL140G3~#echo$(/opt/puppetlabs/bin/facterproductname){code} ButonaScientificLinux6:{code}~#/opt/puppetlabs/bin/facterproductnameProLiantDL140G3{code}
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-1137) facter productname fails on CentOS
Title: Message Title Fabrice Bacchella created an issue Facter / FACT-1137 facter productname fails on CentOS Issue Type: Bug Affects Versions: FACT 3.0.1 Assignee: Unassigned Created: 2015/07/21 9:37 AM Environment: ~# lsb_release -a LSB Version: :core-4.0-amd64:core-4.0-ia32:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-ia32:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-ia32:printing-4.0-noarch Distributor ID: CentOS Description: CentOS release 5.11 (Final) Release: 5.11
Jira (FACT-1137) facter productname fails on CentOS
Title: Message Title Fabrice Bacchella commented on FACT-1137 Re: facter productname fails on CentOS ~# /opt/puppetlabs/bin/facter -d productname 21 2015-07-21 20:09:00.986567 INFO puppetlabs.facter - executed with command line: -d productname. 2015-07-21 20:09:00.987506 INFO puppetlabs.facter - ruby loaded from /opt/puppetlabs/puppet/lib/libruby.so.2.1.0. 2015-07-21 20:09:00.994273 INFO puppetlabs.facter - using ruby version 2.1.6 to resolve custom facts. 2015-07-21 20:09:01.033352 INFO puppetlabs.facter - requested queries: productname. 2015-07-21 20:09:01.033631 DEBUG puppetlabs.facter - fact facterversion has resolved to 3.0.1. 2015-07-21 20:09:01.034212 DEBUG puppetlabs.facter - skipping external facts for /opt/puppetlabs/facter/facts.d: No such file or directory 2015-07-21 20:09:01.034329 DEBUG puppetlabs.facter - skipping external facts for /etc/facter/facts.d: No such file or directory 2015-07-21 20:09:01.034458 DEBUG puppetlabs.facter - skipping external facts for /etc/puppetlabs/facter/facts.d: No such file or directory
Jira (FACT-184) Using 'ip addr' over ifconfig
Title: Message Title Fabrice Bacchella commented on FACT-184 Re: Using 'ip addr' over ifconfig You don't intent to fixe it until facter 3 is out ? The current interfaces fact implementation is broken in many way : it still uses ifconfig, which is broken in linux since years it launch ifconfig in a wrong way: sh, -c, /sbin/ifconfig -a 2/dev/null, why fork a shell for that ? it's result are wrong, because ifconfig is deprecated, and ifconfig confuse interfaces and ip address, On a RHEL7, if you have two IP on the same interface, ifconfig gives : bond0: flags=5187UP,BROADCAST,RUNNING,MASTER,MULTICAST mtu 1500 ... bond0:git: flags=5187UP,BROADCAST,RUNNING,MASTER,MULTICAST mtu 1500 ... But ip link list, /proc/net/dev, snmp only see bond0, so the bond0_git interface is unusable in many ways. Add Comment
Jira (PUP-723) Due to prefetching, Yumrepo clobbers any definition that it does not create
Title: Message Title Fabrice Bacchella commented on PUP-723 Re: Due to prefetching, Yumrepo clobbers any definition that it does not create Does it needs 6 years to decide to add a stat(repofile) and rescan a prefetched file if it's newer than the cached version ? That would be much easer than refactor yumrepo to use a provider. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 (PDB-765) Puppetdb connexion to postgresql using client certificate
Title: Message Title Fabrice Bacchella commented on an issue Re: Puppetdb connexion to postgresql using client certificate This setting don't check if the certificate name matches the connection name. One should add : sslhostnameverifier = org.postgresql.ssl.jdbc4.LibPQFactory in the subname. Add Comment PuppetDB / PDB-765 Puppetdb connexion to postgresql using client certificate For people wanting to authenticate on a posgresql server, using a X509 client certificate, this procedure might help. This procedure does it in the java way, ie it take a jks store, not pem files. First create a jks with the private key for your account and put in it all the needed certificates in the chain (both server and user). The cn for user cert... 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
Jira (PDB-765) Puppetdb connexion to postgresql using client certificate
Title: Message Title Fabrice Bacchella created an issue PuppetDB / PDB-765 Puppetdb connexion to postgresql using client certificate Issue Type: Story Affects Versions: 2.1.0 Assignee: Unassigned Components: DOCS Created: 17/Jul/14 7:20 AM Priority: Minor Reporter: Fabrice Bacchella For people wanting to authenticate on a posgresql server, using a X509 client certificate, this procedure might help. This procedure does it in the java way, ie it take a jks store, not pem files. First create a jks with the private key for your account and put in it all the needed certificates in the chain (both server and user). The cn for user certificate should match the username used latter. Add to your JVM args : -Djavax.net.ssl.trustStore=.../puppetdb.jks -Djavax.net.ssl.trustStorePassword=JKS password -Djavax.net.ssl.keyStore=.../puppetdb.jks -Djavax.net.ssl.keyStorePassword=JKS password In case of problems, -Djavax.net.debug=ssl,defaultctx might help. My database.ini is : [database] classname = org.postgresql.Driver subprotocol = postgresql subname =
Jira (PUP-1235) enabling future parser breaks puppet - Do not add methods to model classes directly...
Title: Message Title Fabrice Bacchella commented on an issue Re: enabling future parser breaks puppet - Do not add methods to model classes directly... Got hit by this. What do you need to solve this ? Add Comment Puppet / PUP-1235 enabling future parser breaks puppet - Do not add methods to model classes directly... After enabling the future parser, agent runs fail with Could not parse for environment X: Do not add methods to model classes directly, add them to the ClassModule instead on node foo.bar This happens even with an empty node definition. up-to-date RHEL6.4 on master and agent with puppet 3.3.1 from puppetlabs repo The master is run via apache+pa... 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
