Cloud wide (AWS, Azure, etc) SMT outage?

SUSE Public Cloud Amazon-EC2
1

Hi,

Seems like there is an issue with SMT, using SLES12 SP1:

starting SSL for smt-ec2.susecloud.net:443…
SSL established
← "GET /connect/repositories/installer HTTP/1.1\r
Accept-Encoding: identity\r
Accept: application/json,application/vnd.scc.suse.com.v4+json\r
User-Agent: SUSEConnect/0.3.0\r
Content-Type: application/json\r
Accept-Language: POSIX\r
Connection: close\r
Host: smt-ec2.susecloud.net\r
\r
"
→ "HTTP/1.1 422 Unprocessable Entity\r
"
→ "Date: Mon, 08 Jan 2018 14:16:14 GMT\r
"
→ "Server: Apache\r
"
→ "scc-api-version: v4\r
"
→ "Connection: close\r
"
→ "Transfer-Encoding: chunked\r
"
→ "Content-Type: application/json\r
"
→ "\r
"
→ "65\r
"
reading 101 bytes…
→ “{“error”:“No product specified”,“localized_error”:“No product specified”,“type”:“error”,“status”:422}”
read 101 bytes
reading 2 bytes…
→ “”
→ "\r
"
read 2 bytes
→ "0\r
"
→ "\r
"
Conn close
Error: SCC returned ‘No valid product found’ (422)

Another user on the Azure forum reported the same problem: https://forums.suse.com/showthread.php?10382-SLES-12-1-repository-problems-after-Azure-meltdown-upgrade

Seems SUSE already responded in the other thread, just posting so that other EC2 users see it

2

Hi,

We have tried our best to keep everything working while ate the same time patching the systems. The task has been complicated as we have to handle the roll out of fixes for Meltdown and Spectre at the Cloud Framework level, meaning our servers may have been stopped forcefully and at a very inopportune time for us.We expect that everything is operational at this point Monday, January 9, 9:30 A.M. EST.

As a note, in your first post you are talking about access to SLES 12 SP1 repositories. Note that 12 SP1 does no longer receive updates and you should migrate your system to SLES 12 SP3, which is the most recent version of SUSE Linux Enterprise Server.