Unable to register evaluation install SLES12-SP2 for SUMA

SUSE Linux Enterprise Server 12 SP2 (x86_64) - Lab VM trial for SUMA.

Issue #1 - info
Sadly there doesn’t seem to be any provision for a proxy during the initial installation of SLES12. The network config stuff is nice, but desperately needs a proxy string addition step yesternow. All the great work you’ve done on the subsequent menus (like selecting SUMA as an add on) is probably meaningless to anyone working behind a proxy until you do. :frowning:

Issue #2 - show stopper
In either yast or with SUSEConnect attempts to register the server instance fail with the error:

getaddrinfo: Name or service not known

DNS Resolution and Proxy access have been configured and wget used to confirm access is ok:

wget https://scc.suse.com
--2017-03-06 14:42:00--  https://scc.suse.com/
...
017-03-06 14:42:03 (26.2 KB/s) - ‘index.html’ saved [12468/12468]

Here’s highlights from SUSEConnect

# SUSEConnect -e my@email.address -r <rego code> -u https://scc.suse.com --debug
[B]Executing: 'zypper targetos' Quiet: false
Output: 'sle-12-x86_64'
opening connection to :...
SUSEConnect error: SocketError: getaddrinfo: Name or service not known
[/B]

Using https://updates.suse.com (or http:// variants of the two) had the same result.

Can anyone tell me how to get more diagnostic output from this command, ideally around the “miracle occurs not” bit after opening connection part which is a touch vague! A clue as to the underlying command would help me run it to find out what its reacting to.

Here is the full diag output from SUSEConnect (replaced email/reg with x’s):

# SUSEConnect -e my@email.address -r <rego code>  -u https://scc.suse.com --debug
cmd options: '{:email=>"XXXXX", :token=>"xxxxxxxxxxxxxx", :url=>"https://scc.suse.com", :write_config=>true, :debug=>true, :language=>"en_AU.UTF-8"}'
Merged options: #<SUSE::Connect::Config insecure=false, url="https://scc.suse.com", email="xxxxxxxx", token="xxxxxxxxxxxxx", write_config=true, debug=true, language="en_AU.UTF-8">
Executing: 'uname -i' Quiet: false
Output: 'x86_64'
Executing: 'lscpu' Quiet: false
Output: 'Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                2
On-line CPU(s) list:   0,1
Thread(s) per core:    1
Core(s) per socket:    2
Socket(s):             1
NUMA node(s):          1
Vendor ID:             AuthenticAMD
CPU family:            21
Model:                 48
Model name:            AMD A8-7650K Radeon R7, 10 Compute Cores 4C+6G
Stepping:              1
CPU MHz:               3294.018
BogoMIPS:              6588.03
Hypervisor vendor:     KVM
Virtualization type:   full
L1d cache:             16K
L1i cache:             64K
L2 cache:              2048K
NUMA node0 CPU(s):     0,1
Flags:                 fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm rep_good nopl extd_apicid pni pclmulqdq ssse3 cx16 sse4_1 sse4_2 x2apic popcnt aes xsave avx hypervisor lahf_lm cmp_legacy cr8_legacy abm sse4a misalignsse 3dnowprefetch arat vmmcall'
Executing: 'uname -i' Quiet: false
Output: 'x86_64'
Executing: 'dmidecode -s system-uuid' Quiet: false
Output: 'XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX'
[B]Executing: 'zypper targetos' Quiet: false
Output: 'sle-12-x86_64'
opening connection to :...
SUSEConnect error: SocketError: getaddrinfo: Name or service not known
[/B]/usr/lib64/ruby/2.1.0/net/http.rb:879:in `initialize'
/usr/lib64/ruby/2.1.0/net/http.rb:879:in `open'
/usr/lib64/ruby/2.1.0/net/http.rb:879:in `block in connect'
/usr/lib64/ruby/2.1.0/timeout.rb:76:in `timeout'
/usr/lib64/ruby/2.1.0/net/http.rb:878:in `connect'
/usr/lib64/ruby/2.1.0/net/http.rb:863:in `do_start'
/usr/lib64/ruby/2.1.0/net/http.rb:852:in `start'
/usr/lib64/ruby/2.1.0/net/http.rb:1369:in `request'
/usr/lib64/ruby/gems/2.1.0/gems/suse-connect-0.2.41/lib/suse/connect/connection.rb:60:in `json_request'
/usr/lib64/ruby/gems/2.1.0/gems/suse-connect-0.2.41/lib/suse/connect/connection.rb:42:in `block (2 levels) in <class:Connection>'
/usr/lib64/ruby/gems/2.1.0/gems/suse-connect-0.2.41/lib/suse/connect/api.rb:63:in `announce_system'
/usr/lib64/ruby/gems/2.1.0/gems/suse-connect-0.2.41/lib/suse/connect/client.rb:48:in `announce_system'
/usr/lib64/ruby/gems/2.1.0/gems/suse-connect-0.2.41/lib/suse/connect/client.rb:151:in `announce_or_update'
/usr/lib64/ruby/gems/2.1.0/gems/suse-connect-0.2.41/lib/suse/connect/client.rb:26:in `register!'
/usr/lib64/ruby/gems/2.1.0/gems/suse-connect-0.2.41/lib/suse/connect/cli.rb:47:in `execute!'
/usr/lib64/ruby/gems/2.1.0/gems/suse-connect-0.2.41/bin/SUSEConnect:11:in `<top (required)>'
/usr/sbin/SUSEConnect:23:in `load'
/usr/sbin/SUSEConnect:23:in `<main>'

