Red Hat Bugzilla – Bug 1178104
It is not possible to create NFS data domain via rehvm-shell
Last modified: 2016-02-10 14:04:45 EST
Description of problem: The following command fails with error message: add storagedomain --host-name x.x.x.x --type data --storage-type nfs --format v3 --storage-address x.x.x.x --storage-path /exports/data03 --datacenter-identifier Default --name NFS03 ====================================================== ERROR ==================================================== status: 404 reason: Not Found detail: Entity not found: Storage: name=NFS03 ================================================================================================================= Version-Release number of selected component (if applicable): How reproducible: 100% Actual results: ====================================================== ERROR ==================================================== status: 404 reason: Not Found detail: Entity not found: Storage: name=NFS03 ================================================================================================================= Expected results: Storage domain is created Additional info: The command is taken from the documentation: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.4/html/Technical_Guide/chap-Quick_Start_Example.html
What this action is actually doing is attaching an existing storage domain to the data center. The storage domain needs to be previously created using the top level "storagedomains" collections, thus omitting the "--datacenter-identifier". For example: # add storagedomain --host-name x.x.x.x --type data --storage-type nfs --storage_format v3 --storage-address x.x.x.x --storage-path /exports/data03 --name NFS03 Note also that the "--format" option is used to indicate if the storage should be "formatted", and that it is only applicable when deleting a storage domain, and that it must be a boolean. The option used to specify the storage format version is "--storage_format". The storage domain may take a long time to be created, so it is advisable to wait till it is "unattached", repeating the following command: # show storagedomain --name NFS03 id : 1c79af3c-8df4-4a7c-897a-fef72bb41a2e name : NFS03 master : False status-state : unattached <-- It is ok to continue when this is "unattached" ... Once the storage domain is created with the above command it can be attached to the data center: # add storagedomain --datacenter-identifier Default --name NFS03 I believe that this bug should be closed as NOTABUG, or moved to the documentation component, as the documentation referenced in the description isn't correct.
(In reply to Juan Hernández from comment #1) > What this action is actually doing is attaching an existing storage domain > to the data center. The storage domain needs to be previously created using > the top level "storagedomains" collections, thus omitting the > "--datacenter-identifier". For example: > > # add storagedomain --host-name x.x.x.x --type data --storage-type nfs > --storage_format v3 --storage-address x.x.x.x --storage-path /exports/data03 > --name NFS03 > > Note also that the "--format" option is used to indicate if the storage > should be "formatted", and that it is only applicable when deleting a > storage domain, and that it must be a boolean. The option used to specify > the storage format version is "--storage_format". > > The storage domain may take a long time to be created, so it is advisable to > wait till it is "unattached", repeating the following command: > > # show storagedomain --name NFS03 > id : 1c79af3c-8df4-4a7c-897a-fef72bb41a2e > name : NFS03 > master : False > status-state : unattached <-- It is ok to continue when this is > "unattached" > ... > > Once the storage domain is created with the above command it can be attached > to the data center: > > # add storagedomain --datacenter-identifier Default --name NFS03 > > I believe that this bug should be closed as NOTABUG, or moved to the > documentation component, as the documentation referenced in the description > isn't correct. Hi, thank you. I am moving it to the documentation team.
Can we fix the documentation and properly document how to create, attach and activate the SD? At lease this chapter is not correct. https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.4/html/Technical_Guide/chap-Quick_Start_Example.html
Checked all command again. Cannot verify step17.
Hey guys, I keep getting this error for step17 'show event --id 60' ============================= UNKNOWN ERROR ============================= cannot convert dictionary update sequence element #0 to a sequence ============================================================================ Anyone has a fix? Cheers, Julie
Hey Julie The command should be: show event --id '60' QA: I've updated step 17 accordingly and made some line changes to the topic. Revision History also updated.
(In reply to Andrew Burden from comment #9) > Hey Julie > The command should be: > show event --id '60' > > QA: > I've updated step 17 accordingly and made some line changes to the topic. > Revision History also updated. Thanks Andrew.