[ovirt-users] Re: VM Unknow Status

[Andrei Verovski via Users]

Hi,

You have to ask Sandro or Arik on this list, I don’t know.

PS. Can you just shut down this node, force remove, and reinstall again ?


> On 12 Jan 2024, at 11:17, ankit--- via Users  wrote:
> 
> Hi Andrei,
> 
> FYI .. On 4th Jan 2024 this node itself rebooted. 
> 
> 1. Yes, i did already restart node. 
> 
> 2. i have tried to delete SNMP as it has some issue because it was getting 
> timeout intermittently and noticed that vdsm warning and found and compared 
> packages from working node some packages were missing. But after reboot vdsm 
> status is ok. 
> 
> 3. What is table name for host or node in the database? Actually, the node is 
> non-responsive mode when i tried to bring it into maintenance mode so it's 
> giving an error that some VM's are still running on this host so cannot go in 
> maintenance mode but it in host>>virtual machine is showing 7 VM, however it 
> has no VM running on it. So tried to change the status from database. But I 
> am unable to find a table or say where I need to change or update.
> 
> Can you please suggest where i need to update the status of host>>virtual 
> machine.
> 
> Regards,
> Ankit Sharma
> ___
> 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/3TRKDY3G3TB5WF4SHJL3IO2BPRGBN4LW/
___
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/E6GDON2TTGKQ47OUGCHUE5EFBGRGBKT3/

[ovirt-users] Re: VM Unknow Status

[Andrei Verovski via Users]

Hi,

Can you just restart node?

So you manually did delete some packages in problematic node? It so it was not 
a good idea.


> On 11 Jan 2024, at 12:38, ankit--- via Users  wrote:
> 
> Hi Andrei,
> 
> Many thanks. I was able to change the unknown VM's status to down and after 
> that able to move on another node.
> 
> 1. But still non-responsive node is not able to go in Maintenace mode. It 
> gives VM error "Error while executing action: Cannot switch Host to 
> Maintenance mode. Host still has running VMs on it and is in Non-Responsive 
> state."
> 
> 2. nodectl check 
> 
> Status: OK
> Bootloader ... OK
>  Layer boot entries ... OK
>  Valid boot entries ... OK
> Mount points ... OK
>  Separate /var ... OK
>  Discard is used ... OK
> Basic storage ... OK
>  Initialized VG ... OK
>  Initialized Thin Pool ... OK
>  Initialized LVs ... OK
> Thin storage ... OK
>  Checking available space in thinpool ... OK
>  Checking thinpool auto-extend ... OK
> vdsmd ... OK
> =
> 
> 3. service vdsmd status
> Redirecting to /bin/systemctl status vdsmd.service
> Unit vdsmd.service could not be found.
> 
> 4. I have checked vdsm packages installed in working node and non-working 
> node and found that somehow following packages are missing..
> 
> vdsm-4.30.46-1.el7.x86_64
> vdsm-gluster-4.30.46-1.el7.x86_64
> vdsm-hook-ethtool-options-4.30.46-1.el7.noarch
> vdsm-hook-vmfex-dev-4.30.46-1.el7.noarch
> vdsm-hook-fcoe-4.30.46-1.el7.noarch
> 
> 5.When i tried to install this package "vdsm-4.30.46-1.el7.x86_64" so gets 
> error"Error: Package: vdsm-4.30.46-1.el7.x86_64 (/vdsm-4.30.46-1.el7.x86_64)
>   Requires: vdsm-hook-vmfex-dev = 4.30.46-1.el7"
> 
> and 
> 
> if i tried to install this vdsm-hook-vmfex-dev = 4.30.46-1.el7 so get error : 
> Error: Package: vdsm-hook-fcoe-4.30.46-1.el7.noarch 
> (/vdsm-hook-fcoe-4.30.46-1.el7.noarch)
>   Requires: vdsm = 4.30.46-1.el7.
> 
> So, how can reinstall either vdsm or remove node and reinsert successfully?
> 
> Regards,
> Ankit Sharma
> ___
> 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/X24UYAMO4KDOKPQLFEYSYRP5IW6V2VI4/
___
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/VKPUGQXYJ6EWBAGVKWVLCW22TKLIEGI3/

[ovirt-users] Re: VM Unknow Status

[Andrei Verovski via Users]

Hi,

Here is my instruction:

https://www.youtube.com/watch?v=vm55caHxRj8 



> On 10 Jan 2024, at 19:31, ankit--- via Users  > wrote:
> 
> One of node is got non-responsive suddenly and some VM stuck on Unknow 
> Status, I am trying to change status but unable to login in DB. 
> 
> su - postgres
> 
> psql engine 
> psql command not found error.
> 
> Can someone help me to get rid of it?
> 
> Thanks,
> Ankit Sharma
> ___
> 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/CROU2NZCAILXRACSDFHFSPNK4ARB3H2B/
>  
> 

___
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/4MLYLI4WMWOC6NF6MOZUB7OW6SNLVOUK/

[ovirt-users] Re: oVirt 4.6 OS versions

[Andrei Verovski]

Hi, Samuel,

What about HP drivers on Rocky Linux 9 for HP Gen8 RAID cards and SNMP?

Are these software packs fro HP repository can be installed without problems?
HP Service Pack for ProLiant
HP Management Component Pack for ProLiant

Thanks in advance.


> On 13 Dec 2023, at 02:59, samuel@horebdata.cn wrote:
> 
> Plus one
> 
> Do Right Thing (做正确的事) / Pursue Excellence (追求卓越) / Help Others Succeed (成就他人)
>  
> From: d03
> Date: 2023-12-13 06:41
> To: users
> Subject: [ovirt-users] Re: oVirt 4.6 OS versions
>  
> We have had positive experience with Rocky Linux 9.  We run RL9 for most
> of our VMs under oVirt 4.4.  We also run RL9 on some of our stand-alone
> HP Gen8 servers.  We are also currently running oVirt 4.4 on HP Gen8
> servers and will probably run oVirt 4.6 on HP Gen8 servers.
>  
> So, my vote is for Rocky Linux 9 as a base for oVirt 4.6 .?!
>  
> ---
>  
> On 12/12/2023 6:22 AM, Sandro Bonazzola wrote:
> > As oVirt is no longer a RHV-Next upstream, I don't see a reason for
> > trying to convince the community to keep using CentOS Stream as the
> > chosen OS for 4.6 development. As a community, you all can suggest which
> > OS you'd like to have in your datacenter, gather consensus about it and
> > change oVirt as it best fits to the winning OS.
> >
> > Il giorno mar 12 dic 2023 alle ore 12:08 Fabrice Bacchella
> > mailto:fabrice.bacche...@orange.fr>> ha
> > scritto:
> >
> > Whatever it’s Redhat or a clone, the situation is the same, Stream
> > is a risky path, independently of the reliability of the OS by itself.
> >
> >> Le 12 déc. 2023 à 11:29, Fabrice Bacchella
> >> mailto:fabrice.bacche...@orange.fr>>
> >> a écrit :
> >>
> >> I have a problem with CentOS stream.
> >>
> >> The purpose of Redhat and clone is to have good hardware and
> >> software support. Vendors will provide tools and driver to know OS
> >> versions. I’m afraid that in case of problems with  Stream
> >> release, I will be on my own, with unexpected broken node in case
> >> of kernel regression in an hardware driver.
> >>
> >>> Le 12 déc. 2023 à 08:39, Sandro Bonazzola  >>> > a écrit :
> >>>
> >>> Il giorno lun 11 dic 2023 alle ore 21:43  >>> > ha scritto:
> >>>
> >>>
> >>> Has it yet been decided which OS and version will be used for
> >>> the oVirt
> >>> 4.6 Hosted Engine and for 4.6 oVirt Node?
> >>>
> >>>
> >>> As far as I can tell, no. There was a discussion about rebasing
> >>> on CentOS Stream 10 or on Fedora in this list, but I haven't seen
> >>> any patch related to that or any proposal to vote for one of them
> >>> within the community.
> >>>
> >>> --
> >>> Sandro Bonazzola
> >>> MANAGER, SOFTWARE ENGINEERING
> >>> Red Hat In-Vehicle Operating System
> >>>
> >>> Red Hat EMEA 
> >>>
> >>> 
> >>>
> >>> **
> >>> *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/VHHBZQVLD5AYNUO3HBDXK53TBDMYT7RN/
> >>>  
> >>> 
> >>
> >> ___
> >> 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/YCBXO43YIBW2QY3CEBEEF7UPG3XZT475/
> >>  
> >> 
> >
> >
> >
> > --
> >
> > Sandro Bonazzola
> >
> > MANAGER, SOFTWARE ENGINEERING
> >
> > Red Hat In-Vehicle Operating System
> >
> > Red Hat EMEA 
> >
> > 
> >
> > **
> > *Red Hat respects your work life balance. Therefore 

[ovirt-users] Re: Upgrading manger from 4.4 to 4.5 - repo/dependency issues

[Andrei Verovski]

Hi,

In that case what is the latest EL supported by oVirt Node installation (not 
stock node image, native software install from oVirt web) ?
Thanks.

> On 27 Nov 2023, at 14:56, Nathanaël Blanchet via Users  
> wrote:
> 
> Hello Jeremy,
> Unforunately ovirt development have been stopped one year ago with
> el8.7 and setup haven't been tested for above releases of el. You may
> try to relaunch engine-setup on an outdated el 8.7 release and test if
> it is possible to update to 8.9 after a successful installation.
> 
> engine setup success in such conditions are just hypothetics and not
> tested.
> 
> 
> Le vendredi 24 novembre 2023 à 17:40 +,
> jeremy_tourvi...@hotmail.com a écrit :
>> My system is Rocky 8.9
>> I am running into some issues with upgrading.  I am following the
>> guide -
>> https://www.ovirt.org/documentation/upgrade_guide/index.html#Upgrading_the_Manager_to_4-5_4-4_local_db
>> I also followed
>> https://www.ovirt.org/download/install_on_rhel.html and took care of
>> the Rocky sepecific section along with the "Common to RHEL 8.6 and
>> derivatives"
>> 
>> When running the upgrade 3.2. Updating the oVirt Engine, step #3
>> engine-setup fails with:
>> 
>> [ ERROR ] DNF
>>  Problem 1: package ovirt-engine-4.5.4-1.el8.noarch from
>> centos-ovirt45 requires postgresql-jdbc >=
>> 42.2.
>>   14, but none of the providers can be installed
>>   - cannot install the best candidate for the job
>>   - package postgresql-jdbc-42.2.14-0.1.el8_6.noarch from
>> centos-ovirt45 is filtered out by exclude
>> filte
>>   ring
>>   - package postgresql-jdbc-42.2.27-1.el8.noarch from
>> centos-ovirt45 is filtered out by exclude filtering
>>   - package postgresql-jdbc-42.2.14-2.el8.noarch from
>> appstream is filtered out by exclude filtering
>>   - package postgresql-jdbc-42.2.14-2.el8.noarch from devel
>> is filtered out by exclude filtering
>>  Problem 2: problem with installed package ovirt-engine-
>> 4.4.10.7-1.el8.noarch
>>   - cannot install the best update candidate for package
>> ovirt-engine-4.4.10.7-1.el8.noarch
>>   - cannot install the best update candidate for package
>> ansible-runner-service-1.0.7-1.el8.noarch
>>   - package ovirt-engine-4.5.3.1-1.el8.noarch from centos-
>> ovirt45 requires postgresql-jdbc >= 42.2.14,
>> bu   
>>t none of the providers can be installed
>>   - package ovirt-engine-4.5.3.2-1.el8.noarch from centos-
>> ovirt45 requires postgresql-jdbc >= 42.2.14,
>> bu   
>>t none of the providers can be installed
>>   - package ovirt-engine-4.5.4-1.el8.noarch from centos-
>> ovirt45 requires postgresql-jdbc >= 42.2.14,
>> but  
>>  none of the providers can be installed
>>   - package ovirt-engine-4.5.1.2-1.el8.noarch from ovirt-45-
>> upstream requires postgresql-jdbc >=
>> 42.2.14, 
>>   but none of the providers can be installed
>>   - package ovirt-engine-4.5.1.3-1.el8.noarch from ovirt-45-
>> upstream requires postgresql-jdbc >=
>> 42.2.14, 
>>   but none of the providers can be installed
>>   - package ovirt-engine-4.5.2.2-1.el8.noarch from ovirt-45-
>> upstream requires postgresql-jdbc >=
>> 42.2.14, 
>>   but none of the providers can be installed
>>   - package ovirt-engine-4.5.2.4-1.el8.noarch from ovirt-45-
>> upstream requires postgresql-jdbc >=
>> 42.2.14, 
>>   but none of the providers can be installed
>>   - package ovirt-engine-4.5.2.5-1.el8.noarch from ovirt-45-
>> upstream requires postgresql-jdbc >=
>> 42.2.14, 
>>   but none of the providers can be installed
>>   - package postgresql-jdbc-42.2.14-0.1.el8_6.noarch from
>> centos-ovirt45 is filtered out by exclude
>> filte
>>   ring
>>   - package postgresql-jdbc-42.2.27-1.el8.noarch from
>> centos-ovirt45 is filtered out by exclude filtering
>>   - package postgresql-jdbc-42.2.14-2.el8.noarch from
>> appstream is filtered out by exclude filtering
>>   - package postgresql-jdbc-42.2.14-2.el8.noarch from devel
>> is filtered out by exclude filtering
>>  Problem 3: problem 

[ovirt-users] Q: New node install failed

[Andrei Verovski]

Hi,

I’m trying to install new node same way as I did several times before, with 
oVirt 4.5.2.4-1el8.
HP Proliant with clean install of CentOS Stream 9 (in previous installs some 
time ago I used Stream 8). 
Add new node failed with this error (at the bottom of this e-mail), 
ovirt-host-deploy-ansible-20230803161025-node15.starlett.lv-827b7fc4-68b6-410f-aa90-f33884923ee8.log
 (from /var/log/ovirt-engine/host-deploy/)

I can attach the whole log but it looks it is not necessary.
My engine runs on dedicated PC and is NOT hosted engine.

Thanks in advance for any help.
Andrei



[root@node15 ~]# dnf repolist --enabled
repo id   repo name
appstream CentOS 
Stream 9 - AppStream
baseosCentOS 
Stream 9 - BaseOS
extras-common CentOS 
Stream 9 - Extras packages

--

2023-08-03 16:10:44 EEST - TASK [ovirt-host-deploy-vdsm : Install 
ovirt-hosted-engine-setup package] **
2023-08-03 16:10:47 EEST - {
  "uuid" : "b1ffdae5-0679-40c3-8609-1a5b976edc0e",
  "counter" : 99,
  "stdout" : "fatal: [node15.starlett.lv]: FAILED! => {\"changed\": false, 
\"failures\": [\"No package ovirt-hosted-engine-setup available.\"], \"msg\": 
\"Failed to install some of the specified packages\", \"rc\": 1, \"results\": 
[]}",
  "start_line" : 87,
  "end_line" : 88,
  "runner_ident" : "281cf22b-29e3-4b4f-adc4-a47028b1ba59",
  "event" : "runner_on_failed",
  "pid" : 3199,
  "created" : "2023-08-03T13:10:45.632672",
  "parent_uuid" : "525400a7-0063-c9c3-eaa2-022c",
  "event_data" : {
"playbook" : "ovirt-host-deploy.yml",
"playbook_uuid" : "dcb4654e-2e81-4090-a60e-b007a715eda6",
"play" : "all",
"play_uuid" : "525400a7-0063-c9c3-eaa2-0006",
"play_pattern" : "all",
"task" : "Install ovirt-hosted-engine-setup package",
"task_uuid" : "525400a7-0063-c9c3-eaa2-022c",
"task_action" : "yum",
"task_args" : "",
"task_path" : 
"/usr/share/ovirt-engine/ansible-runner-service-project/project/roles/ovirt-host-deploy-vdsm/tasks/packages.yml:6",
"role" : "ovirt-host-deploy-vdsm",
"host" : "node15.starlett.lv",
"remote_addr" : "node15.starlett.lv",
"res" : {
  "failures" : [ "No package ovirt-hosted-engine-setup available." ],
  "results" : [ ],
  "rc" : 1,
  "msg" : "Failed to install some of the specified packages",
  "invocation" : {
"module_args" : {
  "name" : [ "ovirt-hosted-engine-setup" ],
  "state" : "present",
  "allow_downgrade" : false,
  "autoremove" : false,
  "bugfix" : false,
  "cacheonly" : false,
  "disable_gpg_check" : false,
  "disable_plugin" : [ ],
  "disablerepo" : [ ],
  "download_only" : false,
  "enable_plugin" : [ ],
  "enablerepo" : [ ],
  "exclude" : [ ],
  "installroot" : "/",
  "install_repoquery" : true,
  "install_weak_deps" : true,
  "security" : false,
  "skip_broken" : false,
  "update_cache" : false,
  "update_only" : false,
  "validate_certs" : true,
  "lock_timeout" : 30,
  "allowerasing" : false,
  "nobest" : false,
  "conf_file" : null,
  "disable_excludes" : null,
  "download_dir" : null,
  "list" : null,
  "releasever" : null
}
  },
  "_ansible_no_log" : false,
  "changed" : false
},
"start" : "2023-08-03T13:10:43.563744",
"end" : "2023-08-03T13:10:45.632205",
"duration" : 2.068461,
"ignore_errors" : null,
"event_loop" : null,
"uuid" : "b1ffdae5-0679-40c3-8609-1a5b976edc0e"
  }
}



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

[ovirt-users] Re: How restore nodes ovirt UP from NonResponsive and VMs executing

[Andrei Verovski]

Hi,

Here is my video tutorial for solution of this problem.

https://www.youtube.com/watch?v=vm55caHxRj8



> On 27 Jul 2023, at 18:53, José Pascual  wrote:
> 
> Hello,
> 
> I have ovirt with two nodes that are NonResponsive and all the VMs are 
> properly executing but i cant manage them because are in Unknown state. It 
> seems that nodes lost connection for a while with their gateway.
> 
> I have thought of first restarting the node where the engine is not running 
> and trying to put in UP. Then restart the engine from within de VM to see if 
> it starts up on this node.
> 
> 
> What is the proper way of restoring management? I 
> 
> 
> 
> 
> 
> 
> Thanks,
> Best Regards
> -- 
> Saludos,
> José Pascual Gallud Martínez 
> 
>   ___
> 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/WXRPVJUZIELYQFMACKBZXX6XDNTREF7Z/

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

[ovirt-users] Tutorial: How to Fix Struck Zombie VM Problem

[Andrei Verovski]

Hi,

I made short video tutorial on Youtube - how to fix struck zombie VM problem.

https://www.youtube.com/watch?v=vm55caHxRj8

with best regards
Andrei
___
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/GIUFQ4XRACRSMZ6FTHW5V46H5H3YP3DZ/

[ovirt-users] oVirt and Oracle Linux Virtualization Manager

[Andrei Verovski]

Hi,

Does Oracle plan to continue active development of oVirt, since it is released 
as Oracle Linux Virtualization Manager ?

with best regards
Andrei

___
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/6RKN57UKDBUKZEPM64T7I3H4HZ5MKSBP/

[ovirt-users] Re: Q: VNC Certificate Issue with Windows Server 2022 VM

[Andrei Verovski]

Hi,

Thanks for everyone who replied !

I switched console options to SPICE and everything is OK now.



> On 7 Mar 2023, at 12:16, Volenbovskyi, Konstantin 
>  wrote:
> 
> Hi,
> You need to check whether you use VNC or Spice and check certificates on 
> ovirt host(s)
> /etc/pki/vdsm/libvirt-vnc/server-cert.pem
> /etc/pki/vdsm/libvirt-spice/server-cert.pem
> And the idea is that certificate is signed by CA that is trusted by your 
> client and is not expired.
> 
> Maybe following solutions will be useful : 
> https://access.redhat.com/solutions/6978772 and 
> https://access.redhat.com/solutions/6859551
> 
> BR,
> Konstantin
> 
> On 07.03.23, 09:39, "Andrei Verovski"  <mailto:andre...@starlett.lv>> wrote:
> 
> 
> 
> 
> Hi,
> 
> 
> I have strange issue with certificate trying to connect to Windows Server 
> 2022 VM with Compute -> Virtual machines -> Console:
> Unable to connect to graphic server …console.vv, the certificate is not 
> trusted.
> 
> 
> Same issue with Firefox and Chrome.
> 
> 
> Anyone knows how to fix this?
> 
> 
> Thanks in advance.
> Andrei
> ___
> Users mailing list -- users@ovirt.org <mailto:users@ovirt.org>
> To unsubscribe send an email to users-le...@ovirt.org 
> <mailto:users-le...@ovirt.org>
> Privacy Statement: https://www.ovirt.org/privacy-policy.html 
> <https://www.ovirt.org/privacy-policy.html>
> oVirt Code of Conduct: 
> https://www.ovirt.org/community/about/community-guidelines/ 
> <https://www.ovirt.org/community/about/community-guidelines/>
> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org 
> <mailto:users@ovirt.org>/message/4K3KS63JYHRPZEOR4PNCFMZLFS52OCMO/
> 
> 
> 
___
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/DUGQZ2MXJZ554O73PBRPJVNZUDPOAJ6I/

[ovirt-users] Q: VNC Certificate Issue with Windows Server 2022 VM

[Andrei Verovski]

Hi,

I have strange issue with certificate trying to connect to Windows Server 2022 
VM with Compute -> Virtual machines -> Console:
Unable to connect to graphic server …console.vv, the certificate is not trusted.

Same issue with Firefox and Chrome.

Anyone knows how to fix this?

Thanks in advance.
Andrei
___
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/4K3KS63JYHRPZEOR4PNCFMZLFS52OCMO/

[ovirt-users]Q: Node host “non-operational”

[Andrei Verovski]

Hi,

Is it possible to get node host out of “non-operational” status if one of the 
logical networs is down?


2022-12-14 10:03:15,573+02 INFO  
[org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] 
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-61) 
[77796fef] START, SetVdsStatusVDSCommand(HostName = node11, 
SetVdsStatusVDSCommandParameters:{hostId='3c854f9c-2cdd-423e-bca0-37964ba76702',
 status='NonOperational', nonOperationalReason='NETWORK_UNREACHABLE', 
stopSpmFailureLogged='false', maintenanceReason='null'}), log id: 34ecf0f2
2022-12-14 10:03:15,645+02 ERROR 
[org.ovirt.engine.core.bll.SetNonOperationalVdsCommand] 
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-61) 
[77796fef] Host 'node11' is set to Non-Operational, it is missing the following 
networks: 'DMZ_node14'


Thanks in advance
Andrei

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

[ovirt-users]Re: About oVirt’s future

[Andrei Verovski]

Hi, Sandro,


What are plans for oVirt development and/or migrations for large users, for 
example Brussel Airport ?



> On 15 Nov 2022, at 10:31, Sandro Bonazzola  wrote:
> 
> 
> 
> Il giorno lun 14 nov 2022 alle ore 23:40 Frank Wall  > ha scritto:
> Hi Didi,
> 
> thanks for keeping us updated. However, I'm concerned...
> 
> > Ultimately, the future of oVirt lies in the hands of the community. If
> > you, as a community member, use and like oVirt, and want to see it
> > thrive, now is the best time to help with this!
> 
> I don't want to be rude, but this sounds to me like no developers
> have shown interest in keeping oVirt alive. Is this true? Is no other
> company actively developing oVirt anymore?
> 
> I've contacted directly all the companies with oVirt downstreams I was aware 
> of.
> I also contacted almost all the universities that asked for help in this 
> mailing list.
> I ended up contacting the major RHEL derivatives distributions.
> So far nobody stepped in to take an active role on the oVirt project.
> I saw some patches coming from individual contributors here and there but no 
> company investment so far.
> 
>  
> 
> > We worked hard over the last year or so on making sure the oVirt
> > project will be able to sustain development even without much
> > involvement from us - including moving most of the infrastructure from
> > private systems that were funded by/for oVirt/RHV, elsewhere - code
> > review from Gerrit to GitHub, and CI (Continuous Integration) from
> > jenkins to GitHub/Copr/CentOS CBS.
> 
> I appreciate the effort to make the source code accessible. However,
> I'm also wondering: was any sort of governing organization established,
> so that development could actually take place when RedHat pulls the 
> plug?
> 
> Yes, oVirt has an open governance: 
> https://www.ovirt.org/community/about/governance.html 
> 
> Right now in the oVirt board other than Red Hat there's a member of the 
> Caltech university https://www.ovirt.org/community/about/board.html 
> 
>  
> 
> The answer to this is probably related to my previous question, whether
> or not there are any non-RedHat developers involved.
> 
> 
> Ciao
> - Frank
> ___
> 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/5DQ3OLT3B5QALLFUK4OMKDYJEJXSYP7A/
>  
> 
> 
> 
> -- 
> Sandro Bonazzola
> MANAGER, SOFTWARE ENGINEERING - Red Hat In-Vehicle OS
> 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/IVCGZXVNOAFE44ASIH6UFZGURL3OUFRW/

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

[ovirt-users] Re: expired host certificate

[Andrei Verovski]

Hi,

Yes, please share this ansible role, I had this problem in the past and it was 
nightmare.
Thanks in advance.

> On 16 Nov 2022, at 20:21, j...@usa.net wrote:
> 
> Hi, I got the same issue yesterday when I was trying to migrate a VM. The 
> migration failed because of the expired certificate. As I cannot migrate and 
> VMs must be running I could not put the hypervisor in maintenance mode and do 
> an "Enroll Certificate".
> Instead I found a manual way to renew the certificates and has now created an 
> ansible role/playbook for it that will renew certificates and restart service 
> vdsmd and libvirtd.
> Let me know if you would like to get a copy of the ansible role.
> ___
> 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/XBL2OCDIIYERODQE7QXDP7ZRN3LHONYR/
___
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/RDUNP6MKEXZMLZ6TTGZIPTAHDTXEELHC/

[ovirt-users] Re: Manually Remove Snapshots

[Andrei Verovski]

Checked my old notes, had to directly alter PostgreSQL db several times, 
yet my cases were different.


I think this can be still fixed with editing PostgeSQL database directly.
A blueprint for your solution may be found here, someone from Red Hat 
had to clarify:

https://noeschanga.wordpress.com/2018/02/09/how-to-solve-snapshots-state-locked-in-ovirt-4-1/

This for example is a fix for unknown VM status.
su - postgres
psql engine

select vm_guid from vm_static where vm_name='MyProblematicVM';

   vm_guid
--
 b1b8d576-9567--y-xxx
(1 row)

select status from vm_dynamic where 
vm_guid='b1b8d576-9567--y-xxx';


 status

  7
(1 row)

update vm_dynamic SET status=0 where 
vm_guid='b1b8d576-9567--y-xxx';
update vm_dynamic SET run_on_vds=null  WHERE 
vm_guid='b1b8d576-9567--y-xxx';



On 9/23/22 20:22, Clint Boggio wrote:

Attempting to create another snapshot fails with this snippit:
- Result: 'cleanSuccess'
-- Message: 'VDSGenericException: VDSErrorException: Failed in vdscommand to 
HSMGetAllTasksStatusesVDS, error = Cannot create volume snapshot from illegal 
volume: (u'576b2761-a5bc-427b-95a9-0594447f0705',)',
-- Exception: 'VDSGenericException: VDSErrorException: Failed in vdscommand to 
HSMGetAllTasksStatusesVDS, error = Cannot create volume snapshot from illegal 
volume: (u'576b2761-a5bc-427b-95a9-0594447f0705',)'
2022-09-23 12:17:08,031-05 INFO  
[org.ovirt.engine.core.bll.tasks.CommandAsyncTask] 
(EE-ManagedThreadFactory-engineScheduled-Thread-41) [] 
CommandAsyncTask::endActionIfNecessary: All tasks of command 
'2505390c-dd54-41ff-91f5-b56af5b0b3ee' has ended -> executing 'endAction'
2022-09-23 12:17:08,031-05 INFO  
[org.ovirt.engine.core.bll.tasks.CommandAsyncTask] 
(EE-ManagedThreadFactory-engineScheduled-Thread-41) [] 
CommandAsyncTask::endAction: Ending action for '1' tasks (command ID: 
'2505390c-dd54-41ff-91f5-b56af5b0b3ee'): calling endAction '.
2022-09-23 12:17:08,032-05 INFO  
[org.ovirt.engine.core.bll.tasks.CommandAsyncTask] 
(EE-ManagedThreadFactory-engine-Thread-73809) [] 
CommandAsyncTask::endCommandAction [within thread] context: Attempting to 
endAction 'CreateSnapshot',
2022-09-23 12:17:08,041-05 INFO  
[org.ovirt.engine.core.bll.snapshots.CreateSnapshotCommand] 
(EE-ManagedThreadFactory-engine-Thread-73809) 
[dacd81ee-2d8c-4f8e-a590-181c0082bcea] Command 
[id=2505390c-dd54-41ff-91f5-b56af5b0b3ee]: Updating status to 'FAILED', The 
command end method logic will be executed by one of its parent commands.
2022-09-23 12:17:08,042-05 INFO  
[org.ovirt.engine.core.bll.tasks.CommandAsyncTask] 
(EE-ManagedThreadFactory-engine-Thread-73809) 
[dacd81ee-2d8c-4f8e-a590-181c0082bcea] CommandAsyncTask::HandleEndActionResult 
[within thread]: endAction for action type 'CreateSnapshot' completed, handling 
the result.
2022-09-23 12:17:08,042-05 INFO  
[org.ovirt.engine.core.bll.tasks.CommandAsyncTask] 
(EE-ManagedThreadFactory-engine-Thread-73809) 
[dacd81ee-2d8c-4f8e-a590-181c0082bcea] CommandAsyncTask::HandleEndActionResult 
[within thread]: endAction for action type 'CreateSnapshot' succeeded, clearing 
tasks.
2022-09-23 12:17:08,042-05 INFO  [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] 
(EE-ManagedThreadFactory-engine-Thread-73809) 
[dacd81ee-2d8c-4f8e-a590-181c0082bcea] SPMAsyncTask::ClearAsyncTask: Attempting 
to clear task '835aef5c-ff62-4d14-aa24-4b82321e866d'
2022-09-23 12:17:08,043-05 INFO  
[org.ovirt.engine.core.vdsbroker.irsbroker.SPMClearTaskVDSCommand] 
(EE-ManagedThreadFactory-engine-Thread-73809) 
[dacd81ee-2d8c-4f8e-a590-181c0082bcea] START, SPMClearTaskVDSCommand( 
SPMTaskGuidBaseVDSCommandParameters:{storagePoolId='31fdd642-6b06-11ea-a4c4-00163e333bd2',
 ignoreFailoverLimit='false', taskId='835aef5c-ff62-4d14-aa24-4b82321e866d'}), 
log id: a9fec48
2022-09-23 12:17:08,043-05 INFO  
[org.ovirt.engine.core.vdsbroker.vdsbroker.HSMClearTaskVDSCommand] 
(EE-ManagedThreadFactory-engine-Thread-73809) 
[dacd81ee-2d8c-4f8e-a590-181c0082bcea] START, HSMClearTaskVDSCommand(HostName = 
hprvsr02.locacore.com, 
HSMTaskGuidBaseVDSCommandParameters:{hostId='ecad78a5-58e3-4fcd-8b84-e30e3e1993cf',
 taskId='835aef5c-ff62-4d14-aa24-4b82321e866d'}), log id: 6712f5cc