On 06/03/17 04:24, drax wrote:
[color=blue]

SUSE Linux Enterprise Server 12 SP2 (x86_64) - Lab VM trial for SUMA.

ISSUE #1 - INFO
Sadly there doesn’t seem to be any provision for a proxy during the
initial installation of SLES12. The network config stuff is nice, but
desperately needs a proxy string addition step yesternow. All the great
work you’ve done on the subsequent menus (like selecting SUMA as an add
on) is probably meaningless to anyone working behind a proxy until you
do. :([/color]

At the initial boot screen when installing SUSE Linux you can enter
“proxy=http://USER:PASSWORD@proxy.example.com:PORT” (replacing USER,
PASSWORD, proxy.example.com, and PORT as appropriate) in the Boot
Options field.
[color=blue]

ISSUE #2 - SHOW STOPPER
In either yast or with SUSEConnect attempts to register the server
instance fail with the error:

Code:

getaddrinfo: Name or service not known

DNS Resolution and Proxy access have been configured and wget used to
confirm access is ok:

Code:

wget https://scc.suse.com
–2017-03-06 14:42:00-- https://scc.suse.com/

017-03-06 14:42:03 (26.2 KB/s) - �index.html� saved [12468/12468]


Here’s highlights from SUSEConnect

Code:

SUSEConnect -e my@email.address -r -u https://scc.suse.com --debug

EXECUTING: ‘ZYPPER TARGETOS’ QUIET: FALSE
OUTPUT: ‘SLE-12-X86_64’
OPENING CONNECTION TO :…
SUSECONNECT ERROR: SOCKETERROR: GETADDRINFO: NAME OR SERVICE NOT KNOWN


Using https://updates.suse.com (or http:// variants of the two) had the
same result.

Can anyone tell me how to get more diagnostic output from this command,
ideally around the “miracle occurs not” bit after opening connection
part which is a touch vague! A clue as to the underlying command would
help me run it to find out what its reacting to.

Here is the full diag output from SUSEConnect (replaced email/reg with
x’s):

Code:

SUSEConnect -e my@email.address -r -u https://scc.suse.com --debug

