PDA

View Full Version : SLES 12.1 repository problems after Azure meltdown upgrade?



delampri
08-Jan-2018, 10:16
Hi ,

Zypper suddenly stop to work on Azure,

registercloudguest --force-new does now help and the log file return this errors (cross all machines on the site)

2018-01-08 09:03:12,636 INFO:Writing SMT rootCA: /usr/share/pki/trust/anchors
2018-01-08 09:03:12,638 INFO:Starting new HTTP connection (1): 23.101.150.193
2018-01-08 09:03:12,647 INFO:Updating CA certificates: update-ca-certificates
2018-01-08 09:03:16,140 ERROR:Registration with 23.101.150.193 failed. Trying 23.101.151.152
2018-01-08 09:03:16,141 INFO:Removing credentials: SCCcredentials
2018-01-08 09:03:16,141 INFO:Modified /etc/hosts, added: 23.101.151.152 smt-azure.susecloud.net smt-azure

2018-01-08 09:03:18,936 ERROR:Baseproduct registration failed
2018-01-08 09:03:18,936 ERROR: Error: SCC returned 'No valid product found' (422)

Any idea anyone?

Thanks
David.

aparadis
08-Jan-2018, 15:21
Hi ,

Zypper suddenly stop to work on Azure,

registercloudguest --force-new does now help and the log file return this errors (cross all machines on the site)

2018-01-08 09:03:12,636 INFO:Writing SMT rootCA: /usr/share/pki/trust/anchors
2018-01-08 09:03:12,638 INFO:Starting new HTTP connection (1): 23.101.150.193
2018-01-08 09:03:12,647 INFO:Updating CA certificates: update-ca-certificates
2018-01-08 09:03:16,140 ERROR:Registration with 23.101.150.193 failed. Trying 23.101.151.152
2018-01-08 09:03:16,141 INFO:Removing credentials: SCCcredentials
2018-01-08 09:03:16,141 INFO:Modified /etc/hosts, added: 23.101.151.152 smt-azure.susecloud.net smt-azure

2018-01-08 09:03:18,936 ERROR:Baseproduct registration failed
2018-01-08 09:03:18,936 ERROR: Error: SCC returned 'No valid product found' (422)

Any idea anyone?

Thanks
David.

Getting the same on AWS (EC2):

Merged options: #<SUSE::Connect::Config insecure=false, url="https://smt-ec2.susecloud.net", debug=true, language="POSIX">
opening connection to smt-ec2.susecloud.net:443...
opened
starting SSL for smt-ec2.susecloud.net:443...
SSL established
<- "GET /connect/repositories/installer HTTP/1.1\r\nAccept-Encoding: identity\r\nAccept: application/json,application/vnd.scc.suse.com.v4+json\r\nUser-Agent: SUSEConnect/0.3.0\r\nContent-Type: application/json\r\nAccept-Language: POSIX\r\nConnection: close\r\nHost: smt-ec2.susecloud.net\r\n\r\n"
-> "HTTP/1.1 422 Unprocessable Entity\r\n"
-> "Date: Mon, 08 Jan 2018 14:16:14 GMT\r\n"
-> "Server: Apache\r\n"
-> "scc-api-version: v4\r\n"
-> "Connection: close\r\n"
-> "Transfer-Encoding: chunked\r\n"
-> "Content-Type: application/json\r\n"
-> "\r\n"
-> "65\r\n"
reading 101 bytes...
-> "{\"error\":\"No product specified\",\"localized_error\":\"No product specified\",\"type\":\"error\",\"status\":422}"
read 101 bytes
reading 2 bytes...
-> ""
-> "\r\n"
read 2 bytes
-> "0\r\n"
-> "\r\n"
Conn close
Error: SCC returned 'No valid product found' (422)

rjschwei
08-Jan-2018, 15:29
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.

aparadis
08-Jan-2018, 20:50
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.

Doesn't seem fixed yet.

Trying to force the registration yields the same error:

2018-01-08 19:49:06,151 INFO:Using API: regionInfo
2018-01-08 19:49:06,151 INFO:Using region server: 50.17.208.31
2018-01-08 19:49:06,151 INFO:No cert found: /var/lib/regionService/certs/50.17.208.31.pem skip this server
2018-01-08 19:49:06,151 INFO:Using region server: 54.244.244.107
2018-01-08 19:49:06,154 INFO:Starting new HTTPS connection (1): 54.244.244.107
2018-01-08 19:49:06,720 INFO:Starting new HTTP connection (1): 54.246.90.215
2018-01-08 19:49:06,729 INFO:Modified /etc/hosts, added: 54.246.90.215 smt-ec2.susecloud.net smt-ec2

2018-01-08 19:49:06,921 INFO:[Service] No SMT server found, nothing to do
2018-01-08 19:49:07,054 INFO:Writing SMT rootCA: /usr/share/pki/trust/anchors
2018-01-08 19:49:07,057 INFO:Starting new HTTP connection (1): 54.246.90.215
2018-01-08 19:49:07,060 INFO:Updating CA certificates: update-ca-certificates
2018-01-08 19:49:08,516 ERROR:Registration with 54.246.90.215 failed. Trying 54.75.232.245
2018-01-08 19:49:08,516 INFO:Clean current registration server: 54.246.90.215
2018-01-08 19:49:08,517 INFO:Removing credentials: SCCcredentials
2018-01-08 19:49:08,517 INFO:Modified /etc/hosts, added: 54.75.232.245 smt-ec2.susecloud.net smt-ec2

2018-01-08 19:49:09,650 ERROR:Baseproduct registration failed
2018-01-08 19:49:09,651 ERROR: Error: SCC returned 'No valid product found' (422)

bear454
09-Jan-2018, 03:12
There was an issue with our SMT servers that coincided with the Meltdown updates. We've performed a resync with SCC on all of our update servers; should resolve the issue.

aparadis
10-Jan-2018, 03:45
There was an issue with our SMT servers that coincided with the Meltdown updates. We've performed a resync with SCC on all of our update servers; should resolve the issue.

I can confirm (for AWS/EC2) that it's up and running now, thanks for the help!