(I got this via: https://github.com/kata-containers/ci/issues/253)

Addtionally to the standard repos, the openSUSE Leap images for public clouds
(Azure and GCE), have the "openSUSE-Leap-devel-languages-python-aws" and
"openSUSE-Leap-Cloud-Tools" repositories enabled. However when first calling
zypper the use is asked to import the keys for those repos. E.g. on a freshly
launched instance:

-----------------------
opensuse-leap-15-1:~ # zypper ref
Retrieving repository 'openSUSE-Leap-15.1-Non-Oss' metadata
.......................................................................................[done]
[..]
Retrieving repository 'openSUSE-Leap-devel-languages-python-aws' metadata
----------------------------------------------------------------------------[|]

New repository or package signing key received:

  Repository:       openSUSE-Leap-devel-languages-python-aws                    
  Key Name:         devel:languages:python OBS Project
<devel:languages:python@build.opensuse.org>
  Key Fingerprint:  172CCD6B 0CF49B73 88F1C611 27163A4E EDF0D733                
  Key Created:      Wed Apr 10 17:54:44 2019                                    
  Key Expires:      Fri Jun 18 17:54:44 2021                                    
  Rpm Name:         gpg-pubkey-edf0d733-5cae2de4                                


Do you want to reject the key, trust temporarily, or trust always? [r/t/a/?]
(r): a
-----------------------

It seems the Leap images in AWS have all those keys already imported.