[ovirt-users] Re: not able to upload disks, iso - Connection to ovirt-imageio service has failed. Ensure that ovirt-engine certificate is registered as a valid CA in the browser.

2021-01-11 Thread Vojtech Juranek
On Monday, 11 January 2021 09:44:57 CET dhanaraj.ramesh--- via Users wrote:
> given recommendation is not working.

could you be more specific, what exactly doesn't work, what kind of error you 
got etc?

Thanks
Vojta

signature.asc
Description: This is a digitally signed message part.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/BNZ642XR3N7ZGZTCXUJVGMJK75IOIFNF/


[ovirt-users] Re: not able to upload disks, iso - Connection to ovirt-imageio service has failed. Ensure that ovirt-engine certificate is registered as a valid CA in the browser.

2021-01-08 Thread Vojtech Juranek
Hi,

> We are unning with 4.4.3.12-1.el8 version and so far working fine, but today
> users complained they are unable to upload new disks and upon checking
> found "Connection to ovirt-imageio service has failed. Ensure that
> ovirt-engine certificate is registered as a valid CA in the browser" during
> testing option. please help on this and if there is any temp solution is
> available share me the steps

if you want to upload imgaes from browser, you have to import certificates into 
the *browser*.
So follow the link, download the certificate and import it into the browser as 
a trusted. I.e. this
is related to browser configuration, not oVirt configuration. See [1, 2] for 
more details.

Alternatively, you can upload image using upload_disk example script from 
ovirt-engine-sdk [3], e.g.

curl -k 
"https://$ENGINE_URL/ovirt-engine/services/pki-resource?resource=ca-certificate=X509-PEM-CA;
 > cert.pem
./upload_disk.py --insecure --engine-url $ENGINE_URL --username 
admin@internal --password-file $PASSWD_FILE --disk-format raw --sd-name 
$STORAGE_DOMAIN_NAME -c cert.pem $PATH_TO_IMAGE

HTH
Vojta

[1] Browser configuration section in 
http://ovirt.github.io/ovirt-imageio/configuration.html
[2] https://www.ovirt.org/develop/release-management/features/infra/pki.html
[3] 
https://github.com/oVirt/ovirt-engine-sdk/blob/master/sdk/examples/upload_disk.py

signature.asc
Description: This is a digitally signed message part.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/UQNLKIAMIDEADBRYS7U3CTREKZRKECQC/


[ovirt-users] Re: Imageio Daemon not listening on port 54323

2020-10-13 Thread Vojtech Juranek
On úterý 13. října 2020 9:37:11 CEST Tim Bordemann wrote:
> > On 12. Oct 2020, at 12:15, Vojtech Juranek  wrote:
> > 
> > On pátek 9. října 2020 19:02:32 CEST tim-nospam--- via Users wrote:
> >> Hello.
> >> 
> >> After an upgrade I am not able to upload images anymore via the ovirt ui.
> >> When testing the connection, I always get the error message "Connection
> >> to
> >> ovirt-imageio-proxy service has failed. Make sure the service is
> >> installed,
> >> configured, and ovirt-engine certificate is registered as a valid CA in
> >> the
> >> browser.".
> >> 
> >> I found out that the imageio daemon doesn't listen on port 54323 anymore,
> >> so the browser can not connect to it. The daemon is configured to listen
> >> on port 54323 though:
> >> 
> >> # cat /etc/ovirt-imageio/conf.d/50-engine.conf
> >> [...]
> >> [remote]
> >> port = 54323
> >> [...]
> >> 
> >> The imageio daemon has been started successfully on the engine host as
> >> well
> >> as on the other hosts.
> >> 
> >> I am currently stuck, what should I do next?
> >> The ovirt version I am using is 4.4.
> > 
> > what is exact version of imageio? (rpm -qa|grep imageio)
> 
> # rpm -qa|grep imageio
> ovirt-engine-setup-plugin-imageio-4.4.2.6-1.el8.noarch
> ovirt-imageio-daemon-2.0.10-1.el8.x86_64
> ovirt-imageio-common-2.0.10-1.el8.x86_64
> ovirt-imageio-client-2.0.10-1.el8.x86_64
> 
> > On which port imageio listens? You can use e.g. netstat etc. Also plase
> > check imageio logs (/var/log/ovirt-imageio/daemon.log), what is there,
> > there shold
> > be something like this:
> # netstat -tulpn | grep 543
> tcp0  0 0.0.0.0:54322   0.0.0.0:*   LISTEN  
>2527872/platform-py tcp0  0 127.0.0.1:54324
> 0.0.0.0:*   LISTEN  2527872/platform-py
> > 2020-10-08 08:37:48,906 INFO(MainThread) [services] remote.service
> > listening on ('::', 54323)
> 
> 2020-10-09 17:46:38,216 INFO(MainThread) [server] Starting (pid=2527872,
> version=2.0.10) 2020-10-09 17:46:38,220 INFO(MainThread) [services]
> remote.service listening on ('0.0.0.0', 54322) 2020-10-09 17:46:38,221 INFO
>(MainThread) [services] control.service listening on ('127.0.0.1',
> 54324) 2020-10-09 17:46:38,227 INFO(MainThread) [server] Ready for
> requests
> 
> No entries for Port 54323 in the last 3 months. I found logentries in july
> though:
> 
> [root@helios ~]# cat /var/log/ovirt-imageio/daemon.log | grep 54323
> 2020-07-11 10:13:24,777 INFO(MainThread) [services] remote.service
> listening on ('::', 54323) [...]
> 2020-07-16 19:54:13,398 INFO(MainThread) [services] remote.service
> listening on ('::', 54323) 2020-07-16 19:54:36,715 INFO(MainThread)
> [services] remote.service listening on ('::', 54323)
> > Also, please check if there are any other config files (*.conf) in
> > /etc/ovirt- imageio/conf.d or in /usr/lib/ovirt-imageio/conf.d
> 
> I have, but I couldn't find anything interesting in those two files:
> 
> # ls -l /etc/ovirt-imageio/conf.d/
> total 8
> -rw-r--r--. 1 root root 1458 Oct  9 17:54 50-engine.conf
> -rw-r--r--. 1 root root 1014 Sep 15 11:16 50-vdsm.conf

50-vdsm.conf overwrites 50-engine.conf (later config taken alphabetically 
overwrites previous config if there is any).

If you don't use engine as a host at the same time, stop an uninstall vdsm from 
engine (should remove also 50-vdsm.conf) and restart ovirt-imageio service.

If you use engine as a host at the same time, note that this is unsupported. 
However, there were some patches in this area recently, but they are not 
released yet AFAICT. See [1, 2] for more details.

[1] https://bugzilla.redhat.com/1871348
[2] 
https://lists.ovirt.org/archives/list/users@ovirt.org/thread/W4OTINLXYDWG3YSF2OUQU3NW3ADRPGUR/

> The imageio daemon should listen on Port 54323:
> 
> 
> # /etc/ovirt-imageio/conf.d/50-engine.conf
> [...]
> [remote]
> # Port cannot be changed as it's currently hardcoded in engine code.
> port = 54323
> [...]
> 
> >> There is one machine running the ovirt
> >> engine and there are 2 additional hosts. The OS on the machines is Centos
> >> 8.
> >> 
> >> 
> >> 
> >> 
> >> Thank you,
> >> Tim
> >> ___
> >> Users mailing list -- users@ovirt.org
> >> To unsubscribe send an email to users-le...@ovirt.org
> >> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> >> oVirt 

[ovirt-users] Re: Imageio Daemon not listening on port 54323

