Hi,
todays SUSE-SLE-SERVER-12-SP2-2017-624 may break SUSEConnect if your
environment uses the ‘no_proxy’ variable.
The cause seems to be that a pre-final PTF made it into the update.
There is one part missing to the solution of bsc#1014863, namely
https://github.com/ruby/ruby/commit/556e3da4216c926e71dea9ce4ea4a08dcfdc1275
You can easily apply it by hand to /usr/lib64/ruby/2.1.0/uri/generic.rb
if you already applied the patch or wait for a fixed version of the patch.
Franz
Hi Franz,
As per details in the bug, I think you both reported this issue, and confirmed the solution… ?
Anyway, I have added your comment here to the bug again as well.
Thanks
Hans
Hi Hans,
yes, I was (one of?) the reporter of this bug. That’s why I tested the
channel patch immediately. But to my surprise I saw the same error like
in the first iteration of the PTF and reported it here.
Unfortunately I was totally side-tracked after that and didn’t open a
new SR. But the SLES gods heard me anyway and released
SUSE-SLE-SERVER-12-SP2-2017-643 earlier this week ;-).
Franz.
[QUOTE=Franz Sirl;37646]Hi Hans,
yes, I was (one of?) the reporter of this bug. That’s why I tested the
channel patch immediately. But to my surprise I saw the same error like
in the first iteration of the PTF and reported it here.
Unfortunately I was totally side-tracked after that and didn’t open a
new SR. But the SLES gods heard me anyway and released
SUSE-SLE-SERVER-12-SP2-2017-643 earlier this week ;-).
Franz.[/QUOTE]
Hey Franz,
Thanks for the confirmation.
I did check the bug and was told the fix was on it’s way but I had not had time to update here.
Good to see it is sorted now .
Best regards
Hans