[ovirt-users] Re: w2k19 runOnce GuestTools ISO missing

[Liran Rotenberg]

Hi Uli,
The WGT ISO should be on ISO domain(deprecated) or on your data storage. It
won't be available if it's on the engine/nodes.

Regards,
Liran

On Wed, Jan 5, 2022 at 8:25 AM hellweiss  wrote:

> It is working now.
> I added an ISO Storage Domain and uploaded virtio-win.iso
> I didn't have one before because it was marked as deprecated.
>
> Best
>
> Uli
> ___
> 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/G2C54UOQKTKS55UUDSSBC4A7WCBIEFOR/
>
___
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/KIZ5XOC4KDVAS5G2QUSSJBUFMBMJSZAU/

[ovirt-users] Re: After upgrade to vdsm-4.40.90.4-1.el8 - Internal JSON-RPC error - how to fix?

[Liran Rotenberg]

On Thu, Jan 6, 2022 at 9:20 AM Adam Xu  wrote:

> I also got the error when I try to import an ova from vmware to my ovirt
> cluster using a san storage domain.
>
> I resovled this by importing this ova to a standalone host which is using
> its local storage.
> 在 2021/11/18 17:41, John Mortensen 写道:
>
> Hi,
> After we upgraded to vdsm-4.40.90.4-1.el8 on our two node cluster two things 
> has happned:
> 1. First node that was upgraded now continuously logs this error:
> VDSM  command Get Host Statistics failed: Internal JSON-RPC error: 
> {'reason': "'str' object has no attribute 'decode'"}
>
> Hi,
Looks like [1], however in that report the import process succeeded despite
those errors.
Can you please share the import logs?

[1] https://bugzilla.redhat.com/show_bug.cgi?id=2026809

> 2. During import of two virtual machines from VMware (has done multible 
> before upgrade) the import seems to never finish - currently running on day 
> 2-3...  any clues how to fix this?
> /John
>
> Import and engine logs would be helpful.

> ___
> 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/5AA3L6IEXNCTFRJXARWJPW5A26AOXJYV/
>
> ___
> 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/MWD4ZKXB2SJINOYANVBZCJCJFQQ2TI5O/
>
___
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/SP5K7MOQFUSGCYDUI6X5RCYPZTFCXSR5/

[ovirt-users] sanlock issues after 4.3 to 4.4 migration

[Strahil Nikolov via Users]

Hello All,

I was trying to upgrade my single node setup (Actually it used to be 2+1 
arbiter, but one of the data nodes died) from 4.3.10 to 4.4.? 

The deployment failed on 'hosted-engine --reinitialize-lockspace --force' and 
it seems that sanlock fails to obtain a lock:

# hosted-engine --reinitialize-lockspace --force
Traceback (most recent call last):
  File "/usr/lib64/python3.6/runpy.py", line 193, in _run_module_as_main
"__main__", mod_spec)
  File "/usr/lib64/python3.6/runpy.py", line 85, in _run_code
exec(code, run_globals)
  File 
"/usr/lib/python3.6/site-packages/ovirt_hosted_engine_setup/reinitialize_lockspace.py",
 line 30, in 
ha_cli.reset_lockspace(force)
  File 
"/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/client/client.py", 
line 286, in reset_lockspace
stats = broker.get_stats_from_storage()
  File 
"/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py", 
line 148, in get_stats_from_storage
result = self._proxy.get_stats()
  File "/usr/lib64/python3.6/xmlrpc/client.py", line 1112, in __call__
return self.__send(self.__name, args)
  File "/usr/lib64/python3.6/xmlrpc/client.py", line 1452, in __request
verbose=self.__verbose
  File "/usr/lib64/python3.6/xmlrpc/client.py", line 1154, in request
return self.single_request(host, handler, request_body, verbose)
  File "/usr/lib64/python3.6/xmlrpc/client.py", line 1166, in single_request
http_conn = self.send_request(host, handler, request_body, verbose)
  File "/usr/lib64/python3.6/xmlrpc/client.py", line 1279, in send_request
self.send_content(connection, request_body)
  File "/usr/lib64/python3.6/xmlrpc/client.py", line 1309, in send_content
connection.endheaders(request_body)
  File "/usr/lib64/python3.6/http/client.py", line 1268, in endheaders
self._send_output(message_body, encode_chunked=encode_chunked)
  File "/usr/lib64/python3.6/http/client.py", line 1044, in _send_output
self.send(msg)
  File "/usr/lib64/python3.6/http/client.py", line 982, in send
self.connect()
  File 
"/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/lib/unixrpc.py", line 
74, in connect
self.sock.connect(base64.b16decode(self.host))
FileNotFoundError: [Errno 2] No such file or directory

# grep sanlock /var/log/messages | tail
Jan  6 08:29:48 ovirt2 sanlock[1269]: 2022-01-06 08:29:48 19341 [77108]: s1777 
failed to read device to find sector size error -223 
/run/vdsm/storage/ca3807b9-5afc-4bcd-a557-aacbcc53c340/39ee18b2-3d7b-4d48-8a0e-3ed7947b5038/d95ae3ee-b6d3-46c4-b6a2-75f96134c7f1
Jan  6 08:29:49 ovirt2 sanlock[1269]: 2022-01-06 08:29:49 19342 [1310]: s1777 
add_lockspace fail result -223
Jan  6 08:29:54 ovirt2 sanlock[1269]: 2022-01-06 08:29:54 19347 [77113]: s1778 
failed to read device to find sector size error -223 
/run/vdsm/storage/ca3807b9-5afc-4bcd-a557-aacbcc53c340/39ee18b2-3d7b-4d48-8a0e-3ed7947b5038/d95ae3ee-b6d3-46c4-b6a2-75f96134c7f1
Jan  6 08:29:55 ovirt2 sanlock[1269]: 2022-01-06 08:29:55 19348 [1310]: s1778 
add_lockspace fail result -223
Jan  6 08:30:00 ovirt2 sanlock[1269]: 2022-01-06 08:30:00 19353 [77138]: s1779 
failed to read device to find sector size error -223 
/run/vdsm/storage/ca3807b9-5afc-4bcd-a557-aacbcc53c340/39ee18b2-3d7b-4d48-8a0e-3ed7947b5038/d95ae3ee-b6d3-46c4-b6a2-75f96134c7f1
Jan  6 08:30:01 ovirt2 sanlock[1269]: 2022-01-06 08:30:01 19354 [1311]: s1779 
add_lockspace fail result -223
Jan  6 08:30:06 ovirt2 sanlock[1269]: 2022-01-06 08:30:06 19359 [77144]: s1780 
failed to read device to find sector size error -223 
/run/vdsm/storage/ca3807b9-5afc-4bcd-a557-aacbcc53c340/39ee18b2-3d7b-4d48-8a0e-3ed7947b5038/d95ae3ee-b6d3-46c4-b6a2-75f96134c7f1
Jan  6 08:30:07 ovirt2 sanlock[1269]: 2022-01-06 08:30:07 19360 [1310]: s1780 
add_lockspace fail result -223
Jan  6 08:30:12 ovirt2 sanlock[1269]: 2022-01-06 08:30:12 19365 [77151]: s1781 
failed to read device to find sector size error -223 
/run/vdsm/storage/ca3807b9-5afc-4bcd-a557-aacbcc53c340/39ee18b2-3d7b-4d48-8a0e-3ed7947b5038/d95ae3ee-b6d3-46c4-b6a2-75f96134c7f1
Jan  6 08:30:13 ovirt2 sanlock[1269]: 2022-01-06 08:30:13 19366 [1310]: s1781 
add_lockspace fail result -223


# sanlock client status
daemon 5f37f400-b865-11dc-a4f5-2c4d54502372
p -1 helper
p -1 listener
p -1 status
s 
ca3807b9-5afc-4bcd-a557-aacbcc53c340:1:/rhev/data-center/mnt/glusterSD/ovirt2\:_engine44/ca3807b9-5afc-4bcd-a557-aacbcc53c340/dom_md/ids:0


Could it be related to the sector size of the Gluster's Brick?

# smartctl -a /dev/sdb | grep  'Sector Sizes'
Sector Sizes: 512 bytes logical, 4096 bytes physical


Any hint will be helpful


Best Regads,
Strahil Nikolov
___
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@o

[ovirt-users] Re: After upgrade to vdsm-4.40.90.4-1.el8 - Internal JSON-RPC error - how to fix?

[Adam Xu]

I also got the error when I try to import an ova from vmware to my ovirt 
cluster using a san storage domain.


I resovled this by importing this ova to a standalone host which is 
using its local storage.


在 2021/11/18 17:41, John Mortensen 写道:

Hi,
After we upgraded to vdsm-4.40.90.4-1.el8 on our two node cluster two things 
has happned:
1. First node that was upgraded now continuously logs this error:
VDSM  command Get Host Statistics failed: Internal JSON-RPC error: {'reason': 
"'str' object has no attribute 'decode'"}
2. During import of two virtual machines from VMware (has done multible before 
upgrade) the import seems to never finish - currently running on day 2-3...  
any clues how to fix this?
/John
___
Users mailing list --users@ovirt.org
To unsubscribe send an email tousers-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/5AA3L6IEXNCTFRJXARWJPW5A26AOXJYV/___
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/MWD4ZKXB2SJINOYANVBZCJCJFQQ2TI5O/

[ovirt-users] Re: did 4.3.9 reset bug https://bugzilla.redhat.com/show_bug.cgi?id=1590266

[Yedidyah Bar David]

Hi Sohail,

On Thu, Jan 6, 2022 at 8:38 AM  wrote:
>
> Hi Guys
>
> I am facing same issue in my recent deployment.

Can you please clarify what issue you refer to? You replied to a
1.5-years-old thread without any context.

> There is nothing in the log that points towards the issue. I am deploying the 
> VM on host with Centros Stream OS. Anybody recently faced this issue? Please 
> let me know if need any further information.

Please provide more details: What exact error message you get, at what
point, relevant logs. Thanks.

Best regards,
-- 
Didi
___
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/3WF2XYVWJ4JMKAMPJYBLW2FLM32AX6KF/

[ovirt-users] Re: did 4.3.9 reset bug https://bugzilla.redhat.com/show_bug.cgi?id=1590266

[sohail_akhter3]

Hi Guys

I am facing same issue in my recent deployment. There is nothing in the log 
that points towards the issue. I am deploying the VM on host with Centros 
Stream OS. Anybody recently faced this issue? Please let me know if need any 
further information.

Many Thanks.

Regards
Sohail
___
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/VN6WXMLVIZKW4J4SHSFUHLY4BH5V75X2/

[ovirt-users] Re: Important changes to the oVirt Terraform Provider

[marek]

Hi,

any plan for release?

Marek

Dne 06/10/2021 v 12:53 Janos Bonic napsal(a):


Dear oVirt community,

We are making sweeping and backwards-incompatible changes to the oVirt 
Terraform provider. *We want your feedback before we make these changes.*


Here’s the short list what we would like to change, please read the 
details below.


 1. The current |master| branch will be renamed to |legacy|. The usage
of this provider will be phased out within Red Hat around the end
/ beginning of next year. If you want to create a fork, we are
happy to add a link to your fork to the readme.
 2. A new |main| branch will be created and a *new Terraform provider*
written from scratch on the basis of go-ovirt-client
. (Preview here
)
This provider will only have limited functionality in its first
release.
 3. This new provider will be released to the Terraform registry, and
will have full test coverage and documentation. This provider will
be released as version v2.0.0 when ready to signal that it is
built on the Terraform SDK v2.
 4. A copy of this new Terraform provider will be kept in the |v1|
branch and backported to the Terraform SDK v1 for the benefit of
the OpenShift Installer .
We will not tag any releases, and we will not release this
backported version in binary form.
 5. We are hosting a *community call* on the 14th of October at 13:00
UTC on this link . Please
join to provide feedback and suggest changes to this plan.


Why are we doing this?

The original Terraform provider 
 for oVirt was 
written four years ago by @Maigard  at 
EMSL-MSC . The 
oVirt fork of this provider is about 2 years old and went through 
rapid expansion, adding a large number of features.


Unfortunately, this continuous rapid growth came at a price: the 
original test infrastructure deteriorated and certain resources, 
especially the virtual machine creation ballooned to a size we feel 
has become unmaintainable.


If you tried to contribute to the Terraform provider recently, you may 
have noticed that our review process has become extremely slow. We can 
no longer run the original tests, and our end to end test suite is not 
integrated outside of the OpenShift CI system. Every change to the 
provider requires one of only 3 people to review the code and also run 
a manual test suite that is currently only runable on one computer.


