Bug 1291939

Summary: yum update installs the packages but shows an error after installation completion
Product: Red Hat Enterprise Linux 7 Reporter: Valentin Bajrami <valentin.bajrami>
Component: yumAssignee: Valentina Mukhamedzhanova <vmukhame>
Status: CLOSED DUPLICATE QA Contact: BaseOS QE Security Team <qe-baseos-security>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 7.1CC: james.antill
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-12-16 12:46:03 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
The attachment contains the details which abrt reports. Abrt fails on me as well with message: Error: no processing is specified for event 'report_RHTSupport' none

Description Valentin Bajrami 2015-12-15 22:44:05 UTC
Created attachment 1106230 [details]
The attachment contains the details which abrt reports. Abrt fails on me as well with message:  Error: no processing is specified for event 'report_RHTSupport'

Description of problem:


3.4.3
  Installed: rpm-4.11.1-25.el7.x86_64 at 2015-06-14 22:09
  Built    : Scientific Linux at 2015-03-05 19:53
  Committed: Florian Festi <ffesti> at 2015-01-12

  Installed: yum-3.4.3-125.el7.noarch at 2015-12-08 20:48
  Built    : Scientific Linux at 2015-03-05 15:38
  Committed: Scientific Linux Auto Patch Process <SCIENTIFIC-LINUX-DEVEL.GOV> at 2015-03-05


How reproducible:

yum update

Steps to Reproduce:
1. yum update
2.
3.

Actual results:

See attachment


Expected results:

Yum should install packages without showing the error after completion.


Additional info:

Comment 2 Valentina Mukhamedzhanova 2015-12-16 12:46:03 UTC
This was fixed in yum-3.4.3-132.el7.

For the abrt error please file a separate bugzilla.

*** This bug has been marked as a duplicate of bug 1259837 ***