Bug 1372168 - always got annoying "Timed out waiting for device QEMU_HARDDISK 2." error in journal
Summary: always got annoying "Timed out waiting for device QEMU_HARDDISK 2." error in ...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: cockpit
Version: 25
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Marius Vollmer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-01 06:00 UTC by lnie
Modified: 2017-12-12 10:21 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-12 10:21:37 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
journalctl -p 3 (11.83 KB, text/plain)
2016-09-01 06:00 UTC, lnie
no flags Details
journal -b -1 (179.16 KB, text/plain)
2016-09-01 06:02 UTC, lnie
no flags Details

Description lnie 2016-09-01 06:00:33 UTC
Created attachment 1196598 [details]
journalctl -p 3

Description of problem:
As can be seen from the attached log,there are lots of "Sep 01 13:40:22 localhost.localdomain systemd[1]: Timed out waiting for device QEMU_HARDDISK 2.
"

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

 systemd-231-3.fc25.x86_64
 cockpit-0.117-1.fc25.x86_64

How reproducible:
always 

Steps to Reproduce:
1.add a disk using virt-manager after do a clean installation 
2.play with that disk:create,delete partition things 
3.

Actual results:


Expected results:


Additional info:

Comment 1 lnie 2016-09-01 06:02:29 UTC
Created attachment 1196599 [details]
journal -b -1

Comment 2 Fedora End Of Life 2017-12-12 10:21:37 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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