[ovirt-users] Re: Unable to upload ISO Image in ovirt 4.4.10

2022-03-06 Thread louisb
I don't have the file "ovirt-imageio-proxy" on my system, is there another file 
that I should be looking at?  Once I locate the correct file what content in 
the file needs to change?  

I'm using  the latest release of "Firefox/91.6.0" as my browser,  and i import 
the "Engine CA" after the fact.  However, after the import I tried again and 
got the same results.   

Thanks
___
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/WHEKOE5YSKLPMLBUXMT7KKXXPE6UDAHB/


[ovirt-users] Re: Unable to upload ISO Image in ovirt 4.4.10

2022-03-06 Thread Nir Soffer
On Sun, Mar 6, 2022 at 9:42 PM  wrote:
>
> I don't have the file "ovirt-imageio-proxy" on my system, is there another 
> file that I should be looking at?  Once I locate the correct file what 
> content in the file needs to change?
>
> I'm using  the latest release of "Firefox/91.6.0" as my browser,  and i 
> import the "Engine CA" after the fact.  However, after the import I tried 
> again and got the same results.

In oVirt 4.4 the ovirt-imageio-proxy service was replaced with the
ovirt-imageio service.

The built-in configuration should work with the default (self signed)
CA and with custom
CA without any configuration change.

Is this all-in-one installation, when ovirt-engine is installed on the
single hypervisor,
and the same host is added later as an hypervisor?

To make sure you configured the browser correctly, please open the
"upload" dialog
and click the "Test connection" button. If the testing the connection
works the browser
can communicate with the ovirt-imageio service and your system is
ready for upload
from the browser.

Nir
___
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/4JN43TC3CGMLUZW6OCUTEZHQDNJDMRNP/


[ovirt-users] Re: Unable to upload ISO Image in ovirt 4.4.10

2022-03-06 Thread Nir Soffer
On Sat, Mar 5, 2022 at 4:25 PM Patrick Hibbs  wrote:
>
> That's typically one of three issues:
>
> 1. You've replaced the certificate used by apache, but haven't updated
> the configuration for the ovirt-imageio-proxy.

This should never be needed in 4.4.

> 2. You're using an older web browser. (Pale Moon, Waterfox, older
> versions of Chrome, etc.)
>
> 3. There's an issue that causes the initial transfers (upload or
> download) to fail once or twice every ~24 hours.

We had an issue when upload from the browser fails randomly:
https://bugzilla.redhat.com/1977276

Fix is available since 4.4.9, so it should not happen in 4.4.10.

> If it's the first issue, a quick fix is to simply add your new
> certificate's CA cert to the hidden /etc/pki/ovirt-engine/.truststore
> file (It's a java keystore.) then restart the engine and imageio-proxy.

In 4.4, you need to restart the ovirt-imageio service to pick the new CA
used to communicate with the browser.

Nir
___
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/35NTZMHNJYRXB43PPLFK5AMUKHIKAIPT/


[ovirt-users] Re: Unable to upload ISO Image in ovirt 4.4.10

2022-03-06 Thread Patrick Hibbs
I set up a new ovirt test instance on a clean Rocky Linux 8.5 server
with a custom apache cert about two weeks ago. Uploading a test image
via the browser didn't work until I changed the .truststore file.

I should also point out that I also had to set the cert in apache's
config. Simply replacing the symlink in the cert directory didn't work
as it wasn't pointing to it at all. (Instead it was pointing at some
snakeoil cert generated by apache.) Granted, the apache issue is
specific to Rocky, but the imageio service is definitely in ovirt's
full control.

If the imageio service is supposed to work out of the box with a custom
certificate, there's something amiss.



WARNING: Small rant follows:

Yes, I could have changed a config file instead of changing
.truststore, but it's just another way to achieve the same result. (And
the one I discovered back in ovirt 3.x.) It doesn't make the process
any eaiser, if anything it's just another option to check if something
goes wrong. Instead of checking only .truststore, Now we have to check
.truststore, and any number of extra config files for a redirect
statement, and the load ordering of those config files, *and* whether
or not those redirect statements point to a valid cert or not. Instead
of having just one place to troubleshoot, now there's at least four.
The config file change also doesn't make it any eaiser to perform those
changes. You still need to manually make these changes via ssh on the
engine host. Why would I want to advice changing a config file, and
risk that much of an additional mess to deal with in support, when I
can tell them one specific file to fix that has none of these extras to
deal with? Personally, I would choose the option with less chance for
human error.

/rant

-Patrick Hibbs

On Sun, 2022-03-06 at 21:54 +0200, Nir Soffer wrote:
> On Sun, Mar 6, 2022 at 9:42 PM  wrote:
> > 
> > I don't have the file "ovirt-imageio-proxy" on my system, is there
> > another file that I should be looking at?  Once I locate the
> > correct file what content in the file needs to change?
> > 
> > I'm using  the latest release of "Firefox/91.6.0" as my browser, 
> > and i import the "Engine CA" after the fact.  However, after the
> > import I tried again and got the same results.
> 
> In oVirt 4.4 the ovirt-imageio-proxy service was replaced with the
> ovirt-imageio service.
> 
> The built-in configuration should work with the default (self signed)
> CA and with custom
> CA without any configuration change.
> 
> Is this all-in-one installation, when ovirt-engine is installed on
> the
> single hypervisor,
> and the same host is added later as an hypervisor?
> 
> To make sure you configured the browser correctly, please open the
> "upload" dialog
> and click the "Test connection" button. If the testing the connection
> works the browser
> can communicate with the ovirt-imageio service and your system is
> ready for upload
> from the browser.
> 
> Nir
> ___
> 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/4JN43TC3CGMLUZW6OCUTEZHQDNJDMRNP/

___
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/GJ6UALLOL6NBQA7O5W6AATKBTXC6SELP/


[ovirt-users] Re: Unable to upload ISO Image in ovirt 4.4.10

2022-03-06 Thread Nir Soffer
On Sun, Mar 6, 2022 at 11:42 PM Patrick Hibbs  wrote:
>
> I set up a new ovirt test instance on a clean Rocky Linux 8.5 server
> with a custom apache cert about two weeks ago.

Do you have single server used both for running ovirt-engine and
as a hypervisor? This requires special configuration. If engine is
not running on the hypervisor, for example engine runs in a VM or
on another host, everything should work out of the box.

> Uploading a test image
> via the browser didn't work until I changed the .truststore file.

.truststore file where?

> I should also point out that I also had to set the cert in apache's
> config. Simply replacing the symlink in the cert directory didn't work
> as it wasn't pointing to it at all. (Instead it was pointing at some
> snakeoil cert generated by apache.) Granted, the apache issue is
> specific to Rocky, but the imageio service is definitely in ovirt's
> full control.
>
> If the imageio service is supposed to work out of the box with a custom
> certificate, there's something amiss.

These are the defaults:

$ ovirt-imageio --show-config | jq '.tls'
{
  "ca_file": "/etc/pki/ovirt-engine/apache-ca.pem",
  "cert_file": "/etc/pki/ovirt-engine/certs/apache.cer",
  "enable": true,
  "enable_tls1_1": false,
  "key_file": "/etc/pki/ovirt-engine/keys/apache.key.nopass"
}

The ovirt-imageio service works with apache configuration files.
If these symlinks point to the right files, everything should work
out of the box.

If you change the apache PKI files, you need to modify ovirt-imageio
configuration by adding a drop-in configuration file with the right
configuration:

$ cat /etc/ovirt-imageio/conf.d/99-local.conf
[tls]
key_file = /path/to/keyfile
cert_file = /path/to/certfile
ca_file = /path/to/cafile

Note: the following configuration *must not* change:

$ ovirt-imageio --show-config | jq '.backend_http'
{
  "buffer_size": 8388608,
  "ca_file": "/etc/pki/ovirt-engine/ca.pem"
}

This CA file is used to access the hosts, which are managed by
ovirt-engine self signed CA, and cannot be replaced.

> WARNING: Small rant follows:
>
> Yes, I could have changed a config file instead of changing
> .truststore, but it's just another way to achieve the same result. (And
> the one I discovered back in ovirt 3.x.) It doesn't make the process
> any eaiser, if anything it's just another option to check if something
> goes wrong. Instead of checking only .truststore, Now we have to check
> .truststore, and any number of extra config files for a redirect
> statement, and the load ordering of those config files, *and* whether
> or not those redirect statements point to a valid cert or not. Instead
> of having just one place to troubleshoot, now there's at least four.
> The config file change also doesn't make it any eaiser to perform those
> changes. You still need to manually make these changes via ssh on the
> engine host. Why would I want to advice changing a config file, and
> risk that much of an additional mess to deal with in support, when I
> can tell them one specific file to fix that has none of these extras to
> deal with? Personally, I would choose the option with less chance for
> human error.

It is clear that you think we can have a better way to configure the system,
but it is not clear what is the issue and what is the better solution.

Can you explain in more details what is the problem with the documented
solution on using custom PKI files, and what is the easier way to do this?

If we have an easier way, it should be documented.

Nir

> On Sun, 2022-03-06 at 21:54 +0200, Nir Soffer wrote:
> > On Sun, Mar 6, 2022 at 9:42 PM  wrote:
> > >
> > > I don't have the file "ovirt-imageio-proxy" on my system, is there
> > > another file that I should be looking at?  Once I locate the
> > > correct file what content in the file needs to change?
> > >
> > > I'm using  the latest release of "Firefox/91.6.0" as my browser,
> > > and i import the "Engine CA" after the fact.  However, after the
> > > import I tried again and got the same results.
> >
> > In oVirt 4.4 the ovirt-imageio-proxy service was replaced with the
> > ovirt-imageio service.
> >
> > The built-in configuration should work with the default (self signed)
> > CA and with custom
> > CA without any configuration change.
> >
> > Is this all-in-one installation, when ovirt-engine is installed on
> > the
> > single hypervisor,
> > and the same host is added later as an hypervisor?
> >
> > To make sure you configured the browser correctly, please open the
> > "upload" dialog
> > and click the "Test connection" button. If the testing the connection
> > works the browser
> > can communicate with the ovirt-imageio service and your system is
> > ready for upload
> > from the browser.
> >
> > Nir
___
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.

[ovirt-users] Re: Import an snapshot of an iSCSI Domain

2022-03-06 Thread Nir Soffer
On Fri, Mar 4, 2022 at 8:28 AM Vinícius Ferrão via Users
 wrote:
>
> Hi again, I don’t know if it will be possible to import the storage domain 
> due to conflicts with the UUID of the LVM devices. I’ve tried to issue a 
> vgimportclone to chance the UUIDs and import the volume but it still does not 
> shows up on oVirt.

LVM can change VG/PV UUIDs and names, but storage domain metadata kept in the
VG tags and volume metadata area contain the old VG and PV names and UUIDs,
so it is unlikely to work.

The system is designed so if the original PVs are bad, you can
disconnect them and
connect a backup of the PVs, and import the storage domain again to the system.

Can you explain in more details what you are trying to do?

Nir