2020-10-12 Thread Vojtech Juranek
On pátek 9. října 2020 19:02:32 CEST tim-nospam--- via Users wrote:
> Hello.
> 
> After an upgrade I am not able to upload images anymore via the ovirt ui.
> When testing the connection, I always get the error message "Connection to
> ovirt-imageio-proxy service has failed. Make sure the service is installed,
> configured, and ovirt-engine certificate is registered as a valid CA in the
> browser.".
 
> I found out that the imageio daemon doesn't listen on port 54323 anymore, so
> the browser can not connect to it. The daemon is configured to listen on
> port 54323 though:
 
> # cat /etc/ovirt-imageio/conf.d/50-engine.conf
> [...]
> [remote]
> port = 54323
> [...]
> 
> The imageio daemon has been started successfully on the engine host as well
> as on the other hosts.
 
> I am currently stuck, what should I do next?
> The ovirt version I am using is 4.4.

what is exact version of imageio? (rpm -qa|grep imageio)

On which port imageio listens? You can use e.g. netstat etc. Also plase check 
imageio logs (/var/log/ovirt-imageio/daemon.log), what is there, there shold 
be something like this:

2020-10-08 08:37:48,906 INFO(MainThread) [services] remote.service 
listening on ('::', 54323)


Also, please check if there are any other config files (*.conf) in /etc/ovirt-
imageio/conf.d or in /usr/lib/ovirt-imageio/conf.d

> There is one machine running the ovirt
> engine and there are 2 additional hosts. The OS on the machines is Centos
> 8.




> Thank you,
> Tim
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/ List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/GWIVRHYHNGUVJ
> NSQTYCDQBOG6VFXCZPB/



signature.asc
Description: This is a digitally signed message part.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/KTZ3GQYZD5JREK75DP3LVOEJFYOL3ZR5/


[ovirt-users] Re: oVirt - vdo: ERROR - Device /dev/sd excluded by a filter

2020-09-21 Thread Vojtech Juranek
On sobota 19. září 2020 5:58:43 CEST Jeremey Wise wrote:
> [image: image.png]
> 
> vdo: ERROR - Device /dev/sdc excluded by a filter
> 
> [image: image.png]

when this error happens? When you install ovirt HCI?


> Where is getting this filter.
> I have done gdisk /dev/sdc ( new 1TB Drive) and shows no partition.  I even
> did a full dd if=/dev/zero   and no change.

it's installed by vdsm to exclude ovirt devices from common use



signature.asc
Description: This is a digitally signed message part.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/OK6TE456D37ZHGVT7XBDFLKLT6EH4HAM/


[ovirt-users] Re: Bad volume specification

2020-09-18 Thread Vojtech Juranek
On čtvrtek 17. září 2020 16:07:16 CEST Facundo Garat wrote:
> I don't think so, We have bigger LUNs assigned so if that were the case we
> would have lost access to many LVs.
> 
> Do I have a way to manually query the LVs content to find out if it's still
> there?.

you can ssh to a host and check LV

lvs 55327311-e47c-46b5-b168-258c5924757b/bd714f21-8eed-43ee-a2d4-3d2ef1ee4c3f 
--config 'devices {filter=["a|.*|"]}'

and path

/rhev/data-center/mnt/blockSD/55327311-e47c-46b5-b168-258c5924757b/images/f5bd2e15-a1ab-4724-883a-988b4dc7985b/bd714f21-8eed-43ee-a2d4-3d2ef1ee4c3f

If path exists, you can run qemu-img info on it.

Looking more into vdsm log, it seems that volume 
bd714f21-8eed-43ee-a2d4-3d2ef1ee4c3f
is not part of the disk image (f5bd2e15-a1ab-4724-883a-988b4dc7985b).

Unfortunately no idea how it got into such state, maybe engine DB is out of 
sync with storage?
(you can check the DB on engine, by connecting to postgres DB "engine" and 
running 
select image_group_id from images where 
image_guid='bd714f21-8eed-43ee-a2d4-3d2ef1ee4c3f';
to see to what image this volume belong to according to engine DB)

> On Thu, Sep 17, 2020 at 10:55 AM Vojtech Juranek 
> 
> wrote:
> > On čtvrtek 17. září 2020 14:30:12 CEST Facundo Garat wrote:
> > > Hi Vojtech,
> > > 
> > >   find the log attached.
> > 
> > thanks. It fails as one of the image volumes
> > (6058a880-9ee6-4c57-9db0-5946c6dab676) is now available/present on the
> > storage. You can check manually if there's such LV, but it's not very
> > likely.
> > Didn't you by accident remove the volume?
> > 
> > > On Thu, Sep 17, 2020 at 4:27 AM Vojtech Juranek 
> > 
> > wrote:
> > > > Hi,
> > > > could you please send us also relevant part of vdsm log
> > > > (/var/log/vdsm/
> > > > vdsm.log)?
> > > > Thanks
> > > > Vojta
> > > > 
> > > > > The VM has one snapshot which I can't delete because it shows a
> > 
> > similar
> > 
> > > > > error. That doesn't allow me to attach the disks to another VM. This
> > 
> > VM
> > 
> > > > > will boot ok if the disks are deactivated.
> > > > > 
> > > > > Find the engine.log attached.
> > > > > 
> > > > > The steps associated with the engine log:
> > > > >- The VM is on booted from CD with all disks deactivated
> > > > >- Try to attach all three disks (fail!)
> > > > >- Power off the VM
> > > > >- Activate all three disks
> > > > >- Try to delete the snapshot.
> > > > > 
> > > > > Thanks.
> > > > > 
> > > > > On Wed, Sep 16, 2020 at 9:35 AM Ahmad Khiet 
> > 
> > wrote:
> > > > > > Hi,
> > > > > > 
> > > > > > can you please attach the engine log? what steps did you make
> > 
> > before
> > 
> > > > > > this error is shown? did you tried to create a snapshot and failed
> > > > 
> > > > before
> > > > 
> > > > > > On Wed, Sep 16, 2020 at 7:49 AM Strahil Nikolov via Users
> > > > > > 
> > > > > > 
> > > > > > wrote:
> > > > > >> What happens if you create another VM and attach the disks to it
> > > > > >> ?
> > > > > >> Does it boot properly ?
> > > > > >> 
> > > > > >> Best Regards,
> > > > > >> Strahil Nikolov
> > > > > >> 
> > > > > >> 
> > > > > >> 
> > > > > >> 
> > > > > >> 
> > > > > >> 
> > > > > >> В сряда, 16 септември 2020 г., 02:19:26 Гринуич+3, Facundo Garat
> > > > > >> <
> > > > > >> fga...@gmail.com> написа:
> > > > > >> 
> > > > > >> 
> > > > > >> 
> > > > > >> 
> > > > > >> 
> > > > > >> 
> > > > > >> Hi all,
> > > > > >> 
> > > > > >>  I'm having some issues with one VM. The VM won't start and it's
> > > > 
> > > > showing
> > > > 
> > > > > >> problems with the virtual disks so I started the VM without any
> > 
> > disks
> > 
> > > &

[ovirt-users] Re: Bad volume specification

2020-09-17 Thread Vojtech Juranek
On čtvrtek 17. září 2020 14:30:12 CEST Facundo Garat wrote:
> Hi Vojtech,
>   find the log attached.

thanks. It fails as one of the image volumes 
(6058a880-9ee6-4c57-9db0-5946c6dab676) is now available/present on the 
storage. You can check manually if there's such LV, but it's not very likely. 
Didn't you by accident remove the volume?

