Jira (FACT-1468) facter fails to report correct ipaddress when routing_table fails on default gateway entry

2016-11-01 Thread Diego Abelenda (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Diego Abelenda commented on  FACT-1468 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: facter fails to report correct ipaddress when routing_table fails on default gateway entry  
 
 
 
 
 
 
 
 
 
 
Right, with puppet 4.7.1, agent 1.7.1 there is no issue anymore for this case. Thank you. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1468) facter fails to report correct ipaddress when routing_table fails on default gateway entry

2016-07-25 Thread Diego Abelenda (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Diego Abelenda created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1468 
 
 
 
  facter fails to report correct ipaddress when routing_table fails on default gateway entry  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 FACT 3.y 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/07/25 1:47 AM 
 
 
 

Environment:
 
 
ubuntu 16.04 in virtual kvm environment puppet 4.5.1 (agent 1.5.1-1xenial) 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Diego Abelenda 
 
 
 
 
 
 
 
 
 
 
The routing table is as follows: default via XXX.XXX.XXX.XXX dev ens3 onlink  10.42.0.0/16 dev docker0 proto kernel scope link src 10.42.0.1 XXX.XXX.XXX.XXX/24 dev ens3 proto kernel scope link src XXX.XXX.XXX.XXX 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1  
facter fails to parse the default via line due to onlink (FACT-1405) logging a warning. 
Thus fails to detect the primary_interface and thus returns the first interface it finds namely "docker0" which returns the same IP for every host. (and causes issues with exported resources using ipaddress in our case – sshkey) 
I tried reading the code to find out what happens but could not reach a conclusion. 
From what I can see, there are two possible ways to parse the routing table, the first is by reading the output of

Jira (PUP-6461) pip package provider with "ensure => latest" displays version change when there is none (problem parsing the output string in some cases)

2016-06-30 Thread Diego Abelenda (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Diego Abelenda created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6461 
 
 
 
  pip package provider with "ensure => latest" displays version change when there is none (problem parsing the output string in some cases)  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 4.5.2 
 
 
 

Assignee:
 
 Kylo Ginsberg 
 
 
 

Components:
 

 Types and Providers 
 
 
 

Created:
 

 2016/06/30 7:14 AM 
 
 
 

Environment:
 
 
Debian Jessie pip 1.5.6 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Diego Abelenda 
 
 
 
 
 
 
 
 
 
 
When using  package  {'virtualenv': ensure => latest, provider => 'pip', } 
The return string from " pip install --upgrade virtualenv " is """ Installed version (15.0.2) is most up-to-date (past versions: 15.0.2, 15.0.2, 15.0.1, 15.0.1, 15.0.0, 15.0.0, 14.0.6, 14.0.6, 14.0.5, 14.0.5, 14.0.4, 14.0.4, 14.0.3, 14.0.3, 14.0.2, 14.0.2, 14.0.1, 14.0.1, 14.0.0, 14.0.0, 13.1.2, 13.1.2, 13.1.1, 13.1.1, 13.1.0, 13.1.0, 13.0.3, 13.0.3, 13.0.2, 13.0.2, 13.0.1, 13.0.1, 13.0.0, 13.0.0, 12.1.1, 12.1.1, 12.1.0, 12.1.0, 12.0.7, 12.0.7, 12.0.6, 12.0.5, 12.0.5, 12.0.4, 12.0.4, 12.0.2, 12.0.2, 12.0.1, 12.0.1, 12.0, 12.0,