Bug 1073172 - [RFE][yum] query provides in addition to packages
Summary: [RFE][yum] query provides in addition to packages
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: otopi
Classification: oVirt
Component: Plugins.packagers
Version: ---
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 1.2.0
Assignee: Alon Bar-Lev
QA Contact: Pavel Stehlik
URL:
Whiteboard: infra
Depends On:
Blocks: 1064038
TreeView+ depends on / blocked
 
Reported: 2014-03-06 00:18 UTC by Alon Bar-Lev
Modified: 2016-02-10 19:16 UTC (History)
6 users (show)

Fixed In Version: otopi-1.2.0_rc4
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-03-31 15:04:09 UTC
oVirt Team: Infra
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 25446 0 None None None Never
oVirt gerrit 25702 0 None None None Never

Description Alon Bar-Lev 2014-03-06 00:18:51 UTC
will enable to find vdsm when vdsm3 is the package name and vdsm3 provides vdsm.

Comment 1 Alon Bar-Lev 2014-03-06 20:14:41 UTC
QA note:

This is non trivial change in how we find packages within yum, so need to check all sequences...

1. host deploy fedora - fresh/update.
2. host deploy rhel-6.5 - fresh/update.
3. host deploy rhel-7 - fresh/update, this will check that vdsm3 is installed while host deploy seeks vdsm.
4. host deploy with rollback.
5. engine setup upgrade from previous minor.
6. engine setup upgrade from current minor.
7. engine setup with rollback

I checked all, but should re-check.

Potential is we find more packages we need and yum transaction fails with a very long unrelated error.

Upstream: since otopi-repolib-1.2.0-0.8.master.20140306.git1337eb8
Downstream: since otopi-1.2.0-0.8.master

Comment 2 Alon Bar-Lev 2014-03-12 15:52:22 UTC
all architectures are pulled into yum transaction.

Comment 3 Sandro Bonazzola 2014-03-31 15:04:09 UTC
This is an automated message: moving to Closed CURRENT_RELEASE since oVirt 3.4.0 has been released.


Note You need to log in before you can comment on or make changes to this bug.