2022-09-23 12:17:08,076-05 INFO  
[org.ovirt.engine.core.vdsbroker.vdsbroker.HSMClearTaskVDSCommand] 
(EE-ManagedThreadFactory-engine-Thread-73809) 
[dacd81ee-2d8c-4f8e-a590-181c0082bcea] FINISH, HSMClearTaskVDSCommand, return: 
, log id: 6712f5cc
2022-09-23 12:17:08,076-05 INFO  
[org.ovirt.engine.core.vdsbroker.irsbroker.SPMClearTaskVDSCommand] 
(EE-ManagedThreadFactory-engine-Thread-73809) 
[dacd81ee-2d8c-4f8e-a590-181c0082bcea] FINISH, SPMClearTaskVDSCommand, return: 
, log id: a9fec48
2022-09-23 12:17:08,087-05 INFO  [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] 
(EE-ManagedThreadFactory-engine-Thread-73809) 
[dacd81ee-2d8c-4f8e-a590-181c0082bcea] BaseAsyncTask::removeTaskFromDB: Removed 
task 

[ovirt-users] Re: Manually Remove Snapshots

[Andrei Verovski]

Hi,

There is another way to make a clone.
Can you create a new snapshot, and make a new VM based on this snapshot?


> On 23 Sep 2022, at 17:23, Clint Boggio  wrote:
> 
> I just tried that clone method per your suggestion and I got "VDSM command 
> CopyImageVDS failed: Image is not a legal chain: 
> (u'6af66318-e6f8-45d7-8b4e-2183faf0a917',)"
> ___
> 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/GFV3BWAL3YP24GKDZNWOJT6L6PX2SWUJ/
___
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/JANIWAKABSHVHKEWVQJXNHTWXILP7JPP/

[ovirt-users] Re: Manually Remove Snapshots

[Andrei Verovski]

Hi,

I think the only way is to clone VM and then destroy old copy, someone from 
oVirt dev team please comment.


> On 23 Sep 2022, at 17:07, Clint Boggio  wrote:
> 
> I've got a VM with a pair of snapshots that won't delete and I'm needing a 
> procedure to manually remove the snapshots. I don't need the VM and so while 
> i'd prefer not to destroy it, it wouldn't be critical if I did damage the VM 
> in the process. When I try to delete the snapshots that procedure fails, and 
> when I try to delete the disk that procedure fails. Any pointers would be 
> greatly appreciated.
> ___
> 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/CTTS2LLU57LLHR6NM7YQVU622CC2YWAQ/
___
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/W3AAAZ66WG3IVUZUEMTMNEBN27VCIOGX/

[ovirt-users] Re: Snapshot task stuck at oVirt 4.4.8

[Andrei Verovski]

Hi,


I also recommend upgrade to 4.5.x, it fixed a lot of bugs.


> On 20 Sep 2022, at 14:01, Jirka Simon  wrote:
> 
> Hi Nicolas,
> 
> 
> we had the same problem before we upgraded to 4.5.X
> 
> 
> you can check locks with  
> /usr/share/ovirt-engine/setup/dbutils/unlock_entity.sh -t all  -qc
> 
> 
> and then unlock
> 
> 
> /usr/share/ovirt-engine/setup/dbutils/unlock_entity.sh -t snapshot snapshot_id
> 
> 
> or sometime helped just power off and power on the VM and snapshot task 
> failed.
> 
> Jirka
> 
> 
> 
> On 9/20/22 10:26, nico...@devels.es  wrote:
>> Hi, 
>> 
>> We're running oVirt 4.4.8 and one of our users tried to create a snapshot on 
>> a VM. The snapshot task got stuck (not sure why) and since then a "locked" 
>> icon is being shown on the VM. We need to remove this VM, but since it has a 
>> pending task, we're unable. 
>> 
>> The ovirt-engine log shows hundreds of events like: 
>> 
>> [2022-09-20 09:23:09,286+01 INFO  
>> [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] 
>> (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-27) 
>> [2769dad5-3ec3-4c46-90a2-924746ea8d97] Command 'CreateSnapshotForVm' (id: 
>> '4fcb6ab7-2cd7-4a0c-be97-f6979be25bb9') waiting on child command id: 
>> 'cbb7a2c0-2111-4958-a55d-d48bf2d8591b' type:'CreateLiveSnapshotForVm' to 
>> complete 
>> 
>> An ovirt-engine restart didn't make any difference. 
>> 
>> Is there a way to remove this task manually, even changing something in the 
>> DB? 
>> 
>> 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/SWVFVEJFQ25N7OK2ZQQOX7FN7KXUS6JB/
>>  
>> 
> ___
> 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/3TXGF7RAKIGMFWW6FR3BBEB5AAC5RT5V/

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

[ovirt-users] Re: Certificate doesn't contain valid subject alternative name

[Andrei Verovski]

> On 15 Sep 2022, at 15:54, Strahil Nikolov  wrote:
> 
> Can you live migrate the VM?

Unfortunately, not, I have disabled this feature on all my VMs.

If this error is not critical, I’ll continue to use this node as is.

> 
> Best Regards, Strahil Nikolov 
> 
> On Thu, Sep 15, 2022 at 12:17, Andrei Verovski
>  wrote:
> ___
> Users mailing list -- users@ovirt.org <mailto:users@ovirt.org>
> To unsubscribe send an email to users-le...@ovirt.org 
> <mailto:users-le...@ovirt.org>
> Privacy Statement: https://www.ovirt.org/privacy-policy.html 
> <https://www.ovirt.org/privacy-policy.html>
> oVirt Code of Conduct: 
> https://www.ovirt.org/community/about/community-guidelines/ 
> <https://www.ovirt.org/community/about/community-guidelines/>
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/XNFRWGBB4Y6ECIPSRRFRMGNAQBZDUISQ/
>  
> <https://lists.ovirt.org/archives/list/users@ovirt.org/message/XNFRWGBB4Y6ECIPSRRFRMGNAQBZDUISQ/>
> 

___
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/2IRROTPCE3TME4X4D7B7LVTRWXKJNNIB/

[ovirt-users] Re: Certificate doesn't contain valid subject alternative name

[Andrei Verovski]

Hi,

I’m unexpectedly got same error on oVirt 4.5.2.4. 
Can’t stop node right now and enroll new certificates, its running essential 
VMs.


> On 1 Sep 2022, at 12:02, Ayansh Rocks  wrote:
> 
> Any one faced this issue or any solution from ovirt dev ?
> 
> On Mon, Aug 22, 2022 at 11:16 PM Ayansh Rocks  > wrote:
> Hi All,
> 
> I am getting below alert on my single node ovirt. Can anyone tell me more 
> about it and how I can fix it.I am using ovirt 4.3.8.2.
> 
> Certificate of host host-name.example.com  is 
> invalid. The certificate doesn't contain valid subject alternative name, 
> please enroll new certificate for the host.
> 
> 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/EAMMOIAQVPNZBES72TCCPTG6SAFKHVT5/

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

[ovirt-users] Re: Engine and host certificates expired

[Andrei Verovski]

Hi,

OK, I see you running hosted engine.
I have slightly different setup, engine runs on dedicated VM outside oVirt.


> On 7 Sep 2022, at 00:36, si...@justconnect.ie wrote:
> 
> I tried your 'Try restore old certificates and simply run again engine-setup' 
> but the validation fails with:
> -
> [ ERROR ] It seems that you are running your engine inside of the 
> hosted-engine VM and are not in "Global Maint 
> enance" mode.
> In that case you should put the system into the "Global Maintenance" 
> mode before running engine-setup, 
>  or the hosted-engine HA agent might kill 
> the machine, which might corrupt your data.
> 
> [ ERROR ] Failed to execute stage 'Setup validation': Hosted Engine setup 
> detected, but Global Maintenance is n 
> ot set.
> -
> even though I have placed it into Global Maintenance mode.
> 
> The problem is that all 3 hosts are currently 'Non Responsive'
> 
> FYI - In another environment where the vdsm certificates had expired on one 
> of 2 clusters, copying the certs from a host in the other cluster allowed the 
> hosts to become responsive so I could 'Enroll certificates'.
> 
> Shimme
> ___
> 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/6DEEYA6DPKGLJAAR5W2QVBJJ3CARYFT2/
___
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/N64OQSLPI37XOC27L5POYL2X374SBDCY/

[ovirt-users] Re: Engine and host certificates expired

[Andrei Verovski]

Hi,

I hope you have not erased old certificates which you must restore back.
You can't copy certificates from one host to another, it will not work.
Try restore old certificates and simply run again engine-setup.


On 9/6/22 23:06, si...@justconnect.ie wrote:

I have an environment where the engine wouldn’t start and the certificate 
expiry dates were as follows.

Host1 - 25th Sep 2022
Host2 - 11th Aug 2022
Host3 - 11th Aug 2022

I copied the vdsm certs from Host1 to Host2 & Host3

Engine then started on Host1 and then backed up.

Engine cert expiry 11th Aug 2022

I put the cluster into Global Maintenance mode and then tried:

‘engine-setup —offline’

Which failed as the validation check said the engine wasn’t in Global 
Maintenance mode even though ‘hosted-engine —vm-status said it was.

None of the Hosts are ‘GREEN’ (can’t remember what the status was as I’m 
writing this from memory) but their status is ’RED’.

There are VMs running on the 3 Hosts and I’m reluctant to restart anything at 
the moment.

Is there a way to refresh the engine certificate to get past this or do I need 
to restart vdsm service on each host to bring them back online as far as the 
engine is concerned?

The environment is currently at 4.4.6 and is to be upgraded to 4.5.2 next month.

Any help as always will be greatly appreciated.

Kind regards

Simon
___
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/SKGWY5ZIBAG5GTWHIPDUO5O64PUZN7Y2/

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

[ovirt-users] Re: Q: Engione 4.4.10 and New Host on CentOS Stream 9

[Andrei Verovski]

Hi,

Martin, thanks a lot, now I successfully upgraded Engine to latest 4.5, yet old 
nodes 4.2 / CentOS 7.6 still working fine.
Now I can move VMs and upgrade old nodes.


> On 29 Aug 2022, at 17:27, Martin Perina  wrote:
> 
> Hi,
> 
> you are mixing 2 unrelated versioning parts:
> 
> 1. Supported cluster levels
> - oVirt Engine 4.5 supports cluster level 4.2 - 4.7
>  
> https://github.com/oVirt/ovirt-engine/blob/master/backend/manager/modules/compat/src/main/java/org/ovirt/engine/core/compat/Version.java#L22
>  
> <https://github.com/oVirt/ovirt-engine/blob/master/backend/manager/modules/compat/src/main/java/org/ovirt/engine/core/compat/Version.java#L22>
> - This means that both EL7 based (4.2 and 4.3) and EL8 based (4.4-4.7) 
> hosts can be successfully managed by oVirtEngine 4.5
> 
> 2. OS requirements of oVirt Engine 4.5
> - oVirt Engine 4.5 is supported only on EL 8.6+ and CS8 stream
> - This means that:
> - for standalone engine you need to have a machine with EL8.6 or CS8
> - for hosted engine you need to have a cluster with EL8.6 or CS8 
> hosts, where hosted engine VM based on E8.6 or CS8 can run
> 
> So specifically for your use case you need:
> 
> 1. Standalone engine 4.5 running on EL8.6 or CS8, which can manage 4.2 hosts 
> in 4.2 cluster
> 2. Hosted engine 4.5 running on cluster of EL8.6 or CS8 hosts with additional 
> (different) 4.2 cluster, where your 4.2 hosts reside
> 
> Regards,
> Martin
> 
> 
> On Mon, Aug 29, 2022 at 2:43 PM Jirka Simon  <mailto:ji...@vesim.cz>> wrote:
> Hi Andrei,
> 
> ovirt 4.4+ has to run with centos/ rhel 8, I would not recommend mix 
> versions of ovirt node version within one cluster. (there couldbe / will 
> be a problem with vdsm version on each node)
> 
> And yes cluster compatibility version number doesn't match  ovirt version.
> 
> I would recommend to try to remove the oldest node from the cluster (if 
> upu have some spare nodes) and try to reinstall it to centos 8 or 9 with 
> standalone engine for test if it works or not.
> 
> Jirka
> 
> On 8/29/22 14:26, Andrei Verovski wrote:
> > Hi,
> >
> > My oldest nodes are version 4.2 on CentOS 7.6.
> > What is the latest cluster compatibility level they support?
> > Looks like oVirt Engine version and cluster compatibility level do not 
> > match number to number, e.g. my oVirt engine 4.4.10 seems can set cluster 
> > compatibility level up to 4.6.
> >
> > Someone from Red Hat, please clarify.
> > Thanks in advance.
> >
> >
> >> On 29 Aug 2022, at 15:09, Jirka Simon  >> <mailto:ji...@vesim.cz>> wrote:
> >>
> >> Hi Andrei,
> >>
> >> as I know,  you need to have to have your cluster with at least 4.3 
> >> version to migrate to 4.5. I was facing the same  problem with (not so) 
> >> old hardware. and i started to do step by step migration.
> >>
> >> it means i created new cluster with fresh configuration with ovirt 4.5  
> >> and cluster compatibility version 4.7 next to old one with 4.4.   Iit is a 
> >> good opportunity to prepare whole cluster configuration in ansible for me 
> >> :D
> >>
> >> Then I migrate VMs one by one from old cluster to the new one. When is one 
> >> node free on old cluster I reinstall it and add to new cluster.
> >>
> >> Maybe it is not the fastest solution, but i can arrange maintenance for 
> >> each VM.
> >>
> >> Jirka
> >>
> >> On 8/29/22 10:13, Andrei Verovski wrote:
> >>> Hi,
> >>>
> >>> I have cluster compatibility version 4.2, due to some old nodes.
> >>>  From what I remember in oVirt 4.5 release notes (correct please, may be 
> >>> wrong here), oVirt engine 4.5 requires cluster compatibility version >= 
> >>> 4.3.
> >>> Please clarify. Thanks.
> >>>
> >>>
> >>>>> On 28. 8. 2022, at 18:52, Andrei Verovski  >>>>> <mailto:andre...@starlett.lv>> wrote:
> >>>>>
> >>>>> Hi,
> >>>>>
> >>>>> I have engine version 4.4.10.7-1.el8, is it possible to set up new node 
> >>>>> host on CentOS Stream 9, or I need to upgrade engine to version 4.5 
> >>>>> first (which is not right now possible because of some quite old nodes) 
> >>>>> ?
> >>>> yes, you generally need the latest version
> >>>> You can keep your old nodes old, 4.2 based nodes are still working with 
> >>>> 

[ovirt-users] Re: Ovirt 4.4.7, can't renew certificate of ovirt engine (certificates expired)

[Andrei Verovski]

Hi,

Now certificates on engine and hosts don’t match, engine and vdsm services on 
hosts can’t handshake.

Here it is:
jlsanz - at - albasoft - dot - com


> On 30 Aug 2022, at 13:06, v...@itiviti.com wrote:
> 
> Hi Andrei,
> 
> thx a lot for your answer.
> 
> I tried several time the engine-setup command but it always ends with same 
> above error.
> 
> DO you have the email of Jose?
> 
> A colleague renewed the cert manually on the engine whith these commands:
> 
> # SUBJECT="$(openssl x509 -subject -noout -in 
> /etc/pki/ovirt-engine/certs/apache.cer.20220829164912 | sed 's/subject= //')"
> # /usr/share/ovirt-engine/bin/pki-enroll-pkcs12.sh --name=apache 
> --password="@PASSWORD@" --subject=/C=US/O=/CN=
> # openssl pkcs12 -passin "pass:@PASSWORD@" -nokeys -in 
> /etc/pki/ovirt-engine/keys/apache.p12 > /etc/pki/ovirt-engine/certs/apache.cer
> # openssl pkcs12 -passin "pass:@PASSWORD@" -nocerts -nodes -in 
> /etc/pki/ovirt-engine/keys/apache.p12 > 
> /etc/pki/ovirt-engine/keys/apache.key.nopass
> # chmod 0600 /etc/pki/ovirt-engine/keys/apache.key.nopass
> # systemctl restart httpd.service ovirt-engine.service
> 
> but now, our 2 hosts are unresponsive...
> 
> Thx
> ___
> 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/TOKUA5HCM2SSDSK6H45B7QLX7J6TTGSN/
___
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/6YJAKSCIXJT2MIBJL2AVIR5N6WLKHOBK/

[ovirt-users] Re: Ovirt 4.4.7, can't renew certificate of ovirt engine (certificates expired)

[Andrei Verovski]

Hi,

1) Try to run engine-setup again on oVirt Engine VM, and renew certificates.

2) I had even more nasty problem with zombie node host, which was 
completely unmanageable.
Jose from albasoft.com solved this problem, contact hem via e-mail if 
necessary.



On 8/29/22 20:32, v...@itiviti.com wrote:

Hi Team,

I'm looking for your help since I didn't find any clear documentation. Is there 
somewhere in ovirt website a clear documentation about how to renew the engine 
certificates located in /etc/pki/ovirt-engine/certs/

We have an engine GUI not working, showing error message "PKIX path validation 
failed: java.security.cert.CertPathValidatorException: validity check failed".

After checking, all the cert in /etc/pki/ovirt-engine/certs/ are expired.

I didn't find a clear documentation on ovirt website, or even on redhat website 
(it was always about host but not the engine)

Anyway I've read that the renew process can be done via "engine-setup 
--offline", but when I try it, it generates this error:

   --== PKI CONFIGURATION ==--

[ ERROR ] Failed to execute stage 'Environment customization': Unable to load 
certificate. See 
https://cryptography.io/en/latest/faq/#why-can-t-i-import-my-pem-file for more 
details.

and in log file:

  File 
"/usr/lib64/python3.6/site-packages/cryptography/hazmat/backends/openssl/backend.py",
 line 1371, in load_pem_x509_certificate
 "Unable to load certificate. See https://cryptography.io/en/la;
ValueError: Unable to load certificate. See 
https://cryptography.io/en/latest/faq/#why-can-t-i-import-my-pem-file for more 
details.
2022-08-29 19:16:29,502+0200 ERROR otopi.context context._executeMethod:154 
Failed to execute stage 'Environment customization': Unable to load 
certificate. See 
https://cryptography.io/en/latest/faq/#why-can-t-i-import-my-pem-file for more 
details.

I've also tried the manual procedure (using 
/usr/share/ovirt-engine/bin/pki-enroll-pkcs12.sh)  mentioned in 
https://users.ovirt.narkive.com/4ugjgicE/ovirt-regenerating-new-ssl-certificates-for-ovirt-engine
 (message from Alon Bar-Lev), but the 4th command always says I enter a wrogn 
apssword, but it's not.

we are blocked here and we can't use our ovirt cluster, so it's pretty blocking.

Thx a lot in advance
___
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/RYHJ4XJAYCAN3KVT7BJOGRUU6JEZTXCF/

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

[ovirt-users] Re: Q: Engione 4.4.10 and New Host on CentOS Stream 9

[Andrei Verovski]

Hi,

My oldest nodes are version 4.2 on CentOS 7.6.
What is the latest cluster compatibility level they support? 
Looks like oVirt Engine version and cluster compatibility level do not match 
number to number, e.g. my oVirt engine 4.4.10 seems can set cluster 
compatibility level up to 4.6.

Someone from Red Hat, please clarify.
Thanks in advance.


> On 29 Aug 2022, at 15:09, Jirka Simon  wrote:
> 
> Hi Andrei,
> 
> as I know,  you need to have to have your cluster with at least 4.3 version 
> to migrate to 4.5. I was facing the same  problem with (not so) old hardware. 
> and i started to do step by step migration.
> 
> it means i created new cluster with fresh configuration with ovirt 4.5  and 
> cluster compatibility version 4.7 next to old one with 4.4.   Iit is a good 
> opportunity to prepare whole cluster configuration in ansible for me :D
> 
> Then I migrate VMs one by one from old cluster to the new one. When is one 
> node free on old cluster I reinstall it and add to new cluster.
> 
> Maybe it is not the fastest solution, but i can arrange maintenance for each 
> VM.
> 
> Jirka
> 
> On 8/29/22 10:13, Andrei Verovski wrote:
>> Hi,
>> 
>> I have cluster compatibility version 4.2, due to some old nodes.
>> From what I remember in oVirt 4.5 release notes (correct please, may be 
>> wrong here), oVirt engine 4.5 requires cluster compatibility version >= 4.3.
>> Please clarify. Thanks.
>> 
>> 
>>>> On 28. 8. 2022, at 18:52, Andrei Verovski  wrote:
>>>> 
>>>> Hi,
>>>> 
>>>> I have engine version 4.4.10.7-1.el8, is it possible to set up new node 
>>>> host on CentOS Stream 9, or I need to upgrade engine to version 4.5 first 
>>>> (which is not right now possible because of some quite old nodes) ?
>>> yes, you generally need the latest version
>>> You can keep your old nodes old, 4.2 based nodes are still working with 4.5
>>> 
>>>> Thanks
>>>> Andrei
>>>> ___
>>>> 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/IC3ZW2XY7BAEAU3H72P4VA76Y63F32XU/
>> ___
>> 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/SZCOBNKBBSFUPNDWOIXRLVZ5OOJXHA7D/
___
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/C643UFIPQVG5MSFAR7PWYSHP4XUEZADR/

[ovirt-users] Re: Q: Engione 4.4.10 and New Host on CentOS Stream 9

[Andrei Verovski]

Hi,

I have cluster compatibility version 4.2, due to some old nodes. 
From what I remember in oVirt 4.5 release notes (correct please, may be wrong 
here), oVirt engine 4.5 requires cluster compatibility version >= 4.3.
Please clarify. Thanks.


> 
>> On 28. 8. 2022, at 18:52, Andrei Verovski  wrote:
>> 
>> Hi,
>> 
>> I have engine version 4.4.10.7-1.el8, is it possible to set up new node host 
>> on CentOS Stream 9, or I need to upgrade engine to version 4.5 first (which 
>> is not right now possible because of some quite old nodes) ?
> 
> yes, you generally need the latest version
> You can keep your old nodes old, 4.2 based nodes are still working with 4.5
> 
>> 
>> Thanks
>> Andrei
>> ___
>> 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/IC3ZW2XY7BAEAU3H72P4VA76Y63F32XU/
> 
___
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/SZCOBNKBBSFUPNDWOIXRLVZ5OOJXHA7D/

[ovirt-users] Q: Engione 4.4.10 and New Host on CentOS Stream 9

[Andrei Verovski]

Hi,

I have engine version 4.4.10.7-1.el8, is it possible to set up new node 
host on CentOS Stream 9, or I need to upgrade engine to version 4.5 
first (which is not right now possible because of some quite old nodes) ?


Thanks
Andrei
___
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/IC3ZW2XY7BAEAU3H72P4VA76Y63F32XU/

[ovirt-users] Q: Node Install on Fresh CentOS Stream 8

[Andrei Verovski]

Hi !


I'm going to install oVirt node software on CentOS 8 Stream (I don't use 
node image from Red Hat because of custom monitoring scripts).


Do I need to disable any stock repos (e.g. AppStream) in order to avoid 
installation of anything not suitable, e.g. newer version then one in 
oVirt repo, for oVirt node software?


Thanks in advance.
Andrei
___
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/4PY23LWRMBBW7W6LYPTNETN42QSQSTJX/

[ovirt-users] Re: Failed to delete snapshot

[Andrei Verovski]

Hi, Michal,

You mean latest oVirt engine sw or node sw?

I use Vinchin backup.


> On 23 Aug 2022, at 12:27, Michal Skrivanek  wrote:
> 
> 
> 
>> On 23. 8. 2022, at 10:53, Andrei Verovski > <mailto:andre...@starlett.lv>> wrote:
>> 
>> Hi,
>> 
>> I had same problem with VM of our accounting / stock control system, which 
>> is a top priority which can’t be down no matter what.
>> 
>> Solution: Make a new snapshot on problematic VM, then make a new VM from 
>> that snapshot. This is only a workaround I found so far.
> 
> Make sure you run latest version, there were plenty of live merge bugs solved 
> in the last months.
> Also if you're using vProtect you can likely use the new incremental 
> backup(CBT) feature, that avoids all the snapshotting in the first place
>> 
>> 
>> 
>>> On 23 Aug 2022, at 10:50, Jirka Simon >> <mailto:ji...@vesim.cz>> wrote:
>>> 
>>> Hello there. 
>>> 
>>> we have troubles with one VM ad it's snapshot 
>>> 
>>> here is  short log  from engine.log
>>> 
>>> 2022-08-23 09:02:38,735+02 INFO  
>>> [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] 
>>> (EE-ManagedThreadFactory-engine-Thread-1265784) 
>>> [4d79272b-ffac-4b2b-a987-8c19577cd8c4] CommandAsyncTask::
>>> HandleEndActionResult [within thread]: Removing CommandMultiAsyncTasks 
>>> object for entity '5842cafc-60d4-4131-8da1-8a909123f08c' 
>>> 2022-08-23 09:02:41,435+02 ERROR 
>>> [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand] 
>>> (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-68) 
>>> [4d79272b
>>> -ffac-4b2b-a987-8c19577cd8c4] Command id: 
>>> 'ead3fbba-7439-4337-8aaf-1d6cf65bbb15 failed child command status for step 
>>> 'REDUCE_IMAGE' 
>>> 2022-08-23 09:02:41,435+02 INFO  
>>> [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommandCallback]
>>>  (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-68) [
>>> 4d79272b-ffac-4b2b-a987-8c19577cd8c4] Command 
>>> 'RemoveSnapshotSingleDiskLive' id: 'ead3fbba-7439-4337-8aaf-1d6cf65bbb15' 
>>> child commands '[5b33d970-6ea0-4b8b-bc31-607afd8af1ca, 185d3fec-8c76-
>>> 44d3-a0a1-fe8fff331354, 308baf9d-1fc5-43a1-a624-b5f08f7bec1b, 
>>> f11f3550-4356-417e-af10-a3afb2051dec, 
>>> 5842cafc-60d4-4131-8da1-8a909123f08c]' executions were completed, status 
>>> 'FAILED' 
>>> 2022-08-23 09:02:42,445+02 ERROR 
>>> [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand] 
>>> (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-79) 
>>> [4d79272b
>>> -ffac-4b2b-a987-8c19577cd8c4] Merging of snapshot 
>>> '6634db4e-23d8-4849-a008-864f15d28c3d' images 
>>> 'd24a9199-741b-49cb-96d2-0d76fcd21f48'..'48af3301-0cbb-4a6e-97d1-7299e7de883f'
>>>  failed. Images
>>> have been marked illegal and can no longer be previewed or reverted to. 
>>> Please retry Live Merge on the snapshot to complete the operation. 
>>> 2022-08-23 09:02:42,451+02 ERROR 
>>> [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand] 
>>> (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-79) 
>>> [4d79272b
>>> -ffac-4b2b-a987-8c19577cd8c4] Ending command 
>>> 'org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand' 
>>> with failure. 
>>> 2022-08-23 09:02:42,457+02 INFO  
>>> [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] 
>>> (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-79) 
>>> [4d79272b-ffac
>>> -4b2b-a987-8c19577cd8c4] Command 'RemoveSnapshot' id: 
>>> '73340ac8-07d7-4de2-bfeb-8062fa1e8cfd' child commands 
>>> '[ead3fbba-7439-4337-8aaf-1d6cf65bbb15]' executions were completed, status 
>>> 'FAILE
>>> D' 
>>> 2022-08-23 09:02:43,470+02 ERROR 
>>> [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotCommand] 
>>> (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-22) 
>>> [4d79272b-ffac-4b2b-a98
>>> 7-8c19577cd8c4] Ending command 
>>> 'org.ovirt.engine.core.bll.snapshots.RemoveSnapshotCommand' with failure. 
>>> 2022-08-23 09:02:43,490+02 ERROR 
>>> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
>>> (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-22) 
>>> [4d79272b-ff
>>> ac-4b2b-a987-8c19577cd8c4] EVENT_ID: 
>>> USER_REMOVE_S

[ovirt-users] Re: Failed to delete snapshot

[Andrei Verovski]

Hi,

I had same problem with VM of our accounting / stock control system, which is a 
top priority which can’t be down no matter what.

Solution: Make a new snapshot on problematic VM, then make a new VM from that 
snapshot. This is only a workaround I found so far.



> On 23 Aug 2022, at 10:50, Jirka Simon  > wrote:
> 
> Hello there. 
> 
> we have troubles with one VM ad it's snapshot 
> 
> here is  short log  from engine.log
> 
> 2022-08-23 09:02:38,735+02 INFO  
> [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] 
> (EE-ManagedThreadFactory-engine-Thread-1265784) 
> [4d79272b-ffac-4b2b-a987-8c19577cd8c4] CommandAsyncTask::
> HandleEndActionResult [within thread]: Removing CommandMultiAsyncTasks object 
> for entity '5842cafc-60d4-4131-8da1-8a909123f08c' 
> 2022-08-23 09:02:41,435+02 ERROR 
> [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand] 
> (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-68) 
> [4d79272b
> -ffac-4b2b-a987-8c19577cd8c4] Command id: 
> 'ead3fbba-7439-4337-8aaf-1d6cf65bbb15 failed child command status for step 
> 'REDUCE_IMAGE' 
> 2022-08-23 09:02:41,435+02 INFO  
> [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommandCallback]
>  (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-68) [
> 4d79272b-ffac-4b2b-a987-8c19577cd8c4] Command 'RemoveSnapshotSingleDiskLive' 
> id: 'ead3fbba-7439-4337-8aaf-1d6cf65bbb15' child commands 
> '[5b33d970-6ea0-4b8b-bc31-607afd8af1ca, 185d3fec-8c76-
> 44d3-a0a1-fe8fff331354, 308baf9d-1fc5-43a1-a624-b5f08f7bec1b, 
> f11f3550-4356-417e-af10-a3afb2051dec, 5842cafc-60d4-4131-8da1-8a909123f08c]' 
> executions were completed, status 'FAILED' 
> 2022-08-23 09:02:42,445+02 ERROR 
> [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand] 
> (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-79) 
> [4d79272b
> -ffac-4b2b-a987-8c19577cd8c4] Merging of snapshot 
> '6634db4e-23d8-4849-a008-864f15d28c3d' images 
> 'd24a9199-741b-49cb-96d2-0d76fcd21f48'..'48af3301-0cbb-4a6e-97d1-7299e7de883f'
>  failed. Images
> have been marked illegal and can no longer be previewed or reverted to. 
> Please retry Live Merge on the snapshot to complete the operation. 
> 2022-08-23 09:02:42,451+02 ERROR 
> [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand] 
> (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-79) 
> [4d79272b
> -ffac-4b2b-a987-8c19577cd8c4] Ending command 
> 'org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand' 
> with failure. 
> 2022-08-23 09:02:42,457+02 INFO  
> [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] 
> (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-79) 
> [4d79272b-ffac
> -4b2b-a987-8c19577cd8c4] Command 'RemoveSnapshot' id: 
> '73340ac8-07d7-4de2-bfeb-8062fa1e8cfd' child commands 
> '[ead3fbba-7439-4337-8aaf-1d6cf65bbb15]' executions were completed, status 
> 'FAILE
> D' 
> 2022-08-23 09:02:43,470+02 ERROR 
> [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotCommand] 
> (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-22) 
> [4d79272b-ffac-4b2b-a98
> 7-8c19577cd8c4] Ending command 
> 'org.ovirt.engine.core.bll.snapshots.RemoveSnapshotCommand' with failure. 
> 2022-08-23 09:02:43,490+02 ERROR 
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
> (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-22) 
> [4d79272b-ff
> ac-4b2b-a987-8c19577cd8c4] EVENT_ID: 
> USER_REMOVE_SNAPSHOT_FINISHED_FAILURE(357), Failed to delete snapshot 
> 'vProtect 2022-08-05 22:33:44.088143' for VM 'web1.wiki.prod.hq.sldev.cz 
> -2'.
> 
> 
> 
> Snapshot can't be deleted, and VM is not possible to clone. 
> 
> 
> 
> thank you for any help. 
> 
> 
> 
> Jirka
> 
> ___
> 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/ZOVL22OGZKEG6BXPEB5JQUXX2GXDA2GD/
>  
> 

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

