Skip to Main Content

Infrastructure Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Please ask technical questions in the appropriate category. Thank you!

Update notice ELBA-2022-0617 (from ol7_latest) is broken

User_94NPKOct 12 2022

We are preparing to update several Oracle Linux VM's in Oracle Cloud for a customer and getting the following with yum check-update

Update notice ELBA-2022-0617 (from ol7_latest) is broken, or a bad duplicate, skipping.
You should report this problem to the owner of the ol7_latest repository.
To help pinpoint the issue, please attach the output of "yum updateinfo --verbose" to the report.
Update notice ELBA-2021-4775 (from ol7_latest) is broken, or a bad duplicate, skipping.

Output of updateinfo:

# yum updateinfo -v
Not loading "rhnplugin" plugin, as it is disabled
Loading "ulninfo" plugin
Config time: 0.028
Yum version: 3.4.3
rpmdb time: 0.000
Setting up Package Sacks
pkgsack time: 0.022
Duplicate of ELBA-2022-0617 differs in some fields:
<<<<<<< ol7_latest:issued
'2022-02-23'
=======
'2022-02-23 00:00:00'
>>>>>>> ol7_UEKR5:issued
Update notice ELBA-2022-0617 (from ol7_latest) is broken, or a bad duplicate, skipping.
You should report this problem to the owner of the ol7_latest repository.
To help pinpoint the issue, please attach the output of "yum updateinfo --verbose" to the report.
Duplicate of ELBA-2021-4775 differs in some fields:
<<<<<<< ol7_latest:issued
'2021-11-24'
=======
'2021-11-24 00:00:00'
>>>>>>> ol7_UEKR5:issued
Update notice ELBA-2021-4775 (from ol7_latest) is broken, or a bad duplicate, skipping.
updateinfo time: 2.097
Building updates object
up:Obs Init time: 0.526
up:simple updates time: 0.018
up:obs time: 0.003
up:condense time: 0.000
updates time: 1.004
Duplicate of ELBA-2022-9357 differs in some fields:
<<<<<<< ol7_UEKR5:update_id
'ELBA-2022-9357'
=======
'ELBA-2022-9347'
>>>>>>> ol7_UEKR5:update_id
Updates Information Summary: updates
  45 Security notice(s)
     2 Critical Security notice(s)
    41 Important Security notice(s)
     2 Moderate Security notice(s)
  41 Bugfix notice(s)
updateinfo summary done

It appears similar to the one occurred earlier this year. Any chance of getting this fixed?
We may be able to do a work around using --disablerepo="repo id", just not sure how it would affect overall system after update.
Any assistance would be gratefully received. Thank you.

Comments
Post Details
Added on Oct 12 2022
7 comments
1,009 views