Jira (FACT-380) Private ipaddress is used as ipaddress fact

2015-04-09 Thread Sam Weston (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sam Weston commented on  FACT-380 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Private ipaddress is used as ipaddress fact  
 
 
 
 
 
 
 
 
 
 
Thanks for the updates! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-380) Private ipaddress is used as ipaddress fact

2015-01-30 Thread Sam Weston (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sam Weston commented on  FACT-380 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Private ipaddress is used as ipaddress fact  
 
 
 
 
 
 
 
 
 
 
This fix is much less hacky than mine and won't break when facter updates, so thanks. However I think this is definitely a problem with puppet behaviour and could be triggered in any situation where the primary network interface isn't at the top of the ifconfig list. If I weren't so hopeless at writing code I'd rewrite the ruby method to use default route and use the 'ip' command instead of 'ifconfig' for newer distributions that support it. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 (FACT-380) Private ipaddress is used as ipaddress fact

2015-01-28 Thread Sam Weston (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sam Weston updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Facter /  FACT-380 
 
 
 
  Private ipaddress is used as ipaddress fact  
 
 
 
 
 
 
 
 
 

Change By:
 
 Sam Weston 
 
 
 

Affects Version/s:
 
 FACT2.4.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 (FACT-380) Private ipaddress is used as ipaddress fact

2015-01-28 Thread Sam Weston (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sam Weston commented on  FACT-380 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Private ipaddress is used as ipaddress fact  
 
 
 
 
 
 
 
 
 
 
Your code didn't work properly for me. Instead I used: 
 
 
 
 
 
 
default_route_interface = Facter::Util::Resolution.exec('ip route show |grep default|cut -d   -f 5') 
 
 
 
 
output = Facter::Util::IP.exec_ifconfig([#{default_route_interface} 2/dev/null])}}
 
 
 
 
 
 
 
It's horribly hacky but it works. 
This is really causing us problems since introducing docker a few days ago. Please fix it! 
Thanks 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3203) Errors when using scheduled_task on windows

2014-09-23 Thread Sam Weston (JIRA) 
Title: Message Title










 

 Sam Weston updated an issue


















 Puppet /  PUP-3203



  Errors when using scheduled_task on windows 










Change By:

 Sam Weston




Affects 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 (PUP-3203) Errors when using scheduled_task on windows

2014-09-16 Thread Sam Weston (JIRA) 
Title: Message Title










 

 Sam Weston commented on an issue


















  Re: Errors when using scheduled_task on windows 










Hi Josh. Thanks for the heads up about the windows paths.
Here is the output from that command:


Task'Adobe Flash Player Updater.job'
Command 'C:\Windows\SysWOW64\Macromed\Flash\FlashPlayerUpdateService.exe'
Args''
Working dir ''
User''
Triggers 1
trigger 0
{start_year=2000,
 start_month=1,
 start_day=1,
 end_year=0,
 end_month=0,
 end_day=0,
 start_hour=0,
 start_minute=58,
 minutes_duration=1440,
 minutes_interval=60,
 flags=0,
 trigger_type=:TASK_TIME_TRIGGER_DAILY,
 random_minutes_interval=0,
 type={days_interval=1}}
Task'G2MUpdateTask-S-1-5-21-3845744863-2409227386-321987-5638.job'
Command 'C:\Users\sweston\AppData\Local\Citrix\GoToMeeting\1558\g2mupdate.ex
e'
Args''
Working dir 'C:\Users\sweston\AppData\Local\Citrix\GoToMeeting\1558'
User'SMALLBUSINESS\sweston'
Triggers 1
trigger 0
{start_year=2014,
 start_month=8,
 start_day=26,
 end_year=0,
 end_month=0,
 end_day=0,
 start_hour=13,
 start_minute=29,
 minutes_duration=1439,
 minutes_interval=60,
 flags=0,
 trigger_type=:TASK_TIME_TRIGGER_DAILY,
 random_minutes_interval=0,
 type={days_interval=1}}
Task'GoogleUpdateTaskMachineCore.job'
Command 'C:\Program Files (x86)\Google\Update\GoogleUpdate.exe'
Args'/c'
Working dir ''
User''
Triggers 2
trigger 0
Failed to load trigger 'Run at user logon'
trigger 1
{start_year=2014,
 start_month=9,
 start_day=10,
 end_year=0,
 end_month=0,
 end_day=0,
 start_hour=14,
 start_minute=25,
 minutes_duration=0,
 minutes_interval=0,
 flags=0,
 trigger_type=:TASK_TIME_TRIGGER_DAILY,
 random_minutes_interval=0,
 type={days_interval=1}}
Task'GoogleUpdateTaskMachineUA.job'
Command 'C:\Program Files (x86)\Google\Update\GoogleUpdate.exe'
Args'/ua /installsource scheduler'
Working dir ''
User''
Triggers 1
trigger 0
{start_year=2014,
 start_month=9,
 start_day=10,
 end_year=0,
 end_month=0,
 end_day=0,
 start_hour=14,
 start_minute=25,
 minutes_duration=1440,
 minutes_interval=60,
 flags=0,
 trigger_type=:TASK_TIME_TRIGGER_DAILY,
 random_minutes_interval=0,
 type={days_interval=1}}
Task'GoogleUpdateTaskUserS-1-5-21-3845744863-2409227386-321987-5638C
ore.job'
Command 'C:\Users\sweston\AppData\Local\Google\Update\GoogleUpdate.exe'
Args'/c'
Working dir ''
User'SMALLBUSINESS\sweston'
Triggers 1
trigger 0
{start_year=2014,
 start_month=6,
 start_day=17,
 end_year=0,
 end_month=0,
 end_day=0,
 start_hour=16,
 start_minute=14,
 minutes_duration=0,
 minutes_interval=0,
 flags=0,
 trigger_type=:TASK_TIME_TRIGGER_DAILY,
 random_minutes_interval=0,
 type={days_interval=1}}
Task'GoogleUpdateTaskUserS-1-5-21-3845744863-2409227386-321987-5638U
A.job'
Command 'C:\Users\sweston\AppData\Local\Google\Update\GoogleUpdate.exe'
Args'/ua /installsource scheduler'
Working dir ''
User'SMALLBUSINESS\sweston'
Triggers 1
trigger 0
{start_year=2014,
 start_month=6,
 start_day=17,
 end_year=0,
 end_month=0,
 end_day=0,
 start_hour=16,
 start_minute=14,
 minutes_duration=1440,
 minutes_interval=60,
 flags=0,
 trigger_type=:TASK_TIME_TRIGGER_DAILY,
 random_minutes_interval=0,
 type={days_interval=1}}
Task'Set _JAVA_OPTIONS.job'
Command 'C:\ProgramData\PuppetLabs\javaenv.bat'
Args''
Working dir ''
User''
Triggers 1
trigger 0
{start_year=2014,
 start_month=9,
 start_day=10,
 end_year=0,
 end_month=0,
 end_day=0,
 start_hour=12,
 start_minute=0,
 minutes_duration=0,
 minutes_interval=0,
 flags=0,
 trigger_type=:TASK_TIME_TRIGGER_DAILY,
 random_minutes_interval=0,
 type={days_interval=1}}

Jira (PUP-3203) Errors when using scheduled_task on windows

2014-09-11 Thread Sam Weston (JIRA) 
Title: Message Title










 

 Sam Weston updated an issue


















 Puppet /  PUP-3203



  Errors when using scheduled_task on windows 










Trace as requested.










Change By:

 Sam Weston




Attachment:

 trace.txt












   

 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-3203) Errors when using scheduled_task on windows

2014-09-10 Thread Sam Weston (JIRA) 
Title: Message Title










 

 Sam Weston updated an issue


















 Puppet /  PUP-3203



  Errors when using scheduled_task on windows 










I've downgraded my machine to 3.6.2 and am now pretty confident that this is a problem with 3.7.0 only.










Change By:

 Sam Weston




Labels:

 regression windows












   

 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-3203) Errors when using scheduled_task on windows

2014-09-09 Thread Sam Weston (JIRA) 
Title: Message Title










 

 Sam Weston created an issue


















 Puppet /  PUP-3203



  Errors when using scheduled_task on windows 










Issue Type:

  Bug




Affects Versions:


 3.7.0




Assignee:

 Kylo Ginsberg




Components:


 Types and Providers




Created:


 09/Sep/14 7:05 AM




Environment:


Windows 7 x64




Labels:


 windows




Priority:

  Normal




Reporter:

 Sam Weston










I'm using the scheduled_task provider to create a daily task. The initial task creation goes fine, but on any future puppet run I get things like this: {{change from  {'every' = '1', 'schedule' = 'daily', 'start_date' = '2014-9-9', 'start_time' = '12:00'}
 to [ {'every' = '1', 'schedule' = 'daily', 'start_date' = '2014-9-8', 'start_time' = '12:00'}
] failed: no implicit conversion from nil to integer}}

Jira (PUP-3203) Errors when using scheduled_task on windows

2014-09-09 Thread Sam Weston (JIRA) 
Title: Message Title










 

 Sam Weston updated an issue


















 Puppet /  PUP-3203



  Errors when using scheduled_task on windows 










Change By:

 Sam Weston









 I'musingthescheduled_taskprovidertocreateadailytask.Theinitialtaskcreationgoesfine,butonanyfuturepuppetrunIgetthingslikethis:changefrom{'every'='1','schedule'='daily','start_date'='2014-9-9','start_time'='12:00'}to[{'every'='1','schedule'='daily','start_date'='2014-9-8','start_time'='12:00'}]failed:noimplicitconversionfromniltointeger  Ipreviouslyhadalesscomplicateddefinitionandgotthiserror:changefrom{'every'='1','schedule'='daily','start_date'='2014-9-8','start_time'='12:00'}to[{'schedule'='daily','start_time'='12:00'}]failed:noimplicitconversionfromniltointegerUnfortunatelyI'mnotsureifthiswaspresentin3.6.2asallmymachinesarerunning3.7.0andsettoautomaticallyupgrade.ImadethisclassshortlybeforetheupgradeandIdon'tthinkitwasaproblem.AmItheonlyonehavingthisproblem?












   

 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-3203) Errors when using scheduled_task on windows

2014-09-09 Thread Sam Weston (JIRA) 
Title: Message Title










 

 Sam Weston updated an issue


















 Puppet /  PUP-3203



  Errors when using scheduled_task on windows 










Change By:

 Sam Weston









 I'musingthescheduled_taskprovidertocreateadailytask.Theinitialtaskcreationgoesfine,butonanyfuturepuppetrunIgetthingslikethis: {{ changefrom{'every'='1','schedule'='daily','start_date'='2014-9-9','start_time'='12:00'}to[{'every'='1','schedule'='daily','start_date'='2014-9-8','start_time'='12:00'}]failed:noimplicitconversionfromniltointeger }} Ipreviouslyhadalesscomplicateddefinitionandgotthiserror: {{ changefrom{'every'='1','schedule'='daily','start_date'='2014-9-8','start_time'='12:00'}to[{'schedule'='daily','start_time'='12:00'}]failed:noimplicitconversionfromniltointeger }} UnfortunatelyI'mnotsureifthiswaspresentin3.6.2asallmymachinesarerunning3.7.0andsettoautomaticallyupgrade.ImadethisclassshortlybeforetheupgradeandIdon'tthinkitwasaproblem.AmItheonlyonehavingthisproblem?












   

 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.