[ovirt-users] Re: Problems Installing oVirt 4.5 on Centos Stream 9

[Andrei Verovski]

Hi,

I also have stand-alone engine.
Just stick with Centos Stream 8 as host OS for Engine until it remains 
usable.
I don't think Centos 8 as engine host have to be in sync with Centos as 
node host OS.



On 8/21/22 06:07, David Johnson wrote:

Good evening all,

*High level goal:*
We are preparing to upgrade our hosting OS to Centos Stream 9, and 
update to the latest oVirt patch level.

We are running with a standalone engine.
The immediate goal is to stand up a brand new engine on bare metal 
running CentOS 9.
Once the new engine is configured, the engine database will be 
migrated from the current system production engine to the new to-be 
production engine and upgraded.
After successful engine upgrade, we will be commissioning a new host 
and then upgrading the hosts  in sequence.


*Problem:*
When installing the ovirt standalone engine, there is a requirement to 
follow the instructions at 
https://www.ovirt.org/download/install_on_rhel.html . I found I had to 
enable both epel and crb (formerly powertools) (both undocumented) 
before I could complete this step.


After following those instructions with the necessary pieces I had 
identified as missing, I returned to section 3.2 Enabling the oVirt 
Engine Repositories. The next step is:


[root@ovirt2 administrator]# *dnf install -y centos-release-ovirt45*
Last metadata expiration check: 0:12:58 ago on Sat 20 Aug 2022
09:50:00 PM CDT.
Package centos-release-ovirt45-9.1-2.el9s.noarch is already installed.
Dependencies resolved.
Nothing to do.
Complete!


Following this, The commands to enable the repositories all 
return "Error Unable to find a match: "


Sample:

[root@ovirt2 administrator]# *dnf module -y enable javapackages-tools*
Last metadata expiration check: 0:03:31 ago on Sat 20 Aug 2022
09:50:00 PM CDT.
Error: Problems in request:
missing groups or modules: javapackages-tools
[root@ovirt2 administrator]# *dnf module -y enable postgresql:12*
Last metadata expiration check: 0:07:43 ago on Sat 20 Aug 2022
09:50:00 PM CDT.
Error: Problems in request:
missing groups or modules: postgresql:12


Please advise.

*David Johnson*


___
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/Y5GZDJKN2DUMWW3WB4PJB35JMCE3W6YF/
___
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/6KARU7D7JHIVDCHEEEQGH3TVRB3R44DH/

[ovirt-users] Q: libvirtd-tls startup failure on node (v4.4.10)

[Andrei Verovski]

Hi,

I have one problematic node, and identified a culprit why vdsmd service 
can't start:


-- The unit libvirtd-tls.socket has entered the 'failed' state with 
result 'service-start-limit-hit'.

Aug 13 15:00:45 node14.starlett.lv systemd[1]: Closed Libvirt TLS IP socket.
-- Subject: Unit libvirtd-tls.socket has finished shutting down
-- Defined-By: systemd
-- Support: https://access.redhat.com/support

Node was installed on clean CentOS Stream from oVirt Web (not oVirt node 
disk image), and was working fine until recent problem with certificates.
Can't reinstall/reconfigure node from oVirt Web since it is marked as 
non-responsive.


How to fix this?
Thanks in advance for any help.

-

[root@node14 vdsm]# cat /etc/centos-release
CentOS Stream release 8

[root@node14 vdsm]# rpm -qa | grep vdsm
vdsm-api-4.40.100.2-1.el8.noarch
vdsm-hook-openstacknet-4.40.100.2-1.el8.noarch
vdsm-client-4.40.100.2-1.el8.noarch
vdsm-network-4.40.100.2-1.el8.x86_64
vdsm-hook-vhostmd-4.40.100.2-1.el8.noarch
vdsm-4.40.100.2-1.el8.x86_64
vdsm-http-4.40.100.2-1.el8.noarch
vdsm-common-4.40.100.2-1.el8.noarch
vdsm-hook-fcoe-4.40.100.2-1.el8.noarch
vdsm-python-4.40.100.2-1.el8.noarch
vdsm-jsonrpc-4.40.100.2-1.el8.noarch
vdsm-hook-ethtool-options-4.40.100.2-1.el8.noarch
vdsm-yajsonrpc-4.40.100.2-1.el8.noarch

[root@node14 vdsm]# vdsm-tool validate-config
SUCCESS: ssl configured to true. No conflicts

[root@node14 vdsm]# systemctl --failed
  UNIT  LOAD   ACTIVE SUBDESCRIPTION
● libvirtd.service  loaded failed failed Virtualization daemon
● libvirtd-admin.socket loaded failed failed Libvirt admin socket
● libvirtd-ro.socketloaded failed failed Libvirt local read-only socket
● libvirtd-tls.socket   loaded failed failed Libvirt TLS IP socket
● libvirtd.socket   loaded failed failed Libvirt local socket
___
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/SD5JVRWUSZ7SGOV6XOBJFPCQJVASUTJE/

[ovirt-users] Re: Certificates Expiration Problem - Urgent Help Needed

[Andrei Verovski]

I checked this bash vdsm-gencerts.sh, it does nothing if certificate files 
present.
Renamed old certificates to .*old, now new certificates present.

After vdsmd and vdsm-network restart:

node log:
Aug 09 12:10:44 node14.xxx vdsm[1399211]: WARN MOM not available. Error: [Errno 
111] Connection refused

Engine log:
2022-08-09 12:17:11,419+03 ERROR 
[org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring] 
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-11) [] 
Unable to RefreshCapabilities: VDSNetworkException: VDSGenericException: 
VDSNetworkException: Message timeout which can be caused by communication issues


Is this correct procedure or this new node’s certificates had to be imported 
somewhere into Engine?
I had to do a bit of hacking to get this node up and migrate accounting VM to 
another node.
Thanks.


> On 9 Aug 2022, at 11:16, Andrei Verovski  wrote:
> 
> /usr/libexec/vdsm/vdsm-gencerts.sh /etc/pki/vdsm/certs/cacert.pem 
> /etc/pki/vdsm/keys/vdsmkey.pem  /etc/pki/vdsm/certs/vdsmcert.pem
> 
> Yields nothing. No error messages, and no updated certificates in
> /etc/pki/vdsm/certs/
> 
>> On 9 Aug 2022, at 10:28, Andrei Verovski  wrote:
>> 
>> Hi,
>> 
>> Looks like this is a suitable article.
>> https://microdevsys.com/wp/get-host-capabilities-failed-general-sslengine-problem/
>> 
>> Please note I have problem with 
>> VDSM node14 command Get Host Capabilities failed: PKIX path validation 
>> failed: java.security.cert.CertPathValidatorException: validity check failed
>> 
>> only on 1 node, everything else works just fine.
>> 
>> 
>> Is this correct or outdated/obsolete ?
>> 
>> [root@mdskvm-p01 vdsm]# /usr/libexec/vdsm/vdsm-gencerts.sh 
>> /etc/pki/vdsm/certs/cacert.pem /etc/pki/vdsm/keys/vdsmkey.pem  
>> /etc/pki/vdsm/certs/vdsmcert.pem
>> [root@mdskvm-p01 vdsm]#
>> [root@mdskvm-p01 vdsm]# ls -altri /usr/libexec/vdsm/vdsm-gencerts.sh 
>> /etc/pki/vdsm/certs/cacert.pem /etc/pki/vdsm/keys/vdsmkey.pem  
>> /etc/pki/vdsm/certs/vdsmcert.pem
>> 67445862 -rwxr-xr-x. 1 root root 2362 Jul  9 05:36 
>> /usr/libexec/vdsm/vdsm-gencerts.sh
>>45255 -rw——-. 1 vdsm kvm  5816 Sep 28 17:48 /etc/pki/vdsm/keys/vdsmkey.pem
>> 203185926 -rw——-. 1 vdsm kvm  1127 Sep 28 17:48 
>> /etc/pki/vdsm/certs/cacert.pem
>> 203185790 -rw——-. 1 vdsm kvm  1241 Sep 28 17:48 
>> /etc/pki/vdsm/certs/vdsmcert.pem
>> [root@mdskvm-p01 vdsm]#
>> 
>> 
>> 
>> 
>>> On 9 Aug 2022, at 03:43, adam...@adagene.com.cn wrote:
>>> 
>>> Solution:
>>> https://access.redhat.com/solutions/3532921
>>> 
>>> -邮件原件-
>>> 发件人: Andrei Verovski  
>>> 发送时间: 2022年8月9日 3:14
>>> 收件人: users@ovirt.org
>>> 主题: [ovirt-users] Certificates Expiration Problem - Urgent Help Needed
>>> 
>>> Hi !
>>> 
>>> Today my hosts (engine + all nodes) certificates expired and I re-run 
>>> engine-setup to renew certificates.
>>> 
>>> Then I did for each node host:
>>> Edit host -> Advanced parameters -> Fetch SSH public key (PEM) in order to 
>>> update certificates on nodes, everything was finished just fine.
>>> 
>>> Unfortunately, one of the most crucial nodes (node14) still shows this
>>> error:
>>> 
>>> VDSM node14 command Get Host Capabilities failed: PKIX path validation
>>> failed: java.security.cert.CertPathValidatorException: validity check failed
>>> 
>>> Restarted vdsms and vdsm-network, still same, node is marked as 
>>> non-responsive, and all VM with "?" sign (unknown status).
>>> 
>>> However, node14 pings without any problem, its storage domain shown in 
>>> green (OK), and all VMs are running fine.
>>> 
>>> Service vdsm-network status is OK, vdsmd is NOT:
>>> Aug 08 22:07:27 node14.***.lv vdsm[1264164]: ERROR ssl handshake: socket 
>>> error, address: :::192.168.0.4
>>> 
>>> This node is running our accounting and stock control system, its storage 
>>> domain holds VM disk of that software. If its nonoperational after restart, 
>>> its a BIG trouble, I will not be able to migrate VM disk anywhere. 
>>> Restoring accounting DB from daily backup is a lengthy process for 2 - 3 
>>> hours.
>>> 
>>> Please advice what to do next.
>>> 
>>> Thanks in advance.
>>> ___
>>> Users mailing list -- users@ovirt.org
>>> To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: 
>

[ovirt-users]Re: 回复: Certificates Expiration Problem - Urgent Help Needed

[Andrei Verovski]

/usr/libexec/vdsm/vdsm-gencerts.sh /etc/pki/vdsm/certs/cacert.pem 
/etc/pki/vdsm/keys/vdsmkey.pem  /etc/pki/vdsm/certs/vdsmcert.pem

Yields nothing. No error messages, and no updated certificates in
/etc/pki/vdsm/certs/

> On 9 Aug 2022, at 10:28, Andrei Verovski  wrote:
> 
> Hi,
> 
> Looks like this is a suitable article.
> https://microdevsys.com/wp/get-host-capabilities-failed-general-sslengine-problem/
> 
> Please note I have problem with 
> VDSM node14 command Get Host Capabilities failed: PKIX path validation 
> failed: java.security.cert.CertPathValidatorException: validity check failed
> 
> only on 1 node, everything else works just fine.
> 
> 
> Is this correct or outdated/obsolete ?
> 
> [root@mdskvm-p01 vdsm]# /usr/libexec/vdsm/vdsm-gencerts.sh 
> /etc/pki/vdsm/certs/cacert.pem /etc/pki/vdsm/keys/vdsmkey.pem  
> /etc/pki/vdsm/certs/vdsmcert.pem
> [root@mdskvm-p01 vdsm]#
> [root@mdskvm-p01 vdsm]# ls -altri /usr/libexec/vdsm/vdsm-gencerts.sh 
> /etc/pki/vdsm/certs/cacert.pem /etc/pki/vdsm/keys/vdsmkey.pem  
> /etc/pki/vdsm/certs/vdsmcert.pem
>  67445862 -rwxr-xr-x. 1 root root 2362 Jul  9 05:36 
> /usr/libexec/vdsm/vdsm-gencerts.sh
> 45255 -rw——-. 1 vdsm kvm  5816 Sep 28 17:48 /etc/pki/vdsm/keys/vdsmkey.pem
> 203185926 -rw——-. 1 vdsm kvm  1127 Sep 28 17:48 /etc/pki/vdsm/certs/cacert.pem
> 203185790 -rw——-. 1 vdsm kvm  1241 Sep 28 17:48 
> /etc/pki/vdsm/certs/vdsmcert.pem
> [root@mdskvm-p01 vdsm]#
> 
> 
> 
> 
>> On 9 Aug 2022, at 03:43, adam...@adagene.com.cn wrote:
>> 
>> Solution:
>> https://access.redhat.com/solutions/3532921
>> 
>> -邮件原件-
>> 发件人: Andrei Verovski  
>> 发送时间: 2022年8月9日 3:14
>> 收件人: users@ovirt.org
>> 主题: [ovirt-users] Certificates Expiration Problem - Urgent Help Needed
>> 
>> Hi !
>> 
>> Today my hosts (engine + all nodes) certificates expired and I re-run 
>> engine-setup to renew certificates.
>> 
>> Then I did for each node host:
>> Edit host -> Advanced parameters -> Fetch SSH public key (PEM) in order to 
>> update certificates on nodes, everything was finished just fine.
>> 
>> Unfortunately, one of the most crucial nodes (node14) still shows this
>> error:
>> 
>> VDSM node14 command Get Host Capabilities failed: PKIX path validation
>> failed: java.security.cert.CertPathValidatorException: validity check failed
>> 
>> Restarted vdsms and vdsm-network, still same, node is marked as 
>> non-responsive, and all VM with "?" sign (unknown status).
>> 
>> However, node14 pings without any problem, its storage domain shown in green 
>> (OK), and all VMs are running fine.
>> 
>> Service vdsm-network status is OK, vdsmd is NOT:
>> Aug 08 22:07:27 node14.***.lv vdsm[1264164]: ERROR ssl handshake: socket 
>> error, address: :::192.168.0.4
>> 
>> This node is running our accounting and stock control system, its storage 
>> domain holds VM disk of that software. If its nonoperational after restart, 
>> its a BIG trouble, I will not be able to migrate VM disk anywhere. Restoring 
>> accounting DB from daily backup is a lengthy process for 2 - 3 hours.
>> 
>> Please advice what to do next.
>> 
>> Thanks in advance.
>> ___
>> 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/7ERPAMDT2KO4W6VYYMNTYIMDHH7WTZGB/
>> ___
>> 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/SLO6UKLSHM4IGYOAUVW25ZVV4B2FPCKY/
> 
> ___
> 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/FOC2BYMJVGB7BJDA4X2NT6LHAHMLLMYX/
___
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/C6WGV63BHPW5UXE7S53MI3Q6CWUQVFQ3/

[ovirt-users]Re: 回复: Certificates Expiration Problem - Urgent Help Needed

[Andrei Verovski]

Hi,

Looks like this is a suitable article.
https://microdevsys.com/wp/get-host-capabilities-failed-general-sslengine-problem/
 
<https://microdevsys.com/wp/get-host-capabilities-failed-general-sslengine-problem/>

Please note I have problem with 
VDSM node14 command Get Host Capabilities failed: PKIX path validation failed: 
java.security.cert.CertPathValidatorException: validity check failed

only on 1 node, everything else works just fine.


Is this correct or outdated/obsolete ?

[root@mdskvm-p01 vdsm]# /usr/libexec/vdsm/vdsm-gencerts.sh 
/etc/pki/vdsm/certs/cacert.pem /etc/pki/vdsm/keys/vdsmkey.pem  
/etc/pki/vdsm/certs/vdsmcert.pem
[root@mdskvm-p01 vdsm]#
[root@mdskvm-p01 vdsm]# ls -altri /usr/libexec/vdsm/vdsm-gencerts.sh 
/etc/pki/vdsm/certs/cacert.pem /etc/pki/vdsm/keys/vdsmkey.pem  
/etc/pki/vdsm/certs/vdsmcert.pem
 67445862 -rwxr-xr-x. 1 root root 2362 Jul  9 05:36 
/usr/libexec/vdsm/vdsm-gencerts.sh
45255 -rw——-. 1 vdsm kvm  5816 Sep 28 17:48 /etc/pki/vdsm/keys/vdsmkey.pem
203185926 -rw——-. 1 vdsm kvm  1127 Sep 28 17:48 /etc/pki/vdsm/certs/cacert.pem
203185790 -rw——-. 1 vdsm kvm  1241 Sep 28 17:48 /etc/pki/vdsm/certs/vdsmcert.pem
[root@mdskvm-p01 vdsm]#




> On 9 Aug 2022, at 03:43, adam...@adagene.com.cn wrote:
> 
> Solution:
> https://access.redhat.com/solutions/3532921
> 
> -邮件原件-
> 发件人: Andrei Verovski  
> 发送时间: 2022年8月9日 3:14
> 收件人: users@ovirt.org
> 主题: [ovirt-users] Certificates Expiration Problem - Urgent Help Needed
> 
> Hi !
> 
> Today my hosts (engine + all nodes) certificates expired and I re-run 
> engine-setup to renew certificates.
> 
> Then I did for each node host:
> Edit host -> Advanced parameters -> Fetch SSH public key (PEM) in order to 
> update certificates on nodes, everything was finished just fine.
> 
> Unfortunately, one of the most crucial nodes (node14) still shows this
> error:
> 
> VDSM node14 command Get Host Capabilities failed: PKIX path validation
> failed: java.security.cert.CertPathValidatorException: validity check failed
> 
> Restarted vdsms and vdsm-network, still same, node is marked as 
> non-responsive, and all VM with "?" sign (unknown status).
> 
> However, node14 pings without any problem, its storage domain shown in green 
> (OK), and all VMs are running fine.
> 
> Service vdsm-network status is OK, vdsmd is NOT:
> Aug 08 22:07:27 node14.***.lv vdsm[1264164]: ERROR ssl handshake: socket 
> error, address: :::192.168.0.4
> 
> This node is running our accounting and stock control system, its storage 
> domain holds VM disk of that software. If its nonoperational after restart, 
> its a BIG trouble, I will not be able to migrate VM disk anywhere. Restoring 
> accounting DB from daily backup is a lengthy process for 2 - 3 hours.
> 
> Please advice what to do next.
> 
> Thanks in advance.
> ___
> 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/7ERPAMDT2KO4W6VYYMNTYIMDHH7WTZGB/
> ___
> 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/SLO6UKLSHM4IGYOAUVW25ZVV4B2FPCKY/

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

[ovirt-users] Re: Q: How to fix ghost "locked" status of VM

[Andrei Verovski]

Hi,

I re-run engine-setup and it was cleared zombie status of this VM.


On 8/8/22 16:27, Benny Zlotnik wrote:

you can do:
select command_id,root_command_id from command_entities where
root_command_id = '2f8b32d8-fd3c-46c9-90e9-4863d63c0530’;

On Mon, Aug 8, 2022 at 4:19 PM Andrei Verovski  wrote:

Hi, Benny,


select * from command_entities where root_command_id = 
'ed816f9d-e25c-4b58-8c8f-fd0393abda2f’;
-> 0 rows

select * from command_entities where root_command_id = 
'2f8b32d8-fd3c-46c9-90e9-4863d63c0530’;
-> Huge page of smth, have to page out with “more”, is it possible to truncate 
it to meaningful value, e.g. just number of rows?

I can restore this VM from backup copy, bit since it is unmanageable, I can’t 
even remove it.



On 8 Aug 2022, at 13:07, Benny Zlotnik  wrote:

you can look up the relevant command by command_id in the
command_entities table, in your case it would be
2f8b32d8-fd3c-46c9-90e9-4863d63c0530 and
ed816f9d-e25c-4b58-8c8f-fd0393abda2f, there might be more as the log
is trimmed, so I suggest to look it up with
select *
from command_entities
where root_command_id = '2f8b32d8-fd3c-46c9-90e9-4863d63c0530';

Then delete the relevant entries and restart ovirt-engine (as they
might still be present in the cache)

But before doing that, is the command still running? Async commands
like create snapshot are failed automatically after 50 hours and I
believe it has already passed
Also, this manual operation is very intrusive and might have
unexpected consequences so make sure you have backups.





On Mon, Aug 8, 2022 at 9:33 AM Andrei Verovski  wrote:

HI,

OK, how to properly remove this lock? Right now VM is locked and is 
unmanageable at all in any way.
I suppose its with some SQL commands in Postgres.

Thanks.



On 5 Aug 2022, at 11:34, Benny Zlotnik  wrote:

So based on your logs the lock you are seeing is a memory lock,
unlock_entity.sh can't really help with these.
Also, the job table is used mainly for presentation so removing an
entry from will not help.

Do you have the logs from when this snapshot operation started, you
can use the correlation id (28353fa0-5e36-4fe8-8609-e74cd1da6d36) to
search? Also, do you have the vdsm logs (SPM at the time and the host
running the VM), same correlation id can be used for this as well

The table that's used to coordinate this is command_entities, so in
theory removing the entries with this correlation id can help, but I'd
like to see what led to this first

On Fri, Aug 5, 2022 at 8:37 AM Andrei Verovski  wrote:

Hi, Benny,

I have sent log on your mailbox, its too big to post here on mailing list.

Looks like ghost task is still running, anything else need to be removed from 
Postgres DB?

BTW, frozen dead snapshot is in invalid state, is there any way to get rid of 
it? I think it's actually exists, but due to invalid state its not possible to 
do anything with it.


——

Log file still shows zombie task:

2022-08-04 20:57:30,145+03 INFO  
[org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] 
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-24) 
[28353fa0-5e36-4fe8-8609-e74cd1da6d36] Command 'CreateSnapshotForVm' (id: 
'2f8b32d8-fd3c-46c9-90e9-4863d63c0530') waiting on child command id: 
'ed816f9d-e25c-4b58-8c8f-fd0393abda2f' type:'CreateLiveSnapshotForVm' to 
complete
2022-08-04 20:57:40,176+03 INFO  
[org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] 
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-85) 
[28353fa0-5e36-4fe8-8609-e74cd1da6d36] Command 'CreateSnapshotForVm' (id: 
'2f8b32d8-fd3c-46c9-90e9-4863d63c0530') waiting on child command id: 
'ed816f9d-e25c-4b58-8c8f-fd0393abda2f' type:'CreateLiveSnapshotForVm' to 
complete
2022-08-04 20:57:50,252+03 INFO  
[org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] 
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-66) 
[28353fa0-5e36-4fe8-8609-e74cd1da6d36] Command 'CreateSnapshotForVm' (id: 
'2f8b32d8-fd3c-46c9-90e9-4863d63c0530') waiting on child command id: 
'ed816f9d-e25c-4b58-8c8f-fd0393abda2f' type:'CreateLiveSnapshotForVm' to 
complete



On 4 Aug 2022, at 19:06, Benny Zlotnik  wrote:

can you share the logs after restarting ovirt-engine?

On Thu, Aug 4, 2022 at 4:58 PM Andrei Verovski  wrote:

Hi,


Creating snapshot of one of the VM vailed, and zombie tasks was killed with:

su postgres
psql -d engine -U postgres
select * from job order by start_time desc;

