Jira (PUP-4039) package resource doesn't find new packages in yum repo

2017-03-14 Thread Robin Bowes (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Robin Bowes commented on  PUP-4039 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: package resource doesn't find new packages in yum repo  
 
 
 
 
 
 
 
 
 
 
It seems to be in this patch: http://yum.baseurl.org/gitweb?p=yum.git;a=commit;h=d56dcaa8ba266873b32832e713fc8199c9a9f45f 
A quick check on CentOS 6 vs. CentOS 7 reveals it's not in EL6 but is in EL7. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4039) package resource doesn't find new packages in yum repo

2017-03-10 Thread Robin Bowes (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Robin Bowes commented on  PUP-4039 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: package resource doesn't find new packages in yum repo  
 
 
 
 
 
 
 
 
 
 
Two things: 
1. This ticket is marked as "Needs Information". What information does it need? 
2. Why has fix version been moved to 6.0.0? Why not fix it in the next release? 
R. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4030) Add support for no_proxy env var

2016-11-16 Thread Robin Bowes (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Robin Bowes commented on  PUP-4030 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add support for no_proxy env var  
 
 
 
 
 
 
 
 
 
 
This is still causing problems. Please re-enable. 
See ENTERPRISE -956. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 (FACT-627) Boolean facts not printed with facter -p if fact value is false

2016-08-08 Thread Robin Bowes (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Robin Bowes commented on  FACT-627 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Boolean facts not printed with facter -p if fact value is false  
 
 
 
 
 
 
 
 
 
 
Two years old... Any plans to address this? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-4039) package resource doesn't find new packages in yum repo

2016-06-11 Thread Robin Bowes (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Robin Bowes commented on  PUP-4039 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: package resource doesn't find new packages in yum repo  
 
 
 
 
 
 
 
 
 
 
I've done a bit of research into this and wonder if "yum info" is a better command to use? This also exits 1 if the specified package is not found, but updates the yum cache if necessary. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-1924) source function library *before* client sysconfig overrides

2016-05-27 Thread Robin Bowes (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Robin Bowes commented on  PUP-1924 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: source function library *before* client sysconfig overrides  
 
 
 
 
 
 
 
 
 
 
pe-puppet 3.8.7 delivers an init file with the following content: 
 
 
 
 
 
 
#!/bin/bash 
 
 
 
 
# puppetInit script for running the puppet client daemon 
 
 
 
 
# 
 
 
 
 
# Author:   Duane Griffin  
 
 
 
 
#   David Lutterkort  
 
 
 
 
# 
 
 
 
 
# chkconfig: 2345 98 02 
 
 
 
 
# 
 
 
 
 
# description: Enables periodic system configuration checks through puppet. 
 
 
 
 
# processname: puppet

Jira (PUP-1924) source function library *before* client sysconfig overrides

2016-05-27 Thread Robin Bowes (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Robin Bowes commented on  PUP-1924 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: source function library *before* client sysconfig overrides  
 
 
 
 
 
 
 
 
 
 
This appears to have regressed, at least in PE 3.8.5 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-4039) package resource doesn't find new packages in yum repo

2016-04-12 Thread Robin Bowes (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Robin Bowes commented on  PUP-4039 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: package resource doesn't find new packages in yum repo  
 
 
 
 
 
 
 
 
 
 
I would also add that $current_client is on EL6 
R. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-2182) Package resource not working as expected in 3.5.0

2016-04-12 Thread Robin Bowes (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Robin Bowes commented on  PUP-2182 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Package resource not working as expected in 3.5.0  
 
 
 
 
 
 
 
 
 
 
This change causes a regression detailed in PUP-4039 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-4039) package resource doesn't find new packages in yum repo

2016-04-12 Thread Robin Bowes (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Robin Bowes commented on  PUP-4039 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: package resource doesn't find new packages in yum repo  
 
 
 
 
 
 
 
 
 
 
Following some input from Richard Clamp, it seems this is the cause of the regression: 
https://github.com/puppetlabs/puppet/commit/21322de612356b231830ec8cce57371b84306520 
The relevant ticket is 

PUP-2182
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-4039) package resource doesn't find new packages in yum repo

2016-04-12 Thread Robin Bowes (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Robin Bowes commented on  PUP-4039 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: package resource doesn't find new packages in yum repo  
 
 
 
 
 
 
 
 
 
 
Has there been any further progress with this? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-4039) package resource doesn't find new packages in yum repo

2016-03-25 Thread Robin Bowes (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Robin Bowes commented on  PUP-4039 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: package resource doesn't find new packages in yum repo  
 
 
 
 
 
 
 
 
 
 
I'm not sure why it is using yum list in the install method of the yum provider. There's some comment about virtual packages: 
 
 
 
 
 
 
unless @resource.allow_virtual? 
 
 
 
 
  yum *['-d', '0', '-e', '0', '-y', install_options, :list, wanted].compact 
 
 
 
 
end 
 
 
 
 
 
 
To my mind, if we were calling "install" then we should just run "yum install", not run "yum list" before running "yum install" 
R. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to

Jira (PUP-4039) package resource doesn't find new packages in yum repo

2016-03-25 Thread Robin Bowes (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Robin Bowes commented on  PUP-4039 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: package resource doesn't find new packages in yum repo  
 
 
 
 
 
 
 
 
 
 
Michael Stahnke I am the original reporter of this. 
Did you actually try the steps detailed in the original post? 
The problem occurs because the yum command used by the yum provider to test for package availability does not update the cache. 

 
 
 
 
 
 
yum list new_package 
 
 
 
 
 
 does not find new_package if it is not in the local cache 
 
 
 
 
 
 
yum install new_package 
 
 
 
 
 
 does find new_package even if it is not in the cache because it updates the cache. 
I don't consider this to be resolved. 
R. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)

Jira (PUP-2621) ssh_authorized_keys should not use the key 'comment' as a unique identifier (name)

2015-03-20 Thread Robin Bowes (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Robin Bowes commented on  PUP-2621 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: ssh_authorized_keys should not use the key 'comment' as a unique identifier (name)  
 
 
 
 
 
 
 
 
 
 
For me, the ssh_authorized_key resource is unusable because of this issue. 
Is there any enthusiasm for a change to this resource, or even a new one that works? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 (PUP-1175) Puppet ssh_authorized_keys fails on one account if key with same name exists in another account

2015-03-20 Thread Robin Bowes (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Robin Bowes commented on  PUP-1175 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Puppet ssh_authorized_keys fails on one account if key with same name exists in another account  
 
 
 
 
 
 
 
 
 
 
This is related to PUP-2621 
I'm seeing a similar issue (using puppet 3.7.4). 
It's because the ssh_authorized_key resource uses the sshkey comment as a unique identifier in the catalogue - it should not. It is entirely common for the same sshkey (with the same comment) to be installed for multiple users on the same node, and even for a user to have two different sshkeys with the same comment. 
I will put most of my comments in PUP-2621 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 (PUP-1515) When compiling a catalog, providers should be loaded from specified environment

2015-03-10 Thread Robin Bowes (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Robin Bowes commented on  PUP-1515 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: When compiling a catalog, providers should be loaded from specified environment  
 
 
 
 
 
 
 
 
 
 
Thanks Henrik. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 (PUP-1515) When compiling a catalog, providers should be loaded from specified environment

2015-03-09 Thread Robin Bowes (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Robin Bowes commented on  PUP-1515 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: When compiling a catalog, providers should be loaded from specified environment  
 
 
 
 
 
 
 
 
 
 
I appear to be running into this very issue (with the puppetboard module, that uses vcsrepo). 
Is there a fix/workaround? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 (PUP-4052) puppet module generate uses invalid default license identifier

2015-02-26 Thread Robin Bowes (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Robin Bowes created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4052 
 
 
 
  puppet module generate uses invalid default license identifier  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 3.7.4 
 
 
 

Assignee:
 
 Kylo Ginsberg 
 
 
 

Components:
 

 Client 
 
 
 

Created:
 

 2015/02/26 3:54 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Robin Bowes 
 
 
 
 
 
 
 
 
 
 
The default suggested license is Apache 2.0. This is not a valid license identifier as per http://spdx.org/licenses/ 
I'm using garethr's module skeleton as the base for my module(s) and when I run bundle exec rake test, this is the error I see: 
 
 
 
 
 
 
metadata-json-lint metadata.json 
 
 
 
 
Warning: License identifier Apache 2.0 is not in the SPDX list: http://spdx.org/licenses/

Jira (PUP-4039) Add ubnt/ubic deploy keys to CentOS 7 Base

2015-02-24 Thread Robin Bowes (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Robin Bowes created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4039 
 
 
 
  Add ubnt/ubic deploy keys to CentOS 7 Base  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 3.7.4 
 
 
 

Assignee:
 
 Kylo Ginsberg 
 
 
 

Components:
 

 Types and Providers 
 
 
 

Created:
 

 2015/02/24 4:06 PM 
 
 
 

Environment:
 
 
CentOS 7, puppet 3.7.4 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Robin Bowes 
 
 
 
 
 
 
 
 
 
 
I created a new meta RPM and added it to my yum repo. 
I then added a package resource to install the new RPM. 
The manifest fails as follows: 
 
 
 
 
 
 
Error: /Stage[main]/Profile_sensu_client::Nagios_plugins/Package[ubnt-meta-nagios-plugins]/ensure: change from absent to present failed: Execution

Jira (PUP-4039) package resource doesn't find new packages in yum repo

2015-02-24 Thread Robin Bowes (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Robin Bowes updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4039 
 
 
 
  package resource doesn't find new packages in yum repo  
 
 
 
 
 
 
 
 
 

Change By:
 
 Robin Bowes 
 
 
 

Summary:
 
 Addubnt/ubicdeploykeystoCentOS7Base packageresourcedoesn'tfindnewpackagesinyumrepo 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 (PUP-1635) current thread not owner after Puppet Agent receives USR1 signal

2015-01-22 Thread Robin Bowes (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Robin Bowes commented on  PUP-1635 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: current thread not owner after Puppet Agent receives USR1 signal  
 
 
 
 
 
 
 
 
 
 
This is just a me too comment. 
CentOS 7 ruby 2.0.0 (as supplied by CentOS) puppet 3.7.3 (from PL yum repo) mcollective 2.7.0 (from PL yum repo) 

 
 
 
 
 
 
mco puppet runonce 
 
 
 
 
 
 causes puppet to fail with this output in /var/log/messages: 
 
 
 
 
 
 
Jan 22 23:45:55 ip-172-20-14-143 puppet-agent[26617]: Caught USR1; calling reload 
 
 
 
 
Jan 22 23:45:55 ip-172-20-14-143 puppet-agent[26427]: Could not autoload puppet/indirector/node/rest: current thread not owner 
 
 
 
 
Jan 22 23:45:55 ip-172-20-14-143 puppet-agent[26427]: Unable to fetch my node definition, but the agent run will continue: 
 
 
 
 
Jan 22 23:45:55 ip-172-20-14-143 puppet-agent[26427]: Could not autoload puppet/indirector/node/rest: current thread not owner 
 
 
 
 
Jan 22 23:45:55 ip-172-20-14-143 puppet-agent[26427]: Could not autoload puppet/feature/external_facts: current thread not owner 
 
 
 
 
Jan 22 23:45:55 ip-172-20-14-143 puppet-agent[26427]: Failed to apply catalog: Could not autoload puppet/feature/external_facts: current thread not owner

Jira (FACT-718) Allow for disabling certain facts within Facter

2014-12-29 Thread Robin Bowes (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Robin Bowes commented on  FACT-718 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Allow for disabling certain facts within Facter  
 
 
 
 
 
 
 
 
 
 
Additionally, I'd like to disable specific ec2 facts. 
For example, ec2_iam* should not be reported as facts, and ec2_network_interface_macs* are just clutter in an environment with an high turnover of nodes. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 (PUP-3794) puppet fails in odd ways if LANG not set

2014-12-26 Thread Robin Bowes (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Robin Bowes created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3794 
 
 
 
  puppet fails in odd ways if LANG not set  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2014/12/26 1:58 AM 
 
 
 

Environment:
 
 
I discovered this on OSX Yosemite 10.10.1 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Robin Bowes 
 
 
 
 
 
 
 
 
 
 
Background: I'm setting up my kids' three MacBook Pros so I can manage them centrally. I've grabbed facter/hiera/puppet images from http://downloads.puppetlabs.com/mac/ and installed manually in the GUI. 
I then enabled remote ssh and connected remotely to finish the setup/configuration. 
I spent ages trying to figure out why I couldn't get puppet to work: 
 
 
 
 
 
 
Billys-MacBook-Pro:~ robin$ sudo puppet resource group name=puppet ensure=present 
 
 
 
 
Password:

Jira (PUP-3795) Suggested launchd config gives warnings with Yosemite (10.10.1)

2014-12-26 Thread Robin Bowes (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Robin Bowes created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3795 
 
 
 
  Suggested launchd config gives warnings with Yosemite (10.10.1)  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2014/12/26 2:24 AM 
 
 
 

Environment:
 
 
OSX 10.10.1 (Yosemite) 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Robin Bowes 
 
 
 
 
 
 
 
 
 
 
Using the suggested launchd config to start puppet agent on a MacBook Pro I see the following warnings in /var/liog/system.log: 
 
 
 
 
 
 
Dec 26 10:15:23 abby-mbp-wireless com.apple.xpc.launchd[1] (com.puppetlabs.puppet): Unknown key for string: ServiceDescription 
 
 
 
 
Dec 26 10:15:23 abby-mbp-wireless com.apple.xpc.launchd[1] (com.puppetlabs.puppet): Please switch away from OnDemand to KeepAlive. 
 
 
 
 
Dec 26 10:15:23 abby-mbp-wireless

Jira (PDB-135) Improve warning message for invalid UTF-8 byte sequences

2014-12-18 Thread Robin Bowes (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Robin Bowes commented on  PDB-135 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Improve warning message for invalid UTF-8 byte sequences  
 
 
 
 
 
 
 
 
 
 
Is anyone actively looking at this? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-3323) yum provider should be able to install from remote URLs

2014-09-21 Thread Robin Bowes (JIRA) 
Title: Message Title










 

 Robin Bowes created an issue


















 Puppet /  PUP-3323



  yum provider should be able to install from remote URLs 










Issue Type:

  Improvement




Assignee:

 Kylo Ginsberg




Components:


 Types and Providers




Created:


 21/Sep/14 12:01 PM




Environment:


Any platform using the yum provider




Priority:

  Normal




Reporter:

 Robin Bowes










This should result in the remote package being installed, with all dependencies: ``` package {'activemq': source = 'http://www.netconsonance.com/downloads/activemq-5.9.1-2.el6.noarch.rpm', ensure = present, }
``` What actually happens is that the latest version available in the configured yum repos is installed.
Explicitly specifying provider = 'rpm' downloads and installs the remote package, but will fail if all dependencies are not already installed.
yum supports this, ie. yum install http://www.netconsonance.com/downloads/activemq-5.9.1-2.el6.noarch.rpm will download the package and install with all dependencies, so I think the puppet yum provider should support this too.

Jira (PUP-3323) yum provider should be able to install from remote URLs

2014-09-21 Thread Robin Bowes (JIRA) 
Title: Message Title










 

 Robin Bowes updated an issue


















 Puppet /  PUP-3323



  yum provider should be able to install from remote URLs 










Change By:

 Robin Bowes









 Thisshouldresultintheremotepackagebeinginstalled,withalldependencies:  {code}package{'activemq':source='http://www.netconsonance.com/downloads/activemq-5.9.1-2.el6.noarch.rpm',ensure=present,}{code}  Whatactuallyhappensisthatthelatestversionavailableintheconfiguredyumreposisinstalled.Explicitlyspecifyingprovider='rpm'downloadsandinstallstheremotepackage,butwillfailifalldependenciesarenotalreadyinstalled.yumsupportsthis,ie.yuminstallhttp://www.netconsonance.com/downloads/activemq-5.9.1-2.el6.noarch.rpmwilldownloadthepackageandinstallwithalldependencies,soIthinkthepuppetyumprovidershouldsupportthistoo.












   

 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-627) Boolean facts not printed with facter -p if fact value is false

2014-07-23 Thread Robin Bowes (JIRA) 
Title: Message Title










 

 Robin Bowes created an issue


















 Facter /  FACT-627



  Boolean facts not printed with facter -p if fact value is false 










Issue Type:

  Bug




Assignee:

 Eric Sorenson




Created:


 23/Jul/14 6:26 AM




Environment:


RHEL 6, PE 3.1.3




Priority:

  Normal




Reporter:

 Robin Bowes










Boolean facts are not printed with facter -p if the fact value is false.
Example (using a custom fact):


[root@cxdrun01 ~]# facter -p | grep is_cde
is_cde = true
[root@cxdrun01 ~]# facter -p is_cde
true
# fiddle the is_cde fact to be false here
[root@cxdrun01 ~]# facter -p | grep is_cde
is_cde = false
[root@cxdrun01 ~]# facter -p is_cde
(no output printed here)















   

 Add Comment

Jira (FACT-627) Boolean facts not printed with facter -p if fact value is false

2014-07-23 Thread Robin Bowes (JIRA) 
Title: Message Title










 

 Robin Bowes commented on an issue


















  Re: Boolean facts not printed with facter -p if fact value is false 










It seems that this is caused when the plugin code returns a false value instead of a string value false.
This is the code I am now using, and which works:


Facter.add('is_cde') do
  setcode do
if Facter.value(:role).match(/cde/)
  true
else
  false
end
  end
end



I should point out that I copied the code that didn't work correctly from pe_version.rb in stdlib so that code should probably be changed too.












   

 Add Comment

























 Facter /  FACT-627



  Boolean facts not printed with facter -p if fact value is false 







 Boolean facts are not printed with facter -p if the fact value is false.   Example (using a custom fact):  {noformat}  [root@cxdrun01 ~]# facter -p | grep is_cde  is_cde = true  [root@cxdrun01 ~]# facter -p is_cde  true  # fiddle the is_cde fact to be false here  [root@cxdrun01 ~]# facter -p | grep is_cde  is_cde = false  [root@cxdrun01 ~]# facter -p i...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)

Jira (PUP-2079) puppet module generate can't copy template files without parsing/renaming them

2014-03-27 Thread Robin Bowes (JIRA) 
Title: Message Title










 

 Robin Bowes created an issue


















 Puppet /  PUP-2079



  puppet module generate can't copy template files without parsing/renaming them 










Issue Type:

  Bug




Assignee:


 Unassigned




Created:


 27/Mar/14 8:55 AM




Priority:

  Normal




Reporter:

 Robin Bowes










When creating a new module with puppet module generate, any files in the skeleton dir named *.erb are parsed as Ruby erb templates and renamed, removing the file extension. This is a pain if you want to include template files in your skeleton directory.












   

 Add Comment






















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)