cmd options: ‘{:email=>“XXXXX”, :token=>“xxxxxxxxxxxxxx”, :url=>“https://scc.suse.com”, :write_config=>true, :debug=>true, :language=>“en_AU.UTF-8”}’
Merged options: #<SUSE::Connect::Config insecure=false, url=“https://scc.suse.com”, email=“xxxxxxxx”, token=“xxxxxxxxxxxxx”, write_config=true, debug=true, language=“en_AU.UTF-8”>
Executing: ‘uname -i’ Quiet: false
Output: ‘x86_64’
Executing: ‘lscpu’ Quiet: false
Output: ‘Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 2
On-line CPU(s) list: 0,1
Thread(s) per core: 1
Core(s) per socket: 2
Socket(s): 1
NUMA node(s): 1
Vendor ID: AuthenticAMD
CPU family: 21
Model: 48
Model name: AMD A8-7650K Radeon R7, 10 Compute Cores 4C+6G
Stepping: 1
CPU MHz: 3294.018
BogoMIPS: 6588.03
Hypervisor vendor: KVM
Virtualization type: full
L1d cache: 16K
L1i cache: 64K
L2 cache: 2048K
NUMA node0 CPU(s): 0,1
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm rep_good nopl extd_apicid pni pclmulqdq ssse3 cx16 sse4_1 sse4_2 x2apic popcnt aes xsave avx hypervisor lahf_lm cmp_legacy cr8_legacy abm sse4a misalignsse 3dnowprefetch arat vmmcall’
Executing: ‘uname -i’ Quiet: false
Output: ‘x86_64’
Executing: ‘dmidecode -s system-uuid’ Quiet: false
Output: ‘XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX’
*Executing: ‘zypper targetos’ Quiet: false
Output: ‘sle-12-x86_64’
opening connection to :…
SUSEConnect error: SocketError: getaddrinfo: Name or service not known
*/usr/lib64/ruby/2.1.0/net/http.rb:879:in initialize' /usr/lib64/ruby/2.1.0/net/http.rb:879:in open’
/usr/lib64/ruby/2.1.0/net/http.rb:879:in block in connect' /usr/lib64/ruby/2.1.0/timeout.rb:76:in timeout’
/usr/lib64/ruby/2.1.0/net/http.rb:878:in connect' /usr/lib64/ruby/2.1.0/net/http.rb:863:in do_start’
/usr/lib64/ruby/2.1.0/net/http.rb:852:in start' /usr/lib64/ruby/2.1.0/net/http.rb:1369:in request’
/usr/lib64/ruby/gems/2.1.0/gems/suse-connect-0.2.41/lib/suse/connect/connection.rb:60:in json_request' /usr/lib64/ruby/gems/2.1.0/gems/suse-connect-0.2.41/lib/suse/connect/connection.rb:42:in block (2 levels) in class:Connection
/usr/lib64/ruby/gems/2.1.0/gems/suse-connect-0.2.41/lib/suse/connect/api.rb:63:in announce_system' /usr/lib64/ruby/gems/2.1.0/gems/suse-connect-0.2.41/lib/suse/connect/client.rb:48:in announce_system’
/usr/lib64/ruby/gems/2.1.0/gems/suse-connect-0.2.41/lib/suse/connect/client.rb:151:in announce_or_update' /usr/lib64/ruby/gems/2.1.0/gems/suse-connect-0.2.41/lib/suse/connect/client.rb:26:in register!’
/usr/lib64/ruby/gems/2.1.0/gems/suse-connect-0.2.41/lib/suse/connect/cli.rb:47:in execute!' /usr/lib64/ruby/gems/2.1.0/gems/suse-connect-0.2.41/bin/SUSEConnect:11:in <top (required)>’
/usr/sbin/SUSEConnect:23:in load' /usr/sbin/SUSEConnect:23:in

--------------------[/color]

Does your reference to proxy in issue 1 suggest that you need to access
the internet via a proxy?

Post-install have you configured your server to use a proxy? What does
“set | grep -i proxy” report?

HTH.

Simon
SUSE Knowledge Partner


If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.

[QUOTE=smflood;36895]On 06/03/17 04:24, drax wrote:
[color=blue]

SUSE Linux Enterprise Server 12 SP2 (x86_64) - Lab VM trial for SUMA.

ISSUE #1 - INFO
Sadly there doesn’t seem to be any provision for a proxy during the
initial installation of SLES12. The network config stuff is nice, but
desperately needs a proxy string addition step yesternow. All the great
work you’ve done on the subsequent menus (like selecting SUMA as an add
on) is probably meaningless to anyone working behind a proxy until you
do. :([/color]

At the initial boot screen when installing SUSE Linux you can enter
“proxy=http://USER:PASSWORD@proxy.example.com:PORT” (replacing USER,
PASSWORD, proxy.example.com, and PORT as appropriate) in the Boot
Options field.
[color=blue]

ISSUE #2 - SHOW STOPPER
In either yast or with SUSEConnect attempts to register the server
instance fail with the error:

Code:

getaddrinfo: Name or service not known

DNS Resolution and Proxy access have been configured and wget used to
confirm access is ok:

Code:

wget https://scc.suse.com
–2017-03-06 14:42:00-- https://scc.suse.com/

017-03-06 14:42:03 (26.2 KB/s) - �index.html� saved [12468/12468]


Here’s highlights from SUSEConnect

Code:

SUSEConnect -e my@email.address -r -u https://scc.suse.com --debug

EXECUTING: ‘ZYPPER TARGETOS’ QUIET: FALSE
OUTPUT: ‘SLE-12-X86_64’
OPENING CONNECTION TO :…
SUSECONNECT ERROR: SOCKETERROR: GETADDRINFO: NAME OR SERVICE NOT KNOWN


Using https://updates.suse.com (or http:// variants of the two) had the
same result.

Can anyone tell me how to get more diagnostic output from this command,
ideally around the “miracle occurs not” bit after opening connection
part which is a touch vague! A clue as to the underlying command would
help me run it to find out what its reacting to.

Here is the full diag output from SUSEConnect (replaced email/reg with
x’s):

Code:

SUSEConnect -e my@email.address -r -u https://scc.suse.com --debug

cmd options: ‘{:email=>“XXXXX”, :token=>“xxxxxxxxxxxxxx”, :url=>“https://scc.suse.com”, :write_config=>true, :debug=>true, :language=>“en_AU.UTF-8”}’
Merged options: #<SUSE::Connect::Config insecure=false, url=“https://scc.suse.com”, email=“xxxxxxxx”, token=“xxxxxxxxxxxxx”, write_config=true, debug=true, language=“en_AU.UTF-8”>
Executing: ‘uname -i’ Quiet: false
Output: ‘x86_64’
Executing: ‘lscpu’ Quiet: false
Output: ‘Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 2
On-line CPU(s) list: 0,1
Thread(s) per core: 1
Core(s) per socket: 2
Socket(s): 1
NUMA node(s): 1
Vendor ID: AuthenticAMD
CPU family: 21
Model: 48
Model name: AMD A8-7650K Radeon R7, 10 Compute Cores 4C+6G
Stepping: 1
CPU MHz: 3294.018
BogoMIPS: 6588.03
Hypervisor vendor: KVM
Virtualization type: full
L1d cache: 16K
L1i cache: 64K
L2 cache: 2048K
NUMA node0 CPU(s): 0,1
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm rep_good nopl extd_apicid pni pclmulqdq ssse3 cx16 sse4_1 sse4_2 x2apic popcnt aes xsave avx hypervisor lahf_lm cmp_legacy cr8_legacy abm sse4a misalignsse 3dnowprefetch arat vmmcall’
Executing: ‘uname -i’ Quiet: false
Output: ‘x86_64’
Executing: ‘dmidecode -s system-uuid’ Quiet: false
Output: ‘XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX’
*Executing: ‘zypper targetos’ Quiet: false
Output: ‘sle-12-x86_64’
opening connection to :…
SUSEConnect error: SocketError: getaddrinfo: Name or service not known
*/usr/lib64/ruby/2.1.0/net/http.rb:879:in initialize' /usr/lib64/ruby/2.1.0/net/http.rb:879:in open’
/usr/lib64/ruby/2.1.0/net/http.rb:879:in block in connect' /usr/lib64/ruby/2.1.0/timeout.rb:76:in timeout’
/usr/lib64/ruby/2.1.0/net/http.rb:878:in connect' /usr/lib64/ruby/2.1.0/net/http.rb:863:in do_start’
/usr/lib64/ruby/2.1.0/net/http.rb:852:in start' /usr/lib64/ruby/2.1.0/net/http.rb:1369:in request’
/usr/lib64/ruby/gems/2.1.0/gems/suse-connect-0.2.41/lib/suse/connect/connection.rb:60:in json_request' /usr/lib64/ruby/gems/2.1.0/gems/suse-connect-0.2.41/lib/suse/connect/connection.rb:42:in block (2 levels) in class:Connection
/usr/lib64/ruby/gems/2.1.0/gems/suse-connect-0.2.41/lib/suse/connect/api.rb:63:in announce_system' /usr/lib64/ruby/gems/2.1.0/gems/suse-connect-0.2.41/lib/suse/connect/client.rb:48:in announce_system’
/usr/lib64/ruby/gems/2.1.0/gems/suse-connect-0.2.41/lib/suse/connect/client.rb:151:in announce_or_update' /usr/lib64/ruby/gems/2.1.0/gems/suse-connect-0.2.41/lib/suse/connect/client.rb:26:in register!’
/usr/lib64/ruby/gems/2.1.0/gems/suse-connect-0.2.41/lib/suse/connect/cli.rb:47:in execute!' /usr/lib64/ruby/gems/2.1.0/gems/suse-connect-0.2.41/bin/SUSEConnect:11:in <top (required)>’
/usr/sbin/SUSEConnect:23:in load' /usr/sbin/SUSEConnect:23:in

--------------------[/color]

Does your reference to proxy in issue 1 suggest that you need to access
the internet via a proxy?

Post-install have you configured your server to use a proxy? What does
“set | grep -i proxy” report?

HTH.

Simon
SUSE Knowledge Partner


If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.
------------------------------------------------------------------------[/QUOTE]
Yes, I need to access the Internet via a proxy in this company, hence Issue #1. I’m pretty sure that’s true in the majority of cases. We’re a little behind the times proxy-wise but aren’t alone in that I suspect.

Thanks for the initial boot proxy config tip, I’ll update our doco to reflect it and see how I go with a reinstall. I’m pretty dead in the water without the ability to register post-install (issue #2), I’m hoping for a better result during the install but won’t be too shocked if the same issue pops up!

In answer to your question, here’s the environment with proxy strings:

set | grep -i proxy
NO_PROXY='localhost, 127.0.0.1'
SOCKS_PROXY=
ftp_proxy=
gopher_proxy=
http_proxy=myproxy.mycompany.com:80
https_proxy=myproxy.mycompany.com:80
no_proxy='localhost, 127.0.0.1'
socks_proxy=

I tried adding this line in on bootup, in the Boot Options input line, prior to clicking on Installation

proxy=http://10.0.1.78:3128

After doing the network setup I tried my luck with the *Register System via scc.suse.com" which time dout with the error:

Error
Connection to registration server failed.
Details: Connection timed out - connect(2) for 'scc.suse.com' port 443

I guess I’ve either used the wrong syntax, or its ignoring proxy settings at this point given the port number mentioned. I’ll try the above again and see if https helps at all.

Some slight progress. Changing to use https helped make it further than the above error. I even noticed a “proxy setup screen” flash past this time around, just prior to the license acceptance screen.

proxy=https://10.0.1.78:3128

Sadly it eventually fails during registration with the error:

Cannot access installation media
https://scc.suse.com/access/services/1346?credentials=SUSE_Linux_Enterprise_server_12_SP2_x86_64

I tried just browsing to the above to see how it reacts, it prompted me for login/password details and dropped to an invalid system credentials error when I tried my scc login/password.
The detailed error on that is:

Timeout exceeded when accessing 'https://scc.suse.com/access/services/1346/repo/repoindex.xml?credentials=SUSE_Linux_Enterprise_Server_12_SP2_x86_64'.

I guess something is being negotiated using the “email address” + “Registration Code” I entered that isn’t handshaking very happily with a proxy in the mix?

Hi,

I noticed the following:

http_proxy=myproxy.mycompany.com:80

vs.

proxy=http://10.0.1.78:3128
and
proxy=https://10.0.1.78:3128

Make sure that /etc/sysconfig/proxy has the proper proxy settings (check any working system - that http:// vs. https:// is depending on the configuration of your proxy and has nothing to do with whether you’re accessing http vs https sites) and either re-login or manually set the http_proxy and https_proxy environment variables - double-check via “env|grep -i proxy” before proceeding.

To test that config, use i.e. “curl http://www.suse.com” to retrieve some test web page and if that works, re-try registration. If it doesn’t work, check for a .curlrc file in the home directory of the root user - maybe there are bad proxy settings stored there, too.

Registering post-installation, when you have shell access, should be possible. It looks like all you need is to get the proper proxy URL defined.

Regards,
J

[QUOTE=jmozdzen;36942]Hi,

I noticed the following:

http_proxy=myproxy.mycompany.com:80

vs.

proxy=http://10.0.1.78:3128
and
proxy=https://10.0.1.78:3128

Make sure that /etc/sysconfig/proxy has the proper proxy settings (check any working system - that http:// vs. https:// is depending on the configuration of your proxy and has nothing to do with whether you’re accessing http vs https sites) and either re-login or manually set the http_proxy and https_proxy environment variables - double-check via “env|grep -i proxy” before proceeding.

To test that config, use i.e. “curl http://www.suse.com” to retrieve some test web page and if that works, re-try registration. If it doesn’t work, check for a .curlrc file in the home directory of the root user - maybe there are bad proxy settings stored there, too.

Registering post-installation, when you have shell access, should be possible. It looks like all you need is to get the proper proxy URL defined.

Regards,
J[/QUOTE]

Hi there J, thanks for pitching in here. I don’t see much difference between the previously mentioned wget and these curl responses so far (with regard to http://www.suse.com), but well worth a try if it more closely emulates the behavior from SUSEConnect.

I get no response at all using curl with http://scc.suse.com and a redirection with https://scc.suse.com to https://scc.suse.com/login so definitely some different behaviour there. It’s followed ok by wget and ignored by curl.

I’m wondering if the problem is our proxy site whitelisting. Is there a way to unveil the sites being used by SUSEConnect to see if it’s redirecting off to something not yet tried before? If I can find out the address(es) being used I can confirm they’re ok to get to via my browser/wget/curl.

Other than that, I may be using the wrong combination of credentials/registration code to negotiate eligibility somehow I guess…

Problem
It looks like Ruby based tools like yast and SUSEConnect are a lot more fussy when it comes to the format you use when configuring the proxy. Using wget and/or curl to “vet” your proxy settings are not a good test as they don’t “react” in the same way.

Issue #1 - Configure proxy pre-installation - FIX
After several dozen attempts with different formats, the following string worked for me when defining the proxy pre-installation at the Boot Option Prompt. Leaving off the trailing slash “/” was a show-stopper!

proxy=http://10.0.1.78:80[B]/[/B]

The Initializing step (after accepting the license) takes a few minutes longer for some reason. Once I completed the Network Configuration on the Registration screen, I was able to Register System via scc.suse.com using my email address and the Registration Code provided at the Evaluation download screen. If all is well, you will be prompted to enable repositories during installation, which in turn results in access to the previously elusive SUSE Manager Server 3.0 x86_64 option!

Issue #2 - Configure proxy post-installation - FIX
The syntax for the /etc/sysconfig/proxy file that worked for me is as follows. Neglecting to put an http:// or https:// is a showstopper for yast or SUSEConnect, but was just fine as far as wget or curl is concerned.

grep http /etc/sysconfig/proxy | grep HTTP

HTTP_PROXY="[B]http://[/B]myproxy.onesteel.com:80"
HTTPS_PROXY="[B]https://[/B]myproxy.onesteel.com:80"

This results in the following environment setup

env | grep http

http_proxy=[B]http://[/B]myproxy.onesteel.com:80
https_proxy=[B]https://[/B]myproxy.onesteel.com:80

Wishlist
A tweak to check the format of the proxy would be very welcome in yast or SUSEConnect. Improving the error messge from “SUSEConnect error: SocketError: getaddrinfo: Name or service not known” with a hint about the proxy format would be very welcome!

Thanks again to jmozdzen & smflood for providing some vital clues!

[QUOTE=drax;36951]Problem
It looks like Ruby based tools like yast and SUSEConnect are a lot more fussy when it comes to the format you use when configuring the proxy. Using wget and/or curl to “vet” your proxy settings are not a good test as they don’t “react” in the same way.

Issue #1 - Configure proxy pre-installation - FIX
After several dozen attempts with different formats, the following string worked for me when defining the proxy pre-installation at the Boot Option Prompt. Leaving off the trailing slash “/” was a show-stopper!

proxy=http://10.0.1.78:80[B]/[/B]

The Initializing step (after accepting the license) takes a few minutes longer for some reason. Once I completed the Network Configuration on the Registration screen, I was able to Register System via scc.suse.com using my email address and the Registration Code provided at the Evaluation download screen. If all is well, you will be prompted to enable repositories during installation, which in turn results in access to the previously elusive SUSE Manager Server 3.0 x86_64 option!

Issue #2 - Configure proxy post-installation - FIX
The syntax for the /etc/sysconfig/proxy file that worked for me is as follows. Neglecting to put an http:// or https:// is a showstopper for yast or SUSEConnect, but was just fine as far as wget or curl is concerned.

grep http /etc/sysconfig/proxy | grep HTTP

HTTP_PROXY="[B]http://[/B]myproxy.onesteel.com:80"
HTTPS_PROXY="[B]https://[/B]myproxy.onesteel.com:80"

This results in the following environment setup

env | grep http

http_proxy=[B]http://[/B]myproxy.onesteel.com:80
https_proxy=[B]https://[/B]myproxy.onesteel.com:80

Wishlist
A tweak to check the format of the proxy would be very welcome in yast or SUSEConnect. Improving the error messge from “SUSEConnect error: SocketError: getaddrinfo: Name or service not known” with a hint about the proxy format would be very welcome!

Thanks again to jmozdzen & smflood for providing some vital clues![/QUOTE]

There is also a wiki with useful information about SUMA: https://wiki.microfocus.com/index.php/SUSE_Manager/Proxy_to_internet

Thomas