Bug 1313525

Summary: MiniYum must support Obsoletes
Product: [oVirt] otopi Reporter: Fabian Deutsch <fdeutsch>
Component: Plugins.packagersAssignee: Yedidyah Bar David <didi>
Status: CLOSED NOTABUG QA Contact: Pavel Stehlik <pstehlik>
Severity: unspecified Docs Contact:
Priority: urgent    
Version: masterCC: bugs, emesika, fdeutsch, oourfali, sbonazzo
Target Milestone: ovirt-3.6.6Flags: fdeutsch: ovirt-3.6.z?
fdeutsch: blocker?
fdeutsch: planning_ack?
fdeutsch: devel_ack?
fdeutsch: testing_ack?
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-03-04 08:38:24 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Integration RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1140646    
Attachments:
Description Flags
host deploy log none

Description Fabian Deutsch 2016-03-01 19:20:16 UTC 
Description of problem:
oVirt Node Next depends support for the rpm Obsoletes directives. MiniYum does currently not support Obsolete dependencies, but it should support it to allow oVirt node Next updates,

Version-Release number of selected component (if applicable):
3.6

How reproducible:
Always

Steps to Reproduce:
1. Try to get updates for packages which use the Obsoletes dependency to express an update
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Fabian Deutsch 2016-03-01 19:20:53 UTC 
This is currently blocking Engine initiated oVirt Node Next upgrade flow
Comment 2 Sandro Bonazzola 2016-03-02 08:09:33 UTC 
As far as I know, miniyum support obsoletes. If something goes wrong it's probably a bug in the spec file with the obsoletes directive.

Can you please provide full log and link to src.rpm of the packages failing the upgrade?
Comment 3 Fabian Deutsch 2016-03-02 11:21:28 UTC 
Eli, can you provide the logs?
Comment 4 Fabian Deutsch 2016-03-02 11:23:17 UTC 
The image wrapper spec is here:

https://gerrit.ovirt.org/gitweb?p=ovirt-node-ng.git;a=blob;f=packaging/ovirt-node-ng.spec.in;h=20fac922f422d97ab64ef6b6c7c082ed38eb77a0;hb=HEAD

The placeholder spec is here:

https://gerrit.ovirt.org/gitweb?p=ovirt-release.git;a=blob;f=ovirt-release-master/ovirt-release-master.spec.in;h=feca8cb0c0b68a473597f52d6cd03ec1020f0d7c;hb=HEAD#l73
Comment 5 Eli Mesika 2016-03-02 11:26:37 UTC 
Created attachment 1132254 [details]
host deploy log

This is the host deploy log , please search for "obsolete" to find  the relevant error that causes miniyum to rollback the yum transaction
Comment 6 Sandro Bonazzola 2016-03-04 08:38:24 UTC 
missing provides in https://gerrit.ovirt.org/gitweb?p=ovirt-node-ng.git;a=blob;f=packaging/ovirt-node-ng.spec.in;h=20fac922f422d97ab64ef6b6c7c082ed38eb77a0;hb=HEAD

Obsoletes:  ovirt-node-ng-image-update-placeholder <= %{version}-%{release}
missing: Provides: ovirt-node-ng-image-update-placeholder  %{version}-%{release}
and the obsoletes should be < not <=

Please reopen if after above changes it still fails.