| Summary: | "Error probing device: Error opening device file /dev/sr0: Permission denied (udisks-error-quark, 0)" | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | lnie <lnie> | ||||||||||||
| Component: | cockpit | Assignee: | Marius Vollmer <mvollmer> | ||||||||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||
| Priority: | unspecified | ||||||||||||||
| Version: | 25 | CC: | ichavero, stefw | ||||||||||||
| 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-01-02 12:56:37 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: | |||||||||||||
| Attachments: |
|
||||||||||||||
Created attachment 1197062 [details]
picture1
Created attachment 1197063 [details]
picture2
Created attachment 1197064 [details]
picture3
Created attachment 1197065 [details]
picture4
I think the relevant bit from the journal is this:
USER_AVC pid=695 uid=81 auid=4294967295 ses=4294967295 subj=system_u:system_r:system_dbusd_t:s0-s0:c0.c1023 msg='avc: denied { acquire_svc } for service=org.freedesktop.UDisks2 spid=1111 scontext=system_u:system_r:udisks2_t:s0 tcontext=system_u:system_r:system_dbusd_t:s0-s0:c0.c1023 tclass=dbus exe="/usr/bin/dbus-daemon" sauid=81 hostname=? addr=? terminal=?'
This is why udisksd didn't appear to start up. This has been fixed since.
I think the "Permission denied" error is not relevant.
|
Created attachment 1197061 [details] problem vm journal Description of problem: I have created a vm and added two disks after the installation, after play with the disk for a while( create ,delete luks disks), the cockpit can't get the storage api anymore,then I created a new one with the same process,the cockpit works well. the strange thing is, both the vm have the exactly the same permission mode,which can be confirmed from the attached pictures. Version-Release number of selected component (if applicable): cockpit-0.117-1.fc25.x86_64 How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: