Cannot upgrade SLES 12 SP2 to SP3 or higher

0

We have 6 on-demand EC2 instances on a public VPC, with SLES 12 SP2 running a SAP workload that we need to upgrade to SP3, then SP4.

This is the procedure we are following:
1.) zypper up
2.) cd /etc/zypp/repos.d
3.) for i in SP2; do newname=${i/SP2/SP3}; cp $i $newname; done
4.) sed -i s/SP2/SP3/ SP3.repo
5.) sed -i s/enabled=0/enabled=1/ SP3.repo
6.) zypper refresh
7.) zypper in zypper
8.) zypper dup

The issue we encounter at step 6 is this:
Permission to access 'https://smt-ec2.susecloud.net/repo/SUSE/Products/SLE-SERVER/12-SP3/x86_64/product_debug/repodata/repomd.xml?credentials=SMT-http_smt-ec2_susecloud_net' denied.

Does any one know the proper credentials to access smt-ec2.susecloud.net? Or any solution to the issue?

Does any one has a proved, documented step by step procedure to share?

Thanks!

preguntada hace 5 años1015 visualizaciones
4 Respuestas
0

I found 2 entries "Added by SMT registration" on /etc/hosts. I commented out one and now I can connect to smt-ec2.susecloud.net.

However, when prompted for credentials, I provide the user and password found in /etc/zypp/credentials.d but those don't authenticate.

I tried running registercloudguest --force new, with the following result:

/usr/lib/python2.7/site-packages/requests/packages/urllib3/connection.py:264: SubjectAltNameWarning: Certificate for 54.244.244.107 has no subjectAltName, falling back to check for a commonName for now. This feature is being removed by major browsers and deprecated by RFC 2818. (See https://github.com/shazow/urllib3/issues/497 for details.)
SubjectAltNameWarning

I found an old post from February 13, 2017 in which rjschwei explains that the issue was because of memory shortage on the registration servers.

Would someone at AWS take a look into this? Apparently the same issue is happening now.

Thanks

respondido hace 5 años
0

I believe this issue is resolved. Will you please try running the registration again?

respondido hace 5 años
0

I think the registercloudguest issue is solved.

I still see a message:

nwdev:/home/admin # registercloudguest --force-new
/usr/lib/python2.7/site-packages/requests/packages/urllib3/connection.py:264: SubjectAltNameWarning: Certificate for 54.253.118.149 has no subjectAltName, falling back to check for a commonName for now. This feature is being removed by major browsers and deprecated by RFC 2818. (See https://github.com/shazow/urllib3/issues/497 for details.)
SubjectAltNameWarning

But new credentials are available:
nwdev:/home/admin # ls -l /etc/zypp/credentials.d
total 36
-rw------- 1 root root 72 Sep 3 22:58 Advanced_Systems_Management_Module_x86_64
-rw------- 1 root root 72 Sep 3 22:58 Containers_Module_x86_64
-rw------- 1 root root 72 Sep 3 22:58 Legacy_Module_x86_64
-rw------- 1 root root 72 Sep 3 22:58 Public_Cloud_Module_x86_64
-rw------- 1 root root 72 Sep 3 22:58 SCCcredentials
-rw------- 1 root root 72 Sep 3 22:58 SUSE_Linux_Enterprise_Server_x86_64
-rw------- 1 root root 72 Sep 3 22:58 SUSE_Linux_Enterprise_Software_Development_Kit_x86_64
-rw------- 1 root root 72 Sep 3 22:58 Toolchain_Module_x86_64
-rw------- 1 root root 72 Sep 3 22:58 Web_and_Scripting_Module_x86_64

I will run the Service Packs update a bit later and if successful, document my findings and tag this thread as Answered.

Thank you very much for the registercloudguest fix!!

Edited by: aluminicaste on Sep 3, 2019 9:09 PM

respondido hace 5 años
0

With the proper SMT registration entry in /etc/hosts and with the command registercloudguest fixed, the upgrade worked perfectly. Also, I found a simpler procedure for SUSE 12, very well documented here:
https://kerneltalks.com/linux/how-to-upgrade-suse-12-sp1-to-sp3-or-sp4/

Briefly:
0.) registercloudguest --force-new
1.) zypper in zypper-migration-plugin
2.) zypper patch
3.) zypper migration
4.) reboot
5.) cat /etc/os-release

Thanks!!!

respondido hace 5 años

No has iniciado sesión. Iniciar sesión para publicar una respuesta.

Una buena respuesta responde claramente a la pregunta, proporciona comentarios constructivos y fomenta el crecimiento profesional en la persona que hace la pregunta.

Pautas para responder preguntas