DCS-10206:Patch Bundle Conflicts With: Running Yum Update Failed
(Doc ID 2983003.1)
Last updated on MAY 02, 2024
Applies to:
Oracle Cloud Infrastructure - Database Service - Version N/A to N/A [Release 1.0]Information in this document applies to any platform.
Symptoms
OS patching pre-check failed.
Job details
----------------------------------------------------------------
ID: abccbdd9-219d-4020-b8ce-bb0a9eb80efd
Description: OS Patching Prechecks
Status: Failure
Created: October 20, 2023 6:16:36 AM CEST
Progress: 84%
Message: DCS-10206:Patch bundle conflicts with: Running yum update failed
Error Code: DCS-10206
Cause: Conflict check failed.
Action: Rollback the conflicting patches and retry the operation.
DCS log shows:
.....
Resolving Dependencies
--> Running transaction check
---> Package jre-1.8-headful.x86_64 0:1.8.0_381-9.el7 will be updated
---> Package jre-1.8-headful.x86_64 0:1.8.0_391-13.el7 will be an update
---> Package kernel.x86_64 0:3.10.0-1160.102.1.0.1.el7 will be installed
---> Package kernel-headers.x86_64 0:3.10.0-1160.99.1.0.1.el7 will be updated
---> Package kernel-headers.x86_64 0:3.10.0-1160.102.1.0.1.el7 will be an update
---> Package nspr.x86_64 0:4.34.0-3.1.el7_9 will be updated
---> Package nspr.x86_64 0:4.35.0-1.el7_9 will be an update
---> Package perf.x86_64 0:3.10.0-1160.99.1.0.1.el7 will be updated
---> Package perf.x86_64 0:3.10.0-1160.102.1.0.1.el7 will be an update
--> Processing Conflict: jre-1.8-headful-1.8.0_391-13.el7.x86_64 conflicts jre-1.8(x86-64)
--> Finished Dependency Resolution
Error: jre-1.8-headful conflicts with jre-1.8-1.8.0_381-9.x86_64 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
You could try using --skip-broken to work around the problem
** Found 1 pre-existing rpmdb problem(s),
'yum check' output follows:
jre-1.8-headful-1.8.0_381-9.el7.x86_64 has installed conflicts jre-1.8(x86-64): jre-1.8-1.8.0_381-9.x86_64
[2023-10-19 13:17:43,416] INFO [Validating OS Patches : JobId=13375539-a8f9-4275-8fc3-59bd0c346f48] com.oracle.dcs.agent.rpc.service.patching.PatchingOperations: Dry run did not complete successsfully.
...
...
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |