Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at

Bug 1382532

Summary: F25 server beta: Storage section empty, "storaged API is not available on this system"
Product: [Fedora] Fedora Reporter: Chris Murphy <bugzilla>
Component: cockpitAssignee: Marius Vollmer <mvollmer>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 25CC: dperpeet, ichavero, stefw
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-10-10 07:50:38 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:
Description Flags
journalctl -b -o short-monotonic none

Description Chris Murphy 2016-10-07 00:31:54 UTC
Description of problem:

Clicking on the Storage option in Cockpit, I get a message:

The "storaged" API is not available on this system.

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


How reproducible:

Steps to Reproduce:
1. Default installation Fedora-Server-netinst-x86_64-25_Beta-1.1.iso in a VM.
2. Browser, connect to the server IP:9090, click on Storage on the left side UI

Actual results:

The "storaged" API is not available on this system.

Expected results:

Bunch of badass storage info.

Additional info:

storaged looks available?

[root@f25v ~]# rpm -qa | grep storaged

Comment 1 Chris Murphy 2016-10-07 00:35:48 UTC
Created attachment 1208061 [details]
journalctl -b -o short-monotonic

Doesn't appear to be that helpful, nothing storage related. udisks2.service is loaded and active.

Comment 2 Marius Vollmer 2016-10-10 07:50:38 UTC
THis is probably caused by storaged/selinux mismatches, see bug 1375156.

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