> On Thu, Sep 17, 2020 at 4:27 AM Vojtech Juranek  wrote:
> > Hi,
> > could you please send us also relevant part of vdsm log (/var/log/vdsm/
> > vdsm.log)?
> > Thanks
> > Vojta
> > 
> > > The VM has one snapshot which I can't delete because it shows a similar
> > > error. That doesn't allow me to attach the disks to another VM. This VM
> > > will boot ok if the disks are deactivated.
> > > 
> > > Find the engine.log attached.
> > > 
> > > The steps associated with the engine log:
> > >- The VM is on booted from CD with all disks deactivated
> > >- Try to attach all three disks (fail!)
> > >- Power off the VM
> > >- Activate all three disks
> > >- Try to delete the snapshot.
> > > 
> > > Thanks.
> > > 
> > > On Wed, Sep 16, 2020 at 9:35 AM Ahmad Khiet  wrote:
> > > > Hi,
> > > > 
> > > > can you please attach the engine log? what steps did you make before
> > > > this error is shown? did you tried to create a snapshot and failed
> > 
> > before
> > 
> > > > On Wed, Sep 16, 2020 at 7:49 AM Strahil Nikolov via Users
> > > > 
> > > > 
> > > > wrote:
> > > >> What happens if you create another VM and attach the disks to it ?
> > > >> Does it boot properly ?
> > > >> 
> > > >> Best Regards,
> > > >> Strahil Nikolov
> > > >> 
> > > >> 
> > > >> 
> > > >> 
> > > >> 
> > > >> 
> > > >> В сряда, 16 септември 2020 г., 02:19:26 Гринуич+3, Facundo Garat <
> > > >> fga...@gmail.com> написа:
> > > >> 
> > > >> 
> > > >> 
> > > >> 
> > > >> 
> > > >> 
> > > >> Hi all,
> > > >> 
> > > >>  I'm having some issues with one VM. The VM won't start and it's
> > 
> > showing
> > 
> > > >> problems with the virtual disks so I started the VM without any disks
> > 
> > and
> > 
> > > >> trying to hot adding the disk and that's fail too.
> > > >> 
> > > >>  The servers are connected thru FC, all the other VMs are working
> > 
> > fine.
> > 
> > > >>   Any ideas?.
> > > >> 
> > > >> Thanks!!
> > > >> 
> > > >> PS: The engine.log is showing this:
> > > >> 2020-09-15 20:10:37,926-03 INFO
> > > >> 
> > > >>  [org.ovirt.engine.core.bll.storage.disk.HotPlugDiskToVmCommand]
> > 
> > (default
> > 
> > > >> task-168) [dd72c8e8-cdbe-470f-8e32-b3d14b96f37a] Lock Acquired to
> > 
> > object
> > 
> > 'EngineLock:{exclusiveLocks='[f5bd2e15-a1ab-4724-883a-988b4dc7985b=DISK]'
> > 
> > > >> ,
> > > >> sharedLocks='[71db02c2-df29-4552-8a7e-cb8bb429a2ac=VM]'}'
> > > >> 2020-09-15 20:10:38,082-03 INFO
> > > >> 
> > > >>  [org.ovirt.engine.core.bll.storage.disk.HotPlugDiskToVmCommand]
> > > >> 
> > > >> (EE-ManagedThreadFactory-engine-Thread-36528)
> > > >> [dd72c8e8-cdbe-470f-8e32-b3d14b96f37a] Running command:
> > > >> HotPlugDiskToVmCommand internal: false. Entities affected :  ID:
> > > >> 71db02c2-df29-4552-8a7e-cb8bb429a2ac Type: VMAction group
> > > >> CONFIGURE_VM_STORAGE with role type USER
> > > >> 2020-09-15 20:10:38,117-03 INFO
> > > >> 
> > > >>  [org.ovirt.engine.core.vdsbroker.vdsbroker.HotPlugDiskVDSCommand]
> > > >> 
> > > >> (EE-ManagedThreadFactory-engine-Thread-36528)
> > > >> [dd72c8e8-cdbe-470f-8e32-b3d14b96f37a] START,
> > > >> HotPlugDiskVDSCommand(HostName = nodo2,
> > 
> > HotPlugDiskVDSParameters:{hostId='1c24c269-76c3-468d-a7ce-d0332beb7aef',
> > 
> > > >> vmId='71db02c2-df29-4552-8a7e-cb8bb429a2ac',
> > > >> diskId='f5bd2e15-a1ab-4724-883a-988b4dc7985

[ovirt-users] Re: Bad volume specification

2020-09-17 Thread Vojtech Juranek
Hi,
could you please send us also relevant part of vdsm log (/var/log/vdsm/
vdsm.log)?
Thanks
Vojta


> The VM has one snapshot which I can't delete because it shows a similar
> error. That doesn't allow me to attach the disks to another VM. This VM
> will boot ok if the disks are deactivated.
> 
> Find the engine.log attached.
> 
> The steps associated with the engine log:
> 
>- The VM is on booted from CD with all disks deactivated
>- Try to attach all three disks (fail!)
>- Power off the VM
>- Activate all three disks
>- Try to delete the snapshot.
> 
> Thanks.
> 
> On Wed, Sep 16, 2020 at 9:35 AM Ahmad Khiet  wrote:
> > Hi,
> > 
> > can you please attach the engine log? what steps did you make before
> > this error is shown? did you tried to create a snapshot and failed before
> > 
> > 
> > On Wed, Sep 16, 2020 at 7:49 AM Strahil Nikolov via Users
> > 
> > 
> > wrote:
> >> What happens if you create another VM and attach the disks to it ?
> >> Does it boot properly ?
> >> 
> >> Best Regards,
> >> Strahil Nikolov
> >> 
> >> 
> >> 
> >> 
> >> 
> >> 
> >> В сряда, 16 септември 2020 г., 02:19:26 Гринуич+3, Facundo Garat <
> >> fga...@gmail.com> написа:
> >> 
> >> 
> >> 
> >> 
> >> 
> >> 
> >> Hi all,
> >> 
> >>  I'm having some issues with one VM. The VM won't start and it's showing
> >> 
> >> problems with the virtual disks so I started the VM without any disks and
> >> trying to hot adding the disk and that's fail too.
> >> 
> >>  The servers are connected thru FC, all the other VMs are working fine.
> >>  
> >>   Any ideas?.
> >> 
> >> Thanks!!
> >> 
> >> PS: The engine.log is showing this:
> >> 2020-09-15 20:10:37,926-03 INFO
> >> 
> >>  [org.ovirt.engine.core.bll.storage.disk.HotPlugDiskToVmCommand] (default
> >> 
> >> task-168) [dd72c8e8-cdbe-470f-8e32-b3d14b96f37a] Lock Acquired to object
> >> 'EngineLock:{exclusiveLocks='[f5bd2e15-a1ab-4724-883a-988b4dc7985b=DISK]'
> >> ,
> >> sharedLocks='[71db02c2-df29-4552-8a7e-cb8bb429a2ac=VM]'}'
> >> 2020-09-15 20:10:38,082-03 INFO
> >> 
> >>  [org.ovirt.engine.core.bll.storage.disk.HotPlugDiskToVmCommand]
> >> 
> >> (EE-ManagedThreadFactory-engine-Thread-36528)
> >> [dd72c8e8-cdbe-470f-8e32-b3d14b96f37a] Running command:
> >> HotPlugDiskToVmCommand internal: false. Entities affected :  ID:
> >> 71db02c2-df29-4552-8a7e-cb8bb429a2ac Type: VMAction group
> >> CONFIGURE_VM_STORAGE with role type USER
> >> 2020-09-15 20:10:38,117-03 INFO
> >> 
> >>  [org.ovirt.engine.core.vdsbroker.vdsbroker.HotPlugDiskVDSCommand]
> >> 
> >> (EE-ManagedThreadFactory-engine-Thread-36528)
> >> [dd72c8e8-cdbe-470f-8e32-b3d14b96f37a] START,
> >> HotPlugDiskVDSCommand(HostName = nodo2,
> >> HotPlugDiskVDSParameters:{hostId='1c24c269-76c3-468d-a7ce-d0332beb7aef',
> >> vmId='71db02c2-df29-4552-8a7e-cb8bb429a2ac',
> >> diskId='f5bd2e15-a1ab-4724-883a-988b4dc7985b', addressMap='null'}), log
> >> id:
> >> f57ee9e
> >> 2020-09-15 20:10:38,125-03 INFO
> >> 
> >>  [org.ovirt.engine.core.vdsbroker.vdsbroker.HotPlugDiskVDSCommand]
> >> 
> >> (EE-ManagedThreadFactory-engine-Thread-36528)
> >> [dd72c8e8-cdbe-470f-8e32-b3d14b96f37a] Disk hot-plug:  >> encoding="UTF-8"?>
> >> 
> >>   
> >>   
> >> 
> >> 
> >>   
> >>>> 
> >> dev="/rhev/data-center/mnt/blockSD/55327311-e47c-46b5-b168-258c5924757b/i
> >> mages/f5bd2e15-a1ab-4724-883a-988b4dc7985b/bd714f21-8eed-43ee-a2d4-3d2ef1
> >> ee4c3f">>> 
> >> 
> >>   
> >>   
> >>>> 
> >> cache="none"/>
> >> 
> >>   
> >>   f5bd2e15-a1ab-4724-883a-988b4dc7985b
> >> 
> >> 
> >>   
> >>   
> >>   http://ovirt.org/vm/1.0;>
> >>   
> >> 
> >> 
> >>   
> >> 
> >> 0001-0001-0001-0001-0311
> >> 
> >> bd714f21-8eed-43ee-a2d4-3d2ef1ee4c3f >> D>
> >> 
> >> f5bd2e15-a1ab-4724-883a-988b4dc7985b
> >> 
> >> 55327311-e47c-46b5-b168-258c5924757b >> D>
> >> 
> >>   
> >> 
> >> 
> >>   
> >>   
> >> 
> >> 
> >> 
> >> 2020-09-15 20:10:38,289-03 ERROR
> >> [org.ovirt.engine.core.vdsbroker.vdsbroker.HotPlugDiskVDSCommand]
> >> (EE-ManagedThreadFactory-engine-Thread-36528)
> >> [dd72c8e8-cdbe-470f-8e32-b3d14b96f37a] Failed in 'HotPlugDiskVDS' method
> >> 2020-09-15 20:10:38,295-03 ERROR
> >> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> >> (EE-ManagedThreadFactory-engine-Thread-36528)
> >> [dd72c8e8-cdbe-470f-8e32-b3d14b96f37a] EVENT_ID:
> >> VDS_BROKER_COMMAND_FAILURE(10,802), VDSM nodo2 command HotPlugDiskVDS
> >> failed: General Exception: ("Bad volume specification {'device': 'disk',
> >> 'type': 'disk', 'diskType': 'block', 'specParams': {}, 'alias':
> >> 'ua-f5bd2e15-a1ab-4724-883a-988b4dc7985b', 'domainID':
> >> '55327311-e47c-46b5-b168-258c5924757b', 'imageID':
> >> 'f5bd2e15-a1ab-4724-883a-988b4dc7985b', 'poolID':
> >> '0001-0001-0001-0001-0311', 'volumeID':
> >> 'bd714f21-8eed-43ee-a2d4-3d2ef1ee4c3f', 'path':
> >> '/rhev/data-center/mnt/blockSD/55327311-e47c-46b5-b168-258c5924757b/image
> >> 

[ovirt-users] Re: Storage Domain won't activate

2020-09-04 Thread Vojtech Juranek
On čtvrtek 3. září 2020 22:49:17 CEST Gillingham, Eric J (US 393D) via Users 
wrote:
> I recently removed a host from my cluster to upgrade it to 4.4, after I
> removed the host from the datacenter VMs started to pause on the second
> system they all migrated to. Investigating via the engine showed the
> storage domain was showing as "unknown", when I try to activate it via the
> engine it cycles to locked then to unknown again.
 
> /var/log/sanlock.log contains a repeating:
> add_lockspace
> e1270474-108c-4cae-83d6-51698cffebbf:1:/dev/e1270474-108c-4cae-83d6-51698cf
> febbf/ids:0 conflicts with name of list1 s1
> e1270474-108c-4cae-83d6-51698cffebbf:3:/dev/e1270474-108c-4cae-83d6-51698cf
> febbf/ids:0

how do you remove the fist host, did you put it into maintenance first? I 
wonder, how this situation (two lockspaces with conflicting names) can occur.

You can try to re-initialize the lockspace directly using sanlock command (see 
man sanlock), but it would be good to understand the situation first.


> 
> vdsm.log contains these (maybe related) snippets:
> ---
> 2020-09-03 20:19:53,483+ INFO  (jsonrpc/6) [vdsm.api] FINISH
> getAllTasksStatuses error=Secured object is not in safe state
> from=:::137.79.52.43,36326, flow_id=18031a91,
> task_id=8e92f059-743a-48c8-aa9d-e7c4c836337b (api:52)
 2020-09-03
> 20:19:53,483+ ERROR (jsonrpc/6) [storage.TaskManager.Task]
> (Task='8e92f059-743a-48c8-aa9d-e7c4c836337b') 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 getAllTasksStatuses
>   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 2201, in
> getAllTasksStatuses
 allTasksStatus = self._pool.getAllTasksStatuses()
>   File "/usr/lib/python2.7/site-packages/vdsm/storage/securable.py", line
> 77, in wrapper
 raise SecureError("Secured object is not in safe state")
> SecureError: Secured object is not in safe state
> 2020-09-03 20:19:53,483+ INFO  (jsonrpc/6) [storage.TaskManager.Task]
> (Task='8e92f059-743a-48c8-aa9d-e7c4c836337b') aborting: Task is aborted:
> u'Secured object is not in safe state' - code 100 (task:1181)
 2020-09-03
> 20:19:53,483+ ERROR (jsonrpc/6) [storage.Dispatcher] FINISH
> getAllTasksStatuses error=Secured object is not in safe state
> (dispatcher:87) Traceback (most recent call last):
>   File "/usr/lib/python2.7/site-packages/vdsm/storage/dispatcher.py", line
> 74, in wrapper
 result = ctask.prepare(func, *args, **kwargs)
>   File "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 108, in
> wrapper
 return m(self, *a, **kw)
>   File "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 1189,
> in prepare
 raise self.error
> SecureError: Secured object is not in safe state
> ---
> 2020-09-03 20:44:23,252+ INFO  (tasks/2)
> [storage.ThreadPool.WorkerThread] START task
> 76415a77-9d29-4b72-ade1-53207cfc503b (cmd= >, args=None) (thre
> adPool:208)
> 2020-09-03 20:44:23,266+ INFO  (tasks/2) [storage.SANLock] Acquiring
> host id for domain e1270474-108c-4cae-83d6-51698cffebbf (id=1, wait=True)
> (clusterlock:313)
 2020-09-03 20:44:23,267+ ERROR (tasks/2)
> [storage.TaskManager.Task] (Task='76415a77-9d29-4b72-ade1-53207cfc503b')
> 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 "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 336, in
> run
 return self.cmd(*self.argslist, **self.argsdict)
>   File "/usr/lib/python2.7/site-packages/vdsm/storage/sp.py", line 317, in
> startSpm
 self.masterDomain.acquireHostId(self.id)
>   File "/usr/lib/python2.7/site-packages/vdsm/storage/sd.py", line 957, in
> acquireHostId
 self._manifest.acquireHostId(hostId, wait)
>   File "/usr/lib/python2.7/site-packages/vdsm/storage/sd.py", line 501, in
> acquireHostId
 self._domainLock.acquireHostId(hostId, wait)
>   File "/usr/lib/python2.7/site-packages/vdsm/storage/clusterlock.py", line
> 344, in acquireHostId
 raise se.AcquireHostIdFailure(self._sdUUID, e)
> AcquireHostIdFailure: Cannot acquire host id:
> ('e1270474-108c-4cae-83d6-51698cffebbf', SanlockException(22, 'Sanlock
> lockspace add failure', 'Invalid argument'))
 ---
> 
> Another symptom is in the hosts view of the engine SPM bounces between
> "Normal" and "Contending". When it's Normal if I select Management ->
> Select as SPM I get "Error while executing action: Cannot force select SPM.
> Unknown Data Center status."
 
> I've tried rebooting the one remaining host in the cluster no to avail,
> hosted-engine --reinitialize-lockspace also seems to not solve the issue.
 
> 
> I'm kind of stumped as to what else to try, would appreciate any guidance on
> how to resolve this.
 
> Thank 

[ovirt-users] Re: HA Storage options

2020-08-19 Thread Vojtech Juranek
On úterý 18. srpna 2020 1:37:09 CEST David White via Users wrote:
> Hi,
> I started an email thread a couple months ago, and felt like I got some
> great feedback and suggestions on how to best setup an oVirt cluster.
> Thanks for your responses thus far.My goal is to take a total of 3-4
> servers that I can use for both the storage and the virtualization, and I
> want both to be highly available. 
> 
> You guys told me about oVirt Hyperconverged with Gluster, and that seemed
> like a great option. However, I'm concerned that this may not actually be
> the best approach. I've spoken with multiple people at Red Hat who I have a
> relationship with (outside of the context of the project I'm working on
> here), and all of them have indicated to me that Gluster is being
> deprecated, and that most of the engineering focus these days is on Ceph. I
> was also told by a Solutions Architect who has extensive experience with
> RHV that the hyperconverged clusters he used to build would always give him
> problems.
> 
> Does oVirt support DRBD or Ceph storage? From what I can find, I think that
> the answer to both of those is, sadly, no.

ceph (and anything supported by cindelib) is available via Managed block 
storage:

https://www.ovirt.org/develop/release-management/features/storage/cinderlib-integration.html


> So now I'm thinking about switching gears, and going with iSCSI instead. 
> But I'm still trying to think about the best way to replicate the storage,
> and possibly use multipathing so that it will be HA for the VMs that rely
> on it.
> 
> Has anyone else experienced problems with the Gluster hyperconverged
> solution? Am I overthinking this whole thing, and am I being too paranoid?
> Is it possible to setup some sort of software-RAID with multiple iSCSI
> targets? 
> 
> As an aside, I now have a machine that I was planning to begin doing some
> testing and practicing with. Previous to my conversations with the folks at
> Red Hat, I was planning on doing some initial testing and config with this
> server before purchasing another 2-3 servers to build the hyperconverged
> cluster.
> 
> Sent with ProtonMail Secure Email.



signature.asc
Description: This is a digitally signed message part.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/DFLKXVLMPN4ZTPVQJXDB33XZCABD3JR2/


[ovirt-users] Re: Ovirt fails to retrieve iSCSI targets during installation

2020-06-18 Thread Vojtech Juranek
> "port\": \"3260,3260\"

this looks strange. Did you specify port correctly?



signature.asc
Description: This is a digitally signed message part.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/RHGFZ5J5HK7DBVD5NONCCJZFFMDTFD6Y/


[ovirt-users] Re: ovirt imageio problem...

2020-06-01 Thread Vojtech Juranek
> I tried the same to perform the upload ignoring the error, the ISO was in
> paused state,

have you imported the certificates? If you click on test connection button in 
upload dialogue, does it work?

If so, please file a bug and attach vdsm logs and imageio logs (/var/log/
ovirt-imageio/daemon.log) both from engine and host.

> I clicked to delete it. The result? iso loaded! How is it
> possible?

this looks like a bug, if you click on delete, it should delete the image

signature.asc
Description: This is a digitally signed message part.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/FOWFP7QAQMBC6LA44VUCSRBU64OSAHI2/


[ovirt-users] Re: ovirt imageio problem...

2020-06-01 Thread Vojtech Juranek
On sobota 30. května 2020 19:59:40 CEST matteo fedeli wrote:
> Hi! I' installed CentOS 8 and ovirt package following this step:
> 
> systemctl enable --now cockpit.socket
> yum install https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm
> yum module -y enable javapackages-tools
> yum module -y enable pki-deps
> yum module -y enable postgresql:12
> yum -y install glibc-locale-source glibc-langpack-en
> localedef -v -c -i en_US -f UTF-8 en_US.UTF-8
> yum update
> yum install ovirt-engine
> engine-setup (by keeping all default)
> 
> It's possible ovirt-imageio-proxy service is not installed? 

yes, imageio-proxy was replaced by imageio-daemon is not installed any more. 
Daemon now takes all proxy responsibilities.

signature.asc
Description: This is a digitally signed message part.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/4HJDFJUHWSZXTGWGNHH3PDMK3MA65Z7O/


[ovirt-users] Re: Can anyone explain what gluster 4k support is?

2020-03-17 Thread Vojtech Juranek
> Is there performance improvements using larger block size?

yes, it *should* give you better performance

> On Tue, Mar 17, 2020 at 5:29 AM Vojtech Juranek  wrote:
> > On pondělí 16. března 2020 22:53:32 CET Strahil Nikolov wrote:
> > > On March 16, 2020 11:08:16 PM GMT+02:00, Vojtech Juranek
> > 
> >  wrote:
> > > >On středa 11. března 2020 21:13:13 CET Jayme wrote:
> > > >> I noticed Gluster 4k support mentioned in recent oVirt release notes.
> > > >
> > > >Can
> > > >
> > > >> anyone explain what this is about?
> > > >
> > > >before we supported only disks with block size 512 B. Now, we support
> > > >also
> > > >disks with 4 kB (aka 4k), for now only on Gluster SD. If you want to
> > > >learn more about
> > > >this feature, you can check slides [1] and I noticed that videos
> > > >recording of
> > > >Nir's talk he had on Fosdem is already available, so you can watch
> > > >whole
> > > >talk [2].
> > > >
> > > >Vojta
> > > >
> > > >[1]
> > 
> > https://docs.google.com/presentation/d/1ClLMZ4XAb8CPhYOw6mNpv0va5JWcAgpyFb
> > J
> > 
> > > >n-Bml_aY/ [2] https://video.fosdem.org/2020/H.1309/vai_ovirt_4k.webm
> > > 
> > > Can I switch off VDO's 512byte emulation ?
> > 
> > yes, now Gluster SD should work without 512 block size
> > emulation___
> > Users mailing list -- users@ovirt.org
> > To unsubscribe send an email to users-le...@ovirt.org
> > Privacy Statement: https://www.ovirt.org/privacy-policy.html
> > oVirt Code of Conduct:
> > https://www.ovirt.org/community/about/community-guidelines/
> > List Archives:
> > https://lists.ovirt.org/archives/list/users@ovirt.org/message/LEG5DXY3A5HS
> > ABLDHQAO2M53G3SC4E2U/



signature.asc
Description: This is a digitally signed message part.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/7M2RTTGZUWNRP2YOMPP6JVBY5JGYWC3R/


[ovirt-users] Re: Can anyone explain what gluster 4k support is?

2020-03-17 Thread Vojtech Juranek
On pondělí 16. března 2020 22:53:32 CET Strahil Nikolov wrote:
> On March 16, 2020 11:08:16 PM GMT+02:00, Vojtech Juranek 
 wrote:
> >On středa 11. března 2020 21:13:13 CET Jayme wrote:
> >> I noticed Gluster 4k support mentioned in recent oVirt release notes.
> >
> >Can
> >
> >> anyone explain what this is about?
> >
> >before we supported only disks with block size 512 B. Now, we support
> >also
> >disks with 4 kB (aka 4k), for now only on Gluster SD. If you want to
> >learn more about
> >this feature, you can check slides [1] and I noticed that videos
> >recording of
> >Nir's talk he had on Fosdem is already available, so you can watch
> >whole
> >talk [2].
> >
> >Vojta
> >
> >[1]
> >https://docs.google.com/presentation/d/1ClLMZ4XAb8CPhYOw6mNpv0va5JWcAgpyFbJ
> >n-Bml_aY/ [2] https://video.fosdem.org/2020/H.1309/vai_ovirt_4k.webm
> 
> Can I switch off VDO's 512byte emulation ?

yes, now Gluster SD should work without 512 block size emulation

signature.asc
Description: This is a digitally signed message part.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/LEG5DXY3A5HSABLDHQAO2M53G3SC4E2U/


[ovirt-users] Re: Can anyone explain what gluster 4k support is?

2020-03-16 Thread Vojtech Juranek
On středa 11. března 2020 21:13:13 CET Jayme wrote:
> I noticed Gluster 4k support mentioned in recent oVirt release notes. Can
> anyone explain what this is about?

before we supported only disks with block size 512 B. Now, we support also 
disks with 4 kB (aka 4k), for now only on Gluster SD. If you want to learn more 
about
this feature, you can check slides [1] and I noticed that videos recording of
Nir's talk he had on Fosdem is already available, so you can watch whole
talk [2].

Vojta

[1] 
https://docs.google.com/presentation/d/1ClLMZ4XAb8CPhYOw6mNpv0va5JWcAgpyFbJn-Bml_aY/
[2] https://video.fosdem.org/2020/H.1309/vai_ovirt_4k.webm

signature.asc
Description: This is a digitally signed message part.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/J5ZVKMKLCZP77CYUSPR53TITX5FDYQDH/


[ovirt-users] Re: oVirt 4.4.0 Alpha release refresh is now available for testing

2020-03-16 Thread Vojtech Juranek
On pondělí 16. března 2020 9:32:53 CET you wrote:
> On Mon, Mar 16, 2020 at 2:37 AM Sakari Poussa  wrote:
> > Hi,
> > 
> > The pre-release seems to be missing the ovirt-imageio-proxy.
> > 
> > Why is that? How can one import a (non-openstack glance) template to the
> > system? Both UI and ovirt.image-template ansible role seems to require
> > it.
> The project is working on getting rid of the duplications between the
> daemon and the proxy, and have a single program doing both functions.

correct, in the future we want only daemon module and remove proxy completely 
as it's not PY3 ready

> Not sure about current status, adding Vojtech.

WIP, we had some more urgent issue to work on, but I'm returning back to this 
now

> > Thanks, Sakari
> > 
> > On Mon, Mar 9, 2020 at 11:16 AM Sandro Bonazzola  
wrote:
> >> Il giorno dom 8 mar 2020 alle ore 08:49  ha scritto:
> >>> Hi
> >>> Is this also working on Centos Stream?
> >> 
> >> Yes, should work fine on CentOS Stream too.
> >> 
> >>> ___
> >>> Users mailing list -- users@ovirt.org
> >>> To unsubscribe send an email to users-le...@ovirt.org
> >>> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> >>> oVirt Code of Conduct:
> >>> https://www.ovirt.org/community/about/community-guidelines/ List
> >>> Archives:
> >>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/YVJ7AKI7F
> >>> GFUXQN2L4YXJT3N2YQXDAQR/>> 
> >> --
> >> 
> >> Sandro Bonazzola
> >> 
> >> MANAGER, SOFTWARE ENGINEERING, EMEA R RHV
> >> 
> >> Red Hat EMEA
> >> 
> >> sbona...@redhat.com
> >> 
> >> Red Hat respects your work life balance. Therefore there is no need to
> >> answer this email out of your office hours.
> >> ___
> >> Users mailing list -- users@ovirt.org
> >> To unsubscribe send an email to users-le...@ovirt.org
> >> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> >> oVirt Code of Conduct:
> >> https://www.ovirt.org/community/about/community-guidelines/ List
> >> Archives:
> >> https://lists.ovirt.org/archives/list/users@ovirt.org/message/7FHJY4HCHG
> >> ZNPEOBPNEFU663V5DQKBRR/> 
> > --
> > Sakari Poussa
> > 040 348 2970
> > ___
> > Users mailing list -- users@ovirt.org
> > To unsubscribe send an email to users-le...@ovirt.org
> > Privacy Statement: https://www.ovirt.org/privacy-policy.html
> > oVirt Code of Conduct:
> > https://www.ovirt.org/community/about/community-guidelines/ List
> > Archives:
> > https://lists.ovirt.org/archives/list/users@ovirt.org/message/R4PPALDFIHA
> > PRQVCCYL2ZHTZ52BDM7NG/



signature.asc
Description: This is a digitally signed message part.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/MRKJZBMX2OMZFSTOFDBKJAKTIVIHLR3S/


[ovirt-users] Re: Do I need to use self hosted engine with a GlusterFs three node setup

2019-11-14 Thread Vojtech Juranek
> Hi Vojtech 
> 
> Thanks for the info, I have been looking for a method of creating the
> gluster cluster via cockpit on one of my three hosts but the only way I can
> see is via the hosted engine setup. Is it a case that we need to configure
> the hosts to use gluster storage with the cli commands prior to adding it
> to a pre-existing non hosted engine? 

you have to setup Gluster cluster first and then you can connect it as a 
storage domain via engine UI (select Gluster in drop down menu when creating 
new storage). Some documentation (with little bit outdated UI) can be found on 
[1], section "Attaching a Gluster Storage Volume as a Storage Domain".

Check Gluster documentation how to setup Gluster cluster. For quick test you 
can use scripts [2, 3, 4] - but please note these are not intended for 
production use (e.g. turned off firewall etc, also use VDO which you may not 
want to use).

HTH
Vojta

[1] 
https://www.ovirt.org/documentation/admin-guide/chap-Working_with_Gluster_Storage.html
[2] https://github.com/oVirt/vdsm/blob/master/contrib/deploy-gluster.sh
[3] https://github.com/oVirt/vdsm/blob/master/contrib/create-vdo-brick.sh
[4] https://github.com/oVirt/vdsm/blob/master/contrib/create-gluster-volume.sh


> Donagh
> ___
> 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/IIEY3Z3GDGH4V
> 6CPE6LUKYORH4SUVLDA/



signature.asc
Description: This is a digitally signed message part.
___
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/N4RX4ET3QRRJKWBYFT7K4LYTDYXIGHJ4/


[ovirt-users] Re: Do I need to use self hosted engine with a GlusterFs three node setup

2019-11-13 Thread Vojtech Juranek
Hi,

> Every piece of documentation I read regarding the setup of Gluster seems to
> suggest using at least one of the the nodes to host the engine. Is this a
> requirement of can I use an engine that is deployed on a VM on another
> server in the same network?

yes, this is definitely possible, you can create Gluster storage domain and 
use it no matter there your engine runs

> Any info would be much appreciated.
> ___
> 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/LN4CTUMQSTJX4
> EO7ZHHO3QAM2NR6USGS/



signature.asc
Description: This is a digitally signed message part.
___
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/N2STTIQ6AGHMHWRYRSXFLJQI5EX6W4YV/


[ovirt-users] Re: Does ovirt support sshfs?

2019-11-12 Thread Vojtech Juranek
Hi,

> Does ovirt support sshfs for mount locally accessible LUN's instead of NFS?

no, this is not supported.
Vojta

signature.asc
Description: This is a digitally signed message part.
___
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/ESBX3VNNBF6XQ7GSQB74QGSDVBSCX6U7/


[ovirt-users] Re: [ANN] oVirt 4.3.6 is now generally available

2019-09-30 Thread Vojtech Juranek
Hi,

> > Engine reports the block size reported by vdsm. Once we get the system
> > up with your 4k storage domain,
> > we can check that engine reports the right value and update it if needed.
> > I think what you should do is:
> > 
> > 1. Backup storage domain metadata
> > /path/to/domain/domain-uuid/dom_md
> > 
> > 2. Deactivate the storage domain (from engine)
> > 
> > 3. Edit the metadata file:
> > - change BLOCK_SIZE to 4096
> > - delete the checksum line
> > (_SHA_CKSUM=9dde06bbc9f2316efc141565738ff32037b1ff66)
> > 
> > 4. Activate the domain
> > 
> > With vdsm < 4.3.6, the domain should be active, ignoring the block size.
> > 
> > 5. Upgrade back to 4.3.6
> > 
> > The system should detect the block size and work normally.
> > 
> > 6. File ovirt bug for this issue
> > 
> > We need at least to document the way to fix the storage domain manually.
> > 
> > We also should consider checking storage domain metadata during
> > upgrades. I think it will be
> > a better experience if upgrade will fail and you have a working system
> > with older version.
> 
> I've tried this procedure and it has worked! Thanks!
> 
> If you would like me to file a bug, which component should I log it against?

for vdms. Please include all the logs and db dump as Nir mentioned in previous 
email (see bellow).
Thanks

> >> 
> >> Please share more data so we can understand the failure:
> >> 
> >> - complete vdsm log showing the failure to activate the domain
> >>   - with 4.3.6
> >>   - with 4.3.5 (after you downgraded
> >> - contents of
> >> /rhev/data-center/mnt/_/domain-uuid/dom_md/metadata
> >>   (assuming your local domain mount is /domaindir)
> >> - engine db dump
> >> 


signature.asc
Description: This is a digitally signed message part.
___
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/EDTQ3WUXGWEOA7O2LTXQNJXYP6RYQKIB/


[ovirt-users] Re: nfs

2019-09-09 Thread Vojtech Juranek
Hi,

> I`m trying to mount a nfs share.
> 
> 
> 
> if I manually mount it from ssh, I can access it without issues.
> 
> 
> 
> However when I do it from the web config, it keeps failing:

the error means sanlock cannot write a resource on our device. Please check 
you have proper permission on your NFS (has to be writeable by uid:guid 36:36) 
and eventually check /var/log/sanlock.log if there are any details

> 
> 
> Not sure how to solve that.
> 
> 
> 
> Thanks
> 
> 
> 
> Simon
> 
> 
> 
> 2019-09-09 09:08:47,601-0400 INFO  (jsonrpc/5) [jsonrpc.JsonRpcServer] RPC
> call Host.ping2 succeeded in 0.00 seconds (__init__:312)
> 
> 2019-09-09 09:08:47,610-0400 INFO  (jsonrpc/3) [vdsm.api] START
> repoStats(domains=[u'4f4828c2-8f78-4566-a69d-a37cd73446d4']) from=::1,42394,
> task_id=6c1eeef7-ff8c-4d0d-be85-ced03aae4bc2 (api:48)
> 
> 2019-09-09 09:08:47,610-0400 INFO  (jsonrpc/3) [vdsm.api] FINISH repoStats
> return={u'4f4828c2-8f78-4566-a69d-a37cd73446d4': {'code': 0, 'actual': True,
> 'version': 5, 'acquired': True, 'delay': '0.00101971', 'lastCheck': '0.4',
> 'valid': True}} from=::1,42394,
> task_id=6c1eeef7-ff8c-4d0d-be85-ced03aae4bc2 (api:54)
> 
> 2019-09-09 09:08:47,611-0400 INFO  (jsonrpc/3) [jsonrpc.JsonRpcServer] RPC
> call Host.getStorageRepoStats succeeded in 0.00 seconds (__init__:312)
> 
> 2019-09-09 09:08:47,839-0400 INFO  (jsonrpc/4) [jsonrpc.JsonRpcServer] RPC
> call Host.ping2 succeeded in 0.00 seconds (__init__:312)
> 
> 2019-09-09 09:08:47,846-0400 INFO  (jsonrpc/2) [api.host] START
> getCapabilities() from=::1,42394 (api:48)
> 
> 2019-09-09 09:08:48,149-0400 INFO  (jsonrpc/2) [root] managedvolume not
> supported: Managed Volume Not Supported. Missing package os-brick.: ('Cannot
> import os_brick',) (caps:152)
> 
> 2019-09-09 09:08:49,212-0400 INFO  (jsonrpc/6) [jsonrpc.JsonRpcServer] RPC
> call Host.ping2 succeeded in 0.01 seconds (__init__:312)
> 
> 2019-09-09 09:08:49,263-0400 INFO  (jsonrpc/2) [root]
> /usr/libexec/vdsm/hooks/after_get_caps/50_openstacknet: rc=0 err=
> (hooks:114)
> 
> 2019-09-09 09:08:49,497-0400 INFO  (jsonrpc/0) [jsonrpc.JsonRpcServer] RPC
> call Host.ping2 succeeded in 0.00 seconds (__init__:312)
> 
> 2019-09-09 09:08:49,657-0400 INFO  (jsonrpc/1) [jsonrpc.JsonRpcServer] RPC
> call Host.ping2 succeeded in 0.00 seconds (__init__:312)
> 
> 2019-09-09 09:08:49,665-0400 INFO  (jsonrpc/7) [vdsm.api] START
> repoStats(domains=[u'4f4828c2-8f78-4566-a69d-a37cd73446d4']) from=::1,42394,
> task_id=14b596bf-bc1c-412b-b1fc-8d53f17d88f7 (api:48)
> 
> 2019-09-09 09:08:49,666-0400 INFO  (jsonrpc/7) [vdsm.api] FINISH repoStats
> return={u'4f4828c2-8f78-4566-a69d-a37cd73446d4': {'code': 0, 'actual': True,
> 'version': 5, 'acquired': True, 'delay': '0.00101971', 'lastCheck': '2.4',
> 'valid': True}} from=::1,42394,
> task_id=14b596bf-bc1c-412b-b1fc-8d53f17d88f7 (api:54)
> 
> 2019-09-09 09:08:49,667-0400 INFO  (jsonrpc/7) [jsonrpc.JsonRpcServer] RPC
> call Host.getStorageRepoStats succeeded in 0.00 seconds (__init__:312)
> 
> 2019-09-09 09:08:49,800-0400 INFO  (jsonrpc/2) [root]
> /usr/libexec/vdsm/hooks/after_get_caps/openstacknet_utils.py: rc=0 err=
> (hooks:114)
> 
> 2019-09-09 09:08:50,464-0400 INFO  (jsonrpc/2) [root]
> /usr/libexec/vdsm/hooks/after_get_caps/ovirt_provider_ovn_hook: rc=0 err=
> (hooks:114)
> 
> 2019-09-09 09:08:50,467-0400 INFO  (jsonrpc/2) [api.host] FINISH
> getCapabilities return={'status': {'message': 'Done', 'code': 0}, 'info':
> {u'HBAInventory': {u'iSCSI': [{u'InitiatorName':
> u'iqn.1994-05.com.redhat:d8c85fc0ab85'}], u'FC': []}, u'packages2':
> {u'kernel': {u'release': u'957.27.2.el7.x86_64', u'version': u'3.10.0'},
> u'spice-server': {u'release': u'6.el7_6.1', u'version': u'0.14.0'},
> u'librbd1': {u'release': u'4.el7', u'version': u'10.2.5'}, u'vdsm':
> {u'release': u'1.el7', u'version': u'4.30.24'}, u'qemu-kvm': {u'release':
> u'18.el7_6.7.1', u'version': u'2.12.0'}, u'openvswitch': {u'release':
> u'4.el7', u'version': u'2.11.0'}, u'libvirt': {u'release': u'10.el7_6.12',
> u'version': u'4.5.0'}, u'ovirt-hosted-engine-ha': {u'release': u'1.el7',
> u'version': u'2.3.3'}, u'qemu-img': {u'release': u'18.el7_6.7.1',
> u'version': u'2.12.0'}, u'mom': {u'release': u'1.el7.centos', u'version':
> u'0.5.12'}, u'glusterfs-cli': {u'release': u'1.el7', u'version': u'6.5'}},
> u'numaNodeDistance': {u'1': [20, 10], u'0': [10, 20]}, u'cpuModel':
> u'Intel(R) Xeon(R) CPU E5-2640 v2 @ 2.00GHz', u'nestedVirtualization':
> False, u'liveMerge': u'true', u'hooks': {u'before_vm_start':
> {u'50_hostedengine': {u'md5': u'95c810cdcfe4195302a59574a5148289'},
> u'50_vhostmd': {u'md5': u'9206bc390bcbf208b06a8e899581be2d'}},
> u'after_network_setup': {u'30_ethtool_options': {u'md5':
> u'ce1fbad7aa0389e3b06231219140bf0d'}}, u'after_vm_destroy':
> {u'delete_vhostuserclient_hook': {u'md5':
> u'c2f279cc9483a3f842f6c29df13994c1'}, u'50_vhostmd': {u'md5':
> u'bdf4802c0521cf1bae08f2b90a9559cf'}}, u'after_vm_start':
> {u'openstacknet_utils.py': {u'md5': u'1ed38ddf30f8a9c7574589e77e2c0b1f'},

[ovirt-users] Re: Storage domain format version info

2019-07-09 Thread Vojtech Juranek
Hi,

> part of updating a DC from 4.2 to 4.3 consists in updating format of data
> storage domains from V4 to V5.
> Questions:
> - where can I find list of differences between V4 and V5? And in general
> between previous ones?

I'm afraid there's no design doc for it. Here's list of changes:

* domain metadata
  * added: alignment, block_size
  * removed: logblksize, phyblksize

* volume metadata
  * added: cap (replacement for size, capacity is size in bytes, while size 
was in mutiples of block size (512B))
  * removed mtime, pool_uuid, size

If you want more details about the changes, you can check slides [1]

> - can I force only a particular storage domain to remain in V4 while having
> the other ones upgraded to V5, for any reason? Or the reverse: update only
> one of the defined domains?

I don't think this is possible. 

HTH
Vojta

[1] https://github.com/vjuranek/presentations/blob/master/internal/oVirt/
storage_v5/storage_v5.pdf

signature.asc
Description: This is a digitally signed message part.
___
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/2JF5ODAW2LBPPDWHM5VU4FHPSDKLOMVQ/


[ovirt-users] Re: 4K Sector Hard drive Support - oVirt 4.3.4

2019-06-12 Thread Vojtech Juranek
Hi,

> Does anyone have any idea if/when 4K Sector drives will be supported? 
> 
> My understanding is that this was one of the features for 4.3.4

I'm sorry, we didn't make it for 4.3.4 and still working on it. You can follow 
BZ #1592916 [1] to track the progress, but I'd not promise any hard deadlines 
when it's finished.

Thanks
Vojta

[1] https://bugzilla.redhat.com/1592916

signature.asc
Description: This is a digitally signed message part.
___
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/UF6C6HGNNKWS2IITS65P3J6K2VJTFSDJ/


[ovirt-users] Re: ovirt - in docker

2018-10-15 Thread Vojtech Juranek
On neděle 14. října 2018 0:44:22 CEST Vojtech Juranek wrote:
> On pátek 12. října 2018 12:49:03 CEST ReSearchIT Eng wrote:
> > We mainly need a good answers file, while entrypoint might be kept from
> > 4.1, right?
> 
> I looked on it and there are some smaller changes needed. I'll send an
> update soon

patch for oVirt 4.2 for ovirt-container-engine is in gerrit [1]. It works with 
published rmohr/ovirt-postgres (postgres 9.2), but as recommended DB for oVirt 
4.2 is postgres 9.5, you may download patch for 9.5 [2] and build it locally 
(from previous answers it looks like project is not maintained, so review may 
take some time:-)
Let ma know if you spot any issues.
Thanks
Vojta

[1] https://gerrit.ovirt.org/94916
[2] https://github.com/rmohr/docker-ovirt-postgres/pull/3

signature.asc
Description: This is a digitally signed message part.
___
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/SZSNCPHX5DPMLQ247SVY4EMJFP7EUQTV/


[ovirt-users] Re: ovirt - in docker

2018-10-13 Thread Vojtech Juranek
On pátek 12. října 2018 12:49:03 CEST ReSearchIT Eng wrote:
> We mainly need a good answers file, while entrypoint might be kept from
> 4.1, right?

I looked on it and there are some smaller changes needed. I'll send an update 
soon


signature.asc
Description: This is a digitally signed message part.
___
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/J65APKCQW5CSIED2HH3NUHEYMAW4LG3B/


[ovirt-users] Re: Resizing ovirt-engine disk

2018-10-12 Thread Vojtech Juranek
> Do you know if this patch will be backported in 4.2 or it will land only in
> the next major release ?

Unfortunately I don't know (even don't know if the patch will be accepted:-). 
I'm very new to oVirt so don't know yet what the rules for backporting are 
etc. Hopefully someone else on the list can answer it.

Cheers
Vojta



signature.asc
Description: This is a digitally signed message part.
___
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/NYMDHEP5CUTU4UOUWQZ26G3MQQAN7MSJ/


[ovirt-users] Re: Resizing ovirt-engine disk

2018-10-11 Thread Vojtech Juranek
Hi,

> Can we grow the ovirt-engine disk like any other managed VM ?

I assume you mean hosted engine. No, unfortunately this is not possible right 
now. Today I proposed a patch [1] which should fix it.
 
> And if not, how can we grow the ovirt-engine disk out of standard
> installation procedure ?

it's possible, but includes calling vdsm client directly and editing the 
database, so I'd recommend to avoid it.

Cheers
Vojta

[1] https://gerrit.ovirt.org/94855



signature.asc
Description: This is a digitally signed message part.
___
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/GR7MTEEE3ZRJGKUVYQFAJPJTWPQGGJX7/