select DeleteJob('UUID_FROZEN_TASK_ID’);


However, VM remains in locked state (with lock sign left-below red “DOWN” arrow 
in status column of web interface.

I run:
/usr/share/ovirt-engine/setup/dbutils/unlock_entity.sh -t all

then rebooted engine VM, still no luck. Can’t do anything with that VM.

Please advise how to fix.
Thanks in advance.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovi

[ovirt-users] Certificates Expiration Problem - Urgent Help Needed

[Andrei Verovski]

Hi !

Today my hosts (engine + all nodes) certificates expired and I re-run 
engine-setup to renew certificates.


Then I did for each node host:
Edit host -> Advanced parameters -> Fetch SSH public key (PEM)
in order to update certificates on nodes, everything was finished just fine.

Unfortunately, one of the most crucial nodes (node14) still shows this 
error:


VDSM node14 command Get Host Capabilities failed: PKIX path validation 
failed: java.security.cert.CertPathValidatorException: validity check failed


Restarted vdsms and vdsm-network, still same, node is marked as 
non-responsive, and all VM with "?" sign (unknown status).


However, node14 pings without any problem, its storage domain shown in 
green (OK), and all VMs are running fine.


Service vdsm-network status is OK, vdsmd is NOT:
Aug 08 22:07:27 node14.***.lv vdsm[1264164]: ERROR ssl handshake: socket 
error, address: :::192.168.0.4


This node is running our accounting and stock control system, its 
storage domain holds VM disk of that software. If its nonoperational 
after restart, its a BIG trouble, I will not be able to migrate VM disk 
anywhere. Restoring accounting DB from daily backup is a lengthy process 
for 2 - 3 hours.


Please advice what to do next.

Thanks in advance.
___
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/7ERPAMDT2KO4W6VYYMNTYIMDHH7WTZGB/

[ovirt-users] Re: Q: How to fix ghost "locked" status of VM

[Andrei Verovski]

Hi, Benny,

3 records found.

engine=# select command_id,root_command_id from command_entities where 
root_command_id = '2f8b32d8-fd3c-46c9-90e9-4863d63c0530';
  command_id  |   root_command_id
--+--
 2f8b32d8-fd3c-46c9-90e9-4863d63c0530 | 2f8b32d8-fd3c-46c9-90e9-4863d63c0530
 3c09e1ce-1e49-4d03-82dd-2844fb9dc39f | 2f8b32d8-fd3c-46c9-90e9-4863d63c0530
 ed816f9d-e25c-4b58-8c8f-fd0393abda2f | 2f8b32d8-fd3c-46c9-90e9-4863d63c0530


Now this ?
select DeleteJob('2f8b32d8-fd3c-46c9-90e9-4863d63c0530');


> On 8 Aug 2022, at 16:27, Benny Zlotnik  wrote:
> 
> you can do:
> select command_id,root_command_id from command_entities where
> root_command_id = '2f8b32d8-fd3c-46c9-90e9-4863d63c0530’;
> 
> On Mon, Aug 8, 2022 at 4:19 PM Andrei Verovski  wrote:
>> 
>> Hi, Benny,
>> 
>> 
>> select * from command_entities where root_command_id = 
>> 'ed816f9d-e25c-4b58-8c8f-fd0393abda2f’;
>> -> 0 rows
>> 
>> select * from command_entities where root_command_id = 
>> '2f8b32d8-fd3c-46c9-90e9-4863d63c0530’;
>> -> Huge page of smth, have to page out with “more”, is it possible to 
>> truncate it to meaningful value, e.g. just number of rows?
>> 
>> I can restore this VM from backup copy, bit since it is unmanageable, I 
>> can’t even remove it.
>> 
>> 
>>> On 8 Aug 2022, at 13:07, Benny Zlotnik  wrote:
>>> 
>>> you can look up the relevant command by command_id in the
>>> command_entities table, in your case it would be
>>> 2f8b32d8-fd3c-46c9-90e9-4863d63c0530 and
>>> ed816f9d-e25c-4b58-8c8f-fd0393abda2f, there might be more as the log
>>> is trimmed, so I suggest to look it up with
>>> select *
>>> from command_entities
>>> where root_command_id = '2f8b32d8-fd3c-46c9-90e9-4863d63c0530';
>>> 
>>> Then delete the relevant entries and restart ovirt-engine (as they
>>> might still be present in the cache)
>>> 
>>> But before doing that, is the command still running? Async commands
>>> like create snapshot are failed automatically after 50 hours and I
>>> believe it has already passed
>>> Also, this manual operation is very intrusive and might have
>>> unexpected consequences so make sure you have backups.
>>> 
>>> 
>>> 
>>> 
>>> 
>>> On Mon, Aug 8, 2022 at 9:33 AM Andrei Verovski  wrote:
>>>> 
>>>> HI,
>>>> 
>>>> OK, how to properly remove this lock? Right now VM is locked and is 
>>>> unmanageable at all in any way.
>>>> I suppose its with some SQL commands in Postgres.
>>>> 
>>>> Thanks.
>>>> 
>>>> 
>>>>> On 5 Aug 2022, at 11:34, Benny Zlotnik  wrote:
>>>>> 
>>>>> So based on your logs the lock you are seeing is a memory lock,
>>>>> unlock_entity.sh can't really help with these.
>>>>> Also, the job table is used mainly for presentation so removing an
>>>>> entry from will not help.
>>>>> 
>>>>> Do you have the logs from when this snapshot operation started, you
>>>>> can use the correlation id (28353fa0-5e36-4fe8-8609-e74cd1da6d36) to
>>>>> search? Also, do you have the vdsm logs (SPM at the time and the host
>>>>> running the VM), same correlation id can be used for this as well
>>>>> 
>>>>> The table that's used to coordinate this is command_entities, so in
>>>>> theory removing the entries with this correlation id can help, but I'd
>>>>> like to see what led to this first
>>>>> 
>>>>> On Fri, Aug 5, 2022 at 8:37 AM Andrei Verovski  
>>>>> wrote:
>>>>>> 
>>>>>> Hi, Benny,
>>>>>> 
>>>>>> I have sent log on your mailbox, its too big to post here on mailing 
>>>>>> list.
>>>>>> 
>>>>>> Looks like ghost task is still running, anything else need to be removed 
>>>>>> from Postgres DB?
>>>>>> 
>>>>>> BTW, frozen dead snapshot is in invalid state, is there any way to get 
>>>>>> rid of it? I think it's actually exists, but due to invalid state its 
>>>>>> not possible to do anything with it.
>>>>>> 
>>>>>> 
>>>>>> ——
>>>>>> 
>>>>>> Log file still shows zombie task:
>>>>

[ovirt-users] Re: Q: How to fix ghost "locked" status of VM

[Andrei Verovski]

Hi, Benny,


select * from command_entities where root_command_id = 
'ed816f9d-e25c-4b58-8c8f-fd0393abda2f’;
-> 0 rows

select * from command_entities where root_command_id = 
'2f8b32d8-fd3c-46c9-90e9-4863d63c0530’;
-> Huge page of smth, have to page out with “more”, is it possible to truncate 
it to meaningful value, e.g. just number of rows?

I can restore this VM from backup copy, bit since it is unmanageable, I can’t 
even remove it.


> On 8 Aug 2022, at 13:07, Benny Zlotnik  wrote:
> 
> you can look up the relevant command by command_id in the
> command_entities table, in your case it would be
> 2f8b32d8-fd3c-46c9-90e9-4863d63c0530 and
> ed816f9d-e25c-4b58-8c8f-fd0393abda2f, there might be more as the log
> is trimmed, so I suggest to look it up with
> select *
> from command_entities
> where root_command_id = '2f8b32d8-fd3c-46c9-90e9-4863d63c0530';
> 
> Then delete the relevant entries and restart ovirt-engine (as they
> might still be present in the cache)
> 
> But before doing that, is the command still running? Async commands
> like create snapshot are failed automatically after 50 hours and I
> believe it has already passed
> Also, this manual operation is very intrusive and might have
> unexpected consequences so make sure you have backups.
> 
> 
> 
> 
> 
> On Mon, Aug 8, 2022 at 9:33 AM Andrei Verovski  wrote:
>> 
>> HI,
>> 
>> OK, how to properly remove this lock? Right now VM is locked and is 
>> unmanageable at all in any way.
>> I suppose its with some SQL commands in Postgres.
>> 
>> Thanks.
>> 
>> 
>>> On 5 Aug 2022, at 11:34, Benny Zlotnik  wrote:
>>> 
>>> So based on your logs the lock you are seeing is a memory lock,
>>> unlock_entity.sh can't really help with these.
>>> Also, the job table is used mainly for presentation so removing an
>>> entry from will not help.
>>> 
>>> Do you have the logs from when this snapshot operation started, you
>>> can use the correlation id (28353fa0-5e36-4fe8-8609-e74cd1da6d36) to
>>> search? Also, do you have the vdsm logs (SPM at the time and the host
>>> running the VM), same correlation id can be used for this as well
>>> 
>>> The table that's used to coordinate this is command_entities, so in
>>> theory removing the entries with this correlation id can help, but I'd
>>> like to see what led to this first
>>> 
>>> On Fri, Aug 5, 2022 at 8:37 AM Andrei Verovski  wrote:
>>>> 
>>>> Hi, Benny,
>>>> 
>>>> I have sent log on your mailbox, its too big to post here on mailing list.
>>>> 
>>>> Looks like ghost task is still running, anything else need to be removed 
>>>> from Postgres DB?
>>>> 
>>>> BTW, frozen dead snapshot is in invalid state, is there any way to get rid 
>>>> of it? I think it's actually exists, but due to invalid state its not 
>>>> possible to do anything with it.
>>>> 
>>>> 
>>>> ——
>>>> 
>>>> Log file still shows zombie task:
>>>> 
>>>> 2022-08-04 20:57:30,145+03 INFO  
>>>> [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] 
>>>> (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-24) 
>>>> [28353fa0-5e36-4fe8-8609-e74cd1da6d36] Command 'CreateSnapshotForVm' (id: 
>>>> '2f8b32d8-fd3c-46c9-90e9-4863d63c0530') waiting on child command id: 
>>>> 'ed816f9d-e25c-4b58-8c8f-fd0393abda2f' type:'CreateLiveSnapshotForVm' to 
>>>> complete
>>>> 2022-08-04 20:57:40,176+03 INFO  
>>>> [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] 
>>>> (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-85) 
>>>> [28353fa0-5e36-4fe8-8609-e74cd1da6d36] Command 'CreateSnapshotForVm' (id: 
>>>> '2f8b32d8-fd3c-46c9-90e9-4863d63c0530') waiting on child command id: 
>>>> 'ed816f9d-e25c-4b58-8c8f-fd0393abda2f' type:'CreateLiveSnapshotForVm' to 
>>>> complete
>>>> 2022-08-04 20:57:50,252+03 INFO  
>>>> [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] 
>>>> (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-66) 
>>>> [28353fa0-5e36-4fe8-8609-e74cd1da6d36] Command 'CreateSnapshotForVm' (id: 
>>>> '2f8b32d8-fd3c-46c9-90e9-4863d63c0530') waiting on child command id: 
>>>> 'ed816f9d-e25c-4b58-8c8f-fd0393abda2f' type:'CreateLiveSnapshotForVm' to 
>>>> complete
>>>> 
>>>> 
>>>>> On 4 Aug 2022, at

[ovirt-users] Re: Q: How to fix ghost "locked" status of VM

[Andrei Verovski]

Yes, I did it, not working in my case.

This is explanation from Benny:

So based on your logs the lock you are seeing is a memory lock,
unlock_entity.sh can't really help with these.
Also, the job table is used mainly for presentation so removing an
entry from will not help.


> On 8 Aug 2022, at 15:30, Jirka Simon  wrote:
> 
> Hi Andrei 
> 
> have you cecked locked entries here ?
> 
> /usr/share/ovirt-engine/setup/dbutils/unlock_entity.sh -t all  -qc
> 
> it helped to me to unlock snapshots and disks and then restart VM.  but yes, 
> there is a chance to damage VM, 
> 
> 
> 
> Jirka
> 
> On 8/8/22 08:33, Andrei Verovski wrote:
>> HI,
>> 
>> OK, how to properly remove this lock? Right now VM is locked and is 
>> unmanageable at all in any way.
>> I suppose its with some SQL commands in Postgres.
>> 
>> Thanks.
>> 
>> 
>>> On 5 Aug 2022, at 11:34, Benny Zlotnik  
>>> <mailto:bzlot...@redhat.com> wrote:
>>> 
>>> So based on your logs the lock you are seeing is a memory lock,
>>> unlock_entity.sh can't really help with these.
>>> Also, the job table is used mainly for presentation so removing an
>>> entry from will not help.
>>> 
>>> Do you have the logs from when this snapshot operation started, you
>>> can use the correlation id (28353fa0-5e36-4fe8-8609-e74cd1da6d36) to
>>> search? Also, do you have the vdsm logs (SPM at the time and the host
>>> running the VM), same correlation id can be used for this as well
>>> 
>>> The table that's used to coordinate this is command_entities, so in
>>> theory removing the entries with this correlation id can help, but I'd
>>> like to see what led to this first
>>> 
>>> On Fri, Aug 5, 2022 at 8:37 AM Andrei Verovski  
>>> <mailto:andre...@starlett.lv> wrote:
>>>> Hi, Benny,
>>>> 
>>>> I have sent log on your mailbox, its too big to post here on mailing list.
>>>> 
>>>> Looks like ghost task is still running, anything else need to be removed 
>>>> from Postgres DB?
>>>> 
>>>> BTW, frozen dead snapshot is in invalid state, is there any way to get rid 
>>>> of it? I think it's actually exists, but due to invalid state its not 
>>>> possible to do anything with it.
>>>> 
>>>> 
>>>> ——
>>>> 
>>>> Log file still shows zombie task:
>>>> 
>>>> 2022-08-04 20:57:30,145+03 INFO  
>>>> [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] 
>>>> (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-24) 
>>>> [28353fa0-5e36-4fe8-8609-e74cd1da6d36] Command 'CreateSnapshotForVm' (id: 
>>>> '2f8b32d8-fd3c-46c9-90e9-4863d63c0530') waiting on child command id: 
>>>> 'ed816f9d-e25c-4b58-8c8f-fd0393abda2f' type:'CreateLiveSnapshotForVm' to 
>>>> complete
>>>> 2022-08-04 20:57:40,176+03 INFO  
>>>> [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] 
>>>> (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-85) 
>>>> [28353fa0-5e36-4fe8-8609-e74cd1da6d36] Command 'CreateSnapshotForVm' (id: 
>>>> '2f8b32d8-fd3c-46c9-90e9-4863d63c0530') waiting on child command id: 
>>>> 'ed816f9d-e25c-4b58-8c8f-fd0393abda2f' type:'CreateLiveSnapshotForVm' to 
>>>> complete
>>>> 2022-08-04 20:57:50,252+03 INFO  
>>>> [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] 
>>>> (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-66) 
>>>> [28353fa0-5e36-4fe8-8609-e74cd1da6d36] Command 'CreateSnapshotForVm' (id: 
>>>> '2f8b32d8-fd3c-46c9-90e9-4863d63c0530') waiting on child command id: 
>>>> 'ed816f9d-e25c-4b58-8c8f-fd0393abda2f' type:'CreateLiveSnapshotForVm' to 
>>>> complete
>>>> 
>>>> 
>>>>> On 4 Aug 2022, at 19:06, Benny Zlotnik  
>>>>> <mailto:bzlot...@redhat.com> wrote:
>>>>> 
>>>>> can you share the logs after restarting ovirt-engine?
>>>>> 
>>>>> On Thu, Aug 4, 2022 at 4:58 PM Andrei Verovski  
>>>>> <mailto:andre...@starlett.lv> wrote:
>>>>>> Hi,
>>>>>> 
>>>>>> 
>>>>>> Creating snapshot of one of the VM vailed, and zombie tasks was killed 
>>>>>> with:
>>>>>> 
>>>>>> su postgres
>>>>>> psql -d engine -U postgres
>>

[ovirt-users] Re: Q: How to fix ghost "locked" status of VM

[Andrei Verovski]

> On 8 Aug 2022, at 09:52, Jirka Simon  wrote:
> 
> Hi Benny, Andrei.
> 
> do you have any news?  I deleted frozen task and locked snapshot and disk on 
> Friday and during the weekend everything worked fine. (there were 3 snapshots 
> and backups from Friday to now.)


Deleting zombie task from Postgresql didn’t help.


> 
> Thank you
> 
> Jirka
> 
> On 8/5/22 11:53, Benny Zlotnik wrote:
>> Jirka, I suppose your issue is different than Anderi's no?
>> 
>> In your log I see the command has failed:
>> 2022-08-05 10:26:57,741+02 INFO
>> [org.ovirt.engine.core.bll.VirtJobCallback]
>> (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-92)
>> [8ff04bca-b5a2-4ba3-892
>> 5-1037c5a2850e] Command CreateLiveSnapshotForVm id:
>> '2f94c337-487e-40f7-b8f8-df69225d5c79': execution was completed, the
>> command status is 'FAILED'
>> 2022-08-05 10:26:58,742+02 ERROR
>> [org.ovirt.engine.core.bll.snapshots.CreateLiveSnapshotForVmCommand]
>> (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-35
>> ) [8ff04bca-b5a2-4ba3-8925-1037c5a2850e] Ending command
>> 'org.ovirt.engine.core.bll.snapshots.CreateLiveSnapshotForVmCommand'
>> with failure.
>> 2022-08-05 10:26:59,796+02 INFO
>> [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback]
>> (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-31)
>> [8
>> ff04bca-b5a2-4ba3-8925-1037c5a2850e] Command 'CreateSnapshotForVm' id:
>> '93f98c9c-2936-4615-b12e-c295b90eace0' child commands
>> '[2f94c337-487e-40f7-b8f8-df69225d5c79, 1b3abc1e
>> -f0c1-40f7-b52e-f7df52c52601]' executions were completed, status 'FAILED'
>> 2022-08-05 10:27:00,826+02 ERROR
>> [org.ovirt.engine.core.bll.snapshots.CreateSnapshotForVmCommand]
>> (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-4)
>> [8f
>> f04bca-b5a2-4ba3-8925-1037c5a2850e] Ending command
>> 'org.ovirt.engine.core.bll.snapshots.CreateSnapshotForVmCommand' with
>> failure.
>> 2022-08-05 10:27:00,829+02 ERROR
>> [org.ovirt.engine.core.bll.snapshots.CreateSnapshotDiskCommand]
>> (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-4)
>> [8ff
>> 04bca-b5a2-4ba3-8925-1037c5a2850e] Ending command
>> 'org.ovirt.engine.core.bll.snapshots.CreateSnapshotDiskCommand' with
>> failure.
>> 
>> Generally, live snapshot has a default 30 minute timeout to complete
>> and it looks like it was reached in your case, I don't see a command
>> that's still running
>> 
>> On Fri, Aug 5, 2022 at 12:36 PM Jirka Simon  wrote:
>>> Hi Benny , Andrei,
>>> 
>>> 
>>> here are my logs
>>> 
>>> 
>>> affected job was  " waiting for job '6e73cda8-85d0-471c-b090-4c89719a97f4' 
>>> on host 'ovirt3.corp.sldev.cz' "
>>> 
>>> thank you
>>> 
>>> 
>>> Jirka
>>> 
>>> On 8/5/22 11:00, Andrei Verovski wrote:
>>> 
>>> Hi,
>>> 
>>> I have e-mailed vdsm log to Benny.
>>> Unfortunately, yesterday I deleted engine.log before restarting engine to 
>>> have more shorter log.
>>> 
>>> Jirka, can you e-mail engine.log and vdsm logs (SPM at the time and the host
>>> running the VM) to Benny?
>>> 
>>> 
>>> On 5 Aug 2022, at 11:42, Jirka Simon  wrote:
>>> 
>>> Hi Benny, so we have the same problem last 2 days.
>>> 
>>> there are two affected VMs (furtunately not more) and we cant start any 
>>> snapshot  for these VMS.
>>> 
>>> it looks that the snapshot haven't start yet , then to unlock objects 
>>> (snapshot and disk) shouldn't damage disk (i tried it on both VMS), then i 
>>> restarted them and VMS run again. I made clone from one of them ant the 
>>> clone works properly.
>>> 
>>> 
>>> Jirka
>>> 
>>> On 8/5/22 10:34, Benny Zlotnik wrote:
>>> 
>>> So based on your logs the lock you are seeing is a memory lock,
>>> unlock_entity.sh can't really help with these.
>>> Also, the job table is used mainly for presentation so removing an
>>> entry from will not help.
>>> 
>>> Do you have the logs from when this snapshot operation started, you
>>> can use the correlation id (28353fa0-5e36-4fe8-8609-e74cd1da6d36) to
>>> search? Also, do you have the vdsm logs (SPM at the time and the host
>>> running the VM), same correlation id can be used for this as well
>>> 
>>> The table that's used to coordina

[ovirt-users] Re: Q: How to fix ghost "locked" status of VM

[Andrei Verovski]

HI,

OK, how to properly remove this lock? Right now VM is locked and is 
unmanageable at all in any way.
I suppose its with some SQL commands in Postgres.

Thanks.


> On 5 Aug 2022, at 11:34, Benny Zlotnik  wrote:
> 
> So based on your logs the lock you are seeing is a memory lock,
> unlock_entity.sh can't really help with these.
> Also, the job table is used mainly for presentation so removing an
> entry from will not help.
> 
> Do you have the logs from when this snapshot operation started, you
> can use the correlation id (28353fa0-5e36-4fe8-8609-e74cd1da6d36) to
> search? Also, do you have the vdsm logs (SPM at the time and the host
> running the VM), same correlation id can be used for this as well
> 
> The table that's used to coordinate this is command_entities, so in
> theory removing the entries with this correlation id can help, but I'd
> like to see what led to this first
> 
> On Fri, Aug 5, 2022 at 8:37 AM Andrei Verovski  wrote:
>> 
>> Hi, Benny,
>> 
>> I have sent log on your mailbox, its too big to post here on mailing list.
>> 
>> Looks like ghost task is still running, anything else need to be removed 
>> from Postgres DB?
>> 
>> BTW, frozen dead snapshot is in invalid state, is there any way to get rid 
>> of it? I think it's actually exists, but due to invalid state its not 
>> possible to do anything with it.
>> 
>> 
>> ——
>> 
>> Log file still shows zombie task:
>> 
>> 2022-08-04 20:57:30,145+03 INFO  
>> [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] 
>> (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-24) 
>> [28353fa0-5e36-4fe8-8609-e74cd1da6d36] Command 'CreateSnapshotForVm' (id: 
>> '2f8b32d8-fd3c-46c9-90e9-4863d63c0530') waiting on child command id: 
>> 'ed816f9d-e25c-4b58-8c8f-fd0393abda2f' type:'CreateLiveSnapshotForVm' to 
>> complete
>> 2022-08-04 20:57:40,176+03 INFO  
>> [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] 
>> (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-85) 
>> [28353fa0-5e36-4fe8-8609-e74cd1da6d36] Command 'CreateSnapshotForVm' (id: 
>> '2f8b32d8-fd3c-46c9-90e9-4863d63c0530') waiting on child command id: 
>> 'ed816f9d-e25c-4b58-8c8f-fd0393abda2f' type:'CreateLiveSnapshotForVm' to 
>> complete
>> 2022-08-04 20:57:50,252+03 INFO  
>> [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] 
>> (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-66) 
>> [28353fa0-5e36-4fe8-8609-e74cd1da6d36] Command 'CreateSnapshotForVm' (id: 
>> '2f8b32d8-fd3c-46c9-90e9-4863d63c0530') waiting on child command id: 
>> 'ed816f9d-e25c-4b58-8c8f-fd0393abda2f' type:'CreateLiveSnapshotForVm' to 
>> complete
>> 
>> 
>>> On 4 Aug 2022, at 19:06, Benny Zlotnik  wrote:
>>> 
>>> can you share the logs after restarting ovirt-engine?
>>> 
>>> On Thu, Aug 4, 2022 at 4:58 PM Andrei Verovski  wrote:
>>>> 
>>>> Hi,
>>>> 
>>>> 
>>>> Creating snapshot of one of the VM vailed, and zombie tasks was killed 
>>>> with:
>>>> 
>>>> su postgres
>>>> psql -d engine -U postgres
>>>> select * from job order by start_time desc;
>>>> 
>>>> select DeleteJob('UUID_FROZEN_TASK_ID’);
>>>> 
>>>> 
>>>> However, VM remains in locked state (with lock sign left-below red “DOWN” 
>>>> arrow in status column of web interface.
>>>> 
>>>> I run:
>>>> /usr/share/ovirt-engine/setup/dbutils/unlock_entity.sh -t all
>>>> 
>>>> then rebooted engine VM, still no luck. Can’t do anything with that VM.
>>>> 
>>>> Please advise how to fix.
>>>> Thanks in advance.
>>>> ___
>>>> 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/P2TVMLHC53JWCLDJNK6UXLZ7ZAUOSYFJ/
>>> 
>> 
> 
___
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/RCB2URNPYZGAFCARZX367C54TTNHBH5U/

[ovirt-users] Re: Q: How to fix ghost "locked" status of VM

[Andrei Verovski]

Hi,

I have e-mailed vdsm log to Benny.
Unfortunately, yesterday I deleted engine.log before restarting engine to have 
more shorter log.

Jirka, can you e-mail engine.log and vdsm logs (SPM at the time and the host
running the VM) to Benny?


> On 5 Aug 2022, at 11:42, Jirka Simon  wrote:
> 
> Hi Benny, so we have the same problem last 2 days.
> 
> there are two affected VMs (furtunately not more) and we cant start any 
> snapshot  for these VMS.
> 
> it looks that the snapshot haven't start yet , then to unlock objects 
> (snapshot and disk) shouldn't damage disk (i tried it on both VMS), then i 
> restarted them and VMS run again. I made clone from one of them ant the clone 
> works properly.
> 
> 
> Jirka
> 
> On 8/5/22 10:34, Benny Zlotnik wrote:
>> So based on your logs the lock you are seeing is a memory lock,
>> unlock_entity.sh can't really help with these.
>> Also, the job table is used mainly for presentation so removing an
>> entry from will not help.
>> 
>> Do you have the logs from when this snapshot operation started, you
>> can use the correlation id (28353fa0-5e36-4fe8-8609-e74cd1da6d36) to
>> search? Also, do you have the vdsm logs (SPM at the time and the host
>> running the VM), same correlation id can be used for this as well
>> 
>> The table that's used to coordinate this is command_entities, so in
>> theory removing the entries with this correlation id can help, but I'd
>> like to see what led to this first
>> 
>> On Fri, Aug 5, 2022 at 8:37 AM Andrei Verovski  wrote:
>>> Hi, Benny,
>>> 
>>> I have sent log on your mailbox, its too big to post here on mailing list.
>>> 
>>> Looks like ghost task is still running, anything else need to be removed 
>>> from Postgres DB?
>>> 
>>> BTW, frozen dead snapshot is in invalid state, is there any way to get rid 
>>> of it? I think it's actually exists, but due to invalid state its not 
>>> possible to do anything with it.
>>> 
>>> 
>>> ——
>>> 
>>> Log file still shows zombie task:
>>> 
>>> 2022-08-04 20:57:30,145+03 INFO  
>>> [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] 
>>> (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-24) 
>>> [28353fa0-5e36-4fe8-8609-e74cd1da6d36] Command 'CreateSnapshotForVm' (id: 
>>> '2f8b32d8-fd3c-46c9-90e9-4863d63c0530') waiting on child command id: 
>>> 'ed816f9d-e25c-4b58-8c8f-fd0393abda2f' type:'CreateLiveSnapshotForVm' to 
>>> complete
>>> 2022-08-04 20:57:40,176+03 INFO  
>>> [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] 
>>> (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-85) 
>>> [28353fa0-5e36-4fe8-8609-e74cd1da6d36] Command 'CreateSnapshotForVm' (id: 
>>> '2f8b32d8-fd3c-46c9-90e9-4863d63c0530') waiting on child command id: 
>>> 'ed816f9d-e25c-4b58-8c8f-fd0393abda2f' type:'CreateLiveSnapshotForVm' to 
>>> complete
>>> 2022-08-04 20:57:50,252+03 INFO  
>>> [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] 
>>> (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-66) 
>>> [28353fa0-5e36-4fe8-8609-e74cd1da6d36] Command 'CreateSnapshotForVm' (id: 
>>> '2f8b32d8-fd3c-46c9-90e9-4863d63c0530') waiting on child command id: 
>>> 'ed816f9d-e25c-4b58-8c8f-fd0393abda2f' type:'CreateLiveSnapshotForVm' to 
>>> complete
>>> 
>>> 
>>>> On 4 Aug 2022, at 19:06, Benny Zlotnik  wrote:
>>>> 
>>>> can you share the logs after restarting ovirt-engine?
>>>> 
>>>> On Thu, Aug 4, 2022 at 4:58 PM Andrei Verovski  
>>>> wrote:
>>>>> Hi,
>>>>> 
>>>>> 
>>>>> Creating snapshot of one of the VM vailed, and zombie tasks was killed 
>>>>> with:
>>>>> 
>>>>> su postgres
>>>>> psql -d engine -U postgres
>>>>> select * from job order by start_time desc;
>>>>> 
>>>>> select DeleteJob('UUID_FROZEN_TASK_ID’);
>>>>> 
>>>>> 
>>>>> However, VM remains in locked state (with lock sign left-below red “DOWN” 
>>>>> arrow in status column of web interface.
>>>>> 
>>>>> I run:
>>>>> /usr/share/ovirt-engine/setup/dbutils/unlock_entity.sh -t all
>>>>> 
>>>>> then rebooted engine VM, still no luck. Can’t do anything with that VM.
>>>>> 
>>>>> Please advise how to fix

[ovirt-users] Re: VM snapshot stuck

[Andrei Verovski]

Hi,

I had similar problem, see my posts for last 2 days, already submitted log to 
Benny Zlotnik.


> On 5 Aug 2022, at 10:52, Jirka Simon  wrote:
> 
> Hello Ovirt folks,
> 
> last two days we have troubles with stuck snapshot task on some vms. and VM 
> is frozen and unresponsible.
> 
> task progress is still null
> 
> I can unlock it with command unlock_entity.sh but VM stays frozen.  and VM 
> has to be  force powered down and started again
> 
> in engine log i can see only  that master job is waiting for an other job.
> 
> oVirt  Version 4.4.10.7-1.el8
> 
> OS Rocky Linux 8.6
> last full update was last week on Thurstday
> 
> Log:
> 2022-08-05 09:10:05,461+02 INFO 
> [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] 
> (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-35) 
> [8ff04bca-b5a2-4ba3-8925-1037c5a2850e] Command 'CreateSnapshotForVm' (id: 
> '93f98c9c-2936-4615-b12e-c295b90eace0') waiting on child command id: 
> '2f94c337-487e-40f7-b8f8-df69225d5c79' type:'CreateLiveSnapshotForVm' to 
> complete
> 2022-08-05 09:10:05,462+02 INFO 
> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetHostJobsVDSCommand] 
> (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-35) 
> [8ff04bca-b5a2-4ba3-8925-1037c5a2850e] START, GetHostJobsVDSCommand(HostName 
> = ovirt3.corp.sldev.cz, 
> GetHostJobsVDSCommandParameters:{hostId='15d9a919-63d5-4673-95d2-e84662ef0852',
>  type='virt', jobIds='[6e73cda8-85d0-471c-b090-4c89719a97f4]'}), log id: 
> 515c7e0d
> 2022-08-05 09:10:05,466+02 INFO 
> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetHostJobsVDSCommand] 
> (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-35) 
> [8ff04bca-b5a2-4ba3-8925-1037c5a2850e] FINISH, GetHostJobsVDSCommand, return: 
> {6e73cda8-85d0-471c-b090-4c89719a97f4=HostJobInfo:{id='6e73cda8-85d0-471c-b090-4c89719a97f4',
>  type='virt', description='snapshot_vm', status='running', progress='null', 
> error='null'}}, log id: 515c7e0d
> 2022-08-05 09:10:05,466+02 INFO [org.ovirt.engine.core.bll.VirtJobCallback] 
> (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-35) 
> [8ff04bca-b5a2-4ba3-8925-1037c5a2850e] Command CreateLiveSnapshotForVm id: 
> '2f94c337-487e-40f7-b8f8-df69225d5c79': waiting for job 
> '6e73cda8-85d0-471c-b090-4c89719a97f4' on host 'ovirt3.corp.sldev.cz' (id: 
> '15d9a919-63d5-4673-95d2-e84662ef0852') to complete
> 
> any idea what should I  check ?
> 
> 
> thank you for any help.
> 
> 
> Jirka
> ___
> 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/U4MIGF6PSBURYKAKHUAYXJM3GJ3BTRSU/
___
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/DPELGV66LJZKE7D4OVYWEDWGSLDKFNXR/

[ovirt-users] Re: Q: How to fix ghost "locked" status of VM

[Andrei Verovski]

Hi, Benny,

I have sent log on your mailbox, its too big to post here on mailing list.

Looks like ghost task is still running, anything else need to be removed from 
Postgres DB?

BTW, frozen dead snapshot is in invalid state, is there any way to get rid of 
it? I think it's actually exists, but due to invalid state its not possible to 
do anything with it.


——

Log file still shows zombie task:

2022-08-04 20:57:30,145+03 INFO  
[org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] 
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-24) 
[28353fa0-5e36-4fe8-8609-e74cd1da6d36] Command 'CreateSnapshotForVm' (id: 
'2f8b32d8-fd3c-46c9-90e9-4863d63c0530') waiting on child command id: 
'ed816f9d-e25c-4b58-8c8f-fd0393abda2f' type:'CreateLiveSnapshotForVm' to 
complete
2022-08-04 20:57:40,176+03 INFO  
[org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] 
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-85) 
[28353fa0-5e36-4fe8-8609-e74cd1da6d36] Command 'CreateSnapshotForVm' (id: 
'2f8b32d8-fd3c-46c9-90e9-4863d63c0530') waiting on child command id: 
'ed816f9d-e25c-4b58-8c8f-fd0393abda2f' type:'CreateLiveSnapshotForVm' to 
complete
2022-08-04 20:57:50,252+03 INFO  
[org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] 
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-66) 
[28353fa0-5e36-4fe8-8609-e74cd1da6d36] Command 'CreateSnapshotForVm' (id: 
'2f8b32d8-fd3c-46c9-90e9-4863d63c0530') waiting on child command id: 
'ed816f9d-e25c-4b58-8c8f-fd0393abda2f' type:'CreateLiveSnapshotForVm' to 
complete


