[ovirt-users] Re: Can't connect vdsm storage: Command StorageDomain.getInfo with args failed: (code=350, message=Error in storage domain action
Yes. The problem with permission. But not with permissoin on export directory. Two ways to resolve this: 1) Make 777 permission on directory - dont right solution. 2) anonuid=36,anongid=36 in export - this right solution, very strange that this is not in any documentation, but very important! I has right permission on my export directory, but this is not working before i mke 777 chmod. After i chande parameters in exports file i return chmod to 755 and all working fine now! Thank you and all very much. ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/Y6KJ2PTMHDJTYXBNT63G5QRF7RH3JVMA/
[ovirt-users] Re: Can't connect vdsm storage: Command StorageDomain.getInfo with args failed: (code=350, message=Error in storage domain action
Yes. The problem with permission. But not with permissoin on export directory. Two ways to resolve this: 1) Make 777 permission on directory - dont right solution. 2) anonuid=36,anongid=36 in export - this right solution, very strange that this is not in any documentation, but very important! I has right permission on my export directory, but this is not working before i mke 777 chmod. After i chande parameters in exports file i return chmod to 755 and all working fine now! Thank you and all very much. ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/CRAVOYFYFZCTEQITSIWLTQCTQFBRFC4W/
[ovirt-users] Re: Can't connect vdsm storage: Command StorageDomain.getInfo with args failed: (code=350, message=Error in storage domain action
First of all i have check permission on my storage. And all permission is right: group kvm (36) and user vdsm (36), chown 36:36 and chmod 0755. After i made 0777 permissions and updating all working fine! My NFS storage on Synology NAS, i now i trying to find a way to make anonuid=36,anongid=36 in the export by right way, not by editing of exports file. After i find it, i will try to use it and 755 permission. Thanks to ALL! BR, Alex ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/RRSDPOE4YR4JQKMXAOKHLSMEQ62RYI7A/
[ovirt-users] Re: Can't connect vdsm storage: Command StorageDomain.getInfo with args failed: (code=350, message=Error in storage domain action
One thing not in any of the documentation I have found are the extra options required for the export. I followed all the docs and it was still failing. I had to add, “sync,no_subtree_check,all_squash,anonuid=36,anongid=36”, to my export in order to get it to work. From: Nir Soffer Sent: Saturday, February 1, 2020 4:51 PM To: a...@pioner.kz Cc: users Subject: [ovirt-users] Re: Can't connect vdsm storage: Command StorageDomain.getInfo with args failed: (code=350, message=Error in storage domain action On Sat, Feb 1, 2020 at 5:39 PM mailto:a...@pioner.kz>> wrote: Ok, i will try to set 777 permissoin on NFS storage. This is invalid configuration. See RHV docs for proper configuration: https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.3/html/administration_guide/sect-preparing_and_adding_nfs_storage#Preparing_NFS_Storage_storage_admin But, why this issue starting from updating 4.30.32-1 to 4.30.33-1? Withowt any another changes. I guess you had wrong permissions and ownership on the storage before, but vdsm was not detecting the issue because it was missing validations in older versions. Current version is validating that creating and deleting files and using direct I/O works with the storage when creating and activating a storage domain. Nir ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/OFTUAQS6SY5I5ZNG22R5S42Q6WUE75ZM/
[ovirt-users] Re: Can't connect vdsm storage: Command StorageDomain.getInfo with args failed: (code=350, message=Error in storage domain action
On Sat, Feb 1, 2020 at 5:39 PM wrote: > Ok, i will try to set 777 permissoin on NFS storage. This is invalid configuration. See RHV docs for proper configuration: https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.3/html/administration_guide/sect-preparing_and_adding_nfs_storage#Preparing_NFS_Storage_storage_admin > But, why this issue starting from updating 4.30.32-1 to 4.30.33-1? > Withowt any another changes. > I guess you had wrong permissions and ownership on the storage before, but vdsm was not detecting the issue because it was missing validations in older versions. Current version is validating that creating and deleting files and using direct I/O works with the storage when creating and activating a storage domain. Nir ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/NWMDXNEBA62FD6QKKYFQJWEKXBD55VBD/
[ovirt-users] Re: Can't connect vdsm storage: Command StorageDomain.getInfo with args failed: (code=350, message=Error in storage domain action
On Sat, Feb 1, 2020 at 6:39 PM wrote: > Ok, i will try to set 777 permissoin on NFS storage. But, why this issue > starting from updating 4.30.32-1 to 4.30.33-1? Withowt any another > changes. > The differing commit for 4.30.33 over 4.30.32 is the transition into block size probing done by ioprocess-1.3.0: https://github.com/oVirt/vdsm/commit/9bd210e340be0855126d1620cdb94840ced56129 > ___ > Users mailing list -- users@ovirt.org > To unsubscribe send an email to users-le...@ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/ICWRJ75Q7DIZDDNYRP757YHDEN4N537V/ > ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/RO4FS4ESIR5UEAHBMGSMBWQZM6Z5WFJD/
[ovirt-users] Re: Can't connect vdsm storage: Command StorageDomain.getInfo with args failed: (code=350, message=Error in storage domain action
Ok, i will try to set 777 permissoin on NFS storage. But, why this issue starting from updating 4.30.32-1 to 4.30.33-1? Withowt any another changes. ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/ICWRJ75Q7DIZDDNYRP757YHDEN4N537V/
[ovirt-users] Re: Can't connect vdsm storage: Command StorageDomain.getInfo with args failed: (code=350, message=Error in storage domain action
On Saturday, February 1, 2020, wrote:
> Hi! I trying to upgrade my hosts and have problem with it. After uprgading
> one host i see that this one NonOperational. All was fine with
> vdsm-4.30.24-1.el7 but after upgrading with new version
> vdsm-4.30.40-1.el7.x86_64 and some others i have errors.
> Firtst of all i see in ovirt Events: Host srv02 cannot access the Storage
> Domain(s) attached to the Data Center Default. Setting Host state
> to Non-Operational. My Default storage domain with HE VM data on NFS
> storage.
>
> In messages log of host:
> srv02 journal: ovirt-ha-agent ovirt_hosted_engine_ha.agent.agent.Agent
> ERROR Traceback (most recent call last):#012 File "/usr/lib/python2.7/site-
> packages/ovirt_hosted_engine_ha/agent/a
> gent.py", line 131, in _run_agent#012return action(he)#012 File
> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/agent.py",
> line 55, in action_proper#012return he.start_monitoring
> ()#012 File
> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py",
> line 432, in start_monitoring#012self._initialize_broker()#012 File
> "/usr/lib/python2.7/site-packages/
> ovirt_hosted_engine_ha/agent/hosted_engine.py", line 556, in
> _initialize_broker#012m.get('options', {}))#012 File
> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py",
> line 8
> 9, in start_monitor#012).format(t=type, o=options,
> e=e)#012RequestError: brokerlink - failed to start monitor via
> ovirt-ha-broker: [Errno 2] No such file or directory, [monitor: 'network',
> options:
> {'tcp_t_address': None, 'network_test': None, 'tcp_t_port': None, 'addr':
> '192.168.2.248'}]
> Feb 1 15:41:42 srv02 journal: ovirt-ha-agent
> ovirt_hosted_engine_ha.agent.agent.Agent
> ERROR Trying to restart agent
>
> In broker log:
> MainThread::WARNING::2020-02-01 15:43:35,167::storage_broker::
> 97::ovirt_hosted_engine_ha.broker.storage_broker.StorageBroker::(__init__)
> Can't connect vdsm storage: Command StorageDomain.getInfo with ar
> gs {'storagedomainID': 'bbdddea7-9cd6-41e7-ace5-fb9a6795caa8'} failed:
> (code=350, message=Error in storage domain action:
> (u'sdUUID=bbdddea7-9cd6-41e7-ace5-fb9a6795caa8',))
>
> In vdsm.lod
> 2020-02-01 15:44:19,930+0600 INFO (jsonrpc/0) [vdsm.api] FINISH
> getStorageDomainInfo error=[Errno 1] Operation not permitted
> from=::1,57528, task_id=40683f67-d7b0-4105-aab8-6338deb54b00 (api:52)
> 2020-02-01 15:44:19,930+0600 ERROR (jsonrpc/0) [storage.TaskManager.Task]
> (Task='40683f67-d7b0-4105-aab8-6338deb54b00') Unexpected error (task:875)
> Traceback (most recent call last):
> File "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 882,
> in _run
> return fn(*args, **kargs)
> File "", line 2, in getStorageDomainInfo
> File "/usr/lib/python2.7/site-packages/vdsm/common/api.py", line 50, in
> method
> ret = func(*args, **kwargs)
> File "/usr/lib/python2.7/site-packages/vdsm/storage/hsm.py", line 2753,
> in getStorageDomainInfo
> dom = self.validateSdUUID(sdUUID)
> File "/usr/lib/python2.7/site-packages/vdsm/storage/hsm.py", line 305,
> in validateSdUUID
> sdDom = sdCache.produce(sdUUID=sdUUID)
> File "/usr/lib/python2.7/site-packages/vdsm/storage/sdc.py", line 110,
> in produce
> domain.getRealDomain()
> File "/usr/lib/python2.7/site-packages/vdsm/storage/sdc.py", line 51,
> in getRealDomain
> return self._cache._realProduce(self._sdUUID)
> File "/usr/lib/python2.7/site-packages/vdsm/storage/sdc.py", line 134,
> in _realProduce
> domain = self._findDomain(sdUUID)
> File "/usr/lib/python2.7/site-packages/vdsm/storage/sdc.py", line 151,
> in _findDomain
> return findMethod(sdUUID)
> File "/usr/lib/python2.7/site-packages/vdsm/storage/nfsSD.py", line
> 145, in findDomain
> return NfsStorageDomain(NfsStorageDomain.findDomainPath(sdUUID))
> File "/usr/lib/python2.7/site-packages/vdsm/storage/fileSD.py", line
> 378, in __init__
> manifest.sdUUID, manifest.mountpoint)
> File "/usr/lib/python2.7/site-packages/vdsm/storage/fileSD.py", line
> 853, in _detect_block_size
> block_size = iop.probe_block_size(mountpoint)
> File "/usr/lib/python2.7/site-packages/vdsm/storage/outOfProcess.py",
> line 384, in probe_block_size
> return self._ioproc.probe_block_size(dir_path)
> File "/usr/lib/python2.7/site-packages/ioprocess/__init__.py", line
> 602, in probe_block_size
> "probe_block_size", {"dir": dir_path}, self.timeout)
> File "/usr/lib/python2.7/site-packages/ioprocess/__init__.py", line
> 448, in _sendCommand
> raise OSError(errcode, errstr)
> OSError: [Errno 1] Operation not permitted
> 2020-02-01 15:44:19,930+0600 INFO (jsonrpc/0) [storage.TaskManager.Task]
> (Task='40683f67-d7b0-4105-aab8-6338deb54b00') aborting: Task is aborted:
> u'[Errno 1] Operation not permitted' - code 100 (task:1
> 181)
> 2020-02-01 15:44:19,930+0600 ERROR (jsonrpc/0) [storage.Dispatcher] FINISH
> getStorageDomainInfo error=[Errno 1] Operation
[ovirt-users] Re: Can't connect vdsm storage: Command StorageDomain.getInfo with args failed: (code=350, message=Error in storage domain action
Working fine with 4.30.32-1 of course, sorry. ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/PABXTFHRCZE5AOQ2KUWQ7JEVXJRLZVW3/
[ovirt-users] Re: Can't connect vdsm storage: Command StorageDomain.getInfo with args failed: (code=350, message=Error in storage domain action
Htis issue can be resolve by downgrading of the packages: Installing : vdsm-api-4.30.32-1.el7.noarch 1/26 Installing : vdsm-common-4.30.32-1.el7.noarch 2/26 Installing : vdsm-yajsonrpc-4.30.32-1.el7.noarch 3/26 Installing : vdsm-network-4.30.32-1.el7.x86_64 4/26 Installing : vdsm-python-4.30.32-1.el7.noarch 5/26 Installing : vdsm-jsonrpc-4.30.32-1.el7.noarch 6/26 Installing : vdsm-http-4.30.32-1.el7.noarch 7/26 Installing : vdsm-hook-vmfex-dev-4.30.32-1.el7.noarch 8/26 Installing : vdsm-4.30.32-1.el7.x86_64 9/26 Installing : vdsm-gluster-4.30.32-1.el7.x86_64 10/26 Installing : vdsm-hook-ethtool-options-4.30.32-1.el7.noarch 11/26 Installing : vdsm-hook-fcoe-4.30.32-1.el7.noarch 12/26 Installing : vdsm-client-4.30.32-1.el7.noarch 13/26 Cleanup: vdsm-client-4.30.33-1.el7.noarch 14/26 Cleanup: vdsm-hook-ethtool-options-4.30.33-1.el7.noarch 15/26 Cleanup: vdsm-gluster-4.30.33-1.el7.x86_64 16/26 Cleanup: vdsm-hook-fcoe-4.30.33-1.el7.noarch 17/26 Cleanup: vdsm-hook-vmfex-dev-4.30.33-1.el7.noarch 18/26 Cleanup: vdsm-4.30.33-1.el7.x86_64 19/26 Cleanup: vdsm-jsonrpc-4.30.33-1.el7.noarch 20/26 Cleanup: vdsm-http-4.30.33-1.el7.noarch 21/26 Cleanup: vdsm-python-4.30.33-1.el7.noarch 22/26 Cleanup: vdsm-network-4.30.33-1.el7.x86_64 23/26 Cleanup: vdsm-common-4.30.33-1.el7.noarch 24/26 Cleanup: vdsm-api-4.30.33-1.el7.noarch
[ovirt-users] Re: Can't connect to storage
Hi Julio, please send engine and vdsm log. Thank you. Lucie On 3/24/19 3:05 PM, Julio Cesar Bustamante wrote: Hi everyone I hace a problem with ovirtmanager 4.2. in the nodes can't connect to storage. They show these messages. What can I do yo Solve it? ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/6LEJTKNVLE57LMA6XHKODBIP2RGJAHQJ/ -- Lucie Leistnerova Quality Engineer, QE Cloud, RHVM Red Hat EMEA IRC: lleistne @ #rhev-qe ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/ZJRKTY6WCF4IB7KCL656U5NUSYUKDGJN/
[ovirt-users] Re: Can't connect to storage
You can check if any hosts' network is out of sync. Also try ssh from engine to each host. Best Regards, Strahil NikolovOn Mar 24, 2019 16:05, Julio Cesar Bustamante wrote: > > Hi everyone > > I hace a problem with ovirtmanager 4.2. in the nodes can't connect to > storage. They show these messages. What can I do yo Solve it? > > > ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/VGBPIV24CN4JGKKRSRP6XTVZAPSVTKLJ/
