Problem with facter/ipaddress with puppet client 2.7

33 views
Skip to first unread message

puppetstan

unread,
Dec 23, 2014, 1:21:22 PM12/23/14
to puppet...@googlegroups.com
Hi,

On my centos6 and redhat6 i have puppet client update with puppet 2.7.25-2 and facter-1.6.18-7 version with epel repo


My problem is with ipaddress facter, now i have


# facter
ipaddress => eth0      Link encap:Ethernet  HWaddr 00:50:12:AZ:01:F9            inet adr:172.17.03.21  Bcast:172.17.11.255  Masque:255.255.255.0          adr inet6: fe80::250:56ff:feaf:f9/64 Scope:Lien          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1          RX packets:36042965 errors:0 dropped:0 overruns:0 frame:0          TX packets:32410578 errors:0 dropped:0 overruns:0 carrier:0          collisions:0 lg file transmission:1000           RX bytes:14080706754 (13.1 GiB)  TX bytes:41166159624 (38.3 GiB)lo        Link encap:Boucle locale            inet adr:127.0.0.1  Masque:255.0.0.0          adr inet6: ::1/128 Scope:H▒te          UP LOOPBACK RUNNING  MTU:16436  Metric:1          RX packets:10055 errors:0 dropped:0 overruns:0 frame:0          TX packets:10055 errors:0 dropped:0 overruns:0 carrier:0          collisions:0 lg file transmission:0           RX bytes:626380 (611.6 KiB)  TX bytes:626380 (611.6 KiB)


before i had

# facter
ipaddress => x.x.x.x


Can you have this problem with this puppet and facter version?

regards

Felix Frank

unread,
Dec 23, 2014, 6:45:40 PM12/23/14
to puppet...@googlegroups.com
On 12/23/2014 07:21 PM, puppetstan wrote:
>
> Can you have this problem with this puppet and facter version?

No, that's a pretty serious issue. Please note that Facter 1.6.x is
obsolete - from my gut feeling, it's even more dusty than Puppet 2.7.
Any chance for you to get Facter 1.7?

puppetstan

unread,
Dec 24, 2014, 4:38:37 AM12/24/14
to puppet...@googlegroups.com
Thanks a lot for your answer : It's good now with facter 1.7

#  wget https://yum.puppetlabs.com/el/6/products/x86_64/facter-1.7.0-1.el6.x86_64.rpm

# rpm -Uvh facter-1.7.0-1.el6.x86_64.rpm


and it's OK

regards
Reply all
Reply to author
Forward
0 new messages