> On 4 Aug 2022, at 19:06, Benny Zlotnik  wrote:
> 
> can you share the logs after restarting ovirt-engine?
> 
> On Thu, Aug 4, 2022 at 4:58 PM Andrei Verovski  wrote:
>> 
>> Hi,
>> 
>> 
>> Creating snapshot of one of the VM vailed, and zombie tasks was killed with:
>> 
>> su postgres
>> psql -d engine -U postgres
>> select * from job order by start_time desc;
>> 
>> select DeleteJob('UUID_FROZEN_TASK_ID’);
>> 
>> 
>> However, VM remains in locked state (with lock sign left-below red “DOWN” 
>> arrow in status column of web interface.
>> 
>> I run:
>> /usr/share/ovirt-engine/setup/dbutils/unlock_entity.sh -t all
>> 
>> then rebooted engine VM, still no luck. Can’t do anything with that VM.
>> 
>> Please advise how to fix.
>> Thanks in advance.
>> ___
>> 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/P2TVMLHC53JWCLDJNK6UXLZ7ZAUOSYFJ/
> 
___
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/RYWCBE6JYKGXJCLE7HHAEUX7WMYASNMA/

[ovirt-users] Q: How to fix ghost "locked" status of VM

[Andrei Verovski]

Hi,


Creating snapshot of one of the VM vailed, and zombie tasks was killed with:

su postgres
psql -d engine -U postgres
select * from job order by start_time desc;

select DeleteJob('UUID_FROZEN_TASK_ID’);


However, VM remains in locked state (with lock sign left-below red “DOWN” arrow 
in status column of web interface.

I run:
 /usr/share/ovirt-engine/setup/dbutils/unlock_entity.sh -t all

then rebooted engine VM, still no luck. Can’t do anything with that VM.

Please advise how to fix. 
Thanks in advance.
___
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/P2TVMLHC53JWCLDJNK6UXLZ7ZAUOSYFJ/

[ovirt-users] Re: Q: "vdsm-client Host getAllTasksInfo" Fails (Removing frozen task)

[Andrei Verovski]

Hi,

I fixed this with:

su postgres
psql -d engine -U postgres
select * from job order by start_time desc;

select DeleteJob('UUID_FROZEN_TASK_ID');

UUID_FROZEN_TASK_ID = zombie task ID.


Anyway, original question remains about failure:

# sudo vdsm-client Host getAllTasksInfo
> vdsm-client: Command Host.getAllTasksInfo with args {} failed:



> On 4 Aug 2022, at 12:58, Andrei Verovski  wrote:
> 
> Hi,
> 
> 
> I have frozen task (creating snapshot) on one of my oVirt nodes, and trying 
> to kill it.
> However,
> 
> # sudo vdsm-client Host getAllTasksInfo
> vdsm-client: Command Host.getAllTasksInfo with args {} failed:
> 
> However, sudo "vdsm-client Host getVMList” and "sudo vdsm-client Host 
> getVMFullList" working fine.
> 
> # /usr/share/ovirt-engine/setup/dbutils/taskcleaner.sh -v -Z
> 
> select exists (select * from information_schema.tables where table_schema = 
> 'public' and table_name = 'command_entities');
> t
> SELECT 
> command_id,command_type,root_command_id,command_parameters,command_params_class,created_at,status,return_value,return_value_class,executed
>  FROM GetAllCommandsWithZombieTasks();
> 
> So only letter “t” is printed and it is not clear what does it mean.
> 
> I can run "/usr/share/ovirt-engine/setup/dbutils/taskcleaner.sh -vR” but not 
> sure its not too destructive.
> 
> What is the problem with "vdsm-client Host getAllTasksInfo” ?
> 
> Thanks in advance.
> 
> Andrei
> 
> ___
> 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/V4T6G4HWESMJLD7XVDDDREFVO4OQDMGS/
___
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/MUDHEBXTTI3BJ2O6MTNUOHL6ERQVXCLG/

[ovirt-users] Q: "vdsm-client Host getAllTasksInfo" Fails (Removing frozen task)

[Andrei Verovski]

Hi,


I have frozen task (creating snapshot) on one of my oVirt nodes, and trying to 
kill it.
However,

# sudo vdsm-client Host getAllTasksInfo
vdsm-client: Command Host.getAllTasksInfo with args {} failed:

However, sudo "vdsm-client Host getVMList” and "sudo vdsm-client Host 
getVMFullList" working fine.

# /usr/share/ovirt-engine/setup/dbutils/taskcleaner.sh -v -Z

select exists (select * from information_schema.tables where table_schema = 
'public' and table_name = 'command_entities');
 t
SELECT 
command_id,command_type,root_command_id,command_parameters,command_params_class,created_at,status,return_value,return_value_class,executed
 FROM GetAllCommandsWithZombieTasks();

So only letter “t” is printed and it is not clear what does it mean.

I can run "/usr/share/ovirt-engine/setup/dbutils/taskcleaner.sh -vR” but not 
sure its not too destructive.

What is the problem with "vdsm-client Host getAllTasksInfo” ?

Thanks in advance.

Andrei

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

[ovirt-users] GUIDE: oVirt 4.4.7 to 4.4.10 Upgrade + Switch to CentOS Stream

[Andrei Verovski]

Hi,

Having a LOT of trouble upgrading oVirt to 4.4.10 while switching to 
CentOS Stream, I posted a short guide in my blog.


https://www.vacuum-tube.eu/wp/?p=399

Look at entry:
[2022-07-19] oVirt 4.4.7 to 4.4.10 Upgrade + Switch to CentOS Stream


Thanks for everyone who helped me !
___
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/5QV46PC24OVWDFB2BFMEQ3YOP54MO6FY/

[ovirt-users] Re: Please help: Failure Restoring Data on Clean Engine After Migration

[Andrei Verovski]

> On 19 Jul 2022, at 09:51, Yedidyah Bar David  wrote:
> 
> On Tue, Jul 19, 2022 at 9:38 AM Andrei Verovski  wrote:
>> 
>> Hi,
>> 
>> 
>> Thanks, I solved this problem before by means of executing these commands:
>> 
>> su - postgres -s/bin/bash
>> psql -d ovirt_engine_history
>> 
>> CREATE ROLE ovirt_engine_history_grafana;
>> ALTER DEFAULT PRIVILEGES FOR ROLE ovirt_engine_history IN SCHEMA public 
>> GRANT SELECT ON TABLES TO ovirt_engine_history_grafana;
>> ALTER ROLE ovirt_engine_history_grafana WITH ENCRYPTED PASSWORD 
>> ‘my_password';
>> ALTER ROLE ovirt_engine_history_grafana WITH LOGIN;
> 
> So this last one, 'LOGIN', was the missing part. OK.
> 
> Thanks for the update. Glad to hear that you solved it!
> 
> Any other conclusions/suggestions you'd like to make?


It was a hell like experience upgrading 4.4.7 to 4.4.10.

I will post an instruction in my blog.


> 
> 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/RBFLSKIYHHR6O2ZWRLZNVH5MBA3FTFCS/

[ovirt-users] Re: SOLVED: oVirt 4.4.10 Internal server error 500 after engine-setup (vdsm-jsonrpc-java )

[Andrei Verovski]

Hi,


Problem solved with downgrade postgresql-jdbc

dnf --showduplicates list postgresql-jdbc

dnf install postgresql-jdbc-42.2.3-3.el8_2



> On 18 Jul 2022, at 09:28, Andrei Verovski  wrote:
> 
> Hi,
> 
> 
> Finally I managed to migrate 4.4.7 to fresh installation of 4.4.10.
> However, after successful engine-setup I’ve got 500 - Internal Server Error
> 
> I found this:
> https://bugzilla.redhat.com/show_bug.cgi?id=1918022
> 
> Bug 1918022 - oVirt Manager is not loading after engine-setup 
> 
> Article suggested to downgrade vdsm-jsonrpc-java to 1.5.x.
> 
> However, this is not possible:
> dnf --showduplicates list vdsm-jsonrpc-java
> dnf install vdsm-jsonrpc-java-1.5.7-1.el8
> 
> Last metadata expiration check: 0:39:52 ago on Fri 15 Jul 2022 02:32:36 PM 
> EEST.
> Error: 
> Problem: problem with installed package 
> ovirt-engine-backend-4.4.10.7-1.el8.noarch
> - package ovirt-engine-backend-4.4.10.7-1.el8.noarch requires 
> vdsm-jsonrpc-java >= 1.6.0, but none of the providers can be installed
> - cannot install both vdsm-jsonrpc-java-1.5.7-1.el8.noarch and 
> vdsm-jsonrpc-java-1.6.0-1.el8.noarch
> - cannot install both vdsm-jsonrpc-java-1.6.0-1.el8.noarch and 
> vdsm-jsonrpc-java-1.5.7-1.el8.noarch
> 
> 
> How to fix this?
> Thanks in advance.
> 
> 
> *   SERVER LOG *
> 
> 2022-07-15 14:45:44,969+03 ERROR 
> [org.jboss.as.controller.management-operation] (Controller Boot Thread) 
> WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => 
> "engine.ear")]) - failure description: {"WFLYCTL0080: Failed services" => 
> {"jboss.deployment.subunit.\"engine.ear\".\"bll.jar\".component.Backend.START"
>  => "java.lang.IllegalStateException: WFLYEE0042: Failed to construct 
> component instance
>   Caused by: java.lang.IllegalStateException: WFLYEE0042: Failed to construct 
> component instance
>   Caused by: javax.ejb.EJBException: org.jboss.weld.exceptions.WeldException: 
> WELD-49: Unable to invoke protected void 
> org.ovirt.engine.core.bll.TagsDirector.init() on 
> org.ovirt.engine.core.bll.TagsDirector@648487d3
>   Caused by: org.jboss.weld.exceptions.WeldException: WELD-49: Unable to 
> invoke protected void org.ovirt.engine.core.bll.TagsDirector.init() on 
> org.ovirt.engine.core.bll.TagsDirector@648487d3
>   Caused by: java.lang.reflect.InvocationTargetException
>   Caused by: org.springframework.dao.InvalidDataAccessApiUsageException: 
> Unable to determine the correct call signature - no 
> procedure/function/signature for 'gettagsbyparent_id'"}}
> 2022-07-15 14:45:44,981+03 INFO  [org.jboss.as.server] (ServerService Thread 
> Pool -- 25) WFLYSRV0010: Deployed "restapi.war" (runtime-name : "restapi.war")
> 2022-07-15 14:45:44,982+03 INFO  [org.jboss.as.server] (ServerService Thread 
> Pool -- 25) WFLYSRV0010: Deployed "engine.ear" (runtime-name : "engine.ear")
> 2022-07-15 14:45:44,982+03 INFO  [org.jboss.as.server] (ServerService Thread 
> Pool -- 25) WFLYSRV0010: Deployed "apidoc.war" (runtime-name : "apidoc.war")
> 2022-07-15 14:45:44,982+03 INFO  [org.jboss.as.server] (ServerService Thread 
> Pool -- 25) WFLYSRV0010: Deployed "ovirt-web-ui.war" (runtime-name : 
> "ovirt-web-ui.war")
> 2022-07-15 14:45:45,015+03 INFO  [org.jboss.as.controller] (Controller Boot 
> Thread) WFLYCTL0183: Service status report
> WFLYCTL0186:   Services which failed to start:  service 
> jboss.deployment.subunit."engine.ear"."bll.jar".component.Backend.START: 
> java.lang.IllegalStateException: WFLYEE0042: Failed to construct component 
> instance
> WFLYCTL0448: 2 additional services are down due to their dependencies being 
> missing or failed
> 
> ___
> 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/4KT4STN5M6HXXW4WNRI2YUX7RGLZRV2T/
___
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/R3JYGOPYDCHTP5CBAYPG4W6NXXZQ2TOV/

[ovirt-users] Re: Please help: Failure Restoring Data on Clean Engine After Migration

[Andrei Verovski]

Hi,


Thanks, I solved this problem before by means of executing these commands:

su - postgres -s/bin/bash
psql -d ovirt_engine_history

CREATE ROLE ovirt_engine_history_grafana;
ALTER DEFAULT PRIVILEGES FOR ROLE ovirt_engine_history IN SCHEMA public GRANT 
SELECT ON TABLES TO ovirt_engine_history_grafana;
ALTER ROLE ovirt_engine_history_grafana WITH ENCRYPTED PASSWORD ‘my_password';
ALTER ROLE ovirt_engine_history_grafana WITH LOGIN;

my_password from:
/etc/ovirt-engine-dwh/ovirt-engine-dwhd.conf.d/10-setup-grafana-database.conf 


> On 18 Jul 2022, at 15:35, Yedidyah Bar David  wrote:
> 
> On Fri, Jul 15, 2022 at 10:31 AM Andrei Verovski  wrote:
>> 
>> Hi,
>> 
>> I did this and still struck at that Grafana stage.
>> 
>> CREATE ROLE ovirt_engine_history_grafana;
>> ALTER DEFAULT PRIVILEGES FOR ROLE ovirt_engine_history IN SCHEMA public 
>> GRANT SELECT ON TABLES TO ovirt_engine_history_grafana;
>> ALTER ROLE ovirt_engine_history_grafana WITH PASSWORD ‘my_password’;
> 
> 
> You are probably missing pg_hba.conf configuration, see e.g.
> https://www.ovirt.org/documentation/data_warehouse_guide/#Allowing_Read_Only_Access_to_the_History_Database
> .
> 
>> 
>> 
>> How to delete Grafana completely from old setup???
> 
> 
> I don't think we have this documented anywhere.
> 
> If you only want to get rid of the setup issue, it's probably enough
> to edit /etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf,
> changing the line 'OVESETUP_GRAFANA_CORE/enable=bool:True' to
> 'OVESETUP_GRAFANA_CORE/enable=bool:False'.
> 
> This will not "delete Grafana completely", only make engine-setup ignore it.
> 
>> 
>> 
>> I don’t need it.
>> 
>> Thanks in advance.
>> 
>> 
>> 
>>> On 14 Jul 2022, at 17:37, Moritz Baumann  wrote:
>>> 
>>> I had a similar issue.
>>> 
>>> for me, taking the password from
>>> /etc/ovirt-engine-dwh/ovirt-engine-dwhd.conf.d/10-setup-grafana-database.conf
>>>  (GRAFANA_DB_PASSWORD)
>>> 
>>> and set that password in postgres for the
>>> user ovirt_engine_history_grafana did the trick.
>>> 
>>> Best
>>> Mo
>>> 
>>> 
>>> On 7/14/22 16:28, Andrei Verovski wrote:
>>>> Hi,
>>>> I have oVirt engine 4.4.7 running on dedicated PC (not hosted engine).
>>>> After several unsuccessful upgrade attempts of 4.4.7 to 4.4.10 decided to 
>>>> install clean 4.4.10 and migrate data.
>>>> On old engine
>>>> engine-backup --scope=all --mode=backup
>>>> On new engine
>>>> engine-backup --mode=restore --provision-all-databases 
>>>> --no-restore-permissions --file=ovirt-engine-backup-20220713160717.backup
> 
> I am sorry to note that your issue was most likely caused by
> '--no-restore-permissions', although the documentation (including
> --help/manpage) does not hint about this at all. You might want to
> open a doc bug to document this, or even an RFE bug, to make this a
> separate option.
> 
> for a long time, it was mandatory to pass either
> --no-restore-permissions or --restore-permissions:
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=1220791
> 
> But I recently changed this to default to --restore-permissions:
> 
> https://bugzilla.redhat.com/1821018
> 
> With --restore-permissions, if you previously manually created extra
> users and gave them access permissions, e.g. using the doc in above
> link, --mode=restore could not know the passwords for these users, and
> created them with random passwords, outputting "- extra user
> '${extrau}' having grants on database ${database}, created with a
> random password":
> 
> https://bugzilla.redhat.com/1369757
> 
> But for grafana, this isn't true - the password is saved in the
> above-mentioned conf, and so --mode=restore can (and does) create the
> user with the saved password:
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=1837460
> 
> Bottom line:
> 
> I now think that --restore-permissions almost always makes sense,
> therefore changed it to be the default.
> 
> If you have scripts/procedures that pass --no-restore-permissions, I
> recommend rethinking these and considering dropping it altogether,
> relying on the default, or passing --restore-permissions.
> 
> A scenario I can think of where '--no-restore-permissions' does make
> sense: If you do have extra users you created for some other
> applications to access the DWH DB, and would rather not have a restore
> procedure replace their passwords to random ones, but prefer having
> your restore procedure handle this manually - restore/setup with
> --no-restore-permissions, then manually add the users+passwords you
> need and give them permissions.
> 
> 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/CJ6JKNNFGVLCL3F5C36AD5LXSXSLOGFV/

[ovirt-users] How to Fix: oVirt 4.4.10 Internal server error 500 after engine-setup (vdsm-jsonrpc-java )

[Andrei Verovski]

Hi,


Finally I managed to migrate 4.4.7 to fresh installation of 4.4.10.
However, after successful engine-setup I’ve got 500 - Internal Server Error

I found this:
https://bugzilla.redhat.com/show_bug.cgi?id=1918022

Bug 1918022 - oVirt Manager is not loading after engine-setup 

Article suggested to downgrade vdsm-jsonrpc-java to 1.5.x.

However, this is not possible:
dnf --showduplicates list vdsm-jsonrpc-java
dnf install vdsm-jsonrpc-java-1.5.7-1.el8

Last metadata expiration check: 0:39:52 ago on Fri 15 Jul 2022 02:32:36 PM EEST.
Error: 
Problem: problem with installed package 
ovirt-engine-backend-4.4.10.7-1.el8.noarch
 - package ovirt-engine-backend-4.4.10.7-1.el8.noarch requires 
vdsm-jsonrpc-java >= 1.6.0, but none of the providers can be installed
 - cannot install both vdsm-jsonrpc-java-1.5.7-1.el8.noarch and 
vdsm-jsonrpc-java-1.6.0-1.el8.noarch
 - cannot install both vdsm-jsonrpc-java-1.6.0-1.el8.noarch and 
vdsm-jsonrpc-java-1.5.7-1.el8.noarch


How to fix this?
Thanks in advance.


*   SERVER LOG *

2022-07-15 14:45:44,969+03 ERROR [org.jboss.as.controller.management-operation] 
(Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: 
([("deployment" => "engine.ear")]) - failure description: {"WFLYCTL0080: Failed 
services" => 
{"jboss.deployment.subunit.\"engine.ear\".\"bll.jar\".component.Backend.START" 
=> "java.lang.IllegalStateException: WFLYEE0042: Failed to construct component 
instance
   Caused by: java.lang.IllegalStateException: WFLYEE0042: Failed to construct 
component instance
   Caused by: javax.ejb.EJBException: org.jboss.weld.exceptions.WeldException: 
WELD-49: Unable to invoke protected void 
org.ovirt.engine.core.bll.TagsDirector.init() on 
org.ovirt.engine.core.bll.TagsDirector@648487d3
   Caused by: org.jboss.weld.exceptions.WeldException: WELD-49: Unable to 
invoke protected void org.ovirt.engine.core.bll.TagsDirector.init() on 
org.ovirt.engine.core.bll.TagsDirector@648487d3
   Caused by: java.lang.reflect.InvocationTargetException
   Caused by: org.springframework.dao.InvalidDataAccessApiUsageException: 
Unable to determine the correct call signature - no 
procedure/function/signature for 'gettagsbyparent_id'"}}
2022-07-15 14:45:44,981+03 INFO  [org.jboss.as.server] (ServerService Thread 
Pool -- 25) WFLYSRV0010: Deployed "restapi.war" (runtime-name : "restapi.war")
2022-07-15 14:45:44,982+03 INFO  [org.jboss.as.server] (ServerService Thread 
Pool -- 25) WFLYSRV0010: Deployed "engine.ear" (runtime-name : "engine.ear")
2022-07-15 14:45:44,982+03 INFO  [org.jboss.as.server] (ServerService Thread 
Pool -- 25) WFLYSRV0010: Deployed "apidoc.war" (runtime-name : "apidoc.war")
2022-07-15 14:45:44,982+03 INFO  [org.jboss.as.server] (ServerService Thread 
Pool -- 25) WFLYSRV0010: Deployed "ovirt-web-ui.war" (runtime-name : 
"ovirt-web-ui.war")
2022-07-15 14:45:45,015+03 INFO  [org.jboss.as.controller] (Controller Boot 
Thread) WFLYCTL0183: Service status report
WFLYCTL0186:   Services which failed to start:  service 
jboss.deployment.subunit."engine.ear"."bll.jar".component.Backend.START: 
java.lang.IllegalStateException: WFLYEE0042: Failed to construct component 
instance
WFLYCTL0448: 2 additional services are down due to their dependencies being 
missing or failed

___
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/4KT4STN5M6HXXW4WNRI2YUX7RGLZRV2T/

[ovirt-users] Q: oVirt 4.4.10 and vdsm-jsonrpc-java (Internal server error 500 after engine-setup)

[Andrei Verovski]

Hi,


Finally I managed to migrate 4.4.7 to fresh installation of 4.4.10.
However, after successful engine-setup I’ve got 500 - Internal Server Error

I found this:
https://bugzilla.redhat.com/show_bug.cgi?id=1918022

Bug 1918022 - oVirt Manager is not loading after engine-setup 

Article suggested to downgrade vdsm-jsonrpc-java to 1.5.x.

However, this is not possible:
dnf --showduplicates list vdsm-jsonrpc-java
dnf install vdsm-jsonrpc-java-1.5.7-1.el8

Last metadata expiration check: 0:39:52 ago on Fri 15 Jul 2022 02:32:36 PM EEST.
Error: 
 Problem: problem with installed package 
ovirt-engine-backend-4.4.10.7-1.el8.noarch
  - package ovirt-engine-backend-4.4.10.7-1.el8.noarch requires 
vdsm-jsonrpc-java >= 1.6.0, but none of the providers can be installed
  - cannot install both vdsm-jsonrpc-java-1.5.7-1.el8.noarch and 
vdsm-jsonrpc-java-1.6.0-1.el8.noarch
  - cannot install both vdsm-jsonrpc-java-1.6.0-1.el8.noarch and 
vdsm-jsonrpc-java-1.5.7-1.el8.noarch


How to fix this?
Thanks in advance.
 

 *   SERVER LOG *

2022-07-15 14:45:44,969+03 ERROR [org.jboss.as.controller.management-operation] 
(Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: 
([("deployment" => "engine.ear")]) - failure description: {"WFLYCTL0080: Failed 
services" => 
{"jboss.deployment.subunit.\"engine.ear\".\"bll.jar\".component.Backend.START" 
=> "java.lang.IllegalStateException: WFLYEE0042: Failed to construct component 
instance
Caused by: java.lang.IllegalStateException: WFLYEE0042: Failed to construct 
component instance
Caused by: javax.ejb.EJBException: org.jboss.weld.exceptions.WeldException: 
WELD-49: Unable to invoke protected void 
org.ovirt.engine.core.bll.TagsDirector.init() on 
org.ovirt.engine.core.bll.TagsDirector@648487d3
Caused by: org.jboss.weld.exceptions.WeldException: WELD-49: Unable to 
invoke protected void org.ovirt.engine.core.bll.TagsDirector.init() on 
org.ovirt.engine.core.bll.TagsDirector@648487d3
Caused by: java.lang.reflect.InvocationTargetException
Caused by: org.springframework.dao.InvalidDataAccessApiUsageException: 
Unable to determine the correct call signature - no 
procedure/function/signature for 'gettagsbyparent_id'"}}
2022-07-15 14:45:44,981+03 INFO  [org.jboss.as.server] (ServerService Thread 
Pool -- 25) WFLYSRV0010: Deployed "restapi.war" (runtime-name : "restapi.war")
2022-07-15 14:45:44,982+03 INFO  [org.jboss.as.server] (ServerService Thread 
Pool -- 25) WFLYSRV0010: Deployed "engine.ear" (runtime-name : "engine.ear")
2022-07-15 14:45:44,982+03 INFO  [org.jboss.as.server] (ServerService Thread 
Pool -- 25) WFLYSRV0010: Deployed "apidoc.war" (runtime-name : "apidoc.war")
2022-07-15 14:45:44,982+03 INFO  [org.jboss.as.server] (ServerService Thread 
Pool -- 25) WFLYSRV0010: Deployed "ovirt-web-ui.war" (runtime-name : 
"ovirt-web-ui.war")
2022-07-15 14:45:45,015+03 INFO  [org.jboss.as.controller] (Controller Boot 
Thread) WFLYCTL0183: Service status report
WFLYCTL0186:   Services which failed to start:  service 
jboss.deployment.subunit."engine.ear"."bll.jar".component.Backend.START: 
java.lang.IllegalStateException: WFLYEE0042: Failed to construct component 
instance
WFLYCTL0448: 2 additional services are down due to their dependencies being 
missing or failed

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

[ovirt-users] Re: Please help: Failure Restoring Data on Clean Engine After Migration

[Andrei Verovski]

Hi,

I did this and still struck at that Grafana stage.

CREATE ROLE ovirt_engine_history_grafana;
ALTER DEFAULT PRIVILEGES FOR ROLE ovirt_engine_history IN SCHEMA public GRANT 
SELECT ON TABLES TO ovirt_engine_history_grafana;
ALTER ROLE ovirt_engine_history_grafana WITH PASSWORD ‘my_password’;

How to delete Grafana completely from old setup???

I don’t need it.

Thanks in advance.



> On 14 Jul 2022, at 17:37, Moritz Baumann  wrote:
> 
> I had a similar issue.
> 
> for me, taking the password from
> /etc/ovirt-engine-dwh/ovirt-engine-dwhd.conf.d/10-setup-grafana-database.conf 
> (GRAFANA_DB_PASSWORD)
> 
> and set that password in postgres for the
> user ovirt_engine_history_grafana did the trick.
> 
> Best
> Mo
> 
> 
> On 7/14/22 16:28, Andrei Verovski wrote:
>> Hi,
>> I have oVirt engine 4.4.7 running on dedicated PC (not hosted engine).
>> After several unsuccessful upgrade attempts of 4.4.7 to 4.4.10 decided to 
>> install clean 4.4.10 and migrate data.
>> On old engine
>> engine-backup --scope=all --mode=backup
>> On new engine
>> engine-backup --mode=restore --provision-all-databases 
>> --no-restore-permissions --file=ovirt-engine-backup-20220713160717.backup
>> Result:
>> [ ERROR ] Failed to execute stage 'Environment setup': Cannot connect to 
>> database for grafana using existing credentials: 
>> ovirt_engine_history_grafana@localhost:5432
>> How to Remove Grafana Completely During Engine Migration, or skip it during 
>> backup?
>> In fact it would be nice to delete it on active 4.4.7 setup, I don’t need it 
>> anyway.
>> Thanks in advance.
>> # — LOG ———
>> Start of engine-backup with mode 'restore'
>> scope: all
>> archive file: ovirt-engine-backup-20220713160717.backup
>> log file: 
>> /var/log/ovirt-engine-backup/ovirt-engine-restore-20220714170603.log
>> Preparing to restore:
>> - Unpacking file 'ovirt-engine-backup-20220713160717.backup'
>> Restoring:
>> - Files
>> Provisioning PostgreSQL users/databases:
>> - user 'engine', database 'engine'
>> - user 'ovirt_engine_history', database 'ovirt_engine_history'
>> Restoring:
>> - Engine database 'engine'
>>   - Cleaning up temporary tables in engine database 'engine'
>>   - Updating DbJustRestored VdcOption in engine database
>>   - Resetting DwhCurrentlyRunning in dwh_history_timekeeping in engine 
>> database
>>   - Resetting HA VM status
>> --
>> Please note:
>> The engine database was backed up at 2022-07-13 16:07:21.0 +0300 .
>> Objects that were added, removed or changed after this date, such as virtual
>> machines, disks, etc., are missing in the engine, and will probably require
>> recovery or recreation.
>> --
>> - DWH database 'ovirt_engine_history'
>> - Grafana database '/var/lib/grafana/grafana.db'
>> You should now run engine-setup.
>> Done.
>> [root@node00 ovirt-engine-backup]# engine-setup
>> [ INFO  ] Stage: Initializing
>> [ INFO  ] Stage: Environment setup
>>   Configuration files: 
>> /etc/ovirt-engine-setup.conf.d/10-packaging-jboss.conf, 
>> /etc/ovirt-engine-setup.conf.d/10-packaging.conf, 
>> /etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf
>>   Log file: 
>> /var/log/ovirt-engine/setup/ovirt-engine-setup-20220714170757-7072xx.log
>>   Version: otopi-1.9.6 (otopi-1.9.6-1.el8)
>> [ INFO  ] The engine DB has been restored from a backup
>> [ ERROR ] Failed to execute stage 'Environment setup': Cannot connect to 
>> database for grafana using existing credentials: 
>> ovirt_engine_history_grafana@localhost:5432
>> [ INFO  ] Stage: Clean up
>>   Log file is located at 
>> /var/log/ovirt-engine/setup/ovirt-engine-setup-20220714170757-7072xx.log
>> [ INFO  ] Generating answer file 
>> '/var/lib/ovirt-engine/setup/answers/20220714170806-setup.conf'
>> [ INFO  ] Stage: Pre-termination
>> [ INFO  ] Stage: Termination
>> [ ERROR ] Execution of setup failed
>> ___
>> 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/7JORR5ZWZJTGPF2FKDUTVI5DRWB2XI5H/
> _

[ovirt-users] Please help: Failure Restoring Data on Clean Engine After Migration

[Andrei Verovski]

Hi,

I have oVirt engine 4.4.7 running on dedicated PC (not hosted engine).

After several unsuccessful upgrade attempts of 4.4.7 to 4.4.10 decided to 
install clean 4.4.10 and migrate data.

On old engine
engine-backup --scope=all --mode=backup

On new engine
engine-backup --mode=restore --provision-all-databases --no-restore-permissions 
--file=ovirt-engine-backup-20220713160717.backup

Result:
[ ERROR ] Failed to execute stage 'Environment setup': Cannot connect to 
database for grafana using existing credentials: 
ovirt_engine_history_grafana@localhost:5432

How to Remove Grafana Completely During Engine Migration, or skip it during 
backup? 
In fact it would be nice to delete it on active 4.4.7 setup, I don’t need it 
anyway.

Thanks in advance.


# — LOG ———

Start of engine-backup with mode 'restore'
scope: all
archive file: ovirt-engine-backup-20220713160717.backup
log file: /var/log/ovirt-engine-backup/ovirt-engine-restore-20220714170603.log
Preparing to restore:
- Unpacking file 'ovirt-engine-backup-20220713160717.backup'
Restoring:
- Files
Provisioning PostgreSQL users/databases:
- user 'engine', database 'engine'
- user 'ovirt_engine_history', database 'ovirt_engine_history'
Restoring:
- Engine database 'engine'
  - Cleaning up temporary tables in engine database 'engine'
  - Updating DbJustRestored VdcOption in engine database
  - Resetting DwhCurrentlyRunning in dwh_history_timekeeping in engine database
  - Resetting HA VM status
--
Please note:

The engine database was backed up at 2022-07-13 16:07:21.0 +0300 .

Objects that were added, removed or changed after this date, such as virtual
machines, disks, etc., are missing in the engine, and will probably require
recovery or recreation.
--
- DWH database 'ovirt_engine_history'
- Grafana database '/var/lib/grafana/grafana.db'
You should now run engine-setup.
Done.
[root@node00 ovirt-engine-backup]# engine-setup 
[ INFO  ] Stage: Initializing
[ INFO  ] Stage: Environment setup
  Configuration files: 
/etc/ovirt-engine-setup.conf.d/10-packaging-jboss.conf, 
/etc/ovirt-engine-setup.conf.d/10-packaging.conf, 
/etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf
  Log file: 
/var/log/ovirt-engine/setup/ovirt-engine-setup-20220714170757-7072xx.log
  Version: otopi-1.9.6 (otopi-1.9.6-1.el8)
[ INFO  ] The engine DB has been restored from a backup
[ ERROR ] Failed to execute stage 'Environment setup': Cannot connect to 
database for grafana using existing credentials: 
ovirt_engine_history_grafana@localhost:5432
[ INFO  ] Stage: Clean up
  Log file is located at 
/var/log/ovirt-engine/setup/ovirt-engine-setup-20220714170757-7072xx.log
[ INFO  ] Generating answer file 
'/var/lib/ovirt-engine/setup/answers/20220714170806-setup.conf'
[ INFO  ] Stage: Pre-termination
[ INFO  ] Stage: Termination
[ ERROR ] Execution of setup failed

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

[ovirt-users] Q: Instaling Ovirt Engine 4.4.10 on Clean CentOS 8 Stream

[Andrei Verovski]

Hi,

Since I run into a lot of problems upgrading 4.4.7 to 4.4.10, is it OK to 
install clean
CentOS-Stream-8-x86_64-20220712-dvd1.iso 

and restore from backup?
4.4.10 release long before Stream 20220712, may I run again into similar 
problems, or I need to use earlier snapshot of Stream 8 ?

I use dedicated engine PC, not hosted engine.

Thanks in advance for any suggestion(s)

Andrei
___
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/7RUJVMNTGJLB3PWDREKICP7PNX4MLNLT/

[ovirt-users] Re: Lost space in /var/log

[Andrei Verovski]

Hi,

Version 4.4
Its simple 3-node system with no hosted engine (engine on separate server).
Node installed manually, not via factory image.
I just can't any file/dir which eats almost 8 GB on /var/log.


On 6/22/22 23:40, wodel youchi wrote:
Is it an HCI deployment? I have had a similar problem and it was on an 
HCI deployment. The healing process get stuck for some reason that I 
don't know and it fills the space. What I did is reboot the node and 
the free space was there.


What version of ovirt are you using?

Regards

On Wed, Jun 22, 2022, 21:27 Andrei Verovski  wrote:

Hi !

I have strange situation with low disk space on /var/log/, yet I
can't
figure out what have consumed so much space.
Look at the du output.

Thanks in advance for any suggestion(s).


# df -h

Filesystem                       Size  Used Avail Use% Mounted on
/dev/mapper/centos-var           15G  1.3G   13G   9% /var
/dev/mapper/centos-var_log       7.8G  7.1G  293M  97% /var/log
/dev/mapper/centos-var_log_audit 2.0G   41M  1.8G   3% /var/log/audit

#
# du -ah /var/log | sort -n -r | head -n 20

664K    /var/log/vdsm
660K    /var/log/vdsm/vdsm.log
624K    /var/log/gdm
580K    /var/log/anaconda/storage.log
480K    /var/log/anaconda/packaging.log
380K    /var/log/gdm/:0.log.4
316K    /var/log/anaconda/syslog
276K    /var/log/tuned
252K /var/log/libvirt/qemu/NextCloud-Collabora-LVM.log-20210806
220K    /var/log/Xorg.0.log
168K    /var/log/gdm/:0.log
156K    /var/log/yum.log-20191117
156K    /var/log/secure-20180726
132K    /var/log/libvirt/qemu/NextCloud-Collabora-Active.log
128K    /var/log/anaconda/anaconda.log
120K    /var/log/hp-snmp-agents
116K    /var/log/hp-snmp-agents/cma.log
112K    /var/log/vinchin
104K    /var/log/vinchin/kvm_backup_service
104K    /var/log/tuned/tuned.log.2

#
# find . -printf '%s %p\n'| sort -nr | head -10

16311686 ./rhsm/rhsm.log
4070423 ./cron-20180726
3667146 ./anaconda/journal.log
3409071 ./secure
300 ./rhsm/rhsm.log-20180726
2912670 ./audit/audit.log
1418007 ./sanlock.log
1189580 ./vdsm/vdsm.log
592718 ./anaconda/storage.log
487567 ./anaconda/packaging.log
___
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/N566CST3DAXILL77BBB2EYGTFX7ZQ2WY/


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

[ovirt-users] Lost space in /var/log

[Andrei Verovski]

Hi !

I have strange situation with low disk space on /var/log/, yet I can't 
figure out what have consumed so much space.

Look at the du output.

Thanks in advance for any suggestion(s).


# df -h

Filesystem   Size  Used Avail Use% Mounted on
/dev/mapper/centos-var   15G  1.3G   13G   9% /var
/dev/mapper/centos-var_log   7.8G  7.1G  293M  97% /var/log
/dev/mapper/centos-var_log_audit 2.0G   41M  1.8G   3% /var/log/audit

#
# du -ah /var/log | sort -n -r | head -n 20

664K/var/log/vdsm
660K/var/log/vdsm/vdsm.log
624K/var/log/gdm
580K/var/log/anaconda/storage.log
480K/var/log/anaconda/packaging.log
380K/var/log/gdm/:0.log.4
316K/var/log/anaconda/syslog
276K/var/log/tuned
252K/var/log/libvirt/qemu/NextCloud-Collabora-LVM.log-20210806
220K/var/log/Xorg.0.log
168K/var/log/gdm/:0.log
156K/var/log/yum.log-20191117
156K/var/log/secure-20180726
132K/var/log/libvirt/qemu/NextCloud-Collabora-Active.log
128K/var/log/anaconda/anaconda.log
120K/var/log/hp-snmp-agents
116K/var/log/hp-snmp-agents/cma.log
112K/var/log/vinchin
104K/var/log/vinchin/kvm_backup_service
104K/var/log/tuned/tuned.log.2

#
# find . -printf '%s %p\n'| sort -nr | head -10

16311686 ./rhsm/rhsm.log
4070423 ./cron-20180726
3667146 ./anaconda/journal.log
3409071 ./secure
300 ./rhsm/rhsm.log-20180726
2912670 ./audit/audit.log
1418007 ./sanlock.log
1189580 ./vdsm/vdsm.log
592718 ./anaconda/storage.log
487567 ./anaconda/packaging.log
___
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/N566CST3DAXILL77BBB2EYGTFX7ZQ2WY/

[ovirt-users] Q: Error ID 119 - ioctl(KVM_CREATE_VM) failed: Cannot allocate memory

[Andrei Verovski]

Hi !

Does this error message means node runs out of RAM?

Quite strange since there are about 20 GB of free RAN, and VM requires 
only 8.
I noticed this happen till Vinchin was in a process of removing snapshot 
from another VM.


Thanks.

VM Jumis_VM-Active is down with error. Exit message: internal error: 
process exited while connecting to monitor: ioctl(KVM_CREATE_VM) failed: 
12 Cannot allocate memory
2022-06-22T19:50:46.501704Z qemu-kvm: failed to initialize KVM: Cannot 
allocate memory.


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

[ovirt-users] Win Server 2022 and virtio-win 0.1.217-2 update failure

[Andrei Verovski]

Hi,

I'm trying to update to latest virtio-win 0.1.217-2, and install fails 
no matter what, even with real-time protection off.


Log file attached.

Currently installed:

QEMU Guest Agent 103.00
Virtio-guest-tools 0.1.215

How to fix this?
Thanks in advance.

# --

[1B1C:1B10][2022-06-03T21:05:41]i001: Burn v3.11.1.2318, Windows v10.0 
(Build 20348: Service Pack 0), path: 
C:\Windows\Temp\{1EACBA77-7C5A-4A47-AAD4-09AFFBAD6EB5}\.cr\virtio-win-guest-tools.exe
[1B1C:1B10][2022-06-03T21:05:41]i009: Command Line: 
'-burn.clean.room=E:\virtio-win-guest-tools.exe 
-burn.filehandle.attached=568 -burn.filehandle.self=556'
[1B1C:1B10][2022-06-03T21:05:41]i000: Setting string variable 
'WixBundleOriginalSource' to value 'E:\virtio-win-guest-tools.exe'
[1B1C:1B10][2022-06-03T21:05:41]i000: Setting string variable 
'WixBundleOriginalSourceFolder' to value 'E:\'
[1B1C:1B10][2022-06-03T21:05:41]i000: Setting string variable 
'WixBundleLog' to value 
'C:\Users\ADMINI~1\AppData\Local\Temp\Virtio-win-guest-tools_20220603210541.log'
[1B1C:1B10][2022-06-03T21:05:41]i000: Setting string variable 
'WixBundleName' to value 'Virtio-win-guest-tools'
[1B1C:1B10][2022-06-03T21:05:41]i000: Setting string variable 
'WixBundleManufacturer' to value 'Red Hat, Inc.'
[1B1C:1AFC][2022-06-03T21:05:41]i000: Setting numeric variable 
'WixStdBALanguageId' to value 1033
[1B1C:1AFC][2022-06-03T21:05:41]i000: Setting version variable 
'WixBundleFileVersion' to value '0.1.217.0'

[1B1C:1B10][2022-06-03T21:05:41]i100: Detect begin, 8 packages
[1B1C:1B10][2022-06-03T21:05:41]i102: Detected related bundle: 
{e2e8124d-6dd0-4247-bde0-6a6bccde383d}, type: Upgrade, scope: 
PerMachine, version: 0.1.215.0, operation: MajorUpgrade
[1B1C:1B10][2022-06-03T21:05:41]i103: Detected related package: 
{32A54EE9-1358-4C7B-8468-C5BB42F4F849}, scope: PerMachine, version: 
0.1.215.0, language: 0 operation: MajorUpgrade
[1B1C:1B10][2022-06-03T21:05:41]w120: Detected partially cached package: 
vwi.Ix1j, invalid payload: vwi.Ix1j, reason: 0x80070002
[1B1C:1B10][2022-06-03T21:05:41]w120: Detected partially cached package: 
vwi.lFj1, invalid payload: vwi.lFj1, reason: 0x80070002
[1B1C:1B10][2022-06-03T21:05:41]i103: Detected related package: 
{EE3877E4-07B0-41F2-ADB8-B45133DDCE37}, scope: PerMachine, version: 
0.10.5.0, language: 0 operation: Downgrade
[1B1C:1B10][2022-06-03T21:05:41]w120: Detected partially cached package: 
vwi.yP23, invalid payload: vwi.yP23, reason: 0x80070570
[1B1C:1B10][2022-06-03T21:05:41]i101: Detected package: 
virtio_win_gt_x64.msi, state: Absent, cached: None
[1B1C:1B10][2022-06-03T21:05:41]i104: Detected package: 
virtio_win_gt_x64.msi, feature: FE_balloon_driver, state: Absent
[1B1C:1B10][2022-06-03T21:05:41]i104: Detected package: 
virtio_win_gt_x64.msi, feature: FE_network_driver, state: Absent
[1B1C:1B10][2022-06-03T21:05:41]i104: Detected package: 
virtio_win_gt_x64.msi, feature: FE_pvpanic_driver, state: Absent
[1B1C:1B10][2022-06-03T21:05:41]i104: Detected package: 
virtio_win_gt_x64.msi, feature: FE_qemufwcfg_driver, state: Absent
[1B1C:1B10][2022-06-03T21:05:41]i104: Detected package: 
virtio_win_gt_x64.msi, feature: FE_qemupciserial_driver, state: Absent
[1B1C:1B10][2022-06-03T21:05:41]i104: Detected package: 
virtio_win_gt_x64.msi, feature: FE_vioinput_driver, state: Absent
[1B1C:1B10][2022-06-03T21:05:41]i104: Detected package: 
virtio_win_gt_x64.msi, feature: FE_viorng_driver, state: Absent
[1B1C:1B10][2022-06-03T21:05:41]i104: Detected package: 
virtio_win_gt_x64.msi, feature: FE_vioscsi_driver, state: Absent
[1B1C:1B10][2022-06-03T21:05:41]i104: Detected package: 
virtio_win_gt_x64.msi, feature: FE_vioserial_driver, state: Absent
[1B1C:1B10][2022-06-03T21:05:41]i104: Detected package: 
virtio_win_gt_x64.msi, feature: FE_viostor_driver, state: Absent
[1B1C:1B10][2022-06-03T21:05:41]i104: Detected package: 
virtio_win_gt_x64.msi, feature: FE_viofs_driver, state: Absent
[1B1C:1B10][2022-06-03T21:05:41]i104: Detected package: 
virtio_win_gt_x64.msi, feature: FE_viogpudo_driver, state: Absent
[1B1C:1B10][2022-06-03T21:05:41]i101: Detected package: 
virtio_win_gt_x86.msi, state: Absent, cached: None
[1B1C:1B10][2022-06-03T21:05:41]i104: Detected package: 
virtio_win_gt_x86.msi, feature: FE_balloon_driver, state: Absent
[1B1C:1B10][2022-06-03T21:05:41]i104: Detected package: 
virtio_win_gt_x86.msi, feature: FE_network_driver, state: Absent
[1B1C:1B10][2022-06-03T21:05:41]i104: Detected package: 
virtio_win_gt_x86.msi, feature: FE_pvpanic_driver, state: Absent
[1B1C:1B10][2022-06-03T21:05:41]i104: Detected package: 
virtio_win_gt_x86.msi, feature: FE_qemufwcfg_driver, state: Absent
[1B1C:1B10][2022-06-03T21:05:41]i104: Detected package: 
virtio_win_gt_x86.msi, feature: FE_qemupciserial_driver, state: Absent
[1B1C:1B10][2022-06-03T21:05:41]i104: Detected package: 
virtio_win_gt_x86.msi, feature: FE_vioinput_driver, state: Absent
[1B1C:1B10][2022-06-03T21:05:41]i104: Detected package: 

[ovirt-users] Re: Q: How to Fix Frozen "Reboot in progress" VM Status

[Andrei Verovski]

Hi, Arik,

Thanks for help.

su - postgres
psql engine
select vm_guid from vm_static where vm_name='WInServerTerminal-2022';
select status from vm_dynamic where 
vm_guid='7871067f-221c-48ed-a046-f49499ce9be4';
update vm_dynamic set status = 1 where 
vm_guid='7871067f-221c-48ed-a046-f49499ce9be4';
update vm_dynamic set run_on_vds='33453044-4139-5A43-3334-323638385838' where 
vm_guid='7871067f-221c-48ed-a046-f49499ce9be4';

ERROR:  insert or update on table "vm_dynamic" violates foreign key constraint 
"vds_static_vm_dynamic_r"
DETAIL:  Key (run_on_vds)=(33453044-4139-5a43-3334-323638385838) is not present 
in table "vds_static”.

Something is wrong with last query. '33453044-4139-5A43-3334-323638385838’ is 
node UUID from oVirt -> Hosts.

What is correct format with this query ?


> On 31 May 2022, at 11:33, Arik Hadas  wrote:
> 
> On Mon, May 30, 2022 at 5:21 PM Andrei Verovski  wrote:
>> 
>> Hi,
>> 
>> Digging old notes, which unfortunately were not complete, I found also this 
>> query, which was marked as necessary:
>> 
>> update vm_dynamic set run_on_vds='3c854f9c-2cdd-423e-bca0-37964ba76702' 
>> where vm_guid='7871067f-221c-48ed-a046-f49499ce9be4';
>> 
>> but I didn’t remember what is
>> run_on_vds='3c854f9c-2cdd-423e-bca0-37964ba76702’
>> 
>> Is this UUID of the node problematic VM is running on?
> 
> Yes, it should be the UUID of the host that the VM runs on - but the
> issue this update can solve has been addressed and we didn't see it
> for quite a while since then, so unless run_on_vds is set to null I
> wouldn't go this way but rather check what happens within the guest
> and if there's anything unusual in the vdsm log
> 
> 
>> 
>> Thanks.
>> 
>> 
>> On 29 May 2022, at 18:44, Liran Rotenberg  wrote:
>> 
>> 
>> 
>> On Thu, May 26, 2022 at 4:36 PM Andrei Verovski  wrote:
>>> 
>>> Hi,
>>> 
>>> engine=# update vm_dynamic set status = 1 where 
>>> vm_guid='7871067f-221c-48ed-a046-f49499ce9be4';
>>> UPDATE 1
>>> 
>>> Seems like success, but it is not.
>>> 
>>> After few seconds:
>>> engine=# select status from vm_dynamic where 
>>> vm_guid='7871067f-221c-48ed-a046-f49499ce9be4';
>>> status
>>> 
>>> 10
>>> (1 row)
>>> 
>>> Looks like oVirt Engine itself checks something and changes status to “10” 
>>> (Rebooting) again.
>>> 
>>> Is it possible this is somehow related to "virtio-win-0.1.217” I installed 
>>> recently on this Windows Server 2022 VM?
>> 
>> Yes, the engine sets the VM status based on the report from VDSM.
>> VDSM takes the report from the guest-agent, in this case - the one provided 
>> by virtio-win (for windows VMs).
>> Can you make sure it is installed? Also, try to look in vdsm.log if by 
>> searching QEMU you can see one message about getting new capabilities for 
>> the VM?
>> Another option would be to try and check qemu-ga calls to the VM.
>>> 
>>> 
>>> Thanks in advance for any suggestions.
>>> 
>>> 
>>> On 26 May 2022, at 14:53, Liran Rotenberg  wrote:
>>> 
>>> 
>>> 
>>> On Wed, May 25, 2022 at 5:52 PM Andrei Verovski  
>>> wrote:
>>>> 
>>>> Hi,
>>>> 
>>>> I have VM which have restarted successfully yet in oVirt web it is being 
>>>> shown with “Rebooting” status for a very long time.
>>>> 
>>>> I did:
>>>> 
>>>> su - postgres
>>>> psql engine
>>>> select vm_guid from vm_static where vm_name='WInServerTerminal-2022’;
>>>> engine=# select status from vm_dynamic where 
>>>> vm_guid='7871067f-221c-48ed-a046-f49499ce9be4';
>>>> status
>>>> 
>>>> 10
>>>> (1 row)
>>>> 
>>>> How to properly correct status from "Rebooting”?
>>> 
>>> Hi Andrei,
>>> If you wish to change manually the VM status to 'UP' status you may use:
>>> # update vm_dynamic set status = 1 where 
>>> vm_guid='7871067f-221c-48ed-a046-f49499ce9be4';
>>> 
>>> The statuses are the following (VMStatus ENUM):
>>> Unassigned(-1),
>>> Down(0),
>>> Up(1),
>>> PoweringUp(2),
>>> Paused(4),
>>> MigratingFrom(5),
>>> MigratingTo(6),
>>> Unknown(7),
>>> NotResponding(8),
>>> WaitForLaunch(9),
>>> RebootInProgress(10),
>>> SavingState(11),
>>> RestoringStat

[ovirt-users] Re: Q: How to Fix Frozen "Reboot in progress" VM Status

[Andrei Verovski]

Hi,

Digging old notes, which unfortunately were not complete, I found also this 
query, which was marked as necessary:

update vm_dynamic set run_on_vds='3c854f9c-2cdd-423e-bca0-37964ba76702' where 
vm_guid='7871067f-221c-48ed-a046-f49499ce9be4';

but I didn’t remember what is 
run_on_vds='3c854f9c-2cdd-423e-bca0-37964ba76702’

Is this UUID of the node problematic VM is running on?

Thanks.


> On 29 May 2022, at 18:44, Liran Rotenberg  wrote:
> 
> 
> 
> On Thu, May 26, 2022 at 4:36 PM Andrei Verovski  <mailto:andre...@starlett.lv>> wrote:
> Hi,
> 
> engine=# update vm_dynamic set status = 1 where 
> vm_guid='7871067f-221c-48ed-a046-f49499ce9be4';
> UPDATE 1
> 
> Seems like success, but it is not.
> 
> After few seconds:
> engine=# select status from vm_dynamic where 
> vm_guid='7871067f-221c-48ed-a046-f49499ce9be4';
>  status 
> 
>  10
> (1 row)
> 
> Looks like oVirt Engine itself checks something and changes status to “10” 
> (Rebooting) again.
> 
> Is it possible this is somehow related to "virtio-win-0.1.217” I installed 
> recently on this Windows Server 2022 VM?
> Yes, the engine sets the VM status based on the report from VDSM.
> VDSM takes the report from the guest-agent, in this case - the one provided 
> by virtio-win (for windows VMs).
> Can you make sure it is installed? Also, try to look in vdsm.log if by 
> searching QEMU you can see one message about getting new capabilities for the 
> VM?
> Another option would be to try and check qemu-ga calls to the VM.
> 
> Thanks in advance for any suggestions.
> 
> 
>> On 26 May 2022, at 14:53, Liran Rotenberg > <mailto:lrote...@redhat.com>> wrote:
>> 
>> 
>> 
>> On Wed, May 25, 2022 at 5:52 PM Andrei Verovski > <mailto:andre...@starlett.lv>> wrote:
>> Hi,
>> 
>> I have VM which have restarted successfully yet in oVirt web it is being 
>> shown with “Rebooting” status for a very long time.
>> 
>> I did:
>> 
>> su - postgres
>> psql engine
>> select vm_guid from vm_static where vm_name='WInServerTerminal-2022’;
>> engine=# select status from vm_dynamic where 
>> vm_guid='7871067f-221c-48ed-a046-f49499ce9be4';
>>  status 
>> 
>>  10
>> (1 row)
>> 
>> How to properly correct status from "Rebooting”?
>> Hi Andrei,
>> If you wish to change manually the VM status to 'UP' status you may use:
>> # update vm_dynamic set status = 1 where 
>> vm_guid='7871067f-221c-48ed-a046-f49499ce9be4';
>> 
>> The statuses are the following (VMStatus ENUM):
>> Unassigned(-1),
>> Down(0),
>> Up(1),
>> PoweringUp(2),
>> Paused(4),
>> MigratingFrom(5),
>> MigratingTo(6),
>> Unknown(7),
>> NotResponding(8),
>> WaitForLaunch(9),
>> RebootInProgress(10),
>> SavingState(11),
>> RestoringState(12),
>> Suspended(13),
>> ImageIllegal(14),
>> ImageLocked(15),
>> PoweringDown(16);
>> 
>> Regards,
>> Liran
>> 
>> 
>> 
>> Thanks in advance
>> Andrei
>> ___
>> Users mailing list -- users@ovirt.org <mailto:users@ovirt.org>
>> To unsubscribe send an email to users-le...@ovirt.org 
>> <mailto:users-le...@ovirt.org>
>> Privacy Statement: https://www.ovirt.org/privacy-policy.html 
>> <https://www.ovirt.org/privacy-policy.html>
>> oVirt Code of Conduct: 
>> https://www.ovirt.org/community/about/community-guidelines/ 
>> <https://www.ovirt.org/community/about/community-guidelines/>
>> List Archives: 
>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/FSZZOMGVJACZHH3CTWW6HOLTTJXL76QN/
>>  
>> <https://lists.ovirt.org/archives/list/users@ovirt.org/message/FSZZOMGVJACZHH3CTWW6HOLTTJXL76QN/>
> 
> ___
> Users mailing list -- users@ovirt.org <mailto:users@ovirt.org>
> To unsubscribe send an email to users-le...@ovirt.org 
> <mailto:users-le...@ovirt.org>
> Privacy Statement: https://www.ovirt.org/privacy-policy.html 
> <https://www.ovirt.org/privacy-policy.html>
> oVirt Code of Conduct: 
> https://www.ovirt.org/community/about/community-guidelines/ 
> <https://www.ovirt.org/community/about/community-guidelines/>
> List Archives: 
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/SZRORWV6MIOVR3DPA2IMXVPXGJWMGHCQ/
>  
> <https://lists.ovirt.org/archives/list/users@ovirt.org/message/SZRORWV6MIOVR3DPA2IMXVPXGJWMGHCQ/>

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

[ovirt-users] Re: Q: How to Fix Frozen "Reboot in progress" VM Status

[Andrei Verovski]

Hi,

engine=# update vm_dynamic set status = 1 where 
vm_guid='7871067f-221c-48ed-a046-f49499ce9be4';
UPDATE 1

Seems like success, but it is not.

After few seconds:
engine=# select status from vm_dynamic where 
vm_guid='7871067f-221c-48ed-a046-f49499ce9be4';
 status 

 10
(1 row)

Looks like oVirt Engine itself checks something and changes status to “10” 
(Rebooting) again.

Is it possible this is somehow related to "virtio-win-0.1.217” I installed 
recently on this Windows Server 2022 VM?

Thanks in advance for any suggestions.


> On 26 May 2022, at 14:53, Liran Rotenberg  wrote:
> 
> 
> 
> On Wed, May 25, 2022 at 5:52 PM Andrei Verovski  <mailto:andre...@starlett.lv>> wrote:
> Hi,
> 
> I have VM which have restarted successfully yet in oVirt web it is being 
> shown with “Rebooting” status for a very long time.
> 
> I did:
> 
> su - postgres
> psql engine
> select vm_guid from vm_static where vm_name='WInServerTerminal-2022’;
> engine=# select status from vm_dynamic where 
> vm_guid='7871067f-221c-48ed-a046-f49499ce9be4';
>  status 
> 
>  10
> (1 row)
> 
> How to properly correct status from "Rebooting”?
> Hi Andrei,
> If you wish to change manually the VM status to 'UP' status you may use:
> # update vm_dynamic set status = 1 where 
> vm_guid='7871067f-221c-48ed-a046-f49499ce9be4';
> 
> The statuses are the following (VMStatus ENUM):
> Unassigned(-1),
> Down(0),
> Up(1),
> PoweringUp(2),
> Paused(4),
> MigratingFrom(5),
> MigratingTo(6),
> Unknown(7),
> NotResponding(8),
> WaitForLaunch(9),
> RebootInProgress(10),
> SavingState(11),
> RestoringState(12),
> Suspended(13),
> ImageIllegal(14),
> ImageLocked(15),
> PoweringDown(16);
> 
> Regards,
> Liran
> 
> 
> 
> Thanks in advance
> Andrei
> ___
> Users mailing list -- users@ovirt.org <mailto:users@ovirt.org>
> To unsubscribe send an email to users-le...@ovirt.org 
> <mailto:users-le...@ovirt.org>
> Privacy Statement: https://www.ovirt.org/privacy-policy.html 
> <https://www.ovirt.org/privacy-policy.html>
> oVirt Code of Conduct: 
> https://www.ovirt.org/community/about/community-guidelines/ 
> <https://www.ovirt.org/community/about/community-guidelines/>
> List Archives: 
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/FSZZOMGVJACZHH3CTWW6HOLTTJXL76QN/
>  
> <https://lists.ovirt.org/archives/list/users@ovirt.org/message/FSZZOMGVJACZHH3CTWW6HOLTTJXL76QN/>

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

[ovirt-users] Q: How to Fix Frozen "Reboot in progress" VM Status

[Andrei Verovski]

Hi,

I have VM which have restarted successfully yet in oVirt web it is being shown 
with “Rebooting” status for a very long time.

I did:

su - postgres
psql engine
select vm_guid from vm_static where vm_name='WInServerTerminal-2022’;
engine=# select status from vm_dynamic where 
vm_guid='7871067f-221c-48ed-a046-f49499ce9be4';
 status 

 10
(1 row)

How to properly correct status from "Rebooting”?


Thanks in advance
Andrei
___
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/FSZZOMGVJACZHH3CTWW6HOLTTJXL76QN/

[ovirt-users] oVirt / Vinchin Backup Application-Level Consistency

[Andrei Verovski]

Hi,

I’m currently testing oVirt with Vinchin backup, and for application-level 
consistency need to make snapshot with “quiesce” option.
What need to be done in order to activate this feature?

> Guest Quiesce for Application-Level Consistency in Windows/Linux via Guest 
> Agent: Done. Available in oVirt.

Running oVirt version 4.4.7.6

Thanks in advance.
Andrei
___
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/N2OVO5IG2LKUNXX25V7VXGVIS6GE55OH/

[ovirt-users] Re: unable to upgrade engine to 4.4.10 from 4.4.8

[Andrei Verovski]

Hi,

Is this correct order of actions:

1) download ovirt-release44.rpm
2) Remove all repos from /etc/yum.repos.d/ - because of outdated data
3)  Install ovirt-release44.rpm, which does have all correct repos’ list inside.


> On 28 Apr 2022, at 16:46, Patrick Hibbs  wrote:
> 
> That's kinda messed up.
> 
> You did not need to change the mirrorlists for the base installation,
> as the current ovirt-release44.rpm fixes those for you. By doing what
> you did, you now have a base system trying to install most of it's
> packages from the CentOS vault, which is intermittent / slow with out-
> dated packages, and gaining no real benefit from it.
> 
> I'd revert those changes, restore your repo files to their default
> versions, and install the current ovirt-release rpm.
> 
> -Patrick Hibbs
> 
> On Thu, 2022-04-28 at 16:25 +0300, Andrei Verovski wrote:
>> Hi,
>> 
>> I have same issue.
>> Partially I fixed it with conversion to CentOS Stream.
>> 
>> rm -rf /var/cache/dnf
>> cd /etc/yum.repos.d/
>> sed -i 's/mirrorlist/#mirrorlist/g' /etc/yum.repos.d/CentOS-*
>> sed -i
>> 's|#baseurl=http://mirror.centos.org|baseurl=http://vault.centos.org|g'
>>  /etc/yum.repos.d/CentOS-*
>> 
>> sudo dnf install --disablerepo='*'
>> https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm
>> 
>> dnf distro-sync —nobest
>> 
>> It install latest oVirt Engine 4.4.10.2, yet Web UI still shows
>> 4.4.7.6.
>> 
>> engine-setup fails with:
>> [ INFO  ] DNF Downloaded CentOS Linux 8 - AppStream
>> [ ERROR ] DNF Failed to download metadata for repo 'appstream':
>> Cannot prepare internal mirrorlist: No URLs in mirrorlist
>> [ ERROR ] Failed to execute stage 'Environment setup': Failed to
>> download metadata for repo 'appstream': Cannot prepare internal
>> mirrorlist: No URLs in mirrorlist
>> 
>> I don’t know if its safe to leave oVirt Engine in this half-upgraded
>> condition or better to revert back to pristine 4.4.7.6.
>> 
>> 
>> Anyone found solution to upgrade to 4.4.10.2 ?
>> 
>> Thanks in advance.
>> 
>> 
>>> On 28 Apr 2022, at 15:43, Diggy Mc  wrote:
>>> 
>>>> I would add, as you are on CentOS Linux 8, I would recommend
>>>> switching it
>>>> either to some other RHEL clone (Alma, Rocky,...) or to CentOS
>>>> Stream as a
>>>> first step.
>>> 
>>> Wouldn't updating the oVirt packages (# dnf update ovirt\*setup\*)
>>> switch the repositories to CentOS Stream?
>>> ___
>>> 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/EKRUW4BF3LSNT2W2PMQKJK3D7F4V2L4U/
>> ___
>> 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/HPIGXJZNK3BITHWX75JW2YGHB77EPLAR/
> 
> ___
> 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/A5RU5PGZENL3GXI4IISKSYEQJ3RFTLVJ/
___
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/MGU545BI5KUVPZ7TIQDQZJENBUCSOQEU/

[ovirt-users] Re: unable to upgrade engine to 4.4.10 from 4.4.8

[Andrei Verovski]

Hi,

I have same issue.
Partially I fixed it with conversion to CentOS Stream.

rm -rf /var/cache/dnf
cd /etc/yum.repos.d/
sed -i 's/mirrorlist/#mirrorlist/g' /etc/yum.repos.d/CentOS-*
sed -i 's|#baseurl=http://mirror.centos.org|baseurl=http://vault.centos.org|g' 
/etc/yum.repos.d/CentOS-*

sudo dnf install --disablerepo='*' 
https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm

dnf distro-sync —nobest

It install latest oVirt Engine 4.4.10.2, yet Web UI still shows 4.4.7.6.

engine-setup fails with:
[ INFO  ] DNF Downloaded CentOS Linux 8 - AppStream
[ ERROR ] DNF Failed to download metadata for repo 'appstream': Cannot prepare 
internal mirrorlist: No URLs in mirrorlist
[ ERROR ] Failed to execute stage 'Environment setup': Failed to download 
metadata for repo 'appstream': Cannot prepare internal mirrorlist: No URLs in 
mirrorlist

I don’t know if its safe to leave oVirt Engine in this half-upgraded condition 
or better to revert back to pristine 4.4.7.6.


Anyone found solution to upgrade to 4.4.10.2 ?

Thanks in advance.


> On 28 Apr 2022, at 15:43, Diggy Mc  wrote:
> 
>> I would add, as you are on CentOS Linux 8, I would recommend switching it
>> either to some other RHEL clone (Alma, Rocky,...) or to CentOS Stream as a
>> first step.
> 
> Wouldn't updating the oVirt packages (# dnf update ovirt\*setup\*) switch the 
> repositories to CentOS Stream?
> ___
> 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/EKRUW4BF3LSNT2W2PMQKJK3D7F4V2L4U/
___
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/HPIGXJZNK3BITHWX75JW2YGHB77EPLAR/

[ovirt-users] Re: Q: Non-Operational Node Hosts - Ghost Network Problem

[Andrei Verovski]

Hi,


I solved this problem, added network “CloudLink-ISP2” to 2 problematic nodes 
and connected respective Ethernet interfaces to a separate switch bringing 
bringing up.


> On 28 Apr 2022, at 07:45, Patrick Hibbs  wrote:
> 
> Your logs suggest that VDSM hasn't detected the removal of the network
> yet. Did you try clicking on the "Sync Host Networks" button on the
> non-operational hosts?
> 
> If you've changed the network config, VDSM may have failed to set up
> the host properly. What does the output of "ip addr show" on these
> hosts?
> 
> Manually removing the network from the hosts is only a temporary fix.
> VDSM will attempt to recreate the network on restart if VDSM's config
> isn't sync'd with the engine.
> 
> -Patrick Hibbs
> 
> On Wed, 2022-04-27 at 12:36 +0300, Andrei Verovski wrote:
>> Hi,
>> 
>> 
>> I run into nasty and unexpected problem (oVirt 4.4.7.6-1.el8 ) and 2
>> non-operational node hosts, which seem relate to ghost network
>> glitch.
>> Everything worked fine for a very long time until I did the
>> following.
>> 
>> 1) Made a backup of several VMs which have network “CloudLink-ISP2”.
>> 2) Moved VM disks into another node hosts, which don’t have link
>> “CloudLink-ISP2”, and forgot (preliminary to move) to re-configure
>> network interface (remove link to “CloudLink-ISP2”) as I did before..
>> 3) Now I have 2 hosts in non-operational mode which is a really big
>> problem - there are only 3 nodes total in a cluster.
>> 
>> I tried to fix this by adding 3rd network “CloudLink-ISP2” to each
>> non-operational hosts, and connected ethernet interfaces to a switch.
>> Unfortunately, it didn’t helped either because for whatever reason
>> link did not go up.
>> 
>> How I can remove any reference to “CloudLink-ISP2” from node11 and
>> node14? They don’t have any VMs needed that “CloudLink-ISP2”. I
>> edited even inactive VMs and removed “CloudLink-ISP2”.
>> May be there is an option to ignore missing or downed links whn
>> activating node hosts?
>> 
>> Thanks in advance for any help.
>> 
>> 
>> ——
>> 
>> Logs:
>> 
>> 2022-04-27 11:16:59,769+03 ERROR
>> [org.ovirt.engine.core.bll.SetNonOperationalVdsCommand] (EE-
>> ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-51)
>> [5ab20328] Host 'node14' is set to Non-Operational, it is missing the
>> following networks: 'CloudLink-ISP2'
>> 2022-04-27 11:16:59,790+03 WARN 
>> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector
>> ] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-
>> Thread-51) [5ab20328] EVENT_ID: VDS_SET_NONOPERATIONAL_NETWORK(519),
>> Host node14 does not comply with the cluster ClusterRiga11 networks,
>> the following networks are missing on host: 'CloudLink-ISP2'
>> 2022-04-27 11:16:59,884+03 INFO 
>> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector
>> ] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-
>> Thread-51) [55610e1e] EVENT_ID: VDS_DETECTED(13), Status of host
>> node14 was set to NonOperational.
>> 2022-04-27 11:16:59,907+03 INFO 
>> [org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring] (EE-
>> ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-51)
>> [5d6ef791] Host 'node14'(aa871d44-94e2-4fdb-aeb3-ca0ae8dc568f) is
>> already in NonOperational status for reason 'NETWORK_UNREACHABLE'.
>> SetNonOperationalVds command is skipped.
>> 
>> 2022-04-27 11:12:26,050+03 ERROR
>> [org.ovirt.engine.core.bll.SetNonOperationalVdsCommand] (EE-
>> ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-19)
>> [5400352e] Host 'node11' is set to Non-Operational, it is missing the
>> following networks: 'CloudLink-ISP2'
>> 2022-04-27 11:12:26,070+03 WARN 
>> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector
>> ] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-
>> Thread-19) [5400352e] EVENT_ID: VDS_SET_NONOPERATIONAL_NETWORK(519),
>> Host node11 does not comply with the cluster ClusterRiga11 networks,
>> the following networks are missing on host: 'CloudLink-ISP2'
>> 2022-04-27 11:12:26,192+03 INFO 
>> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector
>> ] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-
>> Thread-19) [57d79e54] EVENT_ID: VDS_DETECTED(13), Status of host
>> node11 was set to NonOperational.
>> 2022-04-27 11:12:26,214+03 INFO 
>> [org.ovirt.engine.core.vdsbroker.monitorin

[ovirt-users] Q: Cluster compatibility Level and Old v4.2 Nodes

[Andrei Verovski]

Hi,


I have quite old nodes from early 4.x era (with CentOS 7.6, cluster 
compatibility 4.2 level), and oVirt Engine 4.4.
2 nodes have ovirt-release42.
Upgrade to oVirt Engine 4.5 engine required cluster compatibility >= 4.3 level.

Nodes have been installed with stock CentOS 7.6, not oVirt node image, their 
upgrade is quite problematic right now.

Is it possible to upgrade to cluster compatibility 4.3 while having old 4.2 
nodes?

Thanks in advance.
Andrei
___
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/L4GODZKGD7WO4OHH3LRPXHDPSDH4C3IK/

[ovirt-users] Q: Non-Operational Node Hosts - Ghost Network Problem

[Andrei Verovski]

Hi,


I run into nasty and unexpected problem (oVirt 4.4.7.6-1.el8 ) and 2 
non-operational node hosts, which seem relate to ghost network glitch.
Everything worked fine for a very long time until I did the following.

1) Made a backup of several VMs which have network “CloudLink-ISP2”.
2) Moved VM disks into another node hosts, which don’t have link 
“CloudLink-ISP2”, and forgot (preliminary to move) to re-configure network 
interface (remove link to “CloudLink-ISP2”) as I did before..
3) Now I have 2 hosts in non-operational mode which is a really big problem - 
there are only 3 nodes total in a cluster.

