Jira (PUP-3127) LDAP - introduce LDAP-Certificat Directory
Title: Message Title Andreas Schuster updated an issue Puppet / PUP-3127 LDAP - introduce LDAP-Certificat Directory Change By: Andreas Schuster Fix Version/s: 3.7.0 Add Comment 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 https://groups.google.com/d/optout.
Jira (PUP-3127) LDAP - introduce LDAP-Certificat Directory
Title: Message Title Andreas Schuster updated an issue Puppet / PUP-3127 LDAP - introduce LDAP-Certificat Directory Change By: Andreas Schuster Fix Version/s: 3.7.1 Add Comment 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 https://groups.google.com/d/optout.
Jira (PDB-789) Smoke test packages
Title: Message Title Kenneth Barber commented on an issue Re: Smoke test packages Ubuntu 10.04 smoke tested with HSQLDB, PostgreSQL with and without structured facts. Looks good. Add Comment PuppetDB / PDB-789 Smoke test packages Procedure may vary by project and point in the release cycle. Ask around. 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 https://groups.google.com/d/optout.
Jira (PDB-789) Smoke test packages
Title: Message Title Kenneth Barber commented on an issue Re: Smoke test packages Centos 7 - check Add Comment PuppetDB / PDB-789 Smoke test packages Procedure may vary by project and point in the release cycle. Ask around. 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 https://groups.google.com/d/optout.
Jira (PDB-789) Smoke test packages
Title: Message Title Kenneth Barber commented on an issue Re: Smoke test packages Ubuntu 14.04 - check Add Comment PuppetDB / PDB-789 Smoke test packages Procedure may vary by project and point in the release cycle. Ask around. 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 https://groups.google.com/d/optout.
Jira (FACT-686) Upgrading to 2.2.0 throws errors on all clients
Title: Message Title Dan Schaefer created an issue Facter / FACT-686 Upgrading to 2.2.0 throws errors on all clients Issue Type: Bug Affects Versions: 2.2.0 Assignee: Eric Sorenson Created: 27/Aug/14 6:06 AM Environment: Ubuntu 12.04 Priority: Major Reporter: Dan Schaefer After updating facter from 2.1.0 to 2.2.0 on my Ubuntu 12.04 servers, I'm receiving errors like the following: Error: Failed to apply catalog: Parameter ensure failed on Package[samba]: Invalid value . Valid values are present, absent, purged, held, latest. Valid values match /./. at /etc/puppet/modules/samba/manifests/init.pp:331 Wrapped exception: Invalid value . Valid values are present, absent, purged, held, latest. Valid values match /./. Wrapped exception: Invalid value . Valid values are present, absent, purged, held, latest. Valid values match /./. AND Error: Could not retrieve catalog from remote server: Could not intern from text/pson: Could not intern from data: Could not find relationship target Package[] Warning: Not using cache on failed catalog Error: Could not retrieve catalog; skipping run AND Error: Failed to apply catalog: Parameter ensure failed on Package[mysql]: Invalid value . Valid values are present, absent, purged, held, latest. Valid values match /./. at
Jira (FACT-686) Upgrading to 2.2.0 throws errors on all clients
Title: Message Title Dan Schaefer updated an issue Facter / FACT-686 Upgrading to 2.2.0 throws errors on all clients Change By: Dan Schaefer Afterupdatingfacterfrom2.1.0to2.2.0onmyUbuntu12.04servers,I'mreceivingerrorslikethefollowing:Error:Failedtoapplycatalog:ParameterensurefailedonPackage[samba]:Invalidvalue.Validvaluesarepresent,absent,purged,held,latest.Validvaluesmatch/./.at/etc/puppet/modules/samba/manifests/init.pp:331Wrappedexception:Invalidvalue.Validvaluesarepresent,absent,purged,held,latest.Validvaluesmatch/./.Wrappedexception:Invalidvalue.Validvaluesarepresent,absent,purged,held,latest.Validvaluesmatch/./.ANDError:Couldnotretrievecatalogfromremoteserver:Couldnotinternfromtext/pson:Couldnotinternfromdata:CouldnotfindrelationshiptargetPackage[]Warning:NotusingcacheonfailedcatalogError:Couldnotretrievecatalog;skippingrunANDError:Failedtoapplycatalog:ParameterensurefailedonPackage[mysql]:Invalidvalue.Validvaluesarepresent,absent,purged,held,latest.Validvaluesmatch/./.at/etc/puppet/modules/mysql/manifests/init.pp:360Wrappedexception:Invalidvalue.Validvaluesarepresent,absent,purged,held,latest.Validvaluesmatch/./.Wrappedexception:Invalidvalue.Validvaluesarepresent,absent,purged,held,latest.Validvaluesmatch/./.TheseerrorsleadmetobelievethatthevaluesIhaveinmyhierafilesarenotbeingreadcorrectly,duetoafactoranumberoffactsnotbeingsetcorrectly duringthepuppetrun .ThefactsIusetodeterminethehierarchyinmyhierafilesare:$::fqdn,$::operatingsystem,$::lsbmajdistrelease,$::is_virtual,and$::osfamily.Alloftheseappearintheoutputwhenrunningfacter-pforboth2.1.0and2.2.0. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are
Jira (FACT-686) Upgrading to 2.2.0 throws errors on all clients
Title: Message Title
Dan Schaefer updated an issue
Facter / FACT-686
Upgrading to 2.2.0 throws errors on all clients
Change By:
Dan Schaefer
Afterupdatingfacterfrom2.1.0to2.2.0onmyUbuntu12.04servers,I'mreceivingerrorslikethefollowing: {code} Error:Failedtoapplycatalog:ParameterensurefailedonPackage[samba]:Invalidvalue.Validvaluesarepresent,absent,purged,held,latest.Validvaluesmatch/./.at/etc/puppet/modules/samba/manifests/init.pp:331Wrappedexception:Invalidvalue.Validvaluesarepresent,absent,purged,held,latest.Validvaluesmatch/./.Wrappedexception:Invalidvalue.Validvaluesarepresent,absent,purged,held,latest.Validvaluesmatch/./. {code} AND {code} Error:Couldnotretrievecatalogfromremoteserver:Couldnotinternfromtext/pson:Couldnotinternfromdata:CouldnotfindrelationshiptargetPackage[]Warning:NotusingcacheonfailedcatalogError:Couldnotretrievecatalog;skippingrun {code} AND {code} Error:Failedtoapplycatalog:ParameterensurefailedonPackage[mysql]:Invalidvalue.Validvaluesarepresent,absent,purged,held,latest.Validvaluesmatch/./.at/etc/puppet/modules/mysql/manifests/init.pp:360Wrappedexception:Invalidvalue.Validvaluesarepresent,absent,purged,held,latest.Validvaluesmatch/./.Wrappedexception:Invalidvalue.Validvaluesarepresent,absent,purged,held,latest.Validvaluesmatch/./. {code} TheseerrorsleadmetobelievethatthevaluesIhaveinmyhierafilesarenotbeingreadcorrectly,duetoafactoranumberoffactsnotbeingsetcorrectlyduringthepuppetrun.ThefactsIusetodeterminethehierarchyinmyhierafilesare:$::fqdn,$::operatingsystem,$::lsbmajdistrelease,$::is_virtual,and$::osfamily.Alloftheseappearintheoutputwhenrunningfacter-pforboth2.1.0and2.2.0.
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PDB-784) Update documentation indexes for new major release
Title: Message Title Kenneth Barber commented on an issue Re: Update documentation indexes for new major release https://github.com/puppetlabs/puppet-docs/pull/375 Add Comment PuppetDB / PDB-784 Update documentation indexes for new major release The current documentation indexes need to be updated for a final release. The main index needs the release to be moved into the stable section, and the index for this release needs the pre-release message removed. 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 https://groups.google.com/d/optout.
Jira (PDB-499) Replication: Sync up with PE team about ruby-puppetb support for multiple masters
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-499 Replication: Sync up with PE team about ruby-puppetb support for multiple masters Change By: Kenneth Barber Sprint: 20140910to20140924 Add Comment 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 https://groups.google.com/d/optout.
Jira (PDB-451) Versions for routes should be handled in a single place
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-451 Versions for routes should be handled in a single place Change By: Kenneth Barber Sprint: 20140827to20140910 Add Comment 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 https://groups.google.com/d/optout.
Jira (PDB-716) HTTP API gets stuck
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-716 HTTP API gets stuck Change By: Kenneth Barber Sprint: 20140827to20140910 Add Comment 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 https://groups.google.com/d/optout.
Jira (PDB-590) Fix unit tests for ActiveRecord
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-590 Fix unit tests for ActiveRecord Change By: Kenneth Barber Sprint: 20140827to20140910 Add Comment 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 https://groups.google.com/d/optout.
Jira (FACT-686) Upgrading to 2.2.0 throws errors on all Ubuntu 12.04 clients
Title: Message Title Dan Schaefer updated an issue Facter / FACT-686 Upgrading to 2.2.0 throws errors on all Ubuntu 12.04 clients Change By: Dan Schaefer Summary: Upgradingto2.2.0throwserrorsonall Ubuntu12.04 clients Add Comment 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 https://groups.google.com/d/optout.
Jira (FACT-686) Upgrading to 2.2.0 throws errors on all Ubuntu 12.04 clients
Title: Message Title
Dan Schaefer commented on an issue
Re: Upgrading to 2.2.0 throws errors on all Ubuntu 12.04 clients
I've narrowed it down to only being my Ubuntu 12.04 nodes. This does not occur with my Ubuntu 10.04, Ubuntu 14.04, or Debian 7.6 nodes
Add Comment
Facter / FACT-686
Upgrading to 2.2.0 throws errors on all Ubuntu 12.04 clients
After updating facter from 2.1.0 to 2.2.0 on my Ubuntu 12.04 servers, I'm receiving errors like the following: {code} Error: Failed to apply catalog: Parameter ensure failed on Package[samba]: Invalid value . Valid values are present, absent, purged, held, latest. Valid values match /./. at /etc/puppet/modules/samba/manifests/init.pp:331 Wrapped ex...
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-687) Xen virtual fact doesn't work on CentOS 6.5
Title: Message Title Alexey created an issue Facter / FACT-687 Xen virtual fact doesn't work on CentOS 6.5 Issue Type: Bug Affects Versions: 2.2.0, 2.0.1 Assignee: Eric Sorenson Created: 27/Aug/14 7:47 AM Priority: Normal Reporter: Alexey I have installed CentOS on Xenserver. facter give me virtual as xenhvm, but my guests work as PV - !not HVM. I try to make clean install and convert new VM to PV like in this article But all my VM already in PV mode and facter cant determine this. Add Comment This message was sent by Atlassian JIRA
Jira (PDB-812) Collapse the produce-body construct from all the HTTP endpoints
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-812 Collapse the produce-body construct from all the HTTP endpoints Change By: Steve Barlow Sprint: 20140813to20140827 ,20140827to20140910 Add Comment 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 https://groups.google.com/d/optout.
Jira (PDB-707) The first request to PuppetDB after DB backend restart fails
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-707 The first request to PuppetDB after DB backend restart fails Change By: Steve Barlow Sprint: 20140813to20140827 ,20140827to20140910 Add Comment 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 https://groups.google.com/d/optout.
Jira (PDB-781) PuppetDB 2.2.0 Release - August 27th
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-781 PuppetDB 2.2.0 Release - August 27th Change By: Steve Barlow Sprint: 20140813to20140827 ,20140827to20140910 Add Comment 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 https://groups.google.com/d/optout.
Jira (PDB-828) PR (1047): (QENG-1071) debian ec2 /etc/init.d/ec2-get-credentials... - anodelman
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-828 PR (1047): (QENG-1071) debian ec2 /etc/init.d/ec2-get-credentials... - anodelman Change By: Steve Barlow Sprint: 20140813to20140827 ,20140827to20140910 Add Comment 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 https://groups.google.com/d/optout.
Jira (PDB-813) Port certificate whitelist handling from PuppetDB into trapperkeeper-webserver-jetty9
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-813 Port certificate whitelist handling from PuppetDB into trapperkeeper-webserver-jetty9 Change By: Steve Barlow Sprint: 20140730to20140813,20140813to20140827 ,20140827to20140910 Add Comment 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 https://groups.google.com/d/optout.
Jira (PDB-663) Convert packaging to use ezbake
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-663 Convert packaging to use ezbake Change By: Steve Barlow Sprint: 20140827to 20140910 to20140924 Add Comment 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 https://groups.google.com/d/optout.
Jira (PDB-844) Format clj code across the board correctly
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-844 Format clj code across the board correctly Issue Type: Task Assignee: Unassigned Created: 27/Aug/14 8:36 AM Priority: Normal Reporter: Kenneth Barber Currently are formatting isn't consistent, we should go through and fix this. Here is Deepak's script for this purpose: https://gist.github.com/grimradical/9123149 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PDB-844) Format clj code across the board correctly
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-844 Format clj code across the board correctly Change By: Steve Barlow Sprint: 20140910to20140924 Add Comment 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 https://groups.google.com/d/optout.
Jira (FACT-672) Smoke test packages
Title: Message Title Justin Nauman commented on an issue Re: Smoke test packages This introduces an inconsistency into the Amazon Linux AMI 2013.09 when upgrading from 2.1.0 to 2.2.0 for the Operating System release. 2.1.0 $ facter --version 2.1.0 $ facter operatingsystemrelease 3.4.73-64.112.amzn1.x86_64 2.2.0 $ facter --version 2.2.0 $ facter operatingsystemrelease 2013.09 Add Comment Facter / FACT-672 Smoke test packages Procedure may vary by project and point in the release cycle. Ask around. In general this should happen on a variety of platforms, i.e. one or two each of kind of package we create (i.e., gem, dmg, msi, deb, rpm, etc). If this is a final release then the previous RC (which should be identical to what is currently being released) will have gone through th... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (FACT-686) Upgrading to 2.2.0 throws errors on all Ubuntu 12.04 clients
Title: Message Title Eric Sorenson updated an issue Facter / FACT-686 Upgrading to 2.2.0 throws errors on all Ubuntu 12.04 clients Change By: Eric Sorenson Assignee: EricSorenson DanSchaefer Add Comment 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 https://groups.google.com/d/optout.
Jira (FACT-686) Upgrading to 2.2.0 throws errors on all Ubuntu 12.04 clients
Title: Message Title
Eric Sorenson commented on an issue
Re: Upgrading to 2.2.0 throws errors on all Ubuntu 12.04 clients
Hi Dan it sounds like there is something in your puppet module that is setting variables based on a fact, whose resolution changed. can you trace back where you have {{ package { mysql: ... }} defined and see if there is an attribute w/ variable interpolation? (Based on mailing list conversation https://groups.google.com/forum/#!msg/puppet-users/Ve0L1iW3NeU/QOFk3GRLp1AJ I would guess it uses $lsbmajdistrelease )
Add Comment
Facter / FACT-686
Upgrading to 2.2.0 throws errors on all Ubuntu 12.04 clients
After updating facter from 2.1.0 to 2.2.0 on my Ubuntu 12.04 servers, I'm receiving errors like the following: {code} Error: Failed to apply catalog: Parameter ensure failed on Package[samba]: Invalid value . Valid values are present, absent, purged, held, latest. Valid values match /./. at /etc/puppet/modules/samba/manifests/init.pp:331 Wrapped ex...
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
Jira (PUP-3136) Intermittent acceptance failure in resource/service/ticket_14297_handle_upstart.rb
Title: Message Title Joshua Partlow commented on an issue Re: Intermittent acceptance failure in resource/service/ticket_14297_handle_upstart.rb So, if I followed William Hopper's test, one way to make the acceptance test less brittle is to replace the separate `puppet resource service` and `service apache2 status` calls, with a small manifest linking the service change to a exec testing status? We should still switch to a different package though. Add Comment Puppet / PUP-3136 Intermittent acceptance failure in resource/service/ticket_14297_handle_upstart.rb Just recently there have been a few intermittent failures in resource/service/ticket_14297_handle_upstart.rb. (Btw note that this test is confined to Ubuntu.) Three examples: https://jenkins.puppetlabs.com/job/Puppet-Package-Acceptance-4.0/label=acc-coord,platform=precise/212/consoleFull https://jenkins.puppetlabs.com/view/Puppet%20FOSS/view/Master/... 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
Jira (FACT-688) Facter reports Ubuntu Major version incorrectly (lsbmajdistrelease)
Title: Message Title Rob Reynolds created an issue Facter / FACT-688 Facter reports Ubuntu Major version incorrectly (lsbmajdistrelease) Issue Type: Bug Assignee: Eric Sorenson Created: 27/Aug/14 9:38 AM Labels: ubuntu Priority: Normal Reporter: Rob Reynolds In most platforms, splitting on the first ‘.’ of an X.Y.Z release would be a sane way of determining the major release, but Ubuntu does its versioning a bit differently. Given the Ubuntu release 10.04, the major version isn't actually 10; it's 10.04 and 10.10 isn't a patch release to 10.04. When Ubuntu does do a minor release for a distribution, they add it as the Z part of the X.Y.Z - for example, 14.04.1 should have a major release of 14.04 and a minor release of 1, not 4. Add Comment
Jira (FACT-688) Facter reports Ubuntu Major version incorrectly (lsbmajdistrelease)
Title: Message Title Rob Reynolds updated an issue Facter / FACT-688 Facter reports Ubuntu Major version incorrectly (lsbmajdistrelease) Change By: Rob Reynolds Fix Version/s: 2.2.0 Add Comment 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 https://groups.google.com/d/optout.
Jira (FACT-688) Facter reports Ubuntu Major version incorrectly (lsbmajdistrelease)
Title: Message Title Rob Reynolds commented on an issue Re: Facter reports Ubuntu Major version incorrectly (lsbmajdistrelease) This change was made at 793b258 Add Comment Facter / FACT-688 Facter reports Ubuntu Major version incorrectly (lsbmajdistrelease) In most platforms, splitting on the first ‘.’ of an X.Y.Z release would be a sane way of determining the major release, but Ubuntu does its versioning a bit differently. Given the Ubuntu release 10.04, the major version isn't actually 10; it's 10.04 and 10.10 isn't a patch release to 10.04. When Ubuntu does do a minor release for a distribution, they ... 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 https://groups.google.com/d/optout.
Jira (FACT-688) Facter reports Ubuntu Major version incorrectly (lsbmajdistrelease)
Title: Message Title Rob Reynolds assigned an issue to Rob Reynolds Facter / FACT-688 Facter reports Ubuntu Major version incorrectly (lsbmajdistrelease) Change By: Rob Reynolds Assignee: EricSorenson RobReynolds Add Comment 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 https://groups.google.com/d/optout.
Jira (FACT-686) Upgrading to 2.2.0 throws errors on all Ubuntu 12.04 clients
Title: Message Title
Dan Schaefer commented on an issue
Re: Upgrading to 2.2.0 throws errors on all Ubuntu 12.04 clients
Thank you Eric. That seems to be the issue. The parameters needed for the erroneous modules are stored in hiera files. The variables specific to Ubuntu 12.04 are stored in a hiera file using $lsbmajdistrelease to determine the correct file. I have verified that the value of $lsbmajdistrelease has changed from 12 to 12.04 after upgrading from facter 2.1.0 to 2.2.0.
Seeing as this if affecting others as you pointed out in the mailing list link, I'm not sure how this bug will be handled. Matt W in the mailing list suggests that the Ubuntu changes should be release in a facter 3.x.x release, since this will break a lot of other environments.
Add Comment
Facter / FACT-686
Upgrading to 2.2.0 throws errors on all Ubuntu 12.04 clients
After updating facter from 2.1.0 to 2.2.0 on my Ubuntu 12.04 servers, I'm receiving errors like the following: {code} Error: Failed to apply catalog: Parameter ensure failed on Package[samba]: Invalid value . Valid values are present, absent, purged, held, latest. Valid values match /./. at /etc/puppet/modules/samba/manifests/init.pp:331 Wrapped ex...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (FACT-689) Facter reports Amazon major release incorrectly (operatingsystemrelease / operatingsystemmajrelease)
Title: Message Title William Hopper created an issue Facter / FACT-689 Facter reports Amazon major release incorrectly (operatingsystemrelease / operatingsystemmajrelease) Issue Type: Bug Assignee: Unassigned Created: 27/Aug/14 10:14 AM Fix Versions: 2.2.0 Priority: Normal Reporter: William Hopper Previously in Amazon linux, when resolving the operatingsystemrelease and operatingsystemmajrelease facts, Facter simply fell back to the value of the kernelrelease when `lsb_release` was not available. To accurately determine the system release, the contents of `/etc/system-release` should be used instead. Add Comment
Jira (FACT-688) Facter reports Ubuntu Major version incorrectly (lsbmajdistrelease)
Title: Message Title Rob Reynolds commented on an issue Re: Facter reports Ubuntu Major version incorrectly (lsbmajdistrelease) This ticket was added for historical reasons and for documentation of a change that went in as part of a larger ticket FACT-614 . Add Comment Facter / FACT-688 Facter reports Ubuntu Major version incorrectly (lsbmajdistrelease) In most platforms, splitting on the first ‘.’ of an X.Y.Z release would be a sane way of determining the major release, but Ubuntu does its versioning a bit differently. Given the Ubuntu release 10.04, the major version isn't actually 10; it's 10.04 and 10.10 isn't a patch release to 10.04. When Ubuntu does do a minor release for a distribution, they ... 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
Jira (FACT-689) Facter reports Amazon release incorrectly (operatingsystemrelease / operatingsystemmajrelease)
Title: Message Title William Hopper updated an issue Facter / FACT-689 Facter reports Amazon release incorrectly (operatingsystemrelease / operatingsystemmajrelease) Change By: William Hopper Summary: FacterreportsAmazon major releaseincorrectly(operatingsystemrelease/operatingsystemmajrelease) Add Comment 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 https://groups.google.com/d/optout.
Jira (FACT-689) Facter reports Amazon release incorrectly (operatingsystemrelease / operatingsystemmajrelease)
Title: Message Title William Hopper commented on an issue Re: Facter reports Amazon release incorrectly (operatingsystemrelease / operatingsystemmajrelease) This ticket was added for historical reasons and for documentation of a change to fix a bug in the value returned for Amazon versions that went in as part of a larger ticket FACT-614 . Add Comment Facter / FACT-689 Facter reports Amazon release incorrectly (operatingsystemrelease / operatingsystemmajrelease) Previously in Amazon linux, when resolving the operatingsystemrelease and operatingsystemmajrelease facts, Facter simply fell back to the value of the kernelrelease when `lsb_release` was not available. To accurately determine the system release, the contents of `/etc/system-release` should be used instead. 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 (FACT-690) Add manjaro linux to the operatingsystem fact
Title: Message Title Joshua Partlow created an issue Facter / FACT-690 Add manjaro linux to the operatingsystem fact Issue Type: Improvement Assignee: Eric Sorenson Components: Community Created: 27/Aug/14 10:28 AM Priority: Normal Reporter: Joshua Partlow Add Comment 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 (FACT-688) Facter reports Ubuntu Major Release version incorrectly (lsbmajdistrelease)
Title: Message Title Rob Reynolds updated an issue Facter / FACT-688 Facter reports Ubuntu Major Release version incorrectly (lsbmajdistrelease) Change By: Rob Reynolds Summary: FacterreportsUbuntuMajor Release versionincorrectly(lsbmajdistrelease) Add Comment 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 https://groups.google.com/d/optout.
Jira (FACT-690) Add manjaro linux to the operatingsystem fact
Title: Message Title Joshua Partlow assigned an issue to Joshua Partlow Facter / FACT-690 Add manjaro linux to the operatingsystem fact Change By: Joshua Partlow Assignee: JoshuaPartlow Add Comment 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 https://groups.google.com/d/optout.
Jira (FACT-690) Add manjaro linux to the operatingsystem fact
Title: Message Title Joshua Partlow updated an issue Facter / FACT-690 Add manjaro linux to the operatingsystem fact Change By: Joshua Partlow Assignee: JoshuaPartlow TimSpence Add Comment 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 https://groups.google.com/d/optout.
Jira (FACT-689) Facter reports Amazon release incorrectly (operatingsystemrelease / operatingsystemmajrelease)
Title: Message Title William Hopper commented on an issue Re: Facter reports Amazon release incorrectly (operatingsystemrelease / operatingsystemmajrelease) This was merged to master on c0812a83 and released with 2.2.0. Add Comment Facter / FACT-689 Facter reports Amazon release incorrectly (operatingsystemrelease / operatingsystemmajrelease) Previously in Amazon linux, when resolving the operatingsystemrelease and operatingsystemmajrelease facts, Facter simply fell back to the value of the kernelrelease when `lsb_release` was not available. To accurately determine the system release, the contents of `/etc/system-release` should be used instead. 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 https://groups.google.com/d/optout.
Jira (PUP-3038) Typemanager wastes CPU cycles with global scope defined types
Title: Message Title Felix Frank commented on an issue Re: Typemanager wastes CPU cycles with global scope defined types According to Josh Cooper this may be unnecessary thanks to the feature implemented for PUP-3032. Add Comment Puppet / PUP-3038 Typemanager wastes CPU cycles with global scope defined types Defined type defined in a global scope will make MetaType::Manager go through all known code locations (modules, gems, loadpaths, etc) looking for that_type.rb That combined with a fact that code locations are not cached makes puppet slow when working with large repositories. I'm preparing 2 PRs related to this issue. 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 https://groups.google.com/d/optout.
Jira (PUP-3093) PMT upgrade fails if installed version has invalid semver
Title: Message Title
Ryan Coleman commented on an issue
Re: PMT upgrade fails if installed version has invalid semver
Alexander Johnson Alex Dreyer, would you please take this on and provide guidance to Anderson and team?
Add Comment
Puppet / PUP-3093
PMT upgrade fails if installed version has invalid semver
If an installed version of a module contains an invalid semver, upgrading to a version with a valid semver fails with the following error: {code} qw9dvmp4zgwz3qf 13:46:39$ env PATH=/usr/bin:/opt/puppet-git-repos/hiera/bin:${PATH} RUBYLIB=/opt/puppet-git-repos/hiera/lib:/opt/puppet-git-repos/hiera-p uppet/lib:${RUBYLIB} puppet module upgrade pmtac...
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 https://groups.google.com/d/optout.
Jira (PUP-3038) Typemanager wastes CPU cycles with global scope defined types
Title: Message Title Josh Cooper commented on an issue Re: Typemanager wastes CPU cycles with global scope defined types See comment https://github.com/puppetlabs/puppet/pull/2952#issuecomment-53618612 in regards to PR 2952. Add Comment Puppet / PUP-3038 Typemanager wastes CPU cycles with global scope defined types Defined type defined in a global scope will make MetaType::Manager go through all known code locations (modules, gems, loadpaths, etc) looking for that_type.rb That combined with a fact that code locations are not cached makes puppet slow when working with large repositories. I'm preparing 2 PRs related to this issue. 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 https://groups.google.com/d/optout.
Jira (PUP-2396) Support ruby 2.0 x64 on windows
Title: Message Title Juha Vainikka updated an issue Puppet / PUP-2396 Support ruby 2.0 x64 on windows Change By: Juha Vainikka Ruby yyRuby x64buildshavebeenavailableasofruby2.0,andthewin32gemcommunityiscatchingup.Itisimportanttosupportpuppetonx64,becauseiteliminatesthefilesystemredirectionnonsensethatcustomershavetodealwithwhenwritingmanifestsandmodulesonWindows.Thereare4mainworkareasinorder:#FFI'ingpuppetcode(PUP-835,PUP-2382,PUP-766,PUP-836,PUP-837,PUP-838,PUP-839,PUP-840,PUP-2385)#Vendoringruby2.xandrelatedgemsinpuppet-win32-rubyrepo(PUP-2389,PUP-2388,PUP-1281)#Validatingpuppetandgemsonruby2x64(PUP-391,PUP-1283,PUP-1760,PUP-392)#Generatingx86andx64MSIs(PUP-2383,PUP-390) Add Comment 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 https://groups.google.com/d/optout.
Jira (PUP-3127) LDAP - introduce LDAP-Certificat Directory
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-3127 LDAP - introduce LDAP-Certificat Directory Change By: Kylo Ginsberg Fix Version/s: 3.7.0 Fix Version/s: 4.0.0 Add Comment 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 https://groups.google.com/d/optout.
Jira (PUP-2396) Support ruby 2.0 x64 on windows
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-2396 Support ruby 2.0 x64 on windows Change By: Rob Reynolds yyRuby Ruby x64buildshavebeenavailableasofruby2.0,andthewin32gemcommunityiscatchingup.Itisimportanttosupportpuppetonx64,becauseiteliminatesthefilesystemredirectionnonsensethatcustomershavetodealwithwhenwritingmanifestsandmodulesonWindows.Thereare4mainworkareasinorder:#FFI'ingpuppetcode(PUP-835,PUP-2382,PUP-766,PUP-836,PUP-837,PUP-838,PUP-839,PUP-840,PUP-2385)#Vendoringruby2.xandrelatedgemsinpuppet-win32-rubyrepo(PUP-2389,PUP-2388,PUP-1281)#Validatingpuppetandgemsonruby2x64(PUP-391,PUP-1283,PUP-1760,PUP-392)#Generatingx86andx64MSIs(PUP-2383,PUP-390) Add Comment 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 https://groups.google.com/d/optout.
Jira (PUP-3127) LDAP - introduce LDAP-Certificat Directory
Title: Message Title
Kylo Ginsberg commented on an issue
Re: LDAP - introduce LDAP-Certificat Directory
Linked PR and changed fix version to 4.0 (3.7 is releasing shortly, final list of tickets is in). Thanks!
Add Comment
Puppet / PUP-3127
LDAP - introduce LDAP-Certificat Directory
For *Solaris* based systems it is necessary to establisch the connection to the ldap server a little bit different then for e.g. Linux based systems. Therefore it is necessary to introduce this new config variable {{'ldapcrtdir'}} that allows the use of the server specific ldap certificates. On Solaris it points to {{/var/ldap}}. If {{ldapssl}} is se...
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 https://groups.google.com/d/optout.
Jira (PUP-3094) Distribute separate binaries for master and ca
Title: Message Title Joshua Partlow commented on an issue Re: Distribute separate binaries for master and ca Started a discussion in puppet-dev to talk about using Puppet::Util::SELinux helpers as suggested by Dominic Cleal: https://groups.google.com/forum/#!topic/puppet-dev/VTb2o-Nuxkw Add Comment Puppet / PUP-3094 Distribute separate binaries for master and ca Downstream SELinux-aware distributions need to add shell wrappers for puppet master and puppet ca command to be able set puppet_exec_t file context for successful domain transition. Without this, it is not possible to start master or ca process in the correct (secured) domain. I am going to send this little patch that we have in Fedora and EPEL ... 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 (PUP-3148) No suitable provider for 'user' in Fedora 20 when running as non-root
Title: Message Title
David Lutterkort commented on an issue
Re: No suitable provider for 'user' in Fedora 20 when running as non-root
It seems that a similar symptom is ailing the group provider on Fedora/CentOS
Add Comment
Puppet / PUP-3148
No suitable provider for 'user' in Fedora 20 when running as non-root
As an ordinary user, it is not possible to list yourself with Puppet: {quote} puppet resource user $USER Error: Could not run: undefined method `exists?' for nil:NilClass {quote} Simlarly, puppet apply fails: {quote} puppet apply -e user { $USER: } Notice: Compiled catalog for berna.localdomain in environment production in 0.14 seconds Err...
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 https://groups.google.com/d/optout.
Jira (PUP-3149) Removing packages on Suse should use zypper not rpm
Title: Message Title
Derek McEachern created an issue
Puppet / PUP-3149
Removing packages on Suse should use zypper not rpm
Issue Type:
Improvement
Affects Versions:
3.6.2
Assignee:
Aaron Armstrong
Attachments:
rpm-package-absent-failure.txt
Components:
PE, Types and Providers
Created:
27/Aug/14 1:02 PM
Environment:
SLES, Opensuse
Priority:
Normal
Reporter:
Derek McEachern
When using the package provider to ensure absent like the example below:
package {'emacs': ensure = absent, }
on Suse systems it uses rpm instead of zypper to try and remove the package. If the package has dependencies then rpm -e will fail.
On Suse systems the package absent should use zypper and not rpm so package
Jira (PUP-3093) PMT upgrade fails if installed version has invalid semver
Title: Message Title
Alex Dreyer commented on an issue
Re: PMT upgrade fails if installed version has invalid semver
I agree with Anderson. PMT has safeguards to prevent dangerous upgrades without --force. Some of these rely on being able to compare the version of the previously installed module with the new one. PMT should probably error more cleanly but not overwrite an installed module by default.
Add Comment
Puppet / PUP-3093
PMT upgrade fails if installed version has invalid semver
If an installed version of a module contains an invalid semver, upgrading to a version with a valid semver fails with the following error: {code} qw9dvmp4zgwz3qf 13:46:39$ env PATH=/usr/bin:/opt/puppet-git-repos/hiera/bin:${PATH} RUBYLIB=/opt/puppet-git-repos/hiera/lib:/opt/puppet-git-repos/hiera-p uppet/lib:${RUBYLIB} puppet module upgrade pmtac...
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
Jira (PUP-3149) Removing packages on Suse should use zypper not rpm
Title: Message Title Aaron Armstrong updated an issue Puppet / PUP-3149 Removing packages on Suse should use zypper not rpm Change By: Aaron Armstrong Assignee: AaronArmstrong Add Comment 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 https://groups.google.com/d/optout.
Jira (PUP-1062) Add virtualenv support to the pip package provider
Title: Message Title
Dado Feigenblatt commented on an issue
Re: Add virtualenv support to the pip package provider
I'm surprised there are only 5 votes and 10 watchers for this issue. Are there other worthwhile efforts in getting virtualenv working with puppet? Thanks.
Add Comment
Puppet / PUP-1062
Add virtualenv support to the pip package provider
Now that #6527 is merged into master, it is possible to easily add support for virtualenvs and fully complete #3572. A `virtualenv` argument could be added to the `package` type in order to instrument `pip` to install the requested package into the given virtualenv directory. For example:package { my-python-package: ensure ...
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 https://groups.google.com/d/optout.
Jira (PUP-2817) Solaris Zone properties ip, dataset and inherit are not set upon zone creation
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet / PUP-2817 Solaris Zone properties ip, dataset and inherit are not set upon zone creation Change By: Michael Smith Assignee: MichaelSmith Add Comment 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 https://groups.google.com/d/optout.
Jira (PDB-843) Remove the com. from our namespace and align the test namespace properly
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-843 Remove the com. from our namespace and align the test namespace properly Change By: Kenneth Barber Summary: Removethecom.fromournamespace andalignthetestnamespaceproperly Add Comment 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 https://groups.google.com/d/optout.
Jira (PDB-843) Remove the com. from our namespace and align the test namespace properly
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-843 Remove the com. from our namespace and align the test namespace properly Change By: Kenneth Barber Mostoftheotherprojectshavemadethismove,timeforustodothis?Theconcernisthemetrics,sincewecan'tjustchangethenamesofthose. Alsoweshouldre-alignthetestnamespace.Thereissomebenefitinfollowingthestandardsthatpluginssupport,sowecanswitchbetweensrcandtestinoureditorsquickly. Add Comment 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 https://groups.google.com/d/optout.
Jira (FACT-689) Facter reports Amazon Linux release incorrectly (operatingsystemrelease / operatingsystemmajrelease)
Title: Message Title William Hopper updated an issue Facter / FACT-689 Facter reports Amazon Linux release incorrectly (operatingsystemrelease / operatingsystemmajrelease) Change By: William Hopper Summary: FacterreportsAmazon Linux releaseincorrectly(operatingsystemrelease/operatingsystemmajrelease) Add Comment 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 https://groups.google.com/d/optout.
Jira (PUP-2817) Solaris Zone properties ip, dataset and inherit are not set upon zone creation
Title: Message Title
Michael Smith commented on an issue
Re: Solaris Zone properties ip, dataset and inherit are not set upon zone creation
Verified adding and removing zones with eba493d on Solaris 10. Didn't work with PE 3.3 install on the same system.
Add Comment
Puppet / PUP-2817
Solaris Zone properties ip, dataset and inherit are not set upon zone creation
The {{ip}}, {{dataset}} and {{inherit}} properties of the Zone type each have [insync methods|https://github.com/puppetlabs/puppet/blob/3.6.2/lib/puppet/type/zone.rb#L252-L253] that respond with {{true}} when passed a {{nil}} property value. When a zone resource is first created, the property hash looks like: {code} { ensure = :absent } {code} ...
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 (PDB-767) Show if an event was due to a change in the catalog or not
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-767 Show if an event was due to a change in the catalog or not (Sorry for the delay in getting back to you on this one Carl Caum) So I'm thinking this can be answered with historical catalog storage. If an event was triggered, but the catalog had not changed from the last run, then one can presume this was not caused by Puppet. The gap is obviously in the first run (only 1 catalog) but that would be the case I think with any solution . Although, this could also indicate a module that lacks idempotency as well, as the last even could not reflect reality due to a bug in the resource. This could be proven/disproven if we had some knowledge of module versions changes on the puppet master, combined with the fact that perhaps it was showing the event repeatedly ... I feel like this needs a deeper discussion . Add Comment 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 https://groups.google.com/d/optout.
Jira (PUP-2817) Solaris Zone properties ip, dataset and inherit are not set upon zone creation
Title: Message Title
Michael Smith commented on an issue
Re: Solaris Zone properties ip, dataset and inherit are not set upon zone creation
FR Plan
1. Test ip property (done). 2. Test dataset property. 3. Test inherit property. 4. Repeat on Solaris 11.
Add Comment
Puppet / PUP-2817
Solaris Zone properties ip, dataset and inherit are not set upon zone creation
The {{ip}}, {{dataset}} and {{inherit}} properties of the Zone type each have [insync methods|https://github.com/puppetlabs/puppet/blob/3.6.2/lib/puppet/type/zone.rb#L252-L253] that respond with {{true}} when passed a {{nil}} property value. When a zone resource is first created, the property hash looks like: {code} { ensure = :absent } {code} ...
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.
Jira (PUP-3117) Resource Expression Enhancements
Title: Message Title Henrik Lindberg commented on an issue Re: Resource _expression_ Enhancements We now have the results of the UX research and have discussed and decided to go ahead with the feature as it is currently specified. The PR-3024 contains fixes for the outstanding issues that were put on hold until a decision had been made. We based the decision on the following reasoning: None of the test pilots had any issues guessing / recognizing that a * as an attribute name implies all / everything The * = $hash syntax for unfolding can follow the current formatting rule align on arrow Googlability was not an issue for any of the test pilots, they either came up with other words for the concept / idea, or would go to Puppet's (excellent) documentation and navigate to the relevant section (resource _expression_). We did not pick the runner up of using attributes_hash instead of the * based on the following reasoning: There is no indication that it is different from the other attributes, and that it is different from meta parameters. You would simply have to know this (which you only can if you know all the existing attribute names and meta parameters). There is nothing indicating that it does not hold the value; i.e. you cannot later lookup the attributes_hash parameter. This means that users have to learn that there is the concept of meta parameters that are available on all resources, but then also learn that one of them is special. All test pilots found both the local defaults, and the ability to unfold a hash to be useful. We did not test the allowed left hand side expressions. We decided to make it more strict that what is on master before PR-3024. It is not specified to statically validate that: it is a Qualified name (e.g. notify, file It is a Qualified reference (e.g. Notify, File
Jira (PUP-2817) Solaris Zone properties ip, dataset and inherit are not set upon zone creation
Title: Message Title
Charlie Sharpsteen commented on an issue
Re: Solaris Zone properties ip, dataset and inherit are not set upon zone creation
A note for Solaris 11: Sparse zones were removed from that version of the OS, so inherit won't work.
Add Comment
Puppet / PUP-2817
Solaris Zone properties ip, dataset and inherit are not set upon zone creation
The {{ip}}, {{dataset}} and {{inherit}} properties of the Zone type each have [insync methods|https://github.com/puppetlabs/puppet/blob/3.6.2/lib/puppet/type/zone.rb#L252-L253] that respond with {{true}} when passed a {{nil}} property value. When a zone resource is first created, the property hash looks like: {code} { ensure = :absent } {code} ...
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 (PUP-2817) Solaris Zone properties ip, dataset and inherit are not set upon zone creation
Title: Message Title
Michael Smith commented on an issue
Re: Solaris Zone properties ip, dataset and inherit are not set upon zone creation
2. Test dataset property.
Verified adding and removing zones with the inherit property, as in
zone {test:
path = /zones/test,
inherit = ['/lib','/opt/puppet','/sbin','/usr'],
}
Trying to change the zone after creation results in an error, which is frustrating but better than the alternative (silently deleting the zone and recreating it).
Add Comment
Puppet / PUP-2817
Solaris Zone properties ip, dataset and inherit are not set upon zone creation
The {{ip}}, {{dataset}} and {{inherit}} properties of the Zone type each have [insync methods|https://github.com/puppetlabs/puppet/blob/3.6.2/lib/puppet/type/zone.rb#L252-L253] that respond with {{true}} when passed a {{nil}} property value. When a zone resource is first created, the property hash looks like: {code} { ensure = :absent } {code} ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PDB-843) Remove the com. from our namespace and align the test namespace properly
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-843 Remove the com. from our namespace and align the test namespace properly Change By: Kenneth Barber Mostoftheotherprojectshavemadethismove,timeforustodothis?Theconcernisthemetrics,sincewecan'tjustchangethenamesofthose. Weneedtoprobablymovethethingsattherootofthecom.puppetlabsnamespaceintopuppetlabs.puppetdbaswell. Alsoweshouldre-alignthetestnamespace.Thereissomebenefitinfollowingthestandardsthatpluginssupport,sowecanswitchbetweensrcandtestinoureditorsquickly. Add Comment 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 https://groups.google.com/d/optout.
Jira (PDB-843) Remove the com. from our namespace and align the test namespace properly
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-843 Remove the com. from our namespace and align the test namespace properly Change By: Kenneth Barber Mostoftheotherprojectshavemadethismove,timeforustodothis?Theconcernisthemetrics,sincewecan'tjustchangethenamesofthose.Weneedtoprobablymovethethingsattherootofthecom.puppetlabsnamespaceintopuppetlabs.puppetdbaswell.Alsoweshouldre-alignthetestnamespace.Thereissomebenefitinfollowingthestandardsthat oureditor pluginssupport,sowecanswitchbetweensrcandtest inoureditors quickly. Add Comment 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 https://groups.google.com/d/optout.
Jira (PUP-3150) config_version setting in environment.conf uses relative pathing
Title: Message Title Gary Larizza created an issue Puppet / PUP-3150 config_version setting in environment.conf uses relative pathing Issue Type: Bug Affects Versions: 3.6.0 Assignee: Unassigned Created: 27/Aug/14 3:33 PM Priority: Normal Reporter: Gary Larizza If directory environments are configured, and you create an environment.conf in an environment, and you set the config_version parameter using a command that doesn't include the full path to the binary in question, such as: config_version = 'git --git-dir $confdir/environments/$environment/.git rev-parse HEAD' Puppet will attempt to look for the git binary in the relative environment path and produce the following error: Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Execution of config_version command `/etc/puppetlabs/puppet/environments/production/git --git-dir /etc/puppetlabs/puppet/environments/production/.git rev-parse HEAD` failed: Execution of '/etc/puppetlabs/puppet/environments/production/git --git-dir /etc/puppetlabs/puppet/environments/production/.git rev-parse HEAD' returned 1: on node master.puppetlabs.vm I understand why relative pathing is important for modulepath, and I EVEN see why
Jira (FACT-686) Upgrading to 2.2.0 throws errors on all Ubuntu 12.04 clients
Title: Message Title
Kylo Ginsberg commented on an issue
Re: Upgrading to 2.2.0 throws errors on all Ubuntu 12.04 clients
Dan Schaefer that change was a fix, a very poorly publicized fix unfortunately, for
FACT-688
. It sounds like you're already on the email thread where this was discussed, but for posterity: https://groups.google.com/forum/#!msg/puppet-dev/Ve0L1iW3NeU/EaQ3VEjfnLAJ
Add Comment
Facter / FACT-686
Upgrading to 2.2.0 throws errors on all Ubuntu 12.04 clients
After updating facter from 2.1.0 to 2.2.0 on my Ubuntu 12.04 servers, I'm receiving errors like the following: {code} Error: Failed to apply catalog: Parameter ensure failed on Package[samba]: Invalid value . Valid values are present, absent, purged, held, latest. Valid values match /./. at /etc/puppet/modules/samba/manifests/init.pp:331 Wrapped ex...
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
Jira (PUP-1062) Add virtualenv support to the pip package provider
Title: Message Title
Jason Antman commented on an issue
Re: Add virtualenv support to the pip package provider
We (my employer) have a module that has types and providers for virtualenvs and pip-installed packages within them, that was developed by one of the pypa (pip/virtualenv) maintainers. We're currently working on getting it open sourced (we don't have an OSS policy yet, so it's a big discussion with management, legal, etc.). When that finally happens, it'll be published to the forge and I'll update here.
Add Comment
Puppet / PUP-1062
Add virtualenv support to the pip package provider
Now that #6527 is merged into master, it is possible to easily add support for virtualenvs and fully complete #3572. A `virtualenv` argument could be added to the `package` type in order to instrument `pip` to install the requested package into the given virtualenv directory. For example:package { my-python-package: ensure ...
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 (PUP-2817) Solaris Zone properties ip, dataset and inherit are not set upon zone creation
Title: Message Title
Michael Smith commented on an issue
Re: Solaris Zone properties ip, dataset and inherit are not set upon zone creation
Found a weird set of circumstances where zoneadm doesn't behave well: https://gist.github.com/MikaelSmith/66952db17447f51bed45
If creating a zone fails, trying to do it again after just changing the dataset property still uses the original dataset property. I had to change the name and path as well to get the new dataset property used.
Add Comment
Puppet / PUP-2817
Solaris Zone properties ip, dataset and inherit are not set upon zone creation
The {{ip}}, {{dataset}} and {{inherit}} properties of the Zone type each have [insync methods|https://github.com/puppetlabs/puppet/blob/3.6.2/lib/puppet/type/zone.rb#L252-L253] that respond with {{true}} when passed a {{nil}} property value. When a zone resource is first created, the property hash looks like: {code} { ensure = :absent } {code} ...
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
Jira (FACT-686) Upgrading to 2.2.0 throws errors on all Ubuntu 12.04 clients
Title: Message Title
Dan Schaefer commented on an issue
Re: Upgrading to 2.2.0 throws errors on all Ubuntu 12.04 clients
I will accept that answer I already have an idea of how to workaround this change in my environment.
Add Comment
Facter / FACT-686
Upgrading to 2.2.0 throws errors on all Ubuntu 12.04 clients
After updating facter from 2.1.0 to 2.2.0 on my Ubuntu 12.04 servers, I'm receiving errors like the following: {code} Error: Failed to apply catalog: Parameter ensure failed on Package[samba]: Invalid value . Valid values are present, absent, purged, held, latest. Valid values match /./. at /etc/puppet/modules/samba/manifests/init.pp:331 Wrapped ex...
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 https://groups.google.com/d/optout.
Jira (PUP-2984) MSI downgrade from x64 to x86 does not remove PuppetLabs folders in Program Files due to File System Redirection with 32bit msiexec
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-2984 MSI downgrade from x64 to x86 does not remove PuppetLabs folders in Program Files due to File System Redirection with 32bit msiexec Change By: Josh Cooper Assignee: JoshCooper Add Comment 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 https://groups.google.com/d/optout.
Jira (PUP-2914) Vendor RGen 0.7.0
Title: Message Title
Eric Thompson commented on an issue
Re: Vendor RGen 0.7.0
any tips on validating which libs are getting pulled in? does this need a test moving forward, or is it covered in spec?
Add Comment
Puppet / PUP-2914
Vendor RGen 0.7.0
PUP-2831 updated puppet to work with rgen 0.7.0. Before those fixes it made some mistakes that caused 0.7.0 to create issues, which might cause a problem for old packages of puppet that simply rely on {{= 0.6.5}}. We need to update the various packages that we make to depend on 0.7.0 and publish an RGen 0.7.0 package.
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 https://groups.google.com/d/optout.
Jira (PUP-3150) config_version setting in environment.conf uses relative pathing
Title: Message Title Joshua Partlow assigned an issue to Joshua Partlow Puppet / PUP-3150 config_version setting in environment.conf uses relative pathing Change By: Joshua Partlow Assignee: JoshuaPartlow Add Comment 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 https://groups.google.com/d/optout.
Jira (PUP-2806) puppet module generate ignores ERB files beginning with a dot
Title: Message Title John Duarte updated an issue Puppet / PUP-2806 puppet module generate ignores ERB files beginning with a dot Change By: John Duarte QA Status: Reviewed Add Comment 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 https://groups.google.com/d/optout.
Jira (PUP-2914) Vendor RGen 0.7.0
Title: Message Title
Henrik Lindberg commented on an issue
Re: Vendor RGen 0.7.0
When I really want to know, I figure out where the system library is and then I put a breakpoint there by editing the source of the installed gem. I feel dirty every time I do that, but it is a sure way to know. Say break in initialize in MMBase class (line 188 in metamodel_builder.rb).
The check we have when loading the library does not check specifically for the version, it only checks for certain behavior and 0.6.6 should pass that test. We wanted 0.7.0 mainly for things to come.
Add Comment
Puppet / PUP-2914
Vendor RGen 0.7.0
PUP-2831 updated puppet to work with rgen 0.7.0. Before those fixes it made some mistakes that caused 0.7.0 to create issues, which might cause a problem for old packages of puppet that simply rely on {{= 0.6.5}}. We need to update the various packages that we make to depend on 0.7.0 and publish an RGen 0.7.0 package.
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
Jira (PDB-845) PR (1067): (docs) Fix some spelling mistakes and one word choice. - kylog
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-845 PR (1067): (docs) Fix some spelling mistakes and one word choice. - kylog Issue Type: Task Assignee: Unassigned Created: 27/Aug/14 5:59 PM Labels: github Priority: Normal Reporter: gepetto-bot (docs) Fix some spelling mistakes and one word choice. Author: Kylo Ginsberg Company: Github ID: kylog Pull Request 1067 Discussion Pull Request 1067 File Diff Pull Request Description (webhooks-id: 5cf5343100e294536edf74e986ee67c0)
Jira (PDB-845) PR (1067): (docs) Fix some spelling mistakes and one word choice. - kylog
Title: Message Title gepetto-bot commented on an issue Re: PR (1067): (docs) Fix some spelling mistakes and one word choice. - kylog pljenkinsro commented: Can one of the admins verify this patch? Add Comment PuppetDB / PDB-845 PR (1067): (docs) Fix some spelling mistakes and one word choice. - kylog h2. (docs) Fix some spelling mistakes and one word choice. * Author: Kylo Ginsberg * Company: * Github ID: [kylog|https://github.com/kylog] * [Pull Request 1067 Discussion|https://github.com/puppetlabs/puppetdb/pull/1067] * [Pull Request 1067 File Diff|https://github.com/puppetlabs/puppetdb/pull/1067/files] h2. Pull Request Description ... 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 https://groups.google.com/d/optout.
