7020999: SUSEConnect error: IPAddr::InvalidAddressError: invalid address.

This document (7020999) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Linux Enterprise Server 12 Service Pack 1 (SLES 12 SP1)

SUSE Linux Enterprise Server 12 Service Pack 2 (SLES 12 SP2)

SUSE Linux Enterprise Desktop 12 Service Pack 1 (SLED 12 SP1)

SUSE Linux Enterprise Desktop 12 Service Pack 1 (SLED 12 SP2)

Situation

When using SUSEConnect an error appears:
SUSEConnect error: IPAddr::InvalidAddressError: invalid address
/usr/lib64/ruby/2.1.0/ipaddr.rb:559:in `in6_addr’ /usr/lib64/ruby/2.1.0/ipaddr.rb:496:in `initialize’ /usr/lib64/ruby/2.1.0/ipaddr.rb:514:in `new’ /usr/lib64/ruby/2.1.0/ipaddr.rb:514:in `coerce_other’ /usr/lib64/ruby/2.1.0/ipaddr.rb:170:in `include?’ /usr/lib64/ruby/2.1.0/uri/generic.rb:1676:in `block in find_proxy’ /usr/lib64/ruby/2.1.0/uri/generic.rb:1665:in `scan’ /usr/lib64/ruby/2.1.0/uri/generic.rb:1665:in `find_proxy’ /usr/lib64/ruby/2.1.0/net/http.rb:1034:in `proxy_uri’ /usr/lib64/ruby/2.1.0/net/http.rb:1019:in `proxy?’ /usr/lib64/ruby/gems/2.1.0/gems/suse-connect-0.2.42/lib/suse/connect/connection.rb:24:in `initialize’ /usr/lib64/ruby/gems/2.1.0/gems/suse-connect-0.2.42/lib/suse/connect/api.rb:21:in `new’

Resolution

Update ruby2.1, ruby2.1-stdlib and libruby2_1-2_1 to newer version 2.1.9-18.1

Cause

Regression introduced by a previous update that was intended to fix insufficient support for domain wildcards in the $no_proxy environment variable.

Bug Number

1035988

Internal Notes

21st June 2017 – Peter Smidzar – TID creation

23rd June 2017 – Hans van den Heuvel – Added bug number and released TID.

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

Related:

Leave a Reply