We have a conversion experience test failure where GPG key is not the same before and after the conversion.

The test steps are:

1. Register the system to the insights
2. Create a custom /etc/yum.repos.d/convert2rhel.repo and modify the /etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release (saving the original).
3. Check that the host is visible as CentOS in the UI
4. Run pre-conversion analysis task.
5. Verify that the analysis did not find any issues.
6. Check that the /etc/yum.repos.d/convert2rhel.repo is the same as before running the task, the modified one.
7. Check that the GPG key is the same as before running the task, the modified one.
8. Run conversion task and observe the same behavior.
9. Check that convert2rhel.repo and GPG key files got replaced.

The test is failing in the 9th step when checking the key block. We check that the after-conversion key block should be the same as the key block we saved at the step 2. I attach both files. RPM-GPG-KEY-redhat-release.original is the original GPG key before any task and RPM-GPG-KEY-redhat-release.after  is the file after the conversion. The GPG checksums are different.