Bug 1372158 - got strange errors in journal when I try to create a partition using cockpit
Summary: got strange errors in journal when I try to create a partition using cockpit
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 25
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-01 04:51 UTC by lnie
Modified: 2017-12-12 10:21 UTC (History)
9 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:48 UTC
Type: Bug


Attachments (Terms of Use)
screenshot (67.25 KB, image/png)
2016-09-01 04:51 UTC, lnie
no flags Details
journal -b -1 (179.16 KB, text/plain)
2016-09-01 04:52 UTC, lnie
no flags Details
journal (766.27 KB, text/plain)
2016-09-02 08:50 UTC, lnie
no flags Details
journalctl -b -1(new) (765.65 KB, text/x-vhdl)
2016-09-02 08:54 UTC, lnie
no flags Details
journalctl -p 3 and dnf history (8.05 KB, text/plain)
2016-09-02 08:56 UTC, lnie
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1372160 0 unspecified CLOSED get lots of " systemd-udevd[3266]: inotify_add_watch(9, /dev/sdb1, 10) failed: No such file or directory" 2021-02-22 00:41:40 UTC

Internal Links: 1372160

Description lnie 2016-09-01 04:51:21 UTC
Created attachment 1196584 [details]
screenshot

Description of problem:
I added a disk using virt-manager after the installation.
got:
Sep 01 12:36:25 localhost.localdomain systemd-cryptsetup[1575]: crypt_init() failed: Block device required
Sep 01 12:36:25 localhost.localdomain systemd[1]: Failed to start Cryptography Setup for luks-1d4e0321-ad2e-41e6-85bc-eb969eb76423.
when I try to create a partition on a clean disk(I created a lucks partition,but I have deleted it before I create the partition).

please see the attached picture to see the strange thing.

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.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 lnie 2016-09-01 04:52:47 UTC
Created attachment 1196585 [details]
journal -b -1

Comment 2 lnie 2016-09-02 08:50:23 UTC
Created attachment 1197066 [details]
journal

Comment 3 lnie 2016-09-02 08:54:33 UTC
Created attachment 1197078 [details]
journalctl -b -1(new)

Comment 4 lnie 2016-09-02 08:56:02 UTC
Created attachment 1197079 [details]
journalctl -p 3  and dnf history

Comment 5 lnie 2016-09-02 08:58:40 UTC
It seems that this problem is caused by the python3-blivet installed by me:)

Comment 6 Fedora End Of Life 2017-11-16 19:01:47 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 7 Fedora End Of Life 2017-12-12 10:21:48 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.