> I don’t know how to mount the iSCSI volume to recover the data. The data is 
> there but it’s extremely difficult to get it.
>
> Any ideias?
>
> Thanks.
>
>
> > On 3 Mar 2022, at 20:56, Vinícius Ferrão  wrote:
> >
> > I think I’ve found the root cause, and it’s the LVM inside the iSCSI volume:
> >
> > [root@rhvh5 ~]# pvscan
> >  WARNING: Not using device /dev/mapper/36589cfc00db9cf56949c63d338ef 
> > for PV fTIrnd-gnz2-dI8i-DesK-vIqs-E1BK-mvxtha.
> >  WARNING: PV fTIrnd-gnz2-dI8i-DesK-vIqs-E1BK-mvxtha prefers device 
> > /dev/mapper/36589cfc006f6c96763988802912b because device is used by LV.
> >  PV /dev/mapper/36589cfc006f6c96763988802912bVG 
> > 9377d243-2c18-4620-995f-5fc680e7b4f3   lvm2 [<10.00 TiB / 7.83 TiB free]
> >  PV /dev/mapper/36589cfc00a1b985d3908c07e41adVG 
> > 650b0003-7eec-4fa5-85ea-c019f6408248   lvm2 [199.62 GiB / <123.88 GiB free]
> >  PV /dev/mapper/3600605b00805d8a01c2180fd0d8d8dad3   VG rhvh_rhvh5  
> >lvm2 [<277.27 GiB / 54.55 GiB free]
> >  Total: 3 [<10.47 TiB] / in use: 3 [<10.47 TiB] / in no VG: 0 [0   ]
> >
> > The device that’s not being using is the snapshot. There’s a way to change 
> > the ID of the device so I can import the data domain?
> >
> > Thanks.
> >
> >> On 3 Mar 2022, at 20:21, Vinícius Ferrão via Users  wrote:
> >>
> >> Hello,
> >>
> >> I need to import an old snapshot of my Data domain but oVirt does not find 
> >> the snapshot version when importing on the web interface.
> >>
> >> To be clear, I’ve mounted a snapshot on my storage, and exported it on 
> >> iSCSI. I was expecting that I could be able to import it on the engine.
> >>
> >> On the web interface this Import Pre-Configured Domain finds the relative 
> >> IQN but it does not show up as a target.
> >>
> >> Any ideas?
> >>
> >>
> >> ___
> >> 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/3WEQQHZ46DKQJXHVX5QF4S2UVBYF4URR/
> >
>
> ___
> 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/3XDKQK32V6E4K3IB7BLY5XOGDNHJBW3L/
___
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/2EY4WRDMMKZRDBIWSQEHQPMHODHMVZOA/


[ovirt-users] Re: virt-viewer-x64.msi location

2022-03-06 Thread Strahil Nikolov via Users
I use noVNC with the admin portal and then the browser works as a virt-viewer.
The link was leading to an already dropped 
page:https://www.ovirt.org/dropped/admin-guide/virt/console-client-resources.html
 which points you to http://virt-manager.org/download/ but also explains that 
you need to add the oVirt Engine's CA into the browser, in case you decide to 
give noVNC a try.

Best Regards, Strahil Nikolov
 
 
  On Sat, Mar 5, 2022 at 9:09, auricom...@gmail.com 
wrote:   Hello,

I'm trying to download viewer for connecting to VMs, the documentation
https://www.ovirt.org/documentation/virtual_machine_management_guide/index.html#sect-Installing_Console_Components
mentions the URL should be
https://your-manager-fqdn/ovirt-engine/services/files/spice/virt-viewer-x64.msi

However substituting my ovirt-engine hostname for "your-manager-fqdn", I get 
404.  I even SSH directly into hosted engine VM and was not able to locate 
virt-viewer-x64.msi on the file system.

If I go to https://your-manager-fqdn/ovirt-engine/ landing page.  The "Console 
Client Resources" goes to:
https://www.ovirt.org/documentation/admin-guide/virt/console-client-resources/

Which is also a 404.

Am I supposed to be downloading it from here (weary of unsigned publishers, but 
looks like the only place where this is located)? 
https://virt-manager.org/download/

Version is: Version 4.4.10.6-1.el8
Installed on: CentOS Stream 8 (8.5)
Install instructions used:
https://www.ovirt.org/documentation/installing_ovirt_as_a_self-hosted_engine_using_the_command_line/index.html
___
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/X7CACG45ER2QPHSGH32I2II5WCWEL7WB/
  
___
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/KAGO2MQYIYYZWOGXAOGDRGERGZHLEWJD/