SUSE Enterprise License after migration from AWS

[Alexandre Brito]

Hi there,

I just migrated an EC2 instance running in AWS to GCP via Migrate to Compute Engine successfully. The new compute engine is booting up, I can ssh to it and all data has been cloned as expected. However, the SUSE license is not valid since it is a clone from the AWS one. 

How can I migrate the SUSE Enterprise License so that zypper update is able to work? 

I've also created a new  SUSE  Enterprise compute engine in GCP to check the zypper configurations . I've noticed the /etc/hosts has an entry for smt-gce.sysecloud.net. I've copy paste this entry to the migrated compute engine (and deleted the 'cloned' one) but it didn't work

These are the commands I'm running to try Suse to register:

SUSEConnect –status 

SUSEConnect –cleanup 

registercloudguest --force-new

zypper ref
(attach the error after running this last command. All others don't give errors)

Any help would be much appreciated :-)

Kind regards,
Alex

---

This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. Your privacy is important to us. Accenture uses your personal data only in compliance with data protection laws. For further information on how Accenture processes your personal data, please see our privacy statement at https://www.accenture.com/us-en/privacy-policy.
______________________________________________________________________________________

www.accenture.com

[Fady (Google Cloud Platform)]

Generally, if you want to bring your own physical core license to the cloud, you need to reserve dedicated hardware (called Sole-tenant nodes), and the discussion here is about  premium OS licenses (not free operating systems). Now migrating from a cloud service to another is a bit different as usually Cloud Providers utilizes a concept called "Pay As You Go". Meaning you get billed per usage.  I found this document that explains License differences that should help. 

In your case, most probably you meant you want to bring your own subscription (BYOS) and not your own OS license (BYOL). This is also possible if you are using a BYOS image license type. This is usually done when migrating through waves as you would have to specify the license type string. Here is a good SUSE article that also explains subscriptions. 

One way to verify the license is by describing the boot disk using this command in cloudshell. Example (replace instance name and zone): 

gcloud compute disks describe instanceName --zone us-central1-a | grep licenses

If the BYOS license is not applied, you may try posting on serverfault.com for technical help applying it. However, you may try to use this method making an existing image bootable and forcing the license, as your image is already imported.  I hope this helps.