I tried to fix this by adding 3rd network “CloudLink-ISP2” to each 
non-operational hosts, and connected ethernet interfaces to a switch.
Unfortunately, it didn’t helped either because for whatever reason link did not 
go up.

How I can remove any reference to “CloudLink-ISP2” from node11 and node14? They 
don’t have any VMs needed that “CloudLink-ISP2”. I edited even inactive VMs and 
removed “CloudLink-ISP2”.
May be there is an option to ignore missing or downed links whn activating node 
hosts?

Thanks in advance for any help.


——

Logs:

2022-04-27 11:16:59,769+03 ERROR 
[org.ovirt.engine.core.bll.SetNonOperationalVdsCommand] 
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-51) 
[5ab20328] Host 'node14' is set to Non-Operational, it is missing the following 
networks: 'CloudLink-ISP2'
2022-04-27 11:16:59,790+03 WARN  
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-51) 
[5ab20328] EVENT_ID: VDS_SET_NONOPERATIONAL_NETWORK(519), Host node14 does not 
comply with the cluster ClusterRiga11 networks, the following networks are 
missing on host: 'CloudLink-ISP2'
2022-04-27 11:16:59,884+03 INFO  
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-51) 
[55610e1e] EVENT_ID: VDS_DETECTED(13), Status of host node14 was set to 
NonOperational.
2022-04-27 11:16:59,907+03 INFO  
[org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring] 
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-51) 
[5d6ef791] Host 'node14'(aa871d44-94e2-4fdb-aeb3-ca0ae8dc568f) is already in 
NonOperational status for reason 'NETWORK_UNREACHABLE'. SetNonOperationalVds 
command is skipped.

