Skip to Main Content

Core Infrastructure

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

leapp upgrade from OL7 to OL8 fails

ewesselSep 23 2024

Trying to upgrade several of our cloud instances from OL7 to OL8 using leapp, and I had mitigated the issues brought up when running leapp preupgrade --oci. After rerunning the preupgrade after the mitigation, getting the following errors and inhibitors

Risk Factor: high (error)
Title: Could not check for valid GPG keys
Summary: {"details": "No UsedTargetRepositories facts"}
Key: f61bcffa152743596cc0b18172fd42f05f042c02
----------------------------------------
Risk Factor: high (inhibitor)
Title: There are no enabled target repositories
Summary: This can happen when no custom repositories have been passed on the com
mand line.
Related links:

  • Preparing for the upgrade: https://docs.oracle.com/en/operating-systems/or
    acle-linux/8/leapp
    Remediation: [hint] Check that the --enablerepo option for leapp is set if the
    repositories are defined in any repofiles under the /etc/yum.repos.d/ directory.
    For more information on custom repository files, see the documentation. Finally
    , verify that the "/etc/leapp/files/repomap.json" file is up-to-date.
    Key: 8a43a658c16c3712bb325e5a26f22395ba360542

There were no changes to the repo files after the first preupgrade run, though I did have to remove all the osms-backup filename extensions on many of the repos. I'm not sure where it could be pulling the gpg keys from, and why it's can't get them. Any assistance would be appreciated.

Comments

Post Details

Added on Sep 23 2024
1 comment
677 views