Bug 1525253

Summary: Broken pipe error when upgrading kernel
Product: [Fedora] Fedora Reporter: Dimitris <dimitris.on.linux>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 27CC: airlied, ajax, bskeggs, ewk, hdegoede, ichavero, itamar, jarodwilson, jeremy, jglisse, john.j5live, jonathan, josef, kernel-maint, labbott, linville, mchehab, mjg59, steved
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-12 23:09:50 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:

Description Dimitris 2017-12-12 21:55:18 UTC 
Description of problem:

During kernel upgrade, I see:

Running scriptlet: kernel-core-4.14.5-300.fc27.x86_64                                                                                                                                 12/12 
cat: write error: Broken pipe
  Running scriptlet: kernel-tools-libs-4.14.3-300.fc27.x86_64                                                                                                                           12/12 
Running as unit: run-ra0bef15c44ac4fc9aa520d8889581a0c.service

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

Latest occurrence with the upgrade to 4.14.5-300.fc27

How reproducible:

On every upgrade since 2-3 package versions ago


Steps to Reproduce:
1.  Upgrade kernel
2.  Error appears
3.

Actual results:

Error when running kernel upgrade script.  No other apparent ill effect that I can see so far.

Expected results:

Recent regression, don't remember seeing this before.

Additional info:
Comment 1 Laura Abbott 2017-12-12 23:09:50 UTC 

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