[ovirt-users] Re: Can't connect vdsm storage: Command StorageDomain.getInfo with args failed: (code=350, message=Error in storage domain action

2020-02-01 Thread asm
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

[ovirt-users] Re: Can't connect vdsm storage: Command StorageDomain.getInfo with args failed: (code=350, message=Error in storage domain action

2020-02-01 Thread Robert Webb
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:

[ovirt-users] Re: Can't connect vdsm storage: Command StorageDomain.getInfo with args failed: (code=350, message=Error in storage domain action

2020-02-01 Thread Nir Soffer
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:

[ovirt-users] Re: Can't connect vdsm storage: Command StorageDomain.getInfo with args failed: (code=350, message=Error in storage domain action

2020-02-01 Thread Amit Bawer
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

[ovirt-users] Re: Device /dev/sdb excluded by a filter.\n

2020-02-01 Thread Steve Watkins
After looking at this, I hit upon something. Each machine in this cluster has two drives -- a 500gb and a 1 tb one. Each machine I was installing to the 500gb drive (going to put in bigger drives, but this was what was laying around) I went through and looked at the machines, and the one

[ovirt-users] Re: Device /dev/sdb excluded by a filter.\n

2020-02-01 Thread Amit Bawer
Maybe information on this message thread could help: https://lists.ovirt.org/archives/list/users@ovirt.org/message/N7M57G7HC46NBQTX6T3KSVHEYV3IDDIP/ On Saturday, February 1, 2020, Steve Watkins wrote: > Since I managed to crash my last attempt at installing by uploading an > ISO, I wound up

[ovirt-users] Device /dev/sdb excluded by a filter.\n

2020-02-01 Thread Steve Watkins
Since I managed to crash my last attempt at installing by uploading an ISO, I wound up just reloading all the nodes and starting from scratch. Now one node gets "Device /dev/sdb excluded by a filter.\n" and fails when creating the volumes. Can't seem to get passed that -- the other machiens

[ovirt-users] Re: Can't connect vdsm storage: Command StorageDomain.getInfo with args failed: (code=350, message=Error in storage domain action

2020-02-01 Thread asm
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

[ovirt-users] Re: Can't connect vdsm storage: Command StorageDomain.getInfo with args failed: (code=350, message=Error in storage domain action

2020-02-01 Thread Amit Bawer
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.

[ovirt-users] Re: oVirt upgrade problems...

2020-02-01 Thread matteo fedeli
Ok, so, which is your hint? which log level? And next, which log can I start to see? ___ 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

[ovirt-users] Re: Gluster Heal Issue

2020-02-01 Thread Strahil Nikolov
On February 1, 2020 12:00:43 PM GMT+02:00, a...@pioner.kz wrote: >Hi! >I did it with working Gluster. Just copy missing files from one of the >host and start hesl volume after this. >But the main - i dont understand, why this is happening with this >issue. I saw this many times after maintanance

[ovirt-users] Re: Gluster Heal Issue

2020-02-01 Thread Strahil Nikolov
On February 1, 2020 10:53:59 AM GMT+02:00, Christian Reiss wrote: >Hey Strahil, > >thanks for your answer. > >On 01/02/2020 08:18, Strahil Nikolov wrote: >> There is an active thread in gluster-users , so it will be nice to >mention this there. >> >> About the sync, you can find the paths via:

[ovirt-users] Re: Can't connect vdsm storage: Command StorageDomain.getInfo with args failed: (code=350, message=Error in storage domain action

2020-02-01 Thread asm
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:

[ovirt-users] Re: Can't connect vdsm storage: Command StorageDomain.getInfo with args failed: (code=350, message=Error in storage domain action

2020-02-01 Thread asm
Htis issue can be resolve by downgrading of the packages: Installing : vdsm-api-4.30.32-1.el7.noarch 1/26 Installing :

[ovirt-users] Re: Ovirt-engine-ha cannot to see live status of Hosted Engine

2020-02-01 Thread asm
Hi! You was right. The problem was due to an error in the hosts file. The FQDN of engine has another IP in this file on this host from previous instalation. Thank you very muth. Please help me with my another question. I know that you can help me. ___

[ovirt-users] Re: Gluster Heal Issue

2020-02-01 Thread asm
Hi! I did it with working Gluster. Just copy missing files from one of the host and start hesl volume after this. But the main - i dont understand, why this is happening with this issue. I saw this many times after maintanance of one host, for example.

[ovirt-users] Can't connect vdsm storage: Command StorageDomain.getInfo with args failed: (code=350, message=Error in storage domain action

2020-02-01 Thread asm
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

[ovirt-users] Re: Gluster Heal Issue

2020-02-01 Thread Christian Reiss
Hey Strahil, thanks for your answer. On 01/02/2020 08:18, Strahil Nikolov wrote: There is an active thread in gluster-users , so it will be nice to mention this there. About the sync, you can find the paths via: 1. Mount mount -t glusterfs -o aux-gfid-mount vm1:test /mnt/testvol 2. Find