Bug 1231329 - warning: file /lib/modules/<kernel version>/updates: remove failed: No such file or directory
Summary: warning: file /lib/modules/<kernel version>/updates: remove failed: No such f...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-06-12 17:13 UTC by Kamil Páral
Modified: 2016-09-16 13:57 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-11-23 17:09:08 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
full dnf transaction (109.57 KB, text/plain)
2015-06-12 17:13 UTC, Kamil Páral
no flags Details

Description Kamil Páral 2015-06-12 17:13:13 UTC
Created attachment 1038121 [details]
full dnf transaction

Description of problem:
Often when removing older kernels, I see a following warning printed out during yum/dnf transaction:

  Erasing     : kernel-modules-4.0.4-201.fc21.x86_64                                                                      180/244 
  Erasing     : kernel-core-4.0.4-201.fc21.x86_64                                                                         181/244 
warning: file /lib/modules/4.0.4-201.fc21.x86_64/updates: remove failed: No such file or directory

I don't know what it complains about. But would it be possible to either fix the underlying problem, or make the remove operation go quiet if the file in question doesn't exist?

The less superfluous output we have in yum/dnf transaction, the easier it is to spot possible real problems in there.

This kernel output is also the reason why these transactions are marked with EE (error) in dnf/yum history, which is inconvenient.

Thank you.

Version-Release number of selected component (if applicable):
dnf-1.0.0-1.fc22.noarch  
rpm-4.12.0.1-9.fc22.x86_64
kernel-4.0.4-201.fc21.x86_64 (being removed)


How reproducible:
I see it often, not sure it happens always. Can debug more if needed.

Steps to Reproduce:
1. Probably just try to remove a kernel.

Comment 1 Justin M. Forbes 2015-10-20 19:17:36 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 22 kernel bugs.

Fedora 22 has now been rebased to 4.2.3-200.fc22.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 23, and are still experiencing this issue, please change the version to Fedora 23.

If you experience different issues, please open a new bug report for those.

Comment 2 Fedora Kernel Team 2015-11-23 17:09:08 UTC
*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in over 4 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.

Comment 3 Sudhir Khanger 2016-09-16 13:11:45 UTC
Can you please reopen this bug report? I see this warning with every update and I would like to get the underlying problem fixed.

Please let me know what information you need and I will do my best to provide it.

Comment 4 Kamil Páral 2016-09-16 13:57:03 UTC
Sudhir, this bug is quite old, and I stopped seeing those messages. If you still see this on F24 or better yet F25, please open a fresh bug and put this one in See Also field. Thanks.


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