Bug 1098298 - Some problems in "Chapter 11. Storage pools"
Summary: Some problems in "Chapter 11. Storage pools"
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora Documentation
Classification: Fedora
Component: virtualization-administration-guide
Version: devel
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jaromir Hradilek
QA Contact: Fedora Docs QA
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-05-15 17:03 UTC by David Tonhofer
Modified: 2019-11-07 15:30 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-07 15:30:13 UTC
Embargoed:


Attachments (Terms of Use)

Description David Tonhofer 2014-05-15 17:03:04 UTC
In:

http://docs.fedoraproject.org/en-US/Fedora/18/html/Virtualization_Administration_Guide/chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools.html#sect-dir-based-storage-cmd

I want to create storage pools using virsh.

Corrections:

Create the storage pool definition
- - - - - - - - - - - - - - - - - -

"The path to a file system directory for storing guest image files. If this directory does not exist, virsh will create it."

This is incorrect. "You have to create it afterwards using virsh" is correct.

Create the local directory 
- - - - - - - - - - - - - -

I create the directory under "/home"

Documentation shows that "ls -la /guest_images" shows the directory having permissions "700". This is incorrect, the permissions are "755" (at least for me)

Improvement: Maybe one should also add the output of

ls --lcontext -la /guest_images/

drwxr-xr-x. 2 system_u:object_r:home_root_t:s0 root root 4096 May 15 18:50 .
drwxr-xr-x. 5 system_u:object_r:home_root_t:s0 root root 4096 May 15 18:50 ..

The wrong permissions error is repeated under "6. Verify the storage pool configuration":

ls -la /guest_images/
total 8
drwxr-xr-x. 2 root root 4096 May 15 18:50 .
drwxr-xr-x. 5 root root 4096 May 15 18:50 ..

Comment 2 Petr Bokoc 2019-11-07 15:30:13 UTC
I'm closing this bug as part of a Bugzilla cleanup effort. The most likely reason is that the bug has been opened either against a component we no longer publish, or against Release Notes for an EOL release.


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