2022-04-27 11:12:26,050+03 ERROR 
[org.ovirt.engine.core.bll.SetNonOperationalVdsCommand] 
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-19) 
[5400352e] Host 'node11' is set to Non-Operational, it is missing the following 
networks: 'CloudLink-ISP2'
2022-04-27 11:12:26,070+03 WARN  
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-19) 
[5400352e] EVENT_ID: VDS_SET_NONOPERATIONAL_NETWORK(519), Host node11 does not 
comply with the cluster ClusterRiga11 networks, the following networks are 
missing on host: 'CloudLink-ISP2'
2022-04-27 11:12:26,192+03 INFO  
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-19) 
[57d79e54] EVENT_ID: VDS_DETECTED(13), Status of host node11 was set to 
NonOperational.
2022-04-27 11:12:26,214+03 INFO  
[org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring] 
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-19) 
[151821e3] Host 'node11'(3c854f9c-2cdd-423e-bca0-37964ba76702) is already in 
NonOperational status for reason 'NETWORK_UNREACHABLE'. SetNonOperationalVds 
command is skipped.

2022-04-27 11:51:10,539+03 INFO  [org.ovirt.engine.core.vdsbroker.VdsManager] 
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-62) [] 
Clearing domains data for host node14
2022-04-27 11:51:10,539+03 INFO  
[org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring] 
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-62) [] 
Host 'node14' moved to Non-Operational state because interface/s which are down 
are needed by required network/s in the current cluster: 'eno3 (CloudLink-ISP2)'
2022-04-27 11:51:10,569+03 WARN  
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-62) [] 
EVENT_ID: VDS_SET_NONOPERATIONAL_IFACE_DOWN(603), Host node14 moved to 
Non-Operational state because interfaces which are down are needed by required 
networks in the current cluster: 'eno3 (CloudLink-ISP2)'.

___
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: 

[ovirt-users] Q: oVirt guest agent + spice-vdagent on Debian 11 Bullseye

[Andrei Verovski]

Hi,


Anyone have compiled these deb packages for Debian 11 Bullseye?
oVirt guest agent + spice-vdagent

Packages from Buster can’t be installed on Bullseye because of broken libnl 
dependencies.

Thanks in advance.
Andrei
___
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/FYF7FKKSVZHBO6U3HOBQ7R6AJSATEES3/

[ovirt-users] Q: oVirt guest agent + spice-vdagent on Debian 11 Bullseye

[Andrei Verovski]

Hi,


Anyone have compiled these deb packages for Debian 11 Bullseye?
oVirt guest agent + spice-vdagent

Packages from Buster can’t be installed on Bullseye because of broken libnl 
dependencies.

Thanks in advance.
Andrei
___
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/AGXM6ZSGCDHX55FV763OKAOJZHJIOT3U/

[ovirt-users] Re: Q: Get Host Capabilities Failed after restart

[Andrei Verovski]

Hi,

For whatever weird reason "kill -3 ” produced NO output in 
console.log.
After downgrading vdsm with backport fix and restart of oVier engine problem 
fixed. I did restart of node several times - everything seem to be fine for now.

Current content of console.log.
WARNING: -jaxpmodule is deprecated and may be removed in a future release
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.codehaus.jackson.map.util.ClassUtil 
(jar:file:/usr/share/ovirt-engine-wildfly/modules/system/layers/base/org/codehaus/jackson/jackson-mapper-asl/main/jackson-mapper-asl-1.9.13.redhat-7.jar!/)
 to constructor java.util.Collections$EmptyMap()
WARNING: Please consider reporting this to the maintainers of 
org.codehaus.jackson.map.util.ClassUtil
WARNING: Use --illegal-access=warn to enable warnings of further illegal 
reflective access operations
WARNING: All illegal access operations will be denied in a future release



> On 9 Aug 2021, at 18:28, Artur Socha  wrote:
> 
> You can use that one or this 'simplified' short version 
> https://access.redhat.com/solutions/3227681 
> <https://access.redhat.com/solutions/3227681>
> 
> Artur
> 
> On Mon, Aug 9, 2021 at 5:01 PM Andrei Verovski  <mailto:andre...@starlett.lv>> wrote:
> Hi
> 
> 
> Should  I use threaddump_linux.sh.tar.gz ?
> from:
> 
> https://access.redhat.com/solutions/18178 
> <https://access.redhat.com/solutions/18178>
> 
> 
> > On 9 Aug 2021, at 17:56, Artur Socha  > <mailto:aso...@redhat.com>> wrote:
> > 
> > Actually you could even make 3 thread dumps in 30second intervals. 
> > Artur
> > 
> > On Mon, Aug 9, 2021 at 4:53 PM Artur Socha  > <mailto:aso...@redhat.com>> wrote:
> > Unfortunately I don't see anything wrong in both engine and vdsm logs. 
> > There is one last thing that comes to my mind that you try - restart engine 
> > service. That is exactly the case I have been investigating. 
> > But before restarting I would like to ask you, if possible, for a java 
> > (jvm) thread dump. 
> > The procedure is as follows:
> > 1)  find jboss pid  ie.
> > $ ps -ef | grep jboss | grep -v grep | awk '{ print $2 }'
> > 2) trigger thread dump
> > $ kill -3 
> > 3)  thread dump logs can be found at /var/log/ovirt-engine/console.log
> > 
> > And then restart engine service to check if that helps.
> > 
> > Artur
> > 
> > 
> > On Mon, Aug 9, 2021 at 2:19 PM Andrei Verovski  > <mailto:andre...@starlett.lv>> wrote:
> > Hi, Artur,
> > 
> > Small update with vdsm status, forgot to include in previous post.
> > 
> > I partially fixed problem with VDSM start.
> > 
> > Bug "Failed to create session: Start job for unit user-0.slice failed with 
> > ‘canceled’”
> > is being described here
> > https://bugzilla.redhat.com/show_bug.cgi?id=1967962 
> > <https://bugzilla.redhat.com/show_bug.cgi?id=1967962>
> > and fix seem to be available here, so I have downgraded systemd with 
> > backport fix:
> > http://people.redhat.com/dtardon/systemd/bz1642460-backport-UserStopDelaySec=/
> >  
> > <http://people.redhat.com/dtardon/systemd/bz1642460-backport-UserStopDelaySec=/>
> > 
> > Now vdsmd service starts successfully, but node14 still cannot be activated 
> > because of same error. This is quite strange, before restart on Friday node 
> > just worked. There were no upgrades, nothing, just restart.
> > 
> > [root@node14 ~]# service vdsmd status
> > Redirecting to /bin/systemctl status vdsmd.service
> > ● vdsmd.service - Virtual Desktop Server Manager
> >Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled; vendor 
> > preset: disabled)
> >Active: active (running) since Mon 2021-08-09 15:12:59 EEST; 4min 20s ago
> >   Process: 4066 ExecStartPre=/usr/libexec/vdsm/vdsmd_init_common.sh 
> > --pre-start (code=exited, status=0/SUCCESS)
> >  Main PID: 4130 (vdsmd)
> > Tasks: 41 (limit: 615525)
> >Memory: 59.5M
> >CGroup: /system.slice/vdsmd.service
> >└─4130 /usr/bin/python3 /usr/share/vdsm/vdsmd
> > 
> > Aug 09 15:12:55 node14.***.lv vdsmd_init_common.sh[4066]: vdsm: Running 
> > prepare_transient_repository
> > Aug 09 15:12:57 node14.***.lv vdsmd_init_common.sh[4066]: vdsm: Running 
> > syslog_available
> > Aug 09 15:12:57 node14.***.lv vdsmd_init_common.sh[4066]: vdsm: Running 
> > nwfilter
> > Aug 09 15:12:58 node14.***.lv vdsmd_init_common.sh[4066]: vdsm: Running 
> > dummybr
> > Aug 09 15:12:58 node14.***.lv vdsmd_init_common.sh[4066]: vdsm: Running 
> &g

[ovirt-users] Re: Q: Get Host Capabilities Failed after restart

[Andrei Verovski]

Hi


Should  I use threaddump_linux.sh.tar.gz ?
from:

https://access.redhat.com/solutions/18178


> On 9 Aug 2021, at 17:56, Artur Socha  wrote:
> 
> Actually you could even make 3 thread dumps in 30second intervals. 
> Artur
> 
> On Mon, Aug 9, 2021 at 4:53 PM Artur Socha  wrote:
> Unfortunately I don't see anything wrong in both engine and vdsm logs. 
> There is one last thing that comes to my mind that you try - restart engine 
> service. That is exactly the case I have been investigating. 
> But before restarting I would like to ask you, if possible, for a java (jvm) 
> thread dump. 
> The procedure is as follows:
> 1)  find jboss pid  ie.
> $ ps -ef | grep jboss | grep -v grep | awk '{ print $2 }'
> 2) trigger thread dump
> $ kill -3 
> 3)  thread dump logs can be found at /var/log/ovirt-engine/console.log
> 
> And then restart engine service to check if that helps.
> 
> Artur
> 
> 
> On Mon, Aug 9, 2021 at 2:19 PM Andrei Verovski  wrote:
> Hi, Artur,
> 
> Small update with vdsm status, forgot to include in previous post.
> 
> I partially fixed problem with VDSM start.
> 
> Bug "Failed to create session: Start job for unit user-0.slice failed with 
> ‘canceled’”
> is being described here
> https://bugzilla.redhat.com/show_bug.cgi?id=1967962
> and fix seem to be available here, so I have downgraded systemd with backport 
> fix:
> http://people.redhat.com/dtardon/systemd/bz1642460-backport-UserStopDelaySec=/
> 
> Now vdsmd service starts successfully, but node14 still cannot be activated 
> because of same error. This is quite strange, before restart on Friday node 
> just worked. There were no upgrades, nothing, just restart.
> 
> [root@node14 ~]# service vdsmd status
> Redirecting to /bin/systemctl status vdsmd.service
> ● vdsmd.service - Virtual Desktop Server Manager
>Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled; vendor 
> preset: disabled)
>Active: active (running) since Mon 2021-08-09 15:12:59 EEST; 4min 20s ago
>   Process: 4066 ExecStartPre=/usr/libexec/vdsm/vdsmd_init_common.sh 
> --pre-start (code=exited, status=0/SUCCESS)
>  Main PID: 4130 (vdsmd)
> Tasks: 41 (limit: 615525)
>Memory: 59.5M
>CGroup: /system.slice/vdsmd.service
>└─4130 /usr/bin/python3 /usr/share/vdsm/vdsmd
> 
> Aug 09 15:12:55 node14.***.lv vdsmd_init_common.sh[4066]: vdsm: Running 
> prepare_transient_repository
> Aug 09 15:12:57 node14.***.lv vdsmd_init_common.sh[4066]: vdsm: Running 
> syslog_available
> Aug 09 15:12:57 node14.***.lv vdsmd_init_common.sh[4066]: vdsm: Running 
> nwfilter
> Aug 09 15:12:58 node14.***.lv vdsmd_init_common.sh[4066]: vdsm: Running 
> dummybr
> Aug 09 15:12:58 node14.***.lv vdsmd_init_common.sh[4066]: vdsm: Running 
> tune_system
> Aug 09 15:12:58 node14.***.lv vdsmd_init_common.sh[4066]: vdsm: Running 
> test_space
> Aug 09 15:12:59 node14.***.lv vdsmd_init_common.sh[4066]: vdsm: Running 
> test_lo
> Aug 09 15:12:59 node14.***.lv systemd[1]: Started Virtual Desktop Server 
> Manager.
> Aug 09 15:13:00 node14.***.lv vdsm[4130]: WARN MOM not available. Error: 
> [Errno 111] Connection refused
> Aug 09 15:13:00 node14.***.lv vdsm[4130]: WARN MOM not available, KSM stats 
> will be missing. Error:
> 
> 
> [root@node14]# firewall-cmd --list-all
> public (active)
>   target: default
>   icmp-block-inversion: no
>   interfaces: DMZ_node14 eno1 eno2 ovirtmgmt
>   sources: 
>   services: cockpit dhcpv6-client libvirt-tls mountd nfs ovirt-imageio 
> ovirt-vmconsole rpc-bind snmp ssh vdsm
>   ports: 2301/tcp 2381/tcp 22/tcp 6081/udp
>   protocols: 
>   forward: no
>   masquerade: no
>   forward-ports: 
>   source-ports: 
>   icmp-blocks: 
>   rich rules: 
> [root@node14 andrei]# 
> 
> 
> vdsm-client Host getStats and vdsm-client Host getCapabilities attached.
> 
> 
> 
> 
>> On 9 Aug 2021, at 13:18, Artur Socha  wrote:
>> 
>> Thanks for the logs.  I am checking them at the moment. I have noticed so 
>> far that node14 is serving NFS share which had been marked as problematic 
>> (probably because of the downtime during the migration) but it has 
>> recovered. 
>> 
>> In the meantime, is is possible to get some meaningful results when  calling:
>> $ vdsm-client Host getStats
>> and 
>> $ vdsm-client Host getCapabilities 
>> on node14?
>> 
>> What  is the state for vdsmd service when running systemctl status vdsmd? 
>> One other thing to rule out is the networking/firewall. Here the list of the 
>> ports to be open for the host (the documentation is for hosted engine, but 
>> it applies for standalone setup as well):  
>> https://www.ovirt.o

[ovirt-users] Re: Q: Get Host Capabilities Failed after restart

[Andrei Verovski]

Hi, Artur,Small update with vdsm status, forgot to include in previous post.I partially fixed problem with VDSM start.Bug "Failed to create session: Start job for unit user-0.slice failed with ‘canceled’”is being described herehttps://bugzilla.redhat.com/show_bug.cgi?id=1967962and fix seem to be available here, so I have downgraded systemd with backport fix:http://people.redhat.com/dtardon/systemd/bz1642460-backport-UserStopDelaySec=/Now vdsmd service starts successfully, but node14 still cannot be activated because of same error. This is quite strange, before restart on Friday node just worked. There were no upgrades, nothing, just restart.[root@node14 ~]# service vdsmd statusRedirecting to /bin/systemctl status vdsmd.service● vdsmd.service - Virtual Desktop Server Manager   Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled; vendor preset: disabled)   Active: active (running) since Mon 2021-08-09 15:12:59 EEST; 4min 20s ago  Process: 4066 ExecStartPre=/usr/libexec/vdsm/vdsmd_init_common.sh --pre-start (code=exited, status=0/SUCCESS) Main PID: 4130 (vdsmd)    Tasks: 41 (limit: 615525)   Memory: 59.5M   CGroup: /system.slice/vdsmd.service           └─4130 /usr/bin/python3 /usr/share/vdsm/vdsmdAug 09 15:12:55 node14.***.lv vdsmd_init_common.sh[4066]: vdsm: Running prepare_transient_repositoryAug 09 15:12:57 node14.***.lv vdsmd_init_common.sh[4066]: vdsm: Running syslog_availableAug 09 15:12:57 node14.***.lv vdsmd_init_common.sh[4066]: vdsm: Running nwfilterAug 09 15:12:58 node14.***.lv vdsmd_init_common.sh[4066]: vdsm: Running dummybrAug 09 15:12:58 node14.***.lv vdsmd_init_common.sh[4066]: vdsm: Running tune_systemAug 09 15:12:58 node14.***.lv vdsmd_init_common.sh[4066]: vdsm: Running test_spaceAug 09 15:12:59 node14.***.lv vdsmd_init_common.sh[4066]: vdsm: Running test_loAug 09 15:12:59 node14.***.lv systemd[1]: Started Virtual Desktop Server Manager.Aug 09 15:13:00 node14.***.lv vdsm[4130]: WARN MOM not available. Error: [Errno 111] Connection refusedAug 09 15:13:00 node14.***.lv vdsm[4130]: WARN MOM not available, KSM stats will be missing. Error:[root@node14]# firewall-cmd --list-allpublic (active)  target: default  icmp-block-inversion: no  interfaces: DMZ_node14 eno1 eno2 ovirtmgmt  sources:   services: cockpit dhcpv6-client libvirt-tls mountd nfs ovirt-imageio ovirt-vmconsole rpc-bind snmp ssh vdsm  ports: 2301/tcp 2381/tcp 22/tcp 6081/udp  protocols:   forward: no  masquerade: no  forward-ports:   source-ports:   icmp-blocks:   rich rules: [root@node14 andrei]# vdsm-client Host getStats and vdsm-client Host getCapabilities attached.

capabilities.log
Description: Binary data


stats.log
Description: Binary data
On 9 Aug 2021, at 13:18, Artur Socha <aso...@redhat.com> wrote:Thanks for the logs.  I am checking them at the moment. I have noticed so far that node14 is serving NFS share which had been marked as problematic (probably because of the downtime during the migration) but it has recovered. In the meantime, is is possible to get some meaningful results when  calling:$ vdsm-client Host getStatsand $ vdsm-client Host getCapabilities on node14?What  is the state for vdsmd service when running systemctl status vdsmd? One other thing to rule out is the networking/firewall. Here the list of the ports to be open for the host (the documentation is for hosted engine, but it applies for standalone setup as well):  https://www.ovirt.org/documentation/installing_ovirt_as_a_self-hosted_engine_using_the_command_line/index.html#host-firewall-requirements_SHE_cli_deploybtw. I have been hunting for the rare and hard to recreate bug for quite a long time (without success yet) so any reported connectivity issues between the manager and hosts are super interesting to me. ArturOn Mon, Aug 9, 2021 at 11:44 AM Andrei Verovski <andreil1@***.lv> wrote:Hi, Artur,Thanks for assistance. Zipped engine starting from the day of upgrade attached.Restart via SSH from oVirt Web GUI works.oVirt engine runs on dedicated server, not hosted engine.On 9 Aug 2021, at 11:24, Artur Socha <aso...@redhat.com> wrote:Hi Andrei,Could you also post a relevant piece of engine.log? I don't have high expectations to find the answer there but  I just want  to be sure of it.VDSM.log does not show any trace of error from the vdsm point of view. For example it looks like it started correctly and subscribed to receiving commands from the engine (yet that does not mean I connected to it - only in listening mode). Can you confirm that 'SSH restart' from UI works - by 'works' I mean the host is actually restarted after a few minutes and there are no ssh related (public key etc) errors in engine.log?ArturOn Mon, Aug 9, 2021 at 9:55 AM Andrei Verovski <andreil1@***.lv> wrote:Hi,

I have oVirt 4.4.7.6-1.el8 and one problematic node (HP ProLiant with CentOS 8 stream).
After replacing server rack router switch and restart got this error I can’t recover from:

VDSM node14 command Get Host Capabilities failed: Messag

[ovirt-users] Re: Q: Get Host Capabilities Failed after restart

[Andrei Verovski]

Hi, Artur,I partially fixed problem with VDSM start.Bug "Failed to create session: Start job for unit user-0.slice failed with ‘canceled’”is being described herehttps://bugzilla.redhat.com/show_bug.cgi?id=1967962and fix seem to be available here, so I have downgraded systemd with backport fix:http://people.redhat.com/dtardon/systemd/bz1642460-backport-UserStopDelaySec=/Now vdsmd service starts successfully, but node14 still cannot be activated because of same error. This is quite strange, before restart on Friday node just worked. There were no upgrades, nothing, just restart.[root@node14]# firewall-cmd --list-allpublic (active)  target: default  icmp-block-inversion: no  interfaces: DMZ_node14 eno1 eno2 ovirtmgmt  sources:   services: cockpit dhcpv6-client libvirt-tls mountd nfs ovirt-imageio ovirt-vmconsole rpc-bind snmp ssh vdsm  ports: 2301/tcp 2381/tcp 22/tcp 6081/udp  protocols:   forward: no  masquerade: no  forward-ports:   source-ports:   icmp-blocks:   rich rules: [root@node14 andrei]# vdsm-client Host getStats and vdsm-client Host getCapabilities attached.

capabilities.log
Description: Binary data


stats.log
Description: Binary data
On 9 Aug 2021, at 13:18, Artur Socha  wrote:Thanks for the logs.  I am checking them at the moment. I have noticed so far that node14 is serving NFS share which had been marked as problematic (probably because of the downtime during the migration) but it has recovered. In the meantime, is is possible to get some meaningful results when  calling:$ vdsm-client Host getStatsand $ vdsm-client Host getCapabilities on node14?What  is the state for vdsmd service when running systemctl status vdsmd? One other thing to rule out is the networking/firewall. Here the list of the ports to be open for the host (the documentation is for hosted engine, but it applies for standalone setup as well):  https://www.ovirt.org/documentation/installing_ovirt_as_a_self-hosted_engine_using_the_command_line/index.html#host-firewall-requirements_SHE_cli_deploybtw. I have been hunting for the rare and hard to recreate bug for quite a long time (without success yet) so any reported connectivity issues between the manager and hosts are super interesting to me. ArturOn Mon, Aug 9, 2021 at 11:44 AM Andrei Verovski <andre...@starlett.lv> wrote:Hi, Artur,Thanks for assistance. Zipped engine starting from the day of upgrade attached.Restart via SSH from oVirt Web GUI works.oVirt engine runs on dedicated server, not hosted engine.On 9 Aug 2021, at 11:24, Artur Socha <aso...@redhat.com> wrote:Hi Andrei,Could you also post a relevant piece of engine.log? I don't have high expectations to find the answer there but  I just want  to be sure of it.VDSM.log does not show any trace of error from the vdsm point of view. For example it looks like it started correctly and subscribed to receiving commands from the engine (yet that does not mean I connected to it - only in listening mode). Can you confirm that 'SSH restart' from UI works - by 'works' I mean the host is actually restarted after a few minutes and there are no ssh related (public key etc) errors in engine.log?ArturOn Mon, Aug 9, 2021 at 9:55 AM Andrei Verovski <andre...@starlett.lv> wrote:Hi,

I have oVirt 4.4.7.6-1.el8 and one problematic node (HP ProLiant with CentOS 8 stream).
After replacing server rack router switch and restart got this error I can’t recover from:

VDSM node14 command Get Host Capabilities failed: Message timeout which can be caused by communication issues

vdsm-network running fine, but vdsmd can’t start on node14 for whatever reason. All other nodes running fine.

Aug 09 10:24:12 node14.mydomain.lv vdsmd_init_common.sh[4825]: vdsm: Running dummybr
Aug 09 10:24:13 node14.mydomain.lv vdsmd_init_common.sh[4825]: vdsm: Running tune_system
Aug 09 10:24:13 node14.mydomain.lv vdsmd_init_common.sh[4825]: vdsm: Running test_space
Aug 09 10:24:13 node14.mydomain.lv vdsmd_init_common.sh[4825]: vdsm: Running test_lo
Aug 09 10:24:13 node14.mydomain.lv systemd[1]: Started Virtual Desktop Server Manager.
Aug 09 10:24:16 node14.mydomain.lv sudo[7721]: pam_systemd(sudo:session): Failed to create session: Start job for unit user-0.slice failed with 'canceled'
Aug 09 10:24:16 node14.mydomain.lv sudo[7721]: pam_unix(sudo:session): session opened for user root by (uid=0)
Aug 09 10:24:16 node14.mydomain.lv sudo[7721]: pam_unix(sudo:session): session closed for user root
Aug 09 10:24:17 node14.mydomain.lv vdsm[6754]: WARN MOM not available. Error: [Errno 2] No such file or directory
Aug 09 10:24:17 node14.mydomain.lv vdsm[6754]: WARN MOM not available, KSM stats will be missing. Error:


In web gui -> Management I can’t do anything with the host except restart. Stop aborts with error, all other commands are gray-ed out.
Status is “Unassigned”. Host is answering to pings as usual.
vdsm.log (from node14) attached.

Thanks in advance for any help.


___
Users mailing list -- user

[ovirt-users] Re: Q: #2 Get Host Capabilities Failed after restart

[Andrei Verovski]

Hi, Artur,Thanks for assistance. Zipped engine starting from the day of upgrade attached.oVirt engine runs on dedicated server, not hosted engine. Restart via SSH from oVirt Web GUI works.I cut log to Aug 09 only.  On Friday Aug 6 we replaced switch in server rack, and therefore, there are a lot of non-relevant error messages.vdsm service fail to start.Aug 09 10:24:12 node14.mydomain.lv vdsmd_init_common.sh[4825]: vdsm: Running dummybrAug 09 10:24:13 node14.mydomain.lv vdsmd_init_common.sh[4825]: vdsm: Running tune_systemAug 09 10:24:13 node14.mydomain.lv vdsmd_init_common.sh[4825]: vdsm: Running test_spaceAug 09 10:24:13 node14.mydomain.lv vdsmd_init_common.sh[4825]: vdsm: Running test_loAug 09 10:24:13 node14.mydomain.lv systemd[1]: Started Virtual Desktop Server Manager.Aug 09 10:24:16 node14.mydomain.lv sudo[7721]: pam_systemd(sudo:session): Failed to create session: Start job for unit user-0.slice failed with 'canceled'Aug 09 10:24:16 node14.mydomain.lv sudo[7721]: pam_unix(sudo:session): session opened for user root by (uid=0)Aug 09 10:24:16 node14.mydomain.lv sudo[7721]: pam_unix(sudo:session): session closed for user rootAug 09 10:24:17 node14.mydomain.lv vdsm[6754]: WARN MOM not available. Error: [Errno 2] No such file or directoryAug 09 10:24:17 node14.mydomain.lv vdsm[6754]: WARN MOM not available, KSM stats will be missing. Error:<>
On 9 Aug 2021, at 11:24, Artur Socha <aso...@redhat.com> wrote:Hi Andrei,Could you also post a relevant piece of engine.log? I don't have high expectations to find the answer there but  I just want  to be sure of it.VDSM.log does not show any trace of error from the vdsm point of view. For example it looks like it started correctly and subscribed to receiving commands from the engine (yet that does not mean I connected to it - only in listening mode). Can you confirm that 'SSH restart' from UI works - by 'works' I mean the host is actually restarted after a few minutes and there are no ssh related (public key etc) errors in engine.log?ArturOn Mon, Aug 9, 2021 at 9:55 AM Andrei Verovski <andre...@starlett.lv> wrote:Hi,

I have oVirt 4.4.7.6-1.el8 and one problematic node (HP ProLiant with CentOS 8 stream).
After replacing server rack router switch and restart got this error I can’t recover from:

VDSM node14 command Get Host Capabilities failed: Message timeout which can be caused by communication issues

vdsm-network running fine, but vdsmd can’t start on node14 for whatever reason. All other nodes running fine.

Aug 09 10:24:12 node14.mydomain.lv vdsmd_init_common.sh[4825]: vdsm: Running dummybr
Aug 09 10:24:13 node14.mydomain.lv vdsmd_init_common.sh[4825]: vdsm: Running tune_system
Aug 09 10:24:13 node14.mydomain.lv vdsmd_init_common.sh[4825]: vdsm: Running test_space
Aug 09 10:24:13 node14.mydomain.lv vdsmd_init_common.sh[4825]: vdsm: Running test_lo
Aug 09 10:24:13 node14.mydomain.lv systemd[1]: Started Virtual Desktop Server Manager.
Aug 09 10:24:16 node14.mydomain.lv sudo[7721]: pam_systemd(sudo:session): Failed to create session: Start job for unit user-0.slice failed with 'canceled'
Aug 09 10:24:16 node14.mydomain.lv sudo[7721]: pam_unix(sudo:session): session opened for user root by (uid=0)
Aug 09 10:24:16 node14.mydomain.lv sudo[7721]: pam_unix(sudo:session): session closed for user root
Aug 09 10:24:17 node14.mydomain.lv vdsm[6754]: WARN MOM not available. Error: [Errno 2] No such file or directory
Aug 09 10:24:17 node14.mydomain.lv vdsm[6754]: WARN MOM not available, KSM stats will be missing. Error:


In web gui -> Management I can’t do anything with the host except restart. Stop aborts with error, all other commands are gray-ed out.
Status is “Unassigned”. Host is answering to pings as usual.
vdsm.log (from node14) attached.

Thanks in advance for any help.


___
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/55M65W57Z43ZVPOARDTK7HKHCAMAUGO5/
-- Artur SochaSenior Software Engineer, RHVRed Hat
___
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/EKW3CXXNHWEX4V6UQADAGGNHUQJFMGLG/

[ovirt-users] Q: Strange ping timeouts/network issues when 1 node is down

[Andrei Verovski]

Hi,


I have observed strange ping timeouts/network issues when one of nodes is down, 
for example, for RAM upgrade.
Powering up and connecting node back solves this.
Each node have 2 networks (connected to different Ethernet interfaces), 
ovirtmgmt 192.168.0.xxx and DMZ 192.168.1.x.

Additionally, time consuming operations like VM cloning causes increase of ping 
latency to ALL nodes from local workstations.
VM cloning should load only 1 node but it should not affect the whole ovirt 
mgmt network on all nodes.

How to fix this issue?
Thanks in advance for any help.
Andrei

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

