Bug 1300340

Summary: Yum fails to unpack rhevm-reports-setup package when upgrading
Product: [Retired] ovirt-engine-reports Reporter: Petr Matyáš <pmatyas>
Component: Packaging.rpmAssignee: Anton Marchukov <amarchuk>
Status: CLOSED CURRENTRELEASE QA Contact: Petr Matyáš <pmatyas>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 3.6.2CC: amarchuk, bugs, didi, lveyde, pstehlik, rmartins, sbonazzo, stirabos, ylavi
Target Milestone: ovirt-3.6.2Keywords: TestOnly
Target Release: 3.6.2Flags: sbonazzo: ovirt-3.6.z?
pmatyas: planning_ack?
sbonazzo: devel_ack+
rule-engine: testing_ack+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-02-18 11:13:14 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: External RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Petr Matyáš 2016-01-20 13:58:39 UTC
Description of problem:
After upgrading from 3.6.2-9 yum upgrade fails with:
Error unpacking rpm package rhevm-reports-setup-3.6.2.4-1.el6ev.noarch
error: unpacking of archive failed: cpio: read
rhevm-reports-setup-3.6.2.3-2.el6ev.noarch was supposed to be removed but is not!

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

How reproducible:
always

Steps to Reproduce:
1. yum install rhevm-reports-setup for 3.6.2-9
2. yum update to 3.6.2-10
3.

Actual results:
fails when unpacking

Expected results:
correct installation

Additional info:

Comment 1 Anton Marchukov 2016-01-20 16:04:05 UTC
This is a result of eng-ops problem https://engineering.redhat.com/rt/Ticket/Display.html?id=384646 some packages were downloaded broken from brew.

I have manually verified rpms on 3.6.2-10 using rpm -K and replaced broken packages. Now all checksums are ok.

Comment 2 Red Hat Bugzilla Rules Engine 2016-01-20 16:04:08 UTC
Fixed bug tickets must have version flags set prior to fixing them. Please set the correct version flags and move the bugs back to the previous status after this is corrected.

Comment 3 Red Hat Bugzilla Rules Engine 2016-01-20 16:04:08 UTC
Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone.

Comment 4 Red Hat Bugzilla Rules Engine 2016-01-20 16:04:08 UTC
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Comment 5 Red Hat Bugzilla Rules Engine 2016-01-20 21:17:34 UTC
Bug tickets that are moved to testing must have target release set to make sure tester knows what to test. Please set the correct target release before moving to ON_QA.