We also noticed an increasing number of bugs reported on OpenShift on 
oVirt/RHV related to the Terraform provider.


Our original plan was that we would fix the test infrastructure and 
then subsequently slowly transition API calls to go-ovirt-client, but 
that resulted in a PR that is over 5000 lines in code 
 and 
cannot in good conscience be merged in a single piece. Splitting it up 
is difficult, and would likely result in broken functionality where 
test coverage is not present.



What are we changing for you, the users?

First of all, documentation. You can already preview the documentation 
here 
. 
You will notice that the provider currently only supports a small set 
of features. You can find the full list of features 
 
we are planning for the first release on GitHub. However, if you are 
using resources like cluster creation, etc. these will currently not 
work and we recommend sticking to the old provider for the time being.


The second big change will be how resources are treated. Instead of 
creating large resources that need to call several of the oVirt APIs 
to create, we will create resources that are only calling one API. 
This will lead to fewer bugs. For example:


  * |ovirt_vm| will create the VM, but not attach any disks or network
interfaces to it.
  * |ovirt_disk_attachment| or |ovirt_disk_attachments| will attach a
disk to the VM.
  * |ovirt_nic| will create a network interface.
  * |ovirt_vm_start| will start the virtual machine when provisioned,
stop it when deprovisioned.

You can use the |depends_on| 
 
meta-argument to make sure disks and network interfaces are attached 
before you start the VM. Alternatively, you can hot-plug network 
interfaces later. For example:


|resource "ovirt_vm" "test" { cluster_id = "some-cluster-id" 
template_id = "some-template-id" } resource "ovirt_disk" "test" { 
storagedomain_id = "some-storage-domain-id" format = "cow" size = 512 
alias = "test" sparse = true }

[ovirt-users] Need help in dumping a table

[matthew.st...@fujitsu.com]

I'm planning a re-organization of my oVirt environment.

I need a Postgres command-line to dump a listing of VMs/disks/storage_domains.
___
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/TZPK5JLWDOXWLGH3MIB3RT2C5OJKAK5S/

[ovirt-users] Re: Instability after update

[Ritesh Chikatwar]

Hello 

What’s the qemo version if it’s greater then 6.0.0 then 
Can you please try downgrading qemu version to 6.0.0 and see if it helps? 

Sent from my iPhone

> On 05-Jan-2022, at 21:37, Andrea Chierici  
> wrote:
> 
> Cheers,
> I am in trouble...
> I am running an ovirt manager v4.4.9.5-1.el8. This week I updated all the 
> hosts to latest release (starting from repo 
> ovirt-release44-4.4.9.3-1.el8.noarch) since I hadn't done that when I 
> upgraded the manager. Before that the system was rock solid. Unfortunately, 
> after the upgrade, I get frequent errors on running VMs:
> 
> VM  is down with error. Exit message: Lost connection with qemu 
> process.
> 
> I can't get any hint from the logs, I wonder if someone has any idea of what 
> is going on.
> Thanks,
> 
> Andrea
> 
> 
> -- 
> Andrea Chierici - INFN-CNAF
> Viale Berti Pichat 6/2, 40127 BOLOGNA
> Office Tel: +39 051 2095463
> SkypeID ataruz
> --
> ___
> 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/OJWRVWGH55VP5LK4ATSUMAMJVR4DBXXZ/
___
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/EKUSCKBT2WKPOVTUXK7JH4LQTPRLMMVN/

[ovirt-users] Instability after update

[Andrea Chierici]

Cheers,
I am in trouble...
I am running an ovirt manager v4.4.9.5-1.el8. This week I updated all 
the hosts to latest release (starting from repo 
ovirt-release44-4.4.9.3-1.el8.noarch) since I hadn't done that when I 
upgraded the manager. Before that the system was rock solid. 
Unfortunately, after the upgrade, I get frequent errors on running VMs:


VM  is down with error. Exit message: Lost connection with qemu 
process.


I can't get any hint from the logs, I wonder if someone has any idea of 
what is going on.

Thanks,

Andrea


--
Andrea Chierici - INFN-CNAF 
Viale Berti Pichat 6/2, 40127 BOLOGNA
Office Tel: +39 051 2095463 
SkypeID ataruz
--
___
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/OJWRVWGH55VP5LK4ATSUMAMJVR4DBXXZ/