[suse-sles-e] Registering SLES 12 against SMT

[Werner Flamme]

Hi everyone,

SUSE support seems to be on holidays, so I ask here. Maybe I'm not the
only one subscribed to this list :)

Yesterday, I installed a new SLES (for SAP) 12. I try to register it
against my SMT server, but all I get is something like (taken from the
output of '/usr/bin/SUSEConnect -r "mytoken" --debug'


===snip===
opening connection to sapdisk.intranet.ufz.de:443...
opened
starting SSL for sapdisk.intranet.ufz.de:443...
SSL established
<- "POST /connect/subscriptions/systems HTTP/1.1\r\nAccept-Encoding:
identity\r\nAccept:
application/json,application/vnd.scc.suse.com.v4+json\r\nUser-Agent:
SUSEConnect/0.2.14\r\nAuthorization: Token
token=mytoken\r\nContent-Type: application/json\r\nAccept-Language:
de_DE.UTF-8\r\nConnection: close\r\nHost:
sapdisk.intranet.ufz.de\r\nContent-Length: 187\r\n\r\n"
<-
"{\"hostname\":\"vsapptd\",\"hwinfo\":{\"hostname\":\"vsapptd\",\"cpus\":4,\"sockets\":2,\"hypervisor\":null,\"arch\":\"x86_64\",\"uuid\":\"42343CF3-78CF-3F20-E34B-740076A47E93\"},\"distro_target\":\"sle-12-x86_64\"}"
Conn close because of error end of file reached
Conn close because of error end of file reached
SUSEConnect error: EOFError: end of file reached
/usr/lib64/ruby/2.1.0/openssl/buffering.rb:182:in `sysread_nonblock'
/usr/lib64/ruby/2.1.0/openssl/buffering.rb:182:in `read_nonblock'
/usr/lib64/ruby/2.1.0/net/protocol.rb:153:in `rbuf_fill'
/usr/lib64/ruby/2.1.0/net/protocol.rb:134:in `readuntil'
/usr/lib64/ruby/2.1.0/net/protocol.rb:144:in `readline'
/usr/lib64/ruby/2.1.0/net/http/response.rb:39:in `read_status_line'
/usr/lib64/ruby/2.1.0/net/http/response.rb:28:in `read_new'
/usr/lib64/ruby/2.1.0/net/http.rb:1408:in `block in transport_request'
/usr/lib64/ruby/2.1.0/net/http.rb:1405:in `catch'
/usr/lib64/ruby/2.1.0/net/http.rb:1405:in `transport_request'
/usr/lib64/ruby/2.1.0/net/http.rb:1378:in `request'
/usr/lib64/ruby/2.1.0/net/http.rb:1371:in `block in request'
/usr/lib64/ruby/2.1.0/net/http.rb:853: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.14/lib/suse/connect/connection.rb:60:in
`json_request'
/usr/lib64/ruby/gems/2.1.0/gems/suse-connect-0.2.14/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.14/lib/suse/connect/api.rb:44:in
`announce_system'
/usr/lib64/ruby/gems/2.1.0/gems/suse-connect-0.2.14/lib/suse/connect/client.rb:56:in
`announce_system'
/usr/lib64/ruby/gems/2.1.0/gems/suse-connect-0.2.14/lib/suse/connect/client.rb:123:in
`announce_or_update'
/usr/lib64/ruby/gems/2.1.0/gems/suse-connect-0.2.14/lib/suse/connect/client.rb:38:in
`register!'
/usr/lib64/ruby/gems/2.1.0/gems/suse-connect-0.2.14/lib/suse/connect/cli.rb:42:in
`execute!'
/usr/lib64/ruby/gems/2.1.0/gems/suse-connect-0.2.14/bin/SUSEConnect:10:in `<top
(required)>'
/usr/bin/SUSEConnect:23:in `load'
/usr/bin/SUSEConnect:23:in `<main>'
===pins===

"mytoken" is the replacement for my registration ID in this mail only :)

I succeed when registering against scc.suse.com directly, so I guess it
is a problem in the SMT code, maybe related to SLES 12. BTW, yesterday
the failure contained a HTTP/404 because the authentication didn't work.

What might be the solution for registering against my SMT host (running
smt-2.0.12-0.7.1)? On the SMT host, nothing is logged in /var/log/smt,
but the apache error_log says

===snip===
[Tue Jul 21 07:50:16 2015] [error] [client 141.65.125.85] Invalid user:
SCC_e9cf14705e2d4a3ca5da548f54979227
[Tue Jul 21 07:50:16 2015] [error] [client 141.65.125.85] no acceptable
variant: /usr/share/apache2/error/HTTP_UNAUTHORIZED.html.var
[Tue Jul 21 07:51:19 2015] [error] [client 141.65.125.85] Insecure
$ENV{PATH} while running with -T switch at
/usr/lib/perl5/vendor_perl/5.10.0/SMT/Rest/SCCAPIv1.pm line 557.\n
Assertion ((buffer)->sv_flags & 0x00000400) failed: file "sv.c", line 1741.
===pins===

What might be the unsecure part in $ENV{PATH}?

Regards,
Werner

--

[Werner Flamme]

Post by Werner Flamme
Hi everyone,
SUSE support seems to be on holidays, so I ask here. Maybe I'm not the
only one subscribed to this list :)

I think I am.

FTR: it was a bug that was fixed with the next patch of the smt package.

Werner

--

[Marcus Meissner]

Post by Werner Flamme

Post by Werner Flamme
Hi everyone,
SUSE support seems to be on holidays, so I ask here. Maybe I'm not the
only one subscribed to this list :)

I think I am.
FTR: it was a bug that was fixed with the next patch of the smt package.

I am not sure a lot of people are reading here, but as you noted,
the SUSE support is the right contact point.

(I did not know;)

Ciao, Marcus

[Werner Flamme]

I think there are some, who read ;)
I set up current smt version with SLES11 SP3 Server, and were able to
Mirror SMT for SLES12.

I have (and had) no problems to mirror SLES 12. SLES for SAP seems to
entitle me to mirror a bazillion SLE 12 repos :)

The problem was the registration of my new SLES 12 system against my SMT
host.

During the support case, I got a PTF that will be released as a new SMT
patch soon (smt-2.0.12-0.7.13.9010.0.PTF.939076). I hope :)

I had another SLES 12 host registered against my SMT before, so I was
not sure where to search the problem. It was either a patch of smt on
the SMT server or SUSEConnect on the client.

Regards,
Werner

--