[ovirt-users] Re: 4.4.4 Image Copying / Template Create Fails - No Such File
On Mon, Mar 8, 2021 at 8:15 AM Alex McWhirter wrote: > I apologize for the spam, this seems to be a long standing gluster issue. > https://github.com/gluster/glusterfs/issues/597 > > sharding does not support SEEK_DATA/SEEK_HOLE, with a preallocated image > you likely never see this issue as there are no holes. However with a > sparse image, that's very much not the case. I'm not sure when qemu-img > changed to use these syscalls, as this is not something i experience on 4.3 > / CentOS 7. > > I'd be interested if anyone else can replicate this image copy behavior > using raw sparse (thin provision) disks as the source on a gluster volume > with sharding enabled, on oVirt 4.4.4+ (possibly earlier is also affected) > > If this is something current qemu-img cannot handle, i don't think > supporting sparse disks on sharded gluster volumes is wise. > > > I only remember for sure that with 4.4.0 (and perhaps up to 4.4.2) with single host HCI with Gluster I couldn't use sharding in a lab where I had to create, destroy and recreate many times an Openshift environment composed by many VMs and having thin disks was a must to improve times. I sent several messages regarding this to the list but no active resolution and was forced to disable sharding. I also wrote to Gluster guys. I can try to search and send the links. Gianluca ___ 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/JLRNJGTHQGLWIEI2VW7DADTLFTL73PGR/
[ovirt-users] Re: 4.4.4 Image Copying / Template Create Fails - No Such File
I apologize for the spam, this seems to be a long standing gluster
issue. https://github.com/gluster/glusterfs/issues/597
sharding does not support SEEK_DATA/SEEK_HOLE, with a preallocated image
you likely never see this issue as there are no holes. However with a
sparse image, that's very much not the case. I'm not sure when qemu-img
changed to use these syscalls, as this is not something i experience on
4.3 / CentOS 7.
I'd be interested if anyone else can replicate this image copy behavior
using raw sparse (thin provision) disks as the source on a gluster
volume with sharding enabled, on oVirt 4.4.4+ (possibly earlier is also
affected)
If this is something current qemu-img cannot handle, i don't think
supporting sparse disks on sharded gluster volumes is wise.
On 2021-03-08 01:06, Alex McWhirter wrote:
This actually looks to be related to sharding. Doing a strace on the qemu-img process, i can see that it is using lseek, but after the first shard this turns to EOPNOTSUPP and qemu-img dies.
If i temporarily disable sharding, touch a file (so it will not be sharded), then re-enable sharding and use qemu-img to overwrite that new unsharded file, there are no issues.
On 2021-03-07 18:33, Nir Soffer wrote:
On Sun, Mar 7, 2021 at 1:14 PM Alex McWhirter wrote:
I've been wrestling with this all night, digging through various bits of VDSM code trying to figure why and how this is happening. I need to make some templates, but i simply can't.
VDSM command HSMGetAllTasksStatusesVDS failed: value=low level Image copy failed: ("Command ['/usr/bin/qemu-img', 'convert', '-p', '-t', 'none', '-T', 'none', '-f', 'raw', '-O', 'raw', '/rhev/data-center/mnt/glusterSD/:_Temp/45740f16-b3c9-4bb5-ba5f-3e64657fb663/images/6f87b073-c4ec-42f2-87da-d1cb6a08a150/f2dfb779-b49c-4ec9-86cd-741f3fe5b781', '/rhev/data-center/mnt/glusterSD/:_Temp/45740f16-b3c9-4bb5-ba5f-3e64657fb663/images/84e56da6-8c26-4518-80a4-20bc395214db/039c5ada-ad6d-45c0-8393-bd4db0bbc366'] failed with rc=1 out=b'' err=bytearray(b'qemu-img: error while writing at byte 738197504: No such file or directory\\n')",)
This is a gluster issue that was reported in the past. write() cannot return errno ENOENT
and qemu-img cannot recover from this error.
Can you reproduce this when running the same qemu-img command from the shell?
Are you running the latest gluster version?
Nir
abortedcode=261
3/7/21 5:44:44 AM
Following the VDSM logs, i can see the new image gets created, permissions set, etc... but as soon qemu-img starts, it fails like this. I updated all hosts and the engine, rebooted the entire stack, to no avail. So i detached the storage domain, and wiped every host and fresh installed both engine and all nodes, imported the storage domain, and still no dice. Storage domain is gluster volume, single node, created in ovirt.
It happens when i make a template, copy an image, or make a new vm from a template. I can still create new vms from blank, and upload images via the web ui. Watching the gluster share, i can see the image being created, but its deleted at some point. I appears to not be being deleted by the template / copying process, as immediately after the above error, i get this one.
VDSM command DeleteImageGroupVDS failed: Image does not exist in domain: 'image=4f359545-01a8-439b-832b-18c26194b066, domain=b4507449-ac40-4e35-be66-56441bb696ac'
3/7/21 5:44:44 AM
I thought maybe garbage collection, but don't see any indication of that in the logs.
Any ideas? I redacted host names from the log output.
___
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/75BZNMZUH23ZWCUHCDYCJSC6EZ45UW5O/
___
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/33JF7NWW7XW4KKWM57H52TK5QDBDA4J5/
___
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/AW2L2D66HFFKF7XXWDYZRKW5R36P6HCC/___
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:
[ovirt-users] Re: 4.4.4 Image Copying / Template Create Fails - No Such File
This actually looks to be related to sharding. Doing a strace on the
qemu-img process, i can see that it is using lseek, but after the first
shard this turns to EOPNOTSUPP and qemu-img dies.
If i temporarily disable sharding, touch a file (so it will not be
sharded), then re-enable sharding and use qemu-img to overwrite that new
unsharded file, there are no issues.
On 2021-03-07 18:33, Nir Soffer wrote:
On Sun, Mar 7, 2021 at 1:14 PM Alex McWhirter wrote:
I've been wrestling with this all night, digging through various bits of VDSM code trying to figure why and how this is happening. I need to make some templates, but i simply can't.
VDSM command HSMGetAllTasksStatusesVDS failed: value=low level Image copy failed:
("Command ['/usr/bin/qemu-img', 'convert', '-p', '-t', 'none', '-T', 'none', '-f', 'raw', '-O', 'raw',
'/rhev/data-center/mnt/glusterSD/:_Temp/45740f16-b3c9-4bb5-ba5f-3e64657fb663/images/6f87b073-c4ec-42f2-87da-d1cb6a08a150/f2dfb779-b49c-4ec9-86cd-741f3fe5b781',
'/rhev/data-center/mnt/glusterSD/:_Temp/45740f16-b3c9-4bb5-ba5f-3e64657fb663/images/84e56da6-8c26-4518-80a4-20bc395214db/039c5ada-ad6d-45c0-8393-bd4db0bbc366']
failed with rc=1 out=b'' err=bytearray(b'qemu-img: error while writing at byte 738197504: No such file or
directory\\n')",)
This is a gluster issue that was reported in the past. write() cannot return errno ENOENT
and qemu-img cannot recover from this error.
Can you reproduce this when running the same qemu-img command from the shell?
Are you running the latest gluster version?
Nir
abortedcode=261
3/7/21 5:44:44 AM
Following the VDSM logs, i can see the new image gets created, permissions set, etc... but as soon qemu-img starts, it fails like this. I updated all hosts and the engine, rebooted the entire stack, to no avail. So i detached the storage domain, and wiped every host and fresh installed both engine and all nodes, imported the storage domain, and still no dice. Storage domain is gluster volume, single node, created in ovirt.
It happens when i make a template, copy an image, or make a new vm from a template. I can still create new vms from blank, and upload images via the web ui. Watching the gluster share, i can see the image being created, but its deleted at some point. I appears to not be being deleted by the template / copying process, as immediately after the above error, i get this one.
VDSM command DeleteImageGroupVDS failed: Image does not exist in domain: 'image=4f359545-01a8-439b-832b-18c26194b066, domain=b4507449-ac40-4e35-be66-56441bb696ac'
3/7/21 5:44:44 AM
I thought maybe garbage collection, but don't see any indication of that in the logs.
Any ideas? I redacted host names from the log output.
___
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/75BZNMZUH23ZWCUHCDYCJSC6EZ45UW5O/
___
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/33JF7NWW7XW4KKWM57H52TK5QDBDA4J5/___
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/AW2L2D66HFFKF7XXWDYZRKW5R36P6HCC/
[ovirt-users] Re: 4.4.4 Image Copying / Template Create Fails - No Such File
I see, yes running the command by hand results in the same error.
Gluster version is 8.3 (I upgraded to see if 8.4.5 would result in a
different outcome)
Previously it was gluster 7.9, same issue either way.
On 2021-03-07 18:33, Nir Soffer wrote:
On Sun, Mar 7, 2021 at 1:14 PM Alex McWhirter wrote:
I've been wrestling with this all night, digging through various bits of VDSM code trying to figure why and how this is happening. I need to make some templates, but i simply can't.
VDSM command HSMGetAllTasksStatusesVDS failed: value=low level Image copy failed:
("Command ['/usr/bin/qemu-img', 'convert', '-p', '-t', 'none', '-T', 'none', '-f', 'raw', '-O', 'raw',
'/rhev/data-center/mnt/glusterSD/:_Temp/45740f16-b3c9-4bb5-ba5f-3e64657fb663/images/6f87b073-c4ec-42f2-87da-d1cb6a08a150/f2dfb779-b49c-4ec9-86cd-741f3fe5b781',
'/rhev/data-center/mnt/glusterSD/:_Temp/45740f16-b3c9-4bb5-ba5f-3e64657fb663/images/84e56da6-8c26-4518-80a4-20bc395214db/039c5ada-ad6d-45c0-8393-bd4db0bbc366']
failed with rc=1 out=b'' err=bytearray(b'qemu-img: error while writing at byte 738197504: No such file or
directory\\n')",)
This is a gluster issue that was reported in the past. write() cannot return errno ENOENT
and qemu-img cannot recover from this error.
Can you reproduce this when running the same qemu-img command from the shell?
Are you running the latest gluster version?
Nir
abortedcode=261
3/7/21 5:44:44 AM
Following the VDSM logs, i can see the new image gets created, permissions set, etc... but as soon qemu-img starts, it fails like this. I updated all hosts and the engine, rebooted the entire stack, to no avail. So i detached the storage domain, and wiped every host and fresh installed both engine and all nodes, imported the storage domain, and still no dice. Storage domain is gluster volume, single node, created in ovirt.
It happens when i make a template, copy an image, or make a new vm from a template. I can still create new vms from blank, and upload images via the web ui. Watching the gluster share, i can see the image being created, but its deleted at some point. I appears to not be being deleted by the template / copying process, as immediately after the above error, i get this one.
VDSM command DeleteImageGroupVDS failed: Image does not exist in domain: 'image=4f359545-01a8-439b-832b-18c26194b066, domain=b4507449-ac40-4e35-be66-56441bb696ac'
3/7/21 5:44:44 AM
I thought maybe garbage collection, but don't see any indication of that in the logs.
Any ideas? I redacted host names from the log output.
___
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/75BZNMZUH23ZWCUHCDYCJSC6EZ45UW5O/
___
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/33JF7NWW7XW4KKWM57H52TK5QDBDA4J5/___
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/QHOEFQ6BMRF43PI44ZFAFLTQC6XW3UG3/
[ovirt-users] Re: 4.4.4 Image Copying / Template Create Fails - No Such File
On Sun, Mar 7, 2021 at 1:14 PM Alex McWhirter wrote:
> I've been wrestling with this all night, digging through various bits of
> VDSM code trying to figure why and how this is happening. I need to make
> some templates, but i simply can't.
>
>
> VDSM command HSMGetAllTasksStatusesVDS failed: value=low level
> Image copy failed: ("Command ['/usr/bin/qemu-img', 'convert', '-p', '-t',
> 'none', '-T', 'none', '-f', 'raw', '-O', 'raw',
> '/rhev/data-center/mnt/glusterSD/:_Temp/45740f16-b3c9-4bb5-ba5f-3e64657fb663/images/6f87b073-c4ec-42f2-87da-d1cb6a08a150/f2dfb779-b49c-4ec9-86cd-741f3fe5b781',
> '/rhev/data-center/mnt/glusterSD/:_Temp/45740f16-b3c9-4bb5-ba5f-3e64657fb663/images/84e56da6-8c26-4518-80a4-20bc395214db/039c5ada-ad6d-45c0-8393-bd4db0bbc366']
> failed with rc=1 out=b'' err=bytearray(b'qemu-img: error while writing at
> byte 738197504: No such file or directory\\n')",)
>
This is a gluster issue that was reported in the past. write() cannot
return errno ENOENT
and qemu-img cannot recover from this error.
Can you reproduce this when running the same qemu-img command from the
shell?
Are you running the latest gluster version?
Nir
abortedcode=261
> 3/7/21 5:44:44 AM
>
>
> Following the VDSM logs, i can see the new image gets created, permissions
> set, etc... but as soon qemu-img starts, it fails like this. I updated all
> hosts and the engine, rebooted the entire stack, to no avail. So i detached
> the storage domain, and wiped every host and fresh installed both engine
> and all nodes, imported the storage domain, and still no dice. Storage
> domain is gluster volume, single node, created in ovirt.
>
> It happens when i make a template, copy an image, or make a new vm from a
> template. I can still create new vms from blank, and upload images via the
> web ui. Watching the gluster share, i can see the image being created, but
> its deleted at some point. I appears to not be being deleted by the
> template / copying process, as immediately after the above error, i get
> this one.
>
> VDSM command DeleteImageGroupVDS failed: Image does not exist in domain:
> 'image=4f359545-01a8-439b-832b-18c26194b066,
> domain=b4507449-ac40-4e35-be66-56441bb696ac'
>
> 3/7/21 5:44:44 AM
>
> I thought maybe garbage collection, but don't see any indication of that
> in the logs.
>
> Any ideas? I redacted host names from the log output.
> ___
> 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/75BZNMZUH23ZWCUHCDYCJSC6EZ45UW5O/
>
___
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/33JF7NWW7XW4KKWM57H52TK5QDBDA4J5/
[ovirt-users] Re: Which Operating System to choose
If you're content with the current RHEL licensing terms, its a great choice for now. Noone can tell you the future with certainty. If you're just creating a virtualization cluster with external storage, why not use the node-ng installer iso. It will be updated as necessary for each new released version of oVirt. Today it is CentOS8.3 based, but it will easily be changed once oVirt on Stream is ready. On Sun, Mar 7, 2021 at 5:27 AM wrote: > I want to set up a small cluster consisting of 2 Hypervisor nodes > (self-hosted engine) with shared storage (SAN, ISCSI). > > According to https://www.ovirt.org/download/ the following Operating > Systems are supported with the latest oVirt version (4.4.4): > - Red Hat Enterprise Linux 8.3 > - CentOS Linux 8.3 > - CentOS Stream (Tech Preview) > > My doubts are: > - RHEL 8.3 is free to use up tp 16 hosts, but until when? Red Hat can > decide at anytime to change their subscription program. > - CentOS Linux is no more, support will stop at the end of 2021. > - CentOS Stream is in Tech Preview. I don't like running production > environments on "tech preview / beta" versions. > > I would say CentOS 7, it will receive maintenance updates up to 2024, and > switch to RHEL in 2024 if the free-to-use program is still active. > Unfortunately, CentOS 7 seems not to be supported. > > On what Operating System are you running oVirt 4.4.4 and why? Any feedback > and advice is welcome. 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/2XHHPDCQTEMAFQQNMESEY2KVCLSLFM7A/ > ___ 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/HYKCUVNDO37M2EW626JTGSSJXHTLUYRG/
[ovirt-users] Re: ERROR: Installing oVirt Node & Hosted-Engine on one physical server
> Question 1: In General, can i install oVirt Node and hosted-engine on
one physical server?
Yes and single node hyperconverged is suggested for single node deployments.
> Question 2: What domain names should I specify in the DNS server and
which ones IP should I reserve?
You can use any domain name you have ownership of and control the DNS for,
as seen to and from your host and VMs
not localhost.
You want two hostnames that resolve to the same network/netmask, one for
the hypervisor, one for the engine VM.
The installer will create a network bridge for the engine VM off the host's
ethernet which the two will communicate over
and it will be available for any other VMs you deploy later with that
network..
This network must be reachable via your web browser, so it is usually a
public network address,
For updates, installation needs, etc. both host and engine will want to
reach out to the internet.
If you're planning on adding more storage servers, another network as a
private network and hostname that
resolves to it would be suggested, but it isn't necessary in the single
host case.
> Question 3: "Failed to connect to the host via ssh: ssh: connect to host
ovirt-engine-01.local port 22: No route to host" - Who and where is trying
to establish a connection via SSH?
The host will try to ssh to the engine VM and the engine VM will will try
to communicate to the host.
The main accounts are root and vdsm. I'm not sure of others.
On Sun, Mar 7, 2021 at 2:17 AM wrote:
> oVirt node 4.4.4
>
> Question 1: In General, can i install oVirt Node and hosted-engine on one
> physical server?
>
> Question 2: What domain names should I specify in the DNS server and which
> ones IP should I reserve?
>
> Question 3: "Failed to connect to the host via ssh: ssh: connect to host
> ovirt-engine-01.local port 22: No route to host" - Who and where is trying
> to establish a connection via SSH?
>
> Can someone reply to questions 1-3 above? Any help will be much
> appreciated.
>
> Thanks for the help,
> Ivan.
>
> Logs:
> ERROR otopi.ovirt_hosted_engine_setup.ansible_utils
> ansible_utils._process_output:109 fatal: [localhost]: FAILED! =>
> {"attempts": 180, "changed": true, "cmd": ["hosted-engine", "--vm-status",
> "--json"], "delta": "0:00:00.565239", "end": "2021-03-03 13:36:54.775239",
> "rc": 0, "start": "2021-03-03 13:36:54.21", "stderr": "",
> "stderr_lines": [], "stdout": "{\"1\": {\"host-id\": 1, \"host-ts\": 16377,
> \"score\": 3400, \"engine-status\": {\"vm\": \"up\", \"health\": \"bad\",
> \"detail\": \"Up\", \"reason\": \"failed liveliness check\"}, \"hostname\":
> \"mng-ovirt-engine-01.local\", \"maintenance\": false, \"stopped\": false,
> \"crc32\": \"2b3ee5d1\", \"conf_on_shared_storage\": true,
> \"local_conf_timestamp\": 16377, \"extra\":
> \"metadata_parse_version=1\\nmetadata_feature_version=1\\ntimestamp=16377
> (Wed Mar 3 13:36:48
> 2021)\\nhost-id=1\\nscore=3400\\nvm_conf_refresh_time=16377 (Wed Mar 3
> 13:36:48
> 2021)\\nconf_on_shared_storage=True\\nmaintenance=False\\nstate=EngineStarting\\nstopped=
> False\\n\", \"live-data\": true}, \"global_maintenance\": false}",
> "stdout_lines": ["{\"1\": {\"host-id\": 1, \"host-ts\": 16377, \"score\":
> 3400, \"engine-status\": {\"vm\": \"up\", \"health\": \"bad\", \"detail\":
> \"Up\", \"reason\": \"failed liveliness check\"}, \"hostname\":
> \"mng-ovirt-engine-01.local\", \"maintenance\": false, \"stopped\": false,
> \"crc32\": \"2b3ee5d1\", \"conf_on_shared_storage\": true,
> \"local_conf_timestamp\": 16377, \"extra\":
> \"metadata_parse_version=1\\nmetadata_feature_version=1\\ntimestamp=16377
> (Wed Mar 3 13:36:48
> 2021)\\nhost-id=1\\nscore=3400\\nvm_conf_refresh_time=16377 (Wed Mar 3
> 13:36:48
> 2021)\\nconf_on_shared_storage=True\\nmaintenance=False\\nstate=EngineStarting\\nstopped=False\\n\",
> \"live-data\": true}, \"global_maintenance\": false}"]}
>
> ERROR otopi.ovirt_hosted_engine_setup.ansible_utils
> ansible_utils._process_output:109 fatal: [localhost]: FAILED! =>
> {"changed": false, "msg": "Engine VM IP address is while the engine's
> he_fqdn ovirt-engine-01.local resolves to 10.0.2.250. If you are using
> DHCP, check your DHCP reservation configuration"}
>
> ERROR otopi.ovirt_hosted_engine_setup.ansible_utils
> ansible_utils._process_output:109 fatal: [localhost]: UNREACHABLE! =>
> {"changed": false, "msg": "Failed to connect to the host via ssh: ssh:
> connect to host ovirt-engine-01.local port 22: No route to host",
> "skip_reason": "Host localhost is unreachable", "unreachable": true}
> ___
> 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/VLNLHUJLKQ4SAJY6UJ4IBC3IIWXLP3WW/
>
[ovirt-users] Re: Cold Move VM Storage failing
Brilliant, thank you. ___ 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/PCTYYJ6ERFQQM7DQB6E6OQEXCOWQNBQ7/
[ovirt-users] Re: Gluster version upgrades
I was always running gluster ahead of ovirt's version. Just ensure that there are no pending heals and you always check release notes before upgrading gluster. Best Regards,Strahil Nikolov On Sun, Mar 7, 2021 at 9:15, Sketch wrote: Is the gluster version on an oVirt host tied to the oVirt version, or would it be safe to upgrade to newer versions of gluster? I have noticed gluster is often updated to new major versions on oVirt point release upgrades. We have some compute+storage hosts on 4.3.6 which can't be upgraded easily at the moment, but we are having some gluster issues that appear to be due to bugs that I wonder if upgrading might help. Would an in-place upgrade of gluster be a bad idea without also updating oVirt? ___ 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/XR47MTPOQ6XTPT7TOH6LGEWYCH2YKRS2/ ___ 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/5KI3L4ZFS4A35VURRHCTE7TBWT2YTHSS/
[ovirt-users] 4.4.4 Image Copying / Template Create Fails - No Such File
I've been wrestling with this all night, digging through various bits of
VDSM code trying to figure why and how this is happening. I need to make
some templates, but i simply can't.
VDSM command HSMGetAllTasksStatusesVDS failed: value=low level
Image copy failed: ("Command ['/usr/bin/qemu-img', 'convert', '-p',
'-t', 'none', '-T', 'none', '-f', 'raw', '-O', 'raw',
'/rhev/data-center/mnt/glusterSD/:_Temp/45740f16-b3c9-4bb5-ba5f-3e64657fb663/images/6f87b073-c4ec-42f2-87da-d1cb6a08a150/f2dfb779-b49c-4ec9-86cd-741f3fe5b781',
'/rhev/data-center/mnt/glusterSD/:_Temp/45740f16-b3c9-4bb5-ba5f-3e64657fb663/images/84e56da6-8c26-4518-80a4-20bc395214db/039c5ada-ad6d-45c0-8393-bd4db0bbc366']
failed with rc=1 out=b'' err=bytearray(b'qemu-img: error while writing
at byte 738197504: No such file or directory\\n')",) abortedcode=261
3/7/21 5:44:44 AM
Following the VDSM logs, i can see the new image gets created,
permissions set, etc... but as soon qemu-img starts, it fails like this.
I updated all hosts and the engine, rebooted the entire stack, to no
avail. So i detached the storage domain, and wiped every host and fresh
installed both engine and all nodes, imported the storage domain, and
still no dice. Storage domain is gluster volume, single node, created in
ovirt.
It happens when i make a template, copy an image, or make a new vm from
a template. I can still create new vms from blank, and upload images via
the web ui. Watching the gluster share, i can see the image being
created, but its deleted at some point. I appears to not be being
deleted by the template / copying process, as immediately after the
above error, i get this one.
VDSM command DeleteImageGroupVDS failed: Image does not exist in domain:
'image=4f359545-01a8-439b-832b-18c26194b066,
domain=b4507449-ac40-4e35-be66-56441bb696ac'
3/7/21 5:44:44 AM
I thought maybe garbage collection, but don't see any indication of that
in the logs.
Any ideas? I redacted host names from the log output.___
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/75BZNMZUH23ZWCUHCDYCJSC6EZ45UW5O/
[ovirt-users] Which Operating System to choose
I want to set up a small cluster consisting of 2 Hypervisor nodes (self-hosted engine) with shared storage (SAN, ISCSI). According to https://www.ovirt.org/download/ the following Operating Systems are supported with the latest oVirt version (4.4.4): - Red Hat Enterprise Linux 8.3 - CentOS Linux 8.3 - CentOS Stream (Tech Preview) My doubts are: - RHEL 8.3 is free to use up tp 16 hosts, but until when? Red Hat can decide at anytime to change their subscription program. - CentOS Linux is no more, support will stop at the end of 2021. - CentOS Stream is in Tech Preview. I don't like running production environments on "tech preview / beta" versions. I would say CentOS 7, it will receive maintenance updates up to 2024, and switch to RHEL in 2024 if the free-to-use program is still active. Unfortunately, CentOS 7 seems not to be supported. On what Operating System are you running oVirt 4.4.4 and why? Any feedback and advice is welcome. 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/2XHHPDCQTEMAFQQNMESEY2KVCLSLFM7A/
[ovirt-users] Re: Cold Move VM Storage failing
Hi, Thanks for reporting it. This issue already fixed and you will have it in the next build. On Sun, 7 Mar 2021 at 09:21, wrote: > Morning oVirt. > > I've rebuilt my oVirt environment and I'm currently on 4.4.5.8-1.el8. I > have storage presented via NFS. I'm unable to move / copy VM disks when > powered off. However I can Live migrate the disks when powered on. I have > three storage domains presented and this is repeated across all three no > matter where the storage is located. The disks are thin provisioned. I've > tried deactivating and detaching the disk and it's the same > NullPointerException error. > > 2021-03-06 15:13:17,010Z ERROR > [org.ovirt.engine.core.bll.storage.disk.image.CopyDataCommand] > (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-84) > [af63add0-0ef3-4049-8461-b564abedba02] Command > 'org.ovirt.engine.core.bll.storage.disk.image.CopyDataCommand' failed: null > 2021-03-06 15:13:17,010Z ERROR > [org.ovirt.engine.core.bll.storage.disk.image.CopyDataCommand] > (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-84) > [af63add0-0ef3-4049-8461-b564abedba02] Exception: > java.lang.NullPointerException > > Engine log with stack trace is at https://textuploader.com/1820f > > Vdsm log is at https://textuploader.com/1820z > > I'm just checking I've not missed something obvious before raising a bug > if neccessary > ___ > 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/7O4EFMSKFXGNYUOJXIP4S774XZTES26R/ > -- Regards, Eyal Shenitzky ___ 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/UT4CBML6OD5RNA23JVAQMKYAUKE4QCWL/
