Transactional update failed. k3s-selinux-1.2-2.sle.noarch (Rancher K3s Common (stable)): Signature verification failed

[eremeye]

Automatic transactional update fails every time. Here is the log. I would appreciate any suggestions on how to resolve this.

Retrieving: k3s-selinux-1.2-2.sle.noarch (Rancher K3s Common (stable)) (1/37),  20.5 KiB    
Retrieving: k3s-selinux-1.2-2.sle.noarch.rpm [....done (15.3 KiB/s)]
k3s-selinux-1.2-2.sle.noarch.rpm:
    Header V3 RSA/SHA256 Signature, key ID 925ea29ae257814a: NOKEY
    V3 RSA/SHA256 Signature, key ID 925ea29ae257814a: NOKEY

warning: /var/tmp/AP_0xeOBngm/k3s-selinux-1.2-2.sle.noarch.rpm: Header V3 RSA/SHA256 Signature, key ID e257814a: NOKEY
Looking for gpg key ID E257814A in cache /var/cache/zypp/pubkeys.

New repository or package signing key received:

  Repository:       Rancher K3s Common (stable)
  Key Fingerprint:  C8CF F216 4551 26E9 B9C9 18BE 925E A29A E257 814A
  Key Name:         Rancher (CI) <[email protected]>
  Key Algorithm:    RSA 3072
  Key Created:      Tue Mar 10 22:43:06 2020
  Key Expires:      (does not expire)
  Subkey:           AA7E9EC8FE21FDCF 2020-03-10 [does not expire]
  Rpm Name:         gpg-pubkey-e257814a-5e6817fa

Do you want to reject the key, or trust always? [r/a/?] (r): r
k3s-selinux-1.2-2.sle.noarch (Rancher K3s Common (stable)): Signature verification failed [4-Signatures public key is not available]
Abort, retry, ignore? [a/r/i] (a): a
Problem occurred during or after installation or removal of packages:
Installation has been aborted as directed.
Please see the above error message for a hint.
2023-03-04 00:21:41 Application returned with exit status 8.
2023-03-04 00:21 ERROR: zypper --no-cd dup on /.snapshots/4/snapshot failed with exit code 8!
ERROR: zypper --no-cd dup on /.snapshots/4/snapshot failed with exit code 8!
2023-03-04 00:21 Use '--interactive' for manual problem resolution.
Use '--interactive' for manual problem resolution.
2023-03-04 00:21 Removing snapshot #4...
Removing snapshot #4...

[mysticaltech]

@eremeye This has been fixed almost the same day, too bad I missed this discussion. Please upgrade with terraform init -upgrade and try again.