Re: [Users] SOLVED: New virtual disks will NOT reliably be placed where I specified
On 03/06/2012 12:26 AM, Terry Phelps wrote: When I created my VM's disks, before posing my original question, I did specify which of my (accidentally) two data domain I wanted the disk to go, but it did NOT go there. I presume that's a feature and not a bug, right? no. it would be a bug if you chose a specific data domain for your disks, and it went to another one. please try to reproduce this though and provide clear repro steps ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[Users] permission settings on the specified path do not allow access to the storage
Hi,
My ovirt-engine was setup on a vm host with ip:xxx.xxx.xxx.112. And
I am trying to create a new domain with ovirt-engine UI by the
Storage-- New Domain. And the following error happened. However I
can mount the xxx.xxx.xxx.110:/data by mount -t nfs
xxx.xxx.xxx.110:/data /mnt manually in the ovirt-engine host, also a
new file can be created under the mounted directory with touch xx. It
looks to me that there is no permission problem when I access the remote
nfs path manually. So does ovirt-engine enforce additional permission
check beside the normal unix file permission check here?
[root@ovirt-engine-112 /]# vim /var/log/ovirt-engine/engine.log
[root@ovirt-engine-112 /]# vim /var/log/ovirt-engine/engine.log
2012-03-06 00:38:51,165 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.ValidateStorageServerConnectionVDSCommand]
(http--0.0.0.0-8080-6) START,
ValidateStorageServerConnectionVDSCommand(vdsId =
46a83d56-66d9-11e1-8004-5254009e821b, storagePoolId =
----, storageType = NFS, connectionList
= [{ id: null, connection: xxx.xxx.xxx.110:/data };]), log id: 1899002d
2012-03-06 00:38:51,297 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.ValidateStorageServerConnectionVDSCommand]
(http--0.0.0.0-8080-6) FINISH,
ValidateStorageServerConnectionVDSCommand, return:
{----=469}, log id: 1899002d
2012-03-06 00:38:51,300 ERROR
[org.ovirt.engine.core.bll.storage.NFSStorageHelper]
(http--0.0.0.0-8080-6) The connection with details xxx.xxx.xxx.110:/data
failed because of error code 469 and error message is: permission
settings on the specified path do not allow access to the storage.
verify permission settings on the specified storage path.
2012-03-06 00:38:51,300 WARN
[org.ovirt.engine.core.bll.storage.AddStorageServerConnectionCommand]
(http--0.0.0.0-8080-6) CanDoAction of action AddStorageServerConnection
failed. Reasons:ACTION_TYPE_FAILED_STORAGE_CONNECTION
2012-03-06 00:38:51,425 INFO
[org.ovirt.engine.core.bll.storage.RemoveStorageServerConnectionCommand]
(http--0.0.0.0-8080-4) Running command:
RemoveStorageServerConnectionCommand internal: false. Entities affected
: ID: aaa0----123456789aaa Type: System
--
Shu Mingshum...@linux.vnet.ibm.com
IBM China Systems and Technology Laboratory
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] permission settings on the specified path do not allow access to the storage
It seems that the problem came from the name of the data domain to be
created. I used data to be the name. Is data a reserved name for
the storage domain?
On 2012-3-6 17:30, Shu Ming wrote:
Hi,
My ovirt-engine was setup on a vm host with ip:xxx.xxx.xxx.112. And
I am trying to create a new domain with ovirt-engine UI by the
Storage-- New Domain. And the following error happened. However
I can mount the xxx.xxx.xxx.110:/data by mount -t nfs
xxx.xxx.xxx.110:/data /mnt manually in the ovirt-engine host, also a
new file can be created under the mounted directory with touch xx.
It looks to me that there is no permission problem when I access the
remote nfs path manually. So does ovirt-engine enforce additional
permission check beside the normal unix file permission check here?
[root@ovirt-engine-112 /]# vim /var/log/ovirt-engine/engine.log
[root@ovirt-engine-112 /]# vim /var/log/ovirt-engine/engine.log
2012-03-06 00:38:51,165 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.ValidateStorageServerConnectionVDSCommand]
(http--0.0.0.0-8080-6) START,
ValidateStorageServerConnectionVDSCommand(vdsId =
46a83d56-66d9-11e1-8004-5254009e821b, storagePoolId =
----, storageType = NFS,
connectionList = [{ id: null, connection: xxx.xxx.xxx.110:/data };]),
log id: 1899002d
2012-03-06 00:38:51,297 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.ValidateStorageServerConnectionVDSCommand]
(http--0.0.0.0-8080-6) FINISH,
ValidateStorageServerConnectionVDSCommand, return:
{----=469}, log id: 1899002d
2012-03-06 00:38:51,300 ERROR
[org.ovirt.engine.core.bll.storage.NFSStorageHelper]
(http--0.0.0.0-8080-6) The connection with details
xxx.xxx.xxx.110:/data failed because of error code 469 and error
message is: permission settings on the specified path do not allow
access to the storage.
verify permission settings on the specified storage path.
2012-03-06 00:38:51,300 WARN
[org.ovirt.engine.core.bll.storage.AddStorageServerConnectionCommand]
(http--0.0.0.0-8080-6) CanDoAction of action
AddStorageServerConnection failed.
Reasons:ACTION_TYPE_FAILED_STORAGE_CONNECTION
2012-03-06 00:38:51,425 INFO
[org.ovirt.engine.core.bll.storage.RemoveStorageServerConnectionCommand]
(http--0.0.0.0-8080-4) Running command:
RemoveStorageServerConnectionCommand internal: false. Entities
affected : ID: aaa0----123456789aaa Type: System
--
Shu Mingshum...@linux.vnet.ibm.com
IBM China Systems and Technology Laboratory
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] permission settings on the specified path do not allow access to the storage
Manually mount and touch with kvm:qemu user/group and see if success?
2012/3/6 Shu Ming shum...@linux.vnet.ibm.com:
It seems that the problem came from the name of the data domain to be
created. I used data to be the name. Is data a reserved name for the
storage domain?
On 2012-3-6 17:30, Shu Ming wrote:
Hi,
My ovirt-engine was setup on a vm host with ip:xxx.xxx.xxx.112. And I am
trying to create a new domain with ovirt-engine UI by the Storage-- New
Domain. And the following error happened. However I can mount the
xxx.xxx.xxx.110:/data by mount -t nfs xxx.xxx.xxx.110:/data /mnt manually
in the ovirt-engine host, also a new file can be created under the mounted
directory with touch xx. It looks to me that there is no permission
problem when I access the remote nfs path manually. So does ovirt-engine
enforce additional permission check beside the normal unix file permission
check here?
[root@ovirt-engine-112 /]# vim /var/log/ovirt-engine/engine.log
[root@ovirt-engine-112 /]# vim /var/log/ovirt-engine/engine.log
2012-03-06 00:38:51,165 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.ValidateStorageServerConnectionVDSCommand]
(http--0.0.0.0-8080-6) START,
ValidateStorageServerConnectionVDSCommand(vdsId =
46a83d56-66d9-11e1-8004-5254009e821b, storagePoolId =
----, storageType = NFS, connectionList = [{
id: null, connection: xxx.xxx.xxx.110:/data };]), log id: 1899002d
2012-03-06 00:38:51,297 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.ValidateStorageServerConnectionVDSCommand]
(http--0.0.0.0-8080-6) FINISH, ValidateStorageServerConnectionVDSCommand,
return: {----=469}, log id: 1899002d
2012-03-06 00:38:51,300 ERROR
[org.ovirt.engine.core.bll.storage.NFSStorageHelper] (http--0.0.0.0-8080-6)
The connection with details xxx.xxx.xxx.110:/data failed because of error
code 469 and error message is: permission settings on the specified path do
not allow access to the storage.
verify permission settings on the specified storage path.
2012-03-06 00:38:51,300 WARN
[org.ovirt.engine.core.bll.storage.AddStorageServerConnectionCommand]
(http--0.0.0.0-8080-6) CanDoAction of action AddStorageServerConnection
failed. Reasons:ACTION_TYPE_FAILED_STORAGE_CONNECTION
2012-03-06 00:38:51,425 INFO
[org.ovirt.engine.core.bll.storage.RemoveStorageServerConnectionCommand]
(http--0.0.0.0-8080-4) Running command: RemoveStorageServerConnectionCommand
internal: false. Entities affected : ID:
aaa0----123456789aaa Type: System
--
Shu Mingshum...@linux.vnet.ibm.com
IBM China Systems and Technology Laboratory
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] permission settings on the specified path do not allow access to the storage
The problem was resloved and It might come from the naming problem
using 'data' as domain name.
On 2012-3-6 22:55, Xiaofan wrote:
Manually mount and touch with kvm:qemu user/group and see if success?
2012/3/6 Shu Mingshum...@linux.vnet.ibm.com:
It seems that the problem came from the name of the data domain to be
created. I used data to be the name. Is data a reserved name for the
storage domain?
On 2012-3-6 17:30, Shu Ming wrote:
Hi,
My ovirt-engine was setup on a vm host with ip:xxx.xxx.xxx.112. And I am
trying to create a new domain with ovirt-engine UI by the Storage-- New
Domain. And the following error happened. However I can mount the
xxx.xxx.xxx.110:/data by mount -t nfs xxx.xxx.xxx.110:/data /mnt manually
in the ovirt-engine host, also a new file can be created under the mounted
directory with touch xx. It looks to me that there is no permission
problem when I access the remote nfs path manually. So does ovirt-engine
enforce additional permission check beside the normal unix file permission
check here?
[root@ovirt-engine-112 /]# vim /var/log/ovirt-engine/engine.log
[root@ovirt-engine-112 /]# vim /var/log/ovirt-engine/engine.log
2012-03-06 00:38:51,165 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.ValidateStorageServerConnectionVDSCommand]
(http--0.0.0.0-8080-6) START,
ValidateStorageServerConnectionVDSCommand(vdsId =
46a83d56-66d9-11e1-8004-5254009e821b, storagePoolId =
----, storageType = NFS, connectionList = [{
id: null, connection: xxx.xxx.xxx.110:/data };]), log id: 1899002d
2012-03-06 00:38:51,297 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.ValidateStorageServerConnectionVDSCommand]
(http--0.0.0.0-8080-6) FINISH, ValidateStorageServerConnectionVDSCommand,
return: {----=469}, log id: 1899002d
2012-03-06 00:38:51,300 ERROR
[org.ovirt.engine.core.bll.storage.NFSStorageHelper] (http--0.0.0.0-8080-6)
The connection with details xxx.xxx.xxx.110:/data failed because of error
code 469 and error message is: permission settings on the specified path do
not allow access to the storage.
verify permission settings on the specified storage path.
2012-03-06 00:38:51,300 WARN
[org.ovirt.engine.core.bll.storage.AddStorageServerConnectionCommand]
(http--0.0.0.0-8080-6) CanDoAction of action AddStorageServerConnection
failed. Reasons:ACTION_TYPE_FAILED_STORAGE_CONNECTION
2012-03-06 00:38:51,425 INFO
[org.ovirt.engine.core.bll.storage.RemoveStorageServerConnectionCommand]
(http--0.0.0.0-8080-4) Running command: RemoveStorageServerConnectionCommand
internal: false. Entities affected : ID:
aaa0----123456789aaa Type: System
--
Shu Mingshum...@linux.vnet.ibm.com
IBM China Systems and Technology Laboratory
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
--
Shu Mingshum...@linux.vnet.ibm.com
IBM China Systems and Technology Laboratory
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] adding host with ovirt-engine-cli
On 03/07/2012 08:56 AM, Michael Pasternak wrote: Hi David, On 03/07/2012 12:08 AM, Li, David wrote: Hi Michael, Now I could create a host but couldn't delete it. This is because you using not official release of the cli, (you build cli rpm from the latest git right?!, you should use rpm i gave you) the other option is your ovirt-engine is more advanced than cli, anyway this is one of the risks to be taken when building rpms directly from the latest git, at the moment I'm working to finalise next snapshot and will ping you when official tarballs will be available. so this is due to partly developed/committed feature, if you'll build new rpm now (from the git) and reinstall it (don't forget removing the old one first cause both rpms will have same version) it will work, in future please try to avoid installing non officially released tarballs. [oVirt shell (connected)]# delete host 72b4107c-679d-11e1-9302-000c29cfd59e error: failed locating type async what's the correct syntax for deleting a host? - David -- Michael Pasternak RedHat, ENG-Virtualization RD ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
