Cloud instance repos fail due to outdated packages

To update packages to a supported level, follow these steps:

• Create a PAYG instance with the same OS as instance with broken repos
• login as root
• Create a temporary directory:

mkdir -p /root/packages/rpms

For Google run:

zypper --pkg-cache-dir /root/packages/ download cloud-regionsrv-client cloud-regionsrv-client-plugin-gce regionServiceClientConfigGCE python3-gcemetadata suseconnect-ng python3-cssselect python3-toml python3-lxml python3-M2Crypto python3-zypp-plugin python3-dnspython libsuseconnect suseconnect-ruby-bindings docker docker-bash-completion runc containerd libcontainers-common bash-completion

For AWS:

zypper --pkg-cache-dir /root/packages/ download cloud-regionsrv-client cloud-regionsrv-client-plugin-ec2 regionServiceClientConfigEC2 python3-ec2metadata suseconnect-ng python3-cssselect python3-toml python3-lxml python3-M2Crypto python3-zypp-plugin python3-dnspython libsuseconnect suseconnect-ruby-bindings docker docker-bash-completion runc containerd libcontainers-common bash-completion

For Azure:

SLES 12

zypper --pkg-cache-dir /root/packages/ download cloud-regionsrv-client cloud-regionsrv-client-plugin-azure regionServiceClientConfigAzure python3-azuremetadata python3-cssselect python3-lxml python3-M2Crypto python3-zypp-plugin python3-dnspython suseconnect-ruby-bindings suseconnect-ng

SLES 15

zypper --pkg-cache-dir /root/packages/ download cloud-regionsrv-client cloud-regionsrv-client-plugin-azure regionServiceClientConfigAzure python3-azuremetadata suseconnect-ng python3-cssselect python3-toml python3-lxml python3-M2Crypto python3-zypp-plugin python3-dnspython libsuseconnect suseconnect-ruby-bindings docker docker-bash-completion runc containerd libcontainers-common bash-completion

Then run:

find /root/packages/ -type f -name "*.rpm" -exec cp {} /root/packages/rpms/ \;
cd /root/packages
tar -czvf suse-public-registration.tgz rpms

• Transfer suse-public-registration.tgz to the broken instance

tar xvfz suse-public-registration.tgz
cd rpms
zypper --no-refresh --no-remote --non-interactive install --force *.rpm
registercloudguest --force-new

Zypper may fail running in --non-interactive mode due to additional dependencies requesting to select a solution. If this occurs, run the following and select a solution:

zypper --no-refresh --no-remote install --force *.rpm
registercloudguest --force-new

or as a last resort, run:

rpm -Uvh *.rpm --force
registercloudguest --force-new