Jira (PUP-7658) Puppet 4.10.2 fails when Facter facts contains ampersand

2017-06-15 Thread Steph Gosling (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steph Gosling commented on  PUP-7658 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Puppet 4.10.2 fails when Facter facts contains ampersand  
 
 
 
 
 
 
 
 
 
 
Just a +1 to this as it's hit one of my customers hard and has broken autoscaling for several loadbalancers. An expedited release would be greatly appreciated  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6861) [regression] Mount options not idempotent

2016-11-17 Thread Steph Gosling (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steph Gosling commented on  PUP-6861 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: [regression] Mount options not idempotent  
 
 
 
 
 
 
 
 
 
 
Late to the party it appears but also affects Ubuntu 12.04 with puppet-agent 1.8.0-1precise but not 12.04 with 1.5.2-1precise 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-2132) Puppet 3.X is now broken on Amazon AWS due to Ruby 2.0 being the default

2014-10-09 Thread Steph Gosling (JIRA)
Title: Message Title










 

 Steph Gosling commented on an issue


















  Re: Puppet 3.X is now broken on Amazon AWS due to Ruby 2.0 being the default 










I believe this can be closed as invalid. Yes the yum dependency graph does seem to pull in ruby20 but if you reconfigure your alternatives to use ruby18 and then install rubygems18 it looks to me that 3.7.1 (at least) runs, at least for me.












   

 Add Comment

























 Puppet /  PUP-2132



  Puppet 3.X is now broken on Amazon AWS due to Ruby 2.0 being the default 







 Last week Amazon updated their AMIs (distributions) and repositories to 2014.03 and changed the default Ruby version from 1.8 to 2.0   e.g.:  -- old behaviour  rubygems = rubygems-1.8.25-8.12.amzn1  -- new behaviour  rubygems = rubygems-2.0-0.3.amzn1  -- to get rubygems 1.8  rubygems18 = rubygems-1.8.25-8.12.amzn1   After these changes, Puppet crashes w...















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




 














-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to