[ovirt-users] Re: Q: Node Upgrade Path

[Andrei Verovski]

> On 9 Jul 2021, at 01:37, matthew.st...@fujitsu.com wrote:
> 
> You need to go in steps.
> 
> https://www.ovirt.org/documentation/upgrade_guide/

My nodes run on natively installed CentOS, not factory oVirt node images, 
because of necessary RAID drivers and custom scripts (for example, in case of 
power failure which is over 5 min they loop through all running VMS and 
shutdown them gracefully, then shutdown node itself, + RAID monitoring script 
which sends notifications on Telegram messenger).


This seem to be my case. Anyone from oVirt team can confirm? Thanks.

https://www.ovirt.org/documentation/upgrade_guide/#Manually_Updating_Hosts_minor_updates


> 
> -Original Message-
> From: Andrei Verovski  
> Sent: Thursday, July 8, 2021 2:52 PM
> To: users@ovirt.org
> Cc: Stier, Matthew 
> Subject: Re: [ovirt-users] Q: Node Upgrade Path
> 
> Hi,
> 
> OK, thanks for the tip.
> I always upgraded nodes via oVirt web interface, which is now 4.4.7, and I 
> assume it can't update node 4.2 -> 4.3, because 4.3 is too old. Please 
> correct if I'm wrong here.
> 
> May I use these commands to safely upgrade nodes manually?
> 
> yum check-update
> yum clean all
> yum update
> yum remove ovirt-release42
> yum install
> https://resources.ovirt.org/pub/ovirt-4.3/rpm/el7/noarch/ovirt-node-ng-image-update-4.3.0-1.el7.noarch.rpm
> 
> On 7/8/21 8:41 PM, matthew.st...@fujitsu.com wrote:
>> If the hardware is old, and won't support EL8, the best option is to update 
>> to oVirt 4.3.10 and update CentOS to 7u9.
>> 
>> Some of my systems have megaraid sas2 raid controllers, which Red Hat have 
>> stopped supporting, and all the variant have followed suit.
>> 
>> I have tried the Elrepo DUD's to work around the problem, but my results (in 
>> the 4.4.1/4.4.2 timeframe) were not satisfactory.
>> 
>> -Original Message-
>> From: Andrei Verovski 
>> Sent: Thursday, July 8, 2021 6:42 AM
>> To: users@ovirt.org
>> Subject: [ovirt-users] Q: Node Upgrade Path
>> 
>> Hi,
>> 
>> 
>> I have 2 oVirt nodes still running on CentOS 7.6.
>> rpm -qa | grep ovirt - results in version 4.2.
>> 
>> Does it makes sense to upgrade CentOS 7.6 to Stream, and then upgrade oVirt 
>> Node sw, or just leave for a couple of years till hardware will be trashed?
>> I’m always keep oVirt Engine up to date, so my only concern if at any point 
>> it will stop support old Node sw.
>> 
>> Thanks in advance for any suggestion.
>> Andrei
>> ___
>> 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/6SCBZF3N
>> ASM5UIABKRANHI6UUHXCWG4Y/
> 
___
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/ZY6PHEMHXRFO676TQOG76ELJ5WMYVYDQ/

[ovirt-users] Re: Q: Node Upgrade Path

[Andrei Verovski]

Hi,

OK, thanks for the tip.
I always upgraded nodes via oVirt web interface, which is now 4.4.7, and 
I assume it can't update node 4.2 -> 4.3, because 4.3 is too old. Please 
correct if I'm wrong here.


May I use these commands to safely upgrade nodes manually?

yum check-update
yum clean all
yum update
yum remove ovirt-release42
yum install 
https://resources.ovirt.org/pub/ovirt-4.3/rpm/el7/noarch/ovirt-node-ng-image-update-4.3.0-1.el7.noarch.rpm


On 7/8/21 8:41 PM, matthew.st...@fujitsu.com wrote:

If the hardware is old, and won't support EL8, the best option is to update to 
oVirt 4.3.10 and update CentOS to 7u9.

Some of my systems have megaraid sas2 raid controllers, which Red Hat have 
stopped supporting, and all the variant have followed suit.

I have tried the Elrepo DUD's to work around the problem, but my results (in 
the 4.4.1/4.4.2 timeframe) were not satisfactory.

-Original Message-
From: Andrei Verovski 
Sent: Thursday, July 8, 2021 6:42 AM
To: users@ovirt.org
Subject: [ovirt-users] Q: Node Upgrade Path

Hi,


I have 2 oVirt nodes still running on CentOS 7.6.
rpm -qa | grep ovirt - results in version 4.2.

Does it makes sense to upgrade CentOS 7.6 to Stream, and then upgrade oVirt 
Node sw, or just leave for a couple of years till hardware will be trashed?
I’m always keep oVirt Engine up to date, so my only concern if at any point it 
will stop support old Node sw.

Thanks in advance for any suggestion.
Andrei
___
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/6SCBZF3NASM5UIABKRANHI6UUHXCWG4Y/

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

[ovirt-users] Q: Node Upgrade Path

[Andrei Verovski]

Hi, 


I have 2 oVirt nodes still running on CentOS 7.6.
rpm -qa | grep ovirt - results in version 4.2.

Does it makes sense to upgrade CentOS 7.6 to Stream, and then upgrade oVirt 
Node sw, or just leave for a couple of years till hardware will be trashed?
I’m always keep oVirt Engine up to date, so my only concern if at any point it 
will stop support old Node sw.

Thanks in advance for any suggestion.
Andrei
___
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/6SCBZF3NASM5UIABKRANHI6UUHXCWG4Y/

[ovirt-users] Q: Node host becomes non-operational after upgrade

[Andrei Verovski]

Hi,


Today I upgraded oVirt Engine to 4.4.7.6, and then one of the nodes 
(running Centos Stream).

After upgrade node (node14) becomes non-operational. Same after “Reinstall”.

Additionally, there are MANY error messages:
Host node14 moved to Non-Operational state as host CPU type is not 
supported in this cluster compatibility version or is not supported at all

Quite strange, before upgrade problem with CPU host type didn't exist.
vdsm-networking service is running fine on node14.
vdsmd running but have this error message:
Jul 06 21:19:23 node14.xxx sudo[3565]: pam_systemd(sudo:session): Failed 
to create session: Start job for unit user-0.slice failed with 'canceled'


I suspect that there are unnecessary repos enabled in my CentOS stream 
node, which leads to this kind of errors.

Please can anyone check? Thanks in advance.



[root@node14 ~]# yum repolist enabled

repo id repo name
appstream CentOS Stream 8 - AppStream
baseos CentOS Stream 8 - BaseOS
epel-next Extra Packages for Enterprise Linux 8 - Next - x86_64
extras CentOS Stream 8 - Extras
ovirt-4.4 Latest oVirt 4.4 Release
ovirt-4.4-centos-ceph-pacific Ceph packages for x86_64
ovirt-4.4-centos-gluster8 CentOS-8 - Gluster 8
ovirt-4.4-centos-opstools CentOS-8 - OpsTools - collectd
ovirt-4.4-centos-stream-advanced-virtualization Advanced Virtualization 
CentOS Stream packages for x86_64

ovirt-4.4-centos-stream-nfv-openvswitch CentOS-8 - NFV OpenvSwitch
ovirt-4.4-centos-stream-ovirt44 CentOS-8 Stream - oVirt 4.4
ovirt-4.4-copr:copr.fedorainfracloud.org:mdbarroso:ovsdbapp Copr repo 
for ovsdbapp owned by mdbarroso
ovirt-4.4-copr:copr.fedorainfracloud.org:sac:gluster-ansible Copr repo 
for gluster-ansible owned by sac
ovirt-4.4-copr:copr.fedorainfracloud.org:sbonazzo:EL8_collection Copr 
repo for EL8_collection owned by sbonazzo

ovirt-4.4-epel Extra Packages for Enterprise Linux 8 - x86_64
ovirt-4.4-openstack-train OpenStack Train Repository
ovirt-4.4-virtio-win-latest virtio-win builds roughly matching what will 
be shipped in upcoming RHEL

powertools CentOS Stream 8 - PowerTools



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

[ovirt-users] /var/log has less then 500MB free space left on

[Andrei Verovski]

Hi, 

I started to get messages that /var/log has less then 500MB free space left on 
out of 8GB.
du -h —max-depthh=1
reveals that openswitch log dir consumes 3.6GB, there are files as old as 2018.
Node software was installed on fresh CentOS 7.xx from oVirt admin web console.

I cleaned this directory, yet question remain - why logrotate service is not 
running by default on oVirt node? 
Or this is not recommended?

Thanks in advance.
Andrei


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

[ovirt-users] Re: Q: Sparsify/fstrim don't reduce actual disk image size

[Andrei Verovski]

Hi,

Many thanks, its worked ! Actual size shrunk from 584 to 9 GB, now I have space 
to backup.

Is there any guidelines how to format QCOW2 images (for Linux) so they can be 
shrunk in an efficient way?
With this NextCloud/Collabora LVM I did in the following order:
swap
ext2 boot
ext4 root
ext4 var (large, for data, all cloud data stored here)

Ext4 partitions on LVM.

Or this is not predictable how data will span QCOW2 space?


> On 7 Apr 2021, at 18:43, Nir Soffer  wrote:
> 
> On Wed, Apr 7, 2021 at 5:36 PM Andrei Verovski  wrote:
>> 
>> Hi !
>> 
>> I have VM (under oVirt) with single disk thin provision (~600 GB)
> 
> I guess you are using block storage?
> 
>> running NextCloud on Debian 9.
>> Right now VM HD is almost empty. Unfortunately, it occupies 584 GB (virtual 
>> size = 600 GB)
>> All partition (except swap and boot) are EXT4 with discard option.
> 
> You don't need to use discard mount option. fstrim works without it.
> 
>> in oVirt “enable discard = on”.
>> 
>> # fstrim -av runs successfully:
>> /var: 477.6 GiB (512851144704 bytes) trimmed on 
>> /dev/mapper/vg--system-lv4--data
>> /boot: 853.8 MiB (895229952 bytes) trimmed on 
>> /dev/mapper/vg--system-lv2--boot
>> /: 88.4 GiB (94888611840 bytes) trimmed on /dev/mapper/vg--system-lv3—sys
>> 
>> When fstrim runs again, it trims zero. I even run “Sparsify” in oVirt. 
>> Unfortunately, actual size is still 584 GB.
>> 
>> Here is /etc/fstab
>> /dev/mapper/vg--system-lv3--sys /   ext4
>> discard,noatime,nodiratime,errors=remount-ro 0   1
>> /dev/mapper/vg--system-lv2--boot /boot   ext2defaults0   
>> 2
>> /dev/mapper/vg--system-lv4--data /varext4
>> discard,noatime,nodiratime 0   2
>> /dev/mapper/vg--system-lv1--swap noneswapsw  0   
>> 0
>> 
>> When disk was partitioned/formatted, swap and boot were created first and 
>> positioned at the beginning.
>> 
>> What is wrong here? Is it possible to fix all this ?
> 
> Discarding data mark the areas in the qcow2 image as zero, but it does not 
> move
> actual data around (which is very slow). So if the clusters were at
> the end of the
> image they remain there, and the actual file size is the same.
> 
> The only way to reclaim the space is:
> 1. sparsify disk - must be done *before* copying the disk.
> 2. move this to another storage domain
> 3. move disk back to the original storage domain
> 
> We may have an easier and more efficient way in the future that
> works with single storage domain, but it will have to copy the
> entire disk. If the disk is really mostly empty it should be fast.
> 
> 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/Z4DWCAZLITWXZFUCLLWTSIFIFUUBDPJ7/

[ovirt-users] Q: Sparsify/fstrim don't reduce actual disk image size

[Andrei Verovski]

Hi !

I have VM (under oVirt) with single disk thin provision (~600 GB) running 
NextCloud on Debian 9.
Right now VM HD is almost empty. Unfortunately, it occupies 584 GB (virtual 
size = 600 GB)
All partition (except swap and boot) are EXT4 with discard option. in oVirt 
“enable discard = on”.

# fstrim -av runs successfully:
/var: 477.6 GiB (512851144704 bytes) trimmed on /dev/mapper/vg--system-lv4--data
/boot: 853.8 MiB (895229952 bytes) trimmed on /dev/mapper/vg--system-lv2--boot
/: 88.4 GiB (94888611840 bytes) trimmed on /dev/mapper/vg--system-lv3—sys

When fstrim runs again, it trims zero. I even run “Sparsify” in oVirt. 
Unfortunately, actual size is still 584 GB.

Here is /etc/fstab
/dev/mapper/vg--system-lv3--sys /   ext4
discard,noatime,nodiratime,errors=remount-ro 0   1
/dev/mapper/vg--system-lv2--boot /boot   ext2defaults0  
 2
/dev/mapper/vg--system-lv4--data /varext4
discard,noatime,nodiratime 0   2
/dev/mapper/vg--system-lv1--swap noneswapsw  0  
 0

When disk was partitioned/formatted, swap and boot were created first and 
positioned at the beginning.

What is wrong here? Is it possible to fix all this ?

Thanks in advance.
Andrei
___
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/7KY6WAM7SES3EMQYMGMCADZJJZG74TO7/

[ovirt-users] Re: oVirt longevity after CentOS 8, RHV changes

[Andrei Verovski]

Hi,

Does all this mean oVirt will be sometime and somehow merged with 
OpenShift (or OKD)?
Its not that easy since OKD designed primarily for Kubernetes/Docker 
containers.


Or oVirt may be considered just another abandonware within 2+ years?


On 4/3/21 4:49 PM, David White via Users wrote:

I first received news about the RHEV and OpenShift convergence from my Red Hat 
TAM at one of my jobs.

However, a quick search on Google produces this:
https://access.redhat.com/support/policy/updates/rhev, which says, in part:

Moving forward the RHV management feature set will be converged with OpenShift 
and OpenShift Virtualization providing customers with requirements for 
containers and VMs a migration path and a common platform for deploying and 
managing both.




Sent with ProtonMail Secure Email.

‐‐‐ Original Message ‐‐‐
On Saturday, April 3, 2021 4:52 AM, Timo Veith  
wrote:


Dear David,

do you have a link to that anouncement which you have referenced below "so the 
announcement of RHV's (commercial) demise was poor timing for me“

Cheers
Timo


Am 02.04.2021 um 17:10 schrieb David White via Users users@ovirt.org:
I'm replying to Thomas's thread below, but am creating a new subject so as not 
to hijack the original thread.
I'm sure that this topic has come up before.
I first joined this list last fall, when I began planning and testing with 
oVirt, but as of the past few weeks, I'm paying closer attention to the mailing 
list now that I'm actually using oVirt and am getting ready to deploy to a 
production environment.
I'll also try to jump in and help other people as time permits and as my 
experience grow.
I echo Thomas's concerns here. While I'm thankful for Red Hat's gesture to 
allow people to use up to 16 Red Hat installs at no charge, I'm concerned about 
the longevity of oVirt, now that Red Hat is no longer going to support RHV 
going forward.
What is the benefit to Red Hat / IBM of supporting this platform now that it is 
no longer being commercialized as a Red Hat product? What is to prevent Red Hat 
from pulling the plug on this project, similar to what happened to CentOS 8?
As a user of oVirt (4.5, installed on Red Hat 8.3), how can I and others help 
to contribute to the project to ensure its longevity? Or should I really just 
go find an alternative in the future? (I had been planning to use oVirt for a 
while, and did some testing last fall, so the announcement of RHV's 
(commercial) demise was poor timing for me, because I don't have time to switch 
gears and change my plans to use something else, like Proxmox or something.
 From what I've seen, this is a great product, and I guess I can understand Red 
Hat's decision to pull the plug on the commercial project, now that OpenShift 
supports full VMs. But my understanding is that OpenShift is a lot more 
complicated and requires more resources. I really don't need a full kubernetes 
environment. I just need a stable virtualization platform.
Sent with ProtonMail Secure Email.
‐‐‐ Original Message ‐‐‐
On Thursday, April 1, 2021 5:44 PM, Thomas Hoberg tho...@hoberg.net wrote:


I personally consider the fact that you gave up on 4.3/CentOS7 before CentOS 8 could have 
even been remotely reliable to run "a free open-source virtualization solution for 
your entire enterprise", a rather violent break of trust.
I understand Redhat's motivation with Python 2/3 etc., but users just don't. 
Please just try for a minute to view this from a user's perspective.
With CentOS 7 supported until 2024, we naturally expect the added value on top 
via oVirt to persist just as long.
And with CentOS 8 support lasting until the end of this year, oVirt 4.4 can't be 
considered "Petrus" or a rock to build on.
Most of us run oVirt simply because we are most interested in the VMs it runs 
(tenants paying rent).
We're not interested in keeping oVirt itself stable and from failing after any 
update to the house of cards.
And yes, by now I am sorry to have chosen oVirt at all, finding that 4.3 was 
abandonend before 4.4 or the CentOS 8 below was even stable and long before the 
base OS ran out of support.
To the users out there oVirt is a platform, a tool, not a means to itself.

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

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/UXUMNX46AGN5D3VXROSL6XX3FEGSHQF3/

[ovirt-users] Re: Q: Set host CPU type to kvm64 for a single VM

[Andrei Verovski]

Hi,

OK, thanks, found this option.

But host CPU type “KVM64” is not available here, only Conroe, Penryn, Nehalem, 
Westmere.

Where I can add CPU type “KVM64” in this list?


> On 29 Mar 2021, at 11:00, Ritesh Chikatwar  wrote:
> 
> Hello,
> 
> Yes , There is an option but I have not tried. 
> Log in to the portal and edit the vm properties.
> Steps:
> 
> Select VM -> Edit -> Click System Tab -> then click Advanced Parameter -> 
> Custom CPU Type
> 
> 
> 
> On Mon, Mar 29, 2021 at 12:37 PM Andrei Verovski  <mailto:andre...@starlett.lv>> wrote:
> Hi !
> 
> 
> Is it possible to set host CPU type to kvm64 for a single VM ?
> 
> 
> Thanks.
> Andrei
> 
> ___
> Users mailing list -- users@ovirt.org <mailto:users@ovirt.org>
> To unsubscribe send an email to users-le...@ovirt.org 
> <mailto:users-le...@ovirt.org>
> Privacy Statement: https://www.ovirt.org/privacy-policy.html 
> <https://www.ovirt.org/privacy-policy.html>
> oVirt Code of Conduct: 
> https://www.ovirt.org/community/about/community-guidelines/ 
> <https://www.ovirt.org/community/about/community-guidelines/>
> List Archives: 
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/MFTVL6WIALN6QL6D6MZMUIGLF3D2R2L6/
>  
> <https://lists.ovirt.org/archives/list/users@ovirt.org/message/MFTVL6WIALN6QL6D6MZMUIGLF3D2R2L6/>

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

[ovirt-users] Q: Set host CPU type to kvm64 for a single VM

[Andrei Verovski]

Hi !


Is it possible to set host CPU type to kvm64 for a single VM ?


Thanks.
Andrei

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

[ovirt-users] Set host CPU type to kvm64 for a single VM

[Andrei Verovski]

Hi !


Is it possible to set host CPU type to kvm64 for a single VM ?


Thanks.
Andrei

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

[ovirt-users] Re: Setup Hosts Network Disabled

[Andrei Verovski]

Hi,

I’ve got around this. 
Simply created new logical network, buggy should NOT be deleted, simply rename 
it to temp/dummy/unused or whatever.


> On 10 Mar 2021, at 08:41, Ales Musil  wrote:
> 
> 
> 
> On Tue, Mar 9, 2021 at 4:25 PM Andrei Verovski  <mailto:andre...@starlett.lv>> wrote:
> Hi !
> 
> Hi,
>  
> 
> I run into a problem which looks like a software bug.
> 
> there was no change in this part for a long time but it might be possible 
> that there is some hidden bug. 
>  
> 
> Network -> Networks -> My_Net_Name -> Hosts
> Setup Hosts Network button is disabled (greyed out). I deleted this network, 
> created again, restarted hosted engine - no changes.
> 
> The button here does not work if you have selected multiple hosts at once. 
> 
> 
> Is it  possible to fix this for example from command line ?
> 
> Actually no, there is nothing that you could do from command line, but you 
> can still access the dialog by going into:
> Compute -> Hosts -> $YOUR_HOST -> Network Interfaces -> Setup Host Networks.
> 
> Also there is possibility to do it through REST API.
> 
> Hopefully it helps.
> 
> Best regards,
> Ales
>  
> 
> Thanks in advance.
> ___
> Users mailing list -- users@ovirt.org <mailto:users@ovirt.org>
> To unsubscribe send an email to users-le...@ovirt.org 
> <mailto:users-le...@ovirt.org>
> Privacy Statement: https://www.ovirt.org/privacy-policy.html 
> <https://www.ovirt.org/privacy-policy.html>
> oVirt Code of Conduct: 
> https://www.ovirt.org/community/about/community-guidelines/ 
> <https://www.ovirt.org/community/about/community-guidelines/>
> List Archives: 
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/GN5GSC7JKH5FQCBQAYFSHF5CECZWXTMZ/
>  
> <https://lists.ovirt.org/archives/list/users@ovirt.org/message/GN5GSC7JKH5FQCBQAYFSHF5CECZWXTMZ/>
> 
> 
> -- 
> Ales Musil
> Software Engineer - RHV Network
> Red Hat EMEA <https://www.redhat.com/>
> amu...@redhat.com <mailto:amu...@redhat.com>IM: amusil
>   <https://red.ht/sig>
___
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/I5XK6BOJQJUIBFR2LUCBWCYVX77ACFJQ/

[ovirt-users] Setup Hosts Network Disabled

[Andrei Verovski]

Hi !

I run into a problem which looks like a software bug.

Network -> Networks -> My_Net_Name -> Hosts
Setup Hosts Network button is disabled (greyed out). I deleted this network, 
created again, restarted hosted engine - no changes.

Is it  possible to fix this for example from command line ?

Thanks in advance.
___
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/GN5GSC7JKH5FQCBQAYFSHF5CECZWXTMZ/

[ovirt-users] Re: Strange Glitches with VM and Network (oVirt 4.4.4.7-1.el8)

[Andrei Verovski]

> 
> 
> I’m running oVirt 4.4.4.7-1.el8 and need to connect one of the VMs straight 
> to the ISP link via Ethernet cable.
> oVirt already have 2 networks (ovirt mgmt local + DMZ).
> Created new network provider and assigned to it available physical interface 
> of HP ProLiant, connected via cable to ISP switch with public IP.
> 
> By provider do you mean ovirt-provider-ovn? If so are you using OVS cluster 
> type? The physical interface connection for external networks work only 
> in an OVS switch type cluster. 


If you mean Native Open vSwitch as described here we don’t use it.
https://www.ovirt.org/develop/release-management/features/network/openvswitch/native-openvswitch.html

Current setup is simple 2-node and unfortunately I'm not aware of all deep 
details of oVirt networking.
Since oVirt uses KVM as underlying technology I assume it uses bridged 
networking to connect VMs and physical interfaces.
Each our server uses 2 Ethernet connections, 1 for internal LAN 192.168.0.xxx 
and 2nd for DMZ 192.168.1.xxx.
If so I assumed that it could not be a problem to bridge VM to external IP via 
3rd Ethernet using oVirt networking.
May be its enough to turn on “isolated port” and VM Interface Profile to 
“clean-traffic”?

Please correct if I'm wrong here



>  
> Options of this network: (VM Network = on, Port Isolation = off, NIC Type = 
> VirtIO, the rest are defaults).
> VM is Debian 10.
> 
> Link works but with strange artefacts. If VM left being idle for a while, it 
> cant be connected or pinged from outside, until I initiate pings from VM 
> itself.
> I have only 2 IPs from this ISP so I’m sure there are no IP address conflicts.
> Another port and public IP go to our VyOS router handling internal and DMZ 
> zone.
> 
> When this happens I would suggest to trace where the packets are getting 
> dropped.
>  
> 
> How to fix this problem ?
> Thanks in advance.
> Andrei
> 
> ___
> 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/5SAC77DSZQ4PXCCNT6N6MEG7MYDOHFQU/
>  
> 
> 
> 
> Thank you.
> Best regards,
> Ales
> 
> -- 
> Ales Musil
> Software Engineer - RHV Network
> Red Hat EMEA 
> amu...@redhat.com IM: amusil
>   
___
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/M7LCDYIBUU3GFAY5PSHOCZCQGWT6KTC4/

[ovirt-users] Re: HCI upgrade path from single to three-nodes setup

[Andrei Verovski]

> On 9 Mar 2021, at 13:37, s.bue...@messaufficio.com wrote:
> 
> Hello
> I'm planning an HCI configuration on a single server.
> In my wishlist there's also the opportunity in the future to upgrade the 
> cluster from single to fully fledged three node setup.
> Is there any supported and tested migration path available ?
> Thanks in advance

If you mean migration from oVirt local storage setup to full featured network 
storage domain you can check my video guide:

https://www.youtube.com/watch?v=2ebhZ5U6x_Y


> Best regards
> ___
> 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/2FGE5HKXVB42GYOCE4Y3N7JTOO4ORPRG/
___
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/WT7LEU23YD47HBX27YXQF7ENC4HO4HJE/

[ovirt-users] Strange Glitches with VM and Network (oVirt 4.4.4.7-1.el8)

[Andrei Verovski]

Hi,


I’m running oVirt 4.4.4.7-1.el8 and need to connect one of the VMs straight to 
the ISP link via Ethernet cable.
oVirt already have 2 networks (ovirt mgmt local + DMZ).
Created new network provider and assigned to it available physical interface of 
HP ProLiant, connected via cable to ISP switch with public IP.
Options of this network: (VM Network = on, Port Isolation = off, NIC Type = 
VirtIO, the rest are defaults).
VM is Debian 10.

Link works but with strange artefacts. If VM left being idle for a while, it 
cant be connected or pinged from outside, until I initiate pings from VM itself.
I have only 2 IPs from this ISP so I’m sure there are no IP address conflicts.
Another port and public IP go to our VyOS router handling internal and DMZ zone.

How to fix this problem ?
Thanks in advance.
Andrei

___
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/5SAC77DSZQ4PXCCNT6N6MEG7MYDOHFQU/

[ovirt-users] Re: Q: [SOLVED] Node SW Install from oVirt Engine UI Failed

[Andrei Verovski]

Hi,

I solved this issue.

dnf config-manager —set-disabled spp

For whatever reason HP hardware drivers repo conflicted with oVirt node install.


> On 15 Jan 2021, at 17:30, Andrei Verovski  wrote:
> 
> Hi,
> 
> After installing fresh CentOS stream (on HP ProLiant Node) with recommended 
> partitioning scheme I did in oVirt Engine Web UI Hosts -> New (add node ended 
> with success), the Hosts -> Installation -> Install, and this failed. 
> 
> 
>> On 15 Jan 2021, at 17:11, penguin pages  wrote:
>> 
>> What is in /var/log/messages
>> 
>> 
>> What steps did you take to deploy post CentOS 8 Streams deployment?  Did you 
>> launch from Cockpit UI?
>> 
>> The GUI deployment process does output reasonable logs
>> ___
>> 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/RPYUG7T5724BOHTUEKVAEBKP2WYJNA5R/
> ___
> 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/W57F2T2UYOFCET2YOM2UH4LS2WDBGFC4/
___
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/3YR24F6ZVL5T4UQ34VAA2NSXW2LPRAIX/

[ovirt-users] Re: Q: Node SW Install from oVirt Engine UI Failed

[Andrei Verovski]

Hi,

After installing fresh CentOS stream (on HP ProLiant Node) with recommended 
partitioning scheme I did in oVirt Engine Web UI Hosts -> New (add node ended 
with success), the Hosts -> Installation -> Install, and this failed. 


> On 15 Jan 2021, at 17:11, penguin pages  wrote:
> 
> What is in /var/log/messages
> 
> 
> What steps did you take to deploy post CentOS 8 Streams deployment?  Did you 
> launch from Cockpit UI?
> 
> The GUI deployment process does output reasonable logs
> ___
> 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/RPYUG7T5724BOHTUEKVAEBKP2WYJNA5R/
___
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/W57F2T2UYOFCET2YOM2UH4LS2WDBGFC4/

[ovirt-users] Q: Node SW Install from oVirt Engine UI Failed

[Andrei Verovski]

Hi,

I installed fresh CentOS Stream on HP ProLiant and now trying to install Node 
SW from oVirt Engine WEB UI.
Software installation failed but no comprehensive description displayed in WEB 
UI.
Where I can find detailed logs what’s going wrong?

On node "sudo dnf repolist —all” lists required repos, with unnecessary 
disabled.

Thanks in advance.
Andrei.


repo id  repo name  
  status
appstreamCentOS Stream 
8 - AppStream  enabled
baseos   CentOS Stream 
8 - BaseOS enabled
debuginfoCentOS Stream 
8 - Debuginfo  disabled
extras   CentOS Stream 
8 - Extras enabled
ha   CentOS Stream 
8 - HighAvailability   disabled
media-appstream  CentOS Stream 
8 - Media - AppStream  disabled
media-baseos CentOS Stream 
8 - Media - BaseOS disabled
ovirt-4.4Latest oVirt 
4.4 Release enabled
ovirt-4.4-advanced-virtualization-testingAdvanced 
Virtualization testing pack enabled
ovirt-4.4-centos-nfv-openvswitch CentOS-8 - NFV 
OpenvSwitch   enabled
ovirt-4.4-centos-opstoolsCentOS-8 - 
OpsTools - collectd   enabled
ovirt-4.4-centos-ovirt44-testing CentOS-8 - 
oVirt 4.4 - testing   enabled
ovirt-4.4-copr:copr.fedorainfracloud.org:mdbarroso:ovsdbapp  Copr repo for 
ovsdbapp owned by mdba enabled
ovirt-4.4-copr:copr.fedorainfracloud.org:sac:gluster-ansible Copr repo for 
gluster-ansible owned  enabled
ovirt-4.4-copr:copr.fedorainfracloud.org:sbonazzo:EL8_collection Copr repo for 
EL8_collection owned b enabled
ovirt-4.4-epel   Extra Packages 
for Enterprise Linux  enabled
ovirt-4.4-glusterfs-7-testingGlusterFS 7 
testing packages for x86 enabled
ovirt-4.4-ioprocess-preview  Copr repo for 
iprocess-preview owned enabled
ovirt-4.4-ovirt-imageio-preview  Copr repo for 
ovirt-imageio-preview  enabled
ovirt-4.4-virtio-win-latest  virtio-win 
builds roughly matching w enabled
powertools   CentOS Stream 
8 - PowerTools enabled
rt   CentOS Stream 
8 - RealTime   disabled
spp  Service Pack 
for ProLiantenabled
___
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/XRCXCVC4RPVG6S2FCI72UMZUKJOWJQUG/

[ovirt-users] Q: oVirt 4.4.4.7 Node settings on CentOS Stream

[Andrei Verovski]

Hi !

I’m installing new oVirt 4.4.4 node on CentOS Stream and its seems there are 
some changes since older node on CentOS 7.x.

1) NFS shares for storage domain.
In 7.x I used
chown -Rv nfsnobody:nfsnobody /vmraid/nfs; chmod -Rv 755 /vmraid/nfs
In Stream nfsnobody don’t exists, should I use:
chown -Rv nobody:nobody /vmraid/nfs; chmod -Rv 777 /vmraid/nfs

Is that correct settings?


2) SELinux seems to be more permissive now, looks like I don’t have to tweak it 
to have my custom cron and SNMP scripts running.
Yes, SELinux is running, getenforce -> yields “Enforcing”.

Will oVirt sw node installation change this behaviour?


Thanks in advance
Andrei
___
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/RIHO3XXDJ625VUHTNQVNBNEQDAIEWZVD/