Bug 1278453 - After upgrade from 3.5 to 3.6 host still have old package vdsm-python-zombiereaper-4.16.28-1.el7ev.noarch
Summary: After upgrade from 3.5 to 3.6 host still have old package vdsm-python-zombier...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: vdsm
Classification: oVirt
Component: Packaging.rpm
Version: 4.17.10
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ovirt-3.6.1
: 4.17.11
Assignee: Yeela Kaplan
QA Contact: Lukas Svaty
URL:
Whiteboard: infra
Depends On:
Blocks: RHEV3.6Upgrade
TreeView+ depends on / blocked
 
Reported: 2015-11-05 14:23 UTC by Artyom
Modified: 2016-02-10 19:14 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-16 12:24:35 UTC
oVirt Team: Infra
Embargoed:
ybronhei: ovirt-3.6.z?
rule-engine: planning_ack?
rule-engine: devel_ack+
rule-engine: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 48240 0 None None None Never
oVirt gerrit 48452 0 ovirt-3.6 MERGED spec: zombiereaper is not removed on vdsm upgrade Never

Description Artyom 2015-11-05 14:23:00 UTC 
Description of problem:
After upgrade from 3.5 to 3.6 host still have old package vdsm-python-zombiereaper-4.16.28-1.el7ev.noarch

Version-Release number of selected component (if applicable):
from vdsm-4.16.28-1.el7ev.x86_64
to vdsm-4.17.10.1-0.el7ev.noarch

How reproducible:
Always

Steps to Reproduce:
1. Run yum update -y
2.
3.

Actual results:
yum not clean package vdsm-python-zombiereaper-4.16.28-1.el7ev.noarch

Expected results:
yum clean old package vdsm-python-zombiereaper-4.16.28-1.el7ev.noarch, because new one included under vdsm-infra-4.17.10.1-0.el7ev.noarch

Additional info:
Comment 1 Lukas Svaty 2015-11-26 12:15:35 UTC 
verified in vdsm-4.17.11-0.el7ev.noarch
Comment 2 Sandro Bonazzola 2015-12-16 12:24:35 UTC 
According to verification status and target milestone this issue should be fixed in oVirt 3.6.1. Closing current release.
Note You need to log in before you can comment on or make changes to this bug.