- Users - oVirt List Archives

Unable start self hosted engine after accidental shut down
by Eugène Ngontang 19 May '21

19 May '21

Hi, Our self hosted engine has been accidentally shut down by a teammate and now I'm trying hard to get it back up without success. I've tried the --vm-start command but it says the VM is in WaitForLaunch status. I've set the global maintenance mode but it does nothing. root@milhouse-main ~]# hosted-engine --vm-start VM exists and is down, cleaning up and restarting VM in WaitForLaunch [root@milhouse-main ~]# hosted-engine --set-maintenance --mode=global [root@milhouse-main ~]# hosted-engine --vm-status !! Cluster is in GLOBAL MAINTENANCE mode !! --== Host milhouse-main.envrmnt.local (id: 1) status ==-- conf_on_shared_storage : True Status up-to-date : False Hostname : milhouse-main.envrmnt.local Host ID : 1 Engine status : unknown stale-data Score : 3400 stopped : False Local maintenance : False crc32 : 931b2db9 local_conf_timestamp : 1642052 Host timestamp : 1642052 Extra metadata (valid at timestamp): metadata_parse_version=1 metadata_feature_version=1 timestamp=1642052 (Tue May 18 19:52:59 2021) host-id=1 score=3400 vm_conf_refresh_time=1642052 (Tue May 18 19:53:00 2021) conf_on_shared_storage=True maintenance=False state=EngineDown stopped=False !! Cluster is in GLOBAL MAINTENANCE mode !! You have new mail in /var/spool/mail/root [root@milhouse-main ~]# hosted-engine --vm-start VM exists and is down, cleaning up and restarting VM in WaitForLaunch [root@milhouse-main ~]# And when I list all vms, I can see the hosted engine is in the Shut Off status and the managed vms are all paused [root@milhouse-main ~]# virsh -r list --all setlocale: No such file or directory Id Name State ---------------------------------------------------- 2 hp_gpu-node11 paused 3 fp_gpu-node5 paused 4 hp_gpu-node10 paused 5 hp_gpu-node7 paused 6 cpu-node3 paused 7 hp_gpu-node5 paused 8 fp_gpu-node1 paused 9 fp_gpu-node0 paused 10 cpu-node1 paused 11 fp_gpu-node6 paused 12 hp_gpu-node8 paused 13 fp_gpu-node10 paused 14 fp_gpu-node4 paused 15 fp_gpu-node9 paused 16 hp_gpu-node4 paused 17 fp_gpu-node15 paused 18 fp_gpu-node8 paused 19 hp_gpu-node0 paused 20 fp_gpu-node14 paused 21 fp_gpu-node2 paused 22 fp_gpu-node11 paused 23 hp_gpu-node9 paused 24 cpu-node2 paused 25 hp_gpu-node1 paused 26 hp_gpu-node2 paused 27 fp_gpu-node12 paused 28 hp_gpu-node3 paused 29 hp_gpu-node6 paused 30 infra-vm paused 31 cpu-node0 paused 32 fp_gpu-node3 paused 33 fp_gpu-node7 paused 34 fp_gpu-node13 paused 35 bigip-16.1x-milhouse paused - HostedEngine shut off [root@milhouse-main ~]# I don't want to reboot the host server, cause I could loose all my VMs. Can someone help here please? Thanks. Regards, Eugène NG -- LesCDN <http://lescdn.com> engontang(a)lescdn.com ------------------------------------------------------------ *Aux hommes il faut un chef, et au* * chef il faut des hommes!L'habit ne fait pas le moine, mais lorsqu'on te voit on te juge!*

4 4

Error Deployment New Hosted Engine on 4.4.1 node
by Dominique D 19 May '21

19 May '21

I have a setup with 3 servers production environment with version 4.4.1 that works very well (gluster and hosted-engine) I prepared a lab with the same setup (with the same ISO) to test a update to (4.4.6) The deployment of the Hyperconverge works but when I want to do hosted-engine --deploy or in the cokpit, at some time the host displays this message and reboot and the engine is not installed. I tried with the latest ISO 4.4.6 (Fresh Install) and I have the same message. Is there a network change with version 8.3 of CentOS? [ 33.785588] bondscan-yhEyFK: option fail_over_mac: invalid value (3) [ 33.787183] bondscan-yhEyFK: option arp_all_targets: invalid value (2) [ 33.804832] bondscan-yhEyFK: option arp_validate: invalid value (7) [ 33.807568] bondscan-yhEyFK: option xmit_hash_policy: invalid value (6) [ 33.807884] bondscan-yhEyFK: option lacp_rate: mode dependency failed, not supported in mode broadcast(3) [ 33.809858] bondscan-yhEyFK: option ad_select: invalid value (3) [ 33.811003] bondscan-yhEyFK: option primary_reselect: invalid value (3) [ 33.813490] bondscan-yhEyFK: option fail_over_mac: invalid value (3) [ 33.815175] bondscan-yhEyFK: option arp_all_targets: invalid value (2) [ 33.839036] bondscan-yhEyFK: option arp_validate: mode dependency failed, not supported in mode 802.3ad(4) [ 33.841905] bondscan-yhEyFK: option xmit_hash_policy: invalid value (6) [ 33.842628] bondscan-yhEyFK: option lacp_rate: invalid value (2) [ 33.844573] bondscan-yhEyFK: option ad_select: invalid value (3) [ 33.846293] bondscan-yhEyFK: option primary_reselect: invalid value (3) [ 33.847492] bondscan-yhEyFK: option fail_over_mac: invalid value (3) [ 33.848978] bondscan-yhEyFK: option arp_all_targets: invalid value (2) [ 33.871465] bondscan-yhEyFK: option arp_validate: mode dependency failed, not supported in mode balance-tlb(5) [ 33.874149] bondscan-yhEyFK: option xmit_hash_policy: invalid value (6) [ 33.874475] bondscan-yhEyFK: option lacp_rate: mode dependency failed, not supported in mode balance-tlb(5) [ 33.876514] bondscan-yhEyFK: option ad_select: invalid value (3) [ 33.877381] bondscan-yhEyFK: option primary_reselect: invalid value (3) [ 33.878554] bondscan-yhEyFK: option fail_over_mac: invalid value (3) [ 33.879991] bondscan-yhEyFK: option arp_all_targets: invalid value (2) [ 33.909461] bondscan-yhEyFK: option arp_validate: mode dependency failed, not supported in mode balance-alb(6) [ 33.914593] bondscan-yhEyFK: option xmit_hash_policy: invalid value (6) [ 33.916657] bondscan-yhEyFK: option lacp_rate: mode dependency failed, not supported in mode balance-alb(6) [ 33.920665] bondscan-yhEyFK: option ad_select: invalid value (3) [ 33.927749] bondscan-yhEyFK: option primary_reselect: invalid value (3) [ 33.932404] bondscan-yhEyFK: option fail_over_mac: invalid value (3) [ 33.935589] bondscan-yhEyFK: option arp_all_targets: invalid value(2)

3 5

Gluster volumes not healing (perhaps after host maintenance?)
by David White 18 May '21

18 May '21

I discovered that the servers I purchased did not come with 10Gbps network cards, like I thought they did. So my storage network has been running on a 1Gbps connection for the past week, since I deployed the servers into the datacenter a little over a week ago. I purchased 10Gbps cards, and put one of my hosts into maintenance mode yesterday, prior to replacing the daughter card. It is now back online running fine on the 10Gbps card. All VMs seem to be working, even when I migrate them onto cha2, which is the host I did maintenance on yesterday morning. The other two hosts are still running on the 1Gbps connection, but I plan to do maintenance on them next week. The oVirt manager shows that all 3 hosts are up, and that all of my volumes - and all of my bricks - are up. However, every time I look at the storage, it appears that the self-heal info for 1 of the volumes is 10 minutes, and the self-heal info for another volume is 50+ minutes. This morning is the first time in the last couple of days that I've paid close attention to the numbers, but I don't see them going down. When I log into each of the hosts, I do see everything is connected in gluster. It is interesting to me, in this particular case, though that gluster on cha3 notices the hostname of 10.1.0.10 to be the IP address, and not the hostname (cha1). The host that I did the maintenance on is cha2. [root@cha3-storage dwhite]# gluster peer statusNumber of Peers: 2Hostname: 10.1.0.10Uuid: 87a4f344-321a-48b9-adfb-e3d2b56b8e7bState: Peer in Cluster (Connected)Hostname: cha2-storage.mgt.barredowlweb.comUuid: 93e12dee-c37d-43aa-a9e9-f4740b9cab14State: Peer in Cluster (Connected) When I run `gluster volume heal data`, I see the following: [root@cha3-storage dwhite]# gluster volume heal data Launching heal operation to perform index self heal on volume data has been unsuccessful: Commit failed on cha2-storage.mgt.barredowlweb.com. Please check log file for details. I get the same results if I run the command on cha2, for any volume: [root@cha2-storage dwhite]# gluster volume heal data Launching heal operation to perform index self heal on volume data has been unsuccessful: Glusterd Syncop Mgmt brick op 'Heal' failed. Please check glustershd log file for details. [root@cha2-storage dwhite]# gluster volume heal vmstore Launching heal operation to perform index self heal on volume vmstore has been unsuccessful: Glusterd Syncop Mgmt brick op 'Heal' failed. Please check glustershd log file for details. I see a lot of stuff like this on cha2 /var/log/glusterfs/glustershd.log: [2021-04-24 11:33:01.319888] I [rpc-clnt.c:1975:rpc_clnt_reconfig] 2-engine-client-0: changing port to 49153 (from 0)[2021-04-24 11:33:01.329463] I [MSGID: 114057] [client-handshake.c:1128:select_server_supported_programs] 2-engine-client-0: Using Program [{Program-name=GlusterFS 4.x v1}, {Num=1298437}, {Version=400}][2021-04-24 11:33:01.330075] W [MSGID: 114043] [client-handshake.c:727:client_setvolume_cbk] 2-engine-client-0: failed to set the volume [{errno=2}, {error=No such file or directory}][2021-04-24 11:33:01.330116] W [MSGID: 114007] [client-handshake.c:752:client_setvolume_cbk] 2-engine-client-0: failed to get from reply dict [{process-uuid}, {errno=22}, {error=Invalid argument}][2021-04-24 11:33:01.330140] E [MSGID: 114044] [client-handshake.c:757:client_setvolume_cbk] 2-engine-client-0: SETVOLUME on remote-host failed [{remote-error=Brick not found}, {errno=2}, {error=No such file or directory}][2021-04-24 11:33:01.330155] I [MSGID: 114051] [client-handshake.c:879:client_setvolume_cbk] 2-engine-client-0: sending CHILD_CONNECTING event [][2021-04-24 11:33:01.640480] I [rpc-clnt.c:1975:rpc_clnt_reconfig] 3-vmstore-client-0: changing port to 49154 (from 0)The message "W [MSGID: 114007] [client-handshake.c:752:client_setvolume_cbk] 3-vmstore-client-0: failed to get from reply dict [{process-uuid}, {errno=22}, {error=Invalid argument}]" repeated 4 times between [2021-04-24 11:32:49.602164] and [2021-04-24 11:33:01.649850][2021-04-24 11:33:01.649867] E [MSGID: 114044] [client-handshake.c:757:client_setvolume_cbk] 3-vmstore-client-0: SETVOLUME on remote-host failed [{remote-error=Brick not found}, {errno=2}, {error=No such file or directory}][2021-04-24 11:33:01.649969] I [MSGID: 114051] [client-handshake.c:879:client_setvolume_cbk] 3-vmstore-client-0: sending CHILD_CONNECTING event [][2021-04-24 11:33:01.650095] I [MSGID: 114018] [client.c:2225:client_rpc_notify] 3-vmstore-client-0: disconnected from client, process will keep trying to connect glusterd until brick's port is available [{conn-name=vmstore-client-0}] How do I further troubleshoot? Sent with ProtonMail Secure Email.

3 5

Re: Gluster Geo-Replication Fails
by Strahil Nikolov 18 May '21

18 May '21

Now to make it perfect , leave it running and analyze the AVCs with semanage. In the end SELINUX will remain working and geo-rep should be running also. I've previously tried the rpm generated from https://github.com/gluster/glusterfs-selinux but it didn't help at that time. If possible, give it a try. Best Regards,Strahil Nikolov On Tue, May 18, 2021 at 16:09, Simon Scott<simon(a)justconnect.ie> wrote: _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)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/GB23MBKEQKZNK…

1 0

Re: oVirt deploy new HE Host problem
by Yedidyah Bar David 18 May '21

18 May '21

On Mon, May 17, 2021 at 10:34 AM Marko Vrgotic <M.Vrgotic(a)activevideo.com> wrote: > > Hi gentleman, > > > > Hope you had a great weekend. > > Can I assume that you will be able to look into log files this week ? > > > > As per Yedidyah’s comment, I stopped troubleshooting . > > > > Kindly awaiting your reply. Hi Marko, Please upload somewhere all of /var/log from all hosts and the engine, and share a link. Thanks. In particular, you didn't include 'hosted-engine --deploy' logs from /var/log/ovirt-hosted-engine-setup. Also: the attached ovirt-host-deploy log indicates this is on 4.3, which is EOL and unsupported. Best regards, -- Didi

2 1

Gluster Geo-Replication Fails
by simon＠justconnect.ie 18 May '21

18 May '21

Hi All, I have to sites each with 2 x 3 Node clusters. oVirt 4.4.5 with GlusterFS 8.4. On Site A I have a Replica 3 + Arbiter volume that I want to geo-replicate to Site B. I've setup a Replica 3 + Arbiter volume on Site B. All password-less ssh requirements are in place and the Geo-Replication Session has been created successfully. I issue the 'Start' command successfully but the status switches between 'Initializing', 'Active' & 'Failed' within 20 seconds constantly. Can anyone point me in the direction to get this up and running as it is our proposed DR solution. Kind Regards Shimme

3 3

poweroff and reboot with ovirt_vm ansible module
by Nathanaël Blanchet 18 May '21

18 May '21

Hello, is there a way to poweroff or reboot (without stopped and running state) a vm with the ovirt_vm ansible module? -- Nathanaël Blanchet Supervision réseau Pôle Infrastrutures Informatiques 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 Tél. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 blanchet(a)abes.fr

7 11

[ANN] Async release for oVirt 4.4.6
by Lev Veyde 18 May '21

18 May '21

oVirt 4.4.6 Async update #3 On May 18th 2021 the oVirt project released an async update to the following packages: - Vdsm 4.40.60.7 - oVirt Node 4.4.6.3 Fixing the following bugs: - Bug 1959945 <https://bugzilla.redhat.com/show_bug.cgi?id=1959945> - [NBDE] RHVH 4.4.6 host fails to startup, without prompting for passphrase - Bug 1955571 <https://bugzilla.redhat.com/show_bug.cgi?id=1955571> - Verify if we still need to omit ifcfg and clevis dracut modules for properly working bridged network - Bug 1950209 <https://bugzilla.redhat.com/show_bug.cgi?id=1950209> - Leaf images used by the VM is deleted by the engine during snapshot merge oVirt Node Changes: - Consume above oVirt updates - Updated to Gluster 8.5 <https://docs.gluster.org/en/latest/release-notes/8.5/> Full diff list: --- ovirt-node-ng-image-4.4.6.2.manifest-rpm 2021-05-14 08:58:12.581488678 +0200 +++ ovirt-node-ng-image-4.4.6.3.manifest-rpm 2021-05-18 13:09:07.858527812 +0200 @@ -220,7 +220,7 @@ -glusterfs-8.4-1.el8.x86_64 -glusterfs-cli-8.4-1.el8.x86_64 -glusterfs-client-xlators-8.4-1.el8.x86_64 -glusterfs-events-8.4-1.el8.x86_64 -glusterfs-fuse-8.4-1.el8.x86_64 -glusterfs-geo-replication-8.4-1.el8.x86_64 -glusterfs-server-8.4-1.el8.x86_64 +glusterfs-8.5-1.el8.x86_64 +glusterfs-cli-8.5-1.el8.x86_64 +glusterfs-client-xlators-8.5-1.el8.x86_64 +glusterfs-events-8.5-1.el8.x86_64 +glusterfs-fuse-8.5-1.el8.x86_64 +glusterfs-geo-replication-8.5-1.el8.x86_64 +glusterfs-server-8.5-1.el8.x86_64 @@ -383,6 +383,6 @@ -libgfapi0-8.4-1.el8.x86_64 -libgfchangelog0-8.4-1.el8.x86_64 -libgfrpc0-8.4-1.el8.x86_64 -libgfxdr0-8.4-1.el8.x86_64 -libglusterd0-8.4-1.el8.x86_64 -libglusterfs0-8.4-1.el8.x86_64 +libgfapi0-8.5-1.el8.x86_64 +libgfchangelog0-8.5-1.el8.x86_64 +libgfrpc0-8.5-1.el8.x86_64 +libgfxdr0-8.5-1.el8.x86_64 +libglusterd0-8.5-1.el8.x86_64 +libglusterfs0-8.5-1.el8.x86_64 @@ -643 +643 @@ -ovirt-node-ng-image-update-placeholder-4.4.6.2-1.el8.noarch +ovirt-node-ng-image-update-placeholder-4.4.6.3-1.el8.noarch @@ -651,2 +651,2 @@ -ovirt-release-host-node-4.4.6.2-1.el8.noarch -ovirt-release44-4.4.6.2-1.el8.noarch +ovirt-release-host-node-4.4.6.3-1.el8.noarch +ovirt-release44-4.4.6.3-1.el8.noarch @@ -754 +754 @@ -python3-gluster-8.4-1.el8.x86_64 +python3-gluster-8.5-1.el8.x86_64 @@ -940,15 +940,15 @@ -vdsm-4.40.60.6-1.el8.x86_64 -vdsm-api-4.40.60.6-1.el8.noarch -vdsm-client-4.40.60.6-1.el8.noarch -vdsm-common-4.40.60.6-1.el8.noarch -vdsm-gluster-4.40.60.6-1.el8.x86_64 -vdsm-hook-ethtool-options-4.40.60.6-1.el8.noarch -vdsm-hook-fcoe-4.40.60.6-1.el8.noarch -vdsm-hook-openstacknet-4.40.60.6-1.el8.noarch -vdsm-hook-vhostmd-4.40.60.6-1.el8.noarch -vdsm-hook-vmfex-dev-4.40.60.6-1.el8.noarch -vdsm-http-4.40.60.6-1.el8.noarch -vdsm-jsonrpc-4.40.60.6-1.el8.noarch -vdsm-network-4.40.60.6-1.el8.x86_64 -vdsm-python-4.40.60.6-1.el8.noarch -vdsm-yajsonrpc-4.40.60.6-1.el8.noarch +vdsm-4.40.60.7-1.el8.x86_64 +vdsm-api-4.40.60.7-1.el8.noarch +vdsm-client-4.40.60.7-1.el8.noarch +vdsm-common-4.40.60.7-1.el8.noarch +vdsm-gluster-4.40.60.7-1.el8.x86_64 +vdsm-hook-ethtool-options-4.40.60.7-1.el8.noarch +vdsm-hook-fcoe-4.40.60.7-1.el8.noarch +vdsm-hook-openstacknet-4.40.60.7-1.el8.noarch +vdsm-hook-vhostmd-4.40.60.7-1.el8.noarch +vdsm-hook-vmfex-dev-4.40.60.7-1.el8.noarch +vdsm-http-4.40.60.7-1.el8.noarch +vdsm-jsonrpc-4.40.60.7-1.el8.noarch +vdsm-network-4.40.60.7-1.el8.x86_64 +vdsm-python-4.40.60.7-1.el8.noarch +vdsm-yajsonrpc-4.40.60.7-1.el8.noarch -- Lev Veyde Senior Software Engineer, RHCE | RHCVA | MCITP Red Hat Israel <https://www.redhat.com> lev(a)redhat.com | lveyde(a)redhat.com <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

1 0

Ovirt Engine -- Connection Refused to all hosts
by Nick Polites 18 May '21

18 May '21

Hi All, I am not sure if my original post is being reviewed before posting but trying again in case it failed to send. I tried logging in this morning to oVrit and see that all of my hosts are unresponsive. I am seeing a connection refused error in the engine logs. I am able to SSH and ping the host from the engine. Any help would be appreciated. 2021-05-15 15:19:21,041Z ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesAsyncVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-65) [] Command 'GetCapabilitiesAsyn cVDSCommand(HostName = hlkvm03, VdsIdAndVdsVDSCommandParametersBase:{hostId='2186eca7-4d9d-482f-b1b7-b63ac46b96aa', vds='Host[hlkvm03,2186eca7-4d9d-482f-b1b7 -b63ac46b96aa]'})' execution failed: java.net.ConnectException: Connection refused ~

3 2

Migrating VMs with templates from 4.2.8 to new 4.4.6 instance
by Pavel Strzinek 17 May '21

17 May '21

Hello, I am having hard time migrating vms based on templates from existing 4.2.8 instance to newly installed 4.4.6 HCI with different storage. When I export VMs and corresponding templates to export NFS storage, detach it from source DC and attach the export storage to a new oVirt environment, the import of templates is failing with error "Failed to import Template XXX to Data Center YYY, Cluster ZZZ". I cannot find anything more specific about the error in logs. Am I missing something? Exporting to OVA and importing back does work, but I want to make use of template thin provisioning.

2 3

oVirt 2021 Spring survey
by Sandro Bonazzola 17 May '21

17 May '21

As we continue to develop oVirt 4.4, the Development and Integration teams at Red Hat would value insights on how you are deploying the oVirt environment. Please help us to hit the mark by completing this short survey. Survey will close on *May 30th 2021*. If you're managing multiple oVirt deployments with very different use cases or very different deployments you can consider answering this survey multiple times. *Please note the answers to this survey will be publicly accessible*. This survey is under oVirt Privacy Policy available at https://ovirt.org/privacy-policy.html . The survey form is available at https://docs.google.com/forms/d/e/1FAIpQLScdJGoBYxuW-4IsIvZGVpbiEWhmt4O-oAA… -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

1 1

Re: oVirt deploy new HE Host problem
by Strahil Nikolov 17 May '21

17 May '21

Yes, I did - but I couldn't take a look into them. Best Regards,Strahil Nikolov On Mon, May 10, 2021 at 13:54, Marko Vrgotic<M.Vrgotic(a)activevideo.com> wrote: _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)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/KJCGYLJK4ILZ5…

2 1

Create Brick from Engine host view
by Harry O 16 May '21

16 May '21

When I try to create a single disk brick via host view "storage devices" on engine, I get the following error. Error while executing action Create Brick: Internal Engine Error Failed to create brick lalaf on host hej1.5ervers.lan of cluster Clu1. I want the brick to be single disk no raid, no cache. Is there a way to create it via CLI? Do I need to pull some logs?

2 1

Power management on Dell PowerEdge R320 and R520
by Pavel Strzinek 14 May '21

14 May '21

Hello, I am having trouble configuring fencing on these two servers with iDrac7 module from freshly installed oVirt 4.4.6. I tried drac5, drac7 and ipmilan modules and neither passes the test. I used ipmilan with option "lanplus=1", as noted in previous threads about idrac usage with oVirt/RHEV, but with no success. Also, I am successfully using ipmilan fencing from older oVirt 4.2 on several SuperMicro server nodes. This is the error message in engine.log: 2021-05-14 09:28:41,185+02 ERROR [org.ovirt.engine.core.bll.pm.FenceProxyLocator] (default task-6) [12faf352-da4a-4b24-9ab9-af54559cecd1] Can not run fence action on host 'onode1', no suitable proxy host was found. I can successfully query the idrac module with ipmitool from command line on the node, using the same credentials.

3 4

[ANN] Async release for oVirt 4.4.6
by Sandro Bonazzola 14 May '21

14 May '21

On May 14th 2021 the oVirt project released an async update to the following packages: - ovirt-hosted-engine-ha-2.4.7 - ovirt-release44-4.4.6.2 - ovirt-engine-4.4.6.8 - oVirt Node 4.4.6.2 Fixing the following bugs: - Bug 1909888 <https://bugzilla.redhat.com/show_bug.cgi?id=1909888> - [RFE] Support multiple IQN in hosted-engine.conf for Active-Active DR setup - Bug 1957253 <https://bugzilla.redhat.com/show_bug.cgi?id=1957253> - [cinderlib] Enable using Managed Block Storage on 4.6 cluster by default - Bug 1958869 <https://bugzilla.redhat.com/show_bug.cgi?id=1958869> - Import VM from export domain fails - the imported VM remains in 'image locked' state oVirt Node Changes: - Consume above oVirt updates - Updated hivex (CVE-2021-3504 <https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3504>) Full diff list: *--- ovirt-node-ng-image-4.4.6.1.manifest-rpm* *2021-05-11 08:39:44.714649170 +0200**+++ ovirt-node-ng-image-4.4.6.2.manifest-rpm* *2021-05-14 08:58:12.581488678 +0200*@@ -253 +253 @@-hivex-1.3.18-20.module_el8.5.0+746+bbd5d70c.x86_64+hivex-1.3.18-21.el8s.x86_64@@ -638 +638 @@-ovirt-hosted-engine-ha-2.4.6-1.el8.noarch+ovirt-hosted-engine-ha-2.4.7-1.el8.noarch@@ -643 +643 @@-ovirt-node-ng-image-update-placeholder-4.4.6.1-1.el8.noarch+ovirt-node-ng-image-update-placeholder-4.4.6.2-1.el8.noarch@@ -651,2 +651,2 @@-ovirt-release-host-node-4.4.6.1-1.el8.noarch-ovirt-release44-4.4.6.1-1.el8.noarch+ovirt-release-host-node-4.4.6.2-1.el8.noarch+ovirt-release44-4.4.6.2-1.el8.noarch -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

1 0

[OLVM] Host non responsive after installation
by alan＠softdrive.co 12 May '21

12 May '21

I am using Oracle Linux Virtualization Manager, following this guide: https://docs.oracle.com/en/virtualization/oracle-linux-virtualization-manag… After adding a host to the engine, the host becomes non responsive due to network errors: engine.log 2021-04-27 14:53:02,255Z ERROR [org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand] (EE-ManagedThreadFactory-engine-Thread-32356) [38586e0e] Host installation failed for host 'c97604b3-5774-4260-92fd-633257aa7498', 'GPU2-2': Network error during communication with the host Help resolving this would be much appreciated!

4 9

Moving interfaces for switch maintenance
by David White 12 May '21

12 May '21

So I have two switches. All 3 of my HCI oVirt servers are connected to both switches. 1 switch serves the ovirtmgmt network (internal, gluster communication and everything else on that subnet) The other switch serves the "main" front-end network (Private). It turns out that my datacenter plugged the switches into the wrong power supplies, and now needs to move them. My switches have single PSUs, so when we move them, the network will go down. Obviously, I'm just going to move 1 switch at a time. What I'm wondering, though, is there's an "easy" way to force all the traffic for both networks out one of the single interfaces, so that I don't experience any more downtime during this switch maintenance. Should I assign another temporary IP address on each of the interfaces for each server that is in the same subnet as the switch we're going to take down? Sent with ProtonMail Secure Email.

1 0

Issue upgrading from 4.3 (Centos 7) to 4.4 (Centos 8)
by ling＠aliko.com 12 May '21

12 May '21

Hello, I have been trying to upgrade my self-hosted engine from 4.3 to 4.4 but running into issue while performing hosted-engine deploy. Old hypervisor hosts are all running Centos 8 and old ovirt-engine is also running Centos 7. I created a brand new baremental node running Centos 8, Kernel 4.18.0-240.15.1.el8_3.x86_64 and the following engine versions: ovirt-hosted-engine-setup-2.4.9-1.el8.noarch ovirt-hosted-engine-ha-2.4.6-1.el8.noarch ovirt-engine-appliance-4.4-20210323171213.1.el8.x86_64 python3-ovirt-engine-sdk4-4.4.10-1.el8.x86_64 I have many VLANs in my environment. But on this host, I only have these network devices set up (eth0 is the main network, eth1 for storage): # nmcli con NAME UUID TYPE DEVICE ovirtmgmt 02f64861-d992-4e56-8cec-da1906bac09f bridge ovirtmgmt System eth1 bd9e565f-bdc3-4e43-bbd3-5875b9d7fed7 ethernet eth1 virbr0 78e6875d-70f6-4c89-89dd-180dbb9250b1 bridge virbr0 eth0 743b0e26-aae7-44b8-9215-3754a537e90b ethernet eth0 vnet0 bcfead6d-c5b6-4428-9f89-41589735be02 tun vnet0 When I run hosted-engine --deploy --restore-from-file=backup_050321.bck, it hangs after showing: [ INFO ] TASK [ovirt.ovirt.engine_setup : Copy yum configuration file] [ INFO ] changed: [localhost -> ovirt.safari.apple.com] [ INFO ] TASK [ovirt.ovirt.engine_setup : Set 'best' to false] [ INFO ] changed: [localhost -> ovirt.safari.apple.com] [ INFO ] TASK [ovirt.ovirt.engine_setup : Update all packages] virsh shows the VM is in paused state: # virsh list Id Name State ---------------------------------- 1 HostedEngineLocal paused I was able to ssh onto the VM until that point. Do I need to set up all the network connection for all the VLANs before running the deploy script? And how about engine storage domain? I have a new NFS mount ready but it did not ask me about which storage domain to use. Will it ask in later stage? Thanks.

4 12

Something broke & took down multiple VMs for ~20 minutes
by David White 12 May '21

12 May '21

As the subject suggestions, something in oVirt HCI broke. I have no idea what, and it recovered on its own after about 20 minutes or so. I believe that the issue was limited to a single host (although I don't know that for sure), as we had two VMs go completely unresponsive, but a 3rd VM remained operational. For a while during the outage, I was able to log into the oVirt admin web portal, and I noticed at least 1-2 of my hosts (I have 3 hosts) showed the problematic VMs as being problematic inside of oVirt. Reviewing the oVirt Events, I see that this basically started right when the ETL Service Started. There were no events before that point since yesterday, but right when the ETL Service started, it seems like all hell broke loose. oVirt detected "No faulty multipaths" on any of the hosts, but then very quickly started indicating that hosts, vms, and storage targets were unavailable. See my screenshot below. Around 30 - 35 minutes later, it appears that the Hosted Engine terminated due to a storage issue, and auto recovered on a different host. There's a 2nd screenshot beneath the first. Everything came back up shortly before 9am, and has been stable since. In fact, the Volume replication issues that I saw in my environment after I performed maintenance on 1 of my hosts on Friday are no longer present. It appears that the Hosted Engine sees the storage as being perfectly healthy. How do I even begin to figure out what happened, and try to prevent it from happening again? [Screenshot from 2021-04-26 16-36-47.png] [Screenshot from 2021-04-26 16-44-08.png] Sent with ProtonMail Secure Email.

2 7

pool list vm assign user
by Dominique D 11 May '21

11 May '21

Is there a way to know how to see who the vm of a pool assigned to? I am able on the portal to see those who are "logged-in user" but the others VM I don't know to whom they are assigned.

2 3

[ANN] Async oVirt Node release for oVirt 4.4.6
by Sandro Bonazzola 11 May '21

11 May '21

On May 10th 2021 the oVirt project released an async update of oVirt Node (4.4.6.1) Changes: - Updated Advanced Virtualization packages - Updated ovn2.11 and openvswitch2.11 - Updated ansible 2.9.21 ( https://github.com/ansible/ansible/blob/stable-2.9/changelogs/CHANGELOG-v2.… ) - Update libssh (fixes CVE-2020-16135) Full diff list: --- ovirt-node-ng-image-4.4.6.manifest-rpm 2021-05-04 17:02:01.839123874 +0200 +++ ovirt-node-ng-image-4.4.6.1.manifest-rpm 2021-05-11 08:39:44.714649170 +0200 @@ -24 +24 @@ -ansible-2.9.20-2.el8.noarch +ansible-2.9.21-2.el8.noarch @@ -89 +89 @@ -corosynclib-3.1.0-4.el8.0.1.x86_64 +corosynclib-3.1.0-5.el8.x86_64 @@ -100 +100 @@ -cups-libs-2.2.6-38.el8.x86_64 +cups-libs-2.2.6-39.el8.x86_64 @@ -130,5 +130,5 @@ -dracut-049-135.git20210121.el8.x86_64 -dracut-config-generic-049-135.git20210121.el8.x86_64 -dracut-live-049-135.git20210121.el8.x86_64 -dracut-network-049-135.git20210121.el8.x86_64 -dracut-squash-049-135.git20210121.el8.x86_64 +dracut-049-136.git20210426.el8.x86_64 +dracut-config-generic-049-136.git20210426.el8.x86_64 +dracut-live-049-136.git20210426.el8.x86_64 +dracut-network-049-136.git20210426.el8.x86_64 +dracut-squash-049-136.git20210426.el8.x86_64 @@ -148,36 +148,36 @@ -fence-agents-all-4.2.1-67.el8.x86_64 -fence-agents-amt-ws-4.2.1-67.el8.noarch -fence-agents-apc-4.2.1-67.el8.noarch -fence-agents-apc-snmp-4.2.1-67.el8.noarch -fence-agents-bladecenter-4.2.1-67.el8.noarch -fence-agents-brocade-4.2.1-67.el8.noarch -fence-agents-cisco-mds-4.2.1-67.el8.noarch -fence-agents-cisco-ucs-4.2.1-67.el8.noarch -fence-agents-common-4.2.1-67.el8.noarch -fence-agents-compute-4.2.1-67.el8.noarch -fence-agents-drac5-4.2.1-67.el8.noarch -fence-agents-eaton-snmp-4.2.1-67.el8.noarch -fence-agents-emerson-4.2.1-67.el8.noarch -fence-agents-eps-4.2.1-67.el8.noarch -fence-agents-heuristics-ping-4.2.1-67.el8.noarch -fence-agents-hpblade-4.2.1-67.el8.noarch -fence-agents-ibmblade-4.2.1-67.el8.noarch -fence-agents-ifmib-4.2.1-67.el8.noarch -fence-agents-ilo-moonshot-4.2.1-67.el8.noarch -fence-agents-ilo-mp-4.2.1-67.el8.noarch -fence-agents-ilo-ssh-4.2.1-67.el8.noarch -fence-agents-ilo2-4.2.1-67.el8.noarch -fence-agents-intelmodular-4.2.1-67.el8.noarch -fence-agents-ipdu-4.2.1-67.el8.noarch -fence-agents-ipmilan-4.2.1-67.el8.noarch -fence-agents-kdump-4.2.1-67.el8.x86_64 -fence-agents-mpath-4.2.1-67.el8.noarch -fence-agents-redfish-4.2.1-67.el8.x86_64 -fence-agents-rhevm-4.2.1-67.el8.noarch -fence-agents-rsa-4.2.1-67.el8.noarch -fence-agents-rsb-4.2.1-67.el8.noarch -fence-agents-sbd-4.2.1-67.el8.noarch -fence-agents-scsi-4.2.1-67.el8.noarch -fence-agents-vmware-rest-4.2.1-67.el8.noarch -fence-agents-vmware-soap-4.2.1-67.el8.noarch -fence-agents-wti-4.2.1-67.el8.noarch +fence-agents-all-4.2.1-68.el8.x86_64 +fence-agents-amt-ws-4.2.1-68.el8.noarch +fence-agents-apc-4.2.1-68.el8.noarch +fence-agents-apc-snmp-4.2.1-68.el8.noarch +fence-agents-bladecenter-4.2.1-68.el8.noarch +fence-agents-brocade-4.2.1-68.el8.noarch +fence-agents-cisco-mds-4.2.1-68.el8.noarch +fence-agents-cisco-ucs-4.2.1-68.el8.noarch +fence-agents-common-4.2.1-68.el8.noarch +fence-agents-compute-4.2.1-68.el8.noarch +fence-agents-drac5-4.2.1-68.el8.noarch +fence-agents-eaton-snmp-4.2.1-68.el8.noarch +fence-agents-emerson-4.2.1-68.el8.noarch +fence-agents-eps-4.2.1-68.el8.noarch +fence-agents-heuristics-ping-4.2.1-68.el8.noarch +fence-agents-hpblade-4.2.1-68.el8.noarch +fence-agents-ibmblade-4.2.1-68.el8.noarch +fence-agents-ifmib-4.2.1-68.el8.noarch +fence-agents-ilo-moonshot-4.2.1-68.el8.noarch +fence-agents-ilo-mp-4.2.1-68.el8.noarch +fence-agents-ilo-ssh-4.2.1-68.el8.noarch +fence-agents-ilo2-4.2.1-68.el8.noarch +fence-agents-intelmodular-4.2.1-68.el8.noarch +fence-agents-ipdu-4.2.1-68.el8.noarch +fence-agents-ipmilan-4.2.1-68.el8.noarch +fence-agents-kdump-4.2.1-68.el8.x86_64 +fence-agents-mpath-4.2.1-68.el8.noarch +fence-agents-redfish-4.2.1-68.el8.x86_64 +fence-agents-rhevm-4.2.1-68.el8.noarch +fence-agents-rsa-4.2.1-68.el8.noarch +fence-agents-rsb-4.2.1-68.el8.noarch +fence-agents-sbd-4.2.1-68.el8.noarch +fence-agents-scsi-4.2.1-68.el8.noarch +fence-agents-vmware-rest-4.2.1-68.el8.noarch +fence-agents-vmware-soap-4.2.1-68.el8.noarch +fence-agents-wti-4.2.1-68.el8.noarch @@ -187 +187 @@ -filesystem-3.8-4.el8.x86_64 +filesystem-3.8-3.el8.x86_64 @@ -193 +193 @@ -freetype-2.9.1-5.el8.x86_64 +freetype-2.9.1-4.el8_3.1.x86_64 @@ -199 +199 @@ -fwupd-1.5.5-3.el8.x86_64 +fwupd-1.5.9-1.el8.x86_64 @@ -210 +210 @@ -glib2-2.56.4-10.el8.x86_64 +glib2-2.56.4-11.el8.x86_64 @@ -269,2 +269,2 @@ -iproute-5.9.0-4.el8.x86_64 -iproute-tc-5.9.0-4.el8.x86_64 +iproute-5.12.0-0.el8.x86_64 +iproute-tc-5.12.0-0.el8.x86_64 @@ -317,2 +317,2 @@ -krb5-libs-1.18.2-9.el8.x86_64 -krb5-workstation-1.18.2-9.el8.x86_64 +krb5-libs-1.18.2-10.el8.x86_64 +krb5-workstation-1.18.2-10.el8.x86_64 @@ -381 +381 @@ -libgcc-8.4.1-1.el8.x86_64 +libgcc-8.4.1-2.1.el8.x86_64 @@ -393 +393 @@ -libgomp-8.4.1-1.el8.x86_64 +libgomp-8.4.1-2.1.el8.x86_64 @@ -409 +409 @@ -libkadm5-1.18.2-9.el8.x86_64 +libkadm5-1.18.2-10.el8.x86_64 @@ -469,2 +469,2 @@ -libssh-0.9.4-2.el8.x86_64 -libssh-config-0.9.4-2.el8.noarch +libssh-0.9.4-3.el8.x86_64 +libssh-config-0.9.4-3.el8.noarch @@ -476 +476 @@ -libstdc++-8.4.1-1.el8.x86_64 +libstdc++-8.4.1-2.1.el8.x86_64 @@ -498,26 +498,26 @@ -libvirt-7.0.0-9.el8s.x86_64 -libvirt-admin-7.0.0-9.el8s.x86_64 -libvirt-bash-completion-7.0.0-9.el8s.x86_64 -libvirt-client-7.0.0-9.el8s.x86_64 -libvirt-daemon-7.0.0-9.el8s.x86_64 -libvirt-daemon-config-network-7.0.0-9.el8s.x86_64 -libvirt-daemon-config-nwfilter-7.0.0-9.el8s.x86_64 -libvirt-daemon-driver-interface-7.0.0-9.el8s.x86_64 -libvirt-daemon-driver-network-7.0.0-9.el8s.x86_64 -libvirt-daemon-driver-nodedev-7.0.0-9.el8s.x86_64 -libvirt-daemon-driver-nwfilter-7.0.0-9.el8s.x86_64 -libvirt-daemon-driver-qemu-7.0.0-9.el8s.x86_64 -libvirt-daemon-driver-secret-7.0.0-9.el8s.x86_64 -libvirt-daemon-driver-storage-7.0.0-9.el8s.x86_64 -libvirt-daemon-driver-storage-core-7.0.0-9.el8s.x86_64 -libvirt-daemon-driver-storage-disk-7.0.0-9.el8s.x86_64 -libvirt-daemon-driver-storage-gluster-7.0.0-9.el8s.x86_64 -libvirt-daemon-driver-storage-iscsi-7.0.0-9.el8s.x86_64 -libvirt-daemon-driver-storage-iscsi-direct-7.0.0-9.el8s.x86_64 -libvirt-daemon-driver-storage-logical-7.0.0-9.el8s.x86_64 -libvirt-daemon-driver-storage-mpath-7.0.0-9.el8s.x86_64 -libvirt-daemon-driver-storage-rbd-7.0.0-9.el8s.x86_64 -libvirt-daemon-driver-storage-scsi-7.0.0-9.el8s.x86_64 -libvirt-daemon-kvm-7.0.0-9.el8s.x86_64 -libvirt-libs-7.0.0-9.el8s.x86_64 -libvirt-lock-sanlock-7.0.0-9.el8s.x86_64 +libvirt-7.0.0-14.el8s.x86_64 +libvirt-admin-7.0.0-14.el8s.x86_64 +libvirt-bash-completion-7.0.0-14.el8s.x86_64 +libvirt-client-7.0.0-14.el8s.x86_64 +libvirt-daemon-7.0.0-14.el8s.x86_64 +libvirt-daemon-config-network-7.0.0-14.el8s.x86_64 +libvirt-daemon-config-nwfilter-7.0.0-14.el8s.x86_64 +libvirt-daemon-driver-interface-7.0.0-14.el8s.x86_64 +libvirt-daemon-driver-network-7.0.0-14.el8s.x86_64 +libvirt-daemon-driver-nodedev-7.0.0-14.el8s.x86_64 +libvirt-daemon-driver-nwfilter-7.0.0-14.el8s.x86_64 +libvirt-daemon-driver-qemu-7.0.0-14.el8s.x86_64 +libvirt-daemon-driver-secret-7.0.0-14.el8s.x86_64 +libvirt-daemon-driver-storage-7.0.0-14.el8s.x86_64 +libvirt-daemon-driver-storage-core-7.0.0-14.el8s.x86_64 +libvirt-daemon-driver-storage-disk-7.0.0-14.el8s.x86_64 +libvirt-daemon-driver-storage-gluster-7.0.0-14.el8s.x86_64 +libvirt-daemon-driver-storage-iscsi-7.0.0-14.el8s.x86_64 +libvirt-daemon-driver-storage-iscsi-direct-7.0.0-14.el8s.x86_64 +libvirt-daemon-driver-storage-logical-7.0.0-14.el8s.x86_64 +libvirt-daemon-driver-storage-mpath-7.0.0-14.el8s.x86_64 +libvirt-daemon-driver-storage-rbd-7.0.0-14.el8s.x86_64 +libvirt-daemon-driver-storage-scsi-7.0.0-14.el8s.x86_64 +libvirt-daemon-kvm-7.0.0-14.el8s.x86_64 +libvirt-libs-7.0.0-14.el8s.x86_64 +libvirt-lock-sanlock-7.0.0-14.el8s.x86_64 @@ -533 +533,2 @@ -libxcrypt-4.1.1-5.el8.x86_64 +libxcrypt-4.1.1-6.el8.x86_64 +libxkbcommon-0.9.1-1.el8.x86_64 @@ -618,2 +619,2 @@ -openscap-1.3.4-5.el8.x86_64 -openscap-scanner-1.3.4-5.el8.x86_64 +openscap-1.3.5-2.el8.x86_64 +openscap-scanner-1.3.5-2.el8.x86_64 @@ -626 +627 @@ -openvswitch2.11-2.11.0-50.el8.x86_64 +openvswitch2.11-2.11.3-87.el8s.x86_64 @@ -642 +643 @@ -ovirt-node-ng-image-update-placeholder-4.4.6-1.el8.noarch +ovirt-node-ng-image-update-placeholder-4.4.6.1-1.el8.noarch @@ -650,2 +651,2 @@ -ovirt-release-host-node-4.4.6-1.el8.noarch -ovirt-release44-4.4.6-1.el8.noarch +ovirt-release-host-node-4.4.6.1-1.el8.noarch +ovirt-release44-4.4.6.1-1.el8.noarch @@ -654,2 +655,2 @@ -ovn2.11-2.11.1-39.el8.x86_64 -ovn2.11-host-2.11.1-39.el8.x86_64 +ovn2.11-2.11.1-57.el8s.x86_64 +ovn2.11-host-2.11.1-57.el8s.x86_64 @@ -788 +789 @@ -python3-openvswitch2.11-2.11.0-50.el8.x86_64 +python3-openvswitch2.11-2.11.3-87.el8s.x86_64 @@ -828 +829 @@ -python3-subscription-manager-rhsm-1.28.13-2.el8.x86_64 +python3-subscription-manager-rhsm-1.28.16-1.el8.x86_64 @@ -830 +831 @@ -python3-syspurpose-1.28.13-2.el8.x86_64 +python3-syspurpose-1.28.16-1.el8.x86_64 @@ -836,12 +837,14 @@ -qemu-guest-agent-5.2.0-11.el8s.x86_64 -qemu-img-5.2.0-11.el8s.x86_64 -qemu-kvm-5.2.0-11.el8s.x86_64 -qemu-kvm-block-curl-5.2.0-11.el8s.x86_64 -qemu-kvm-block-gluster-5.2.0-11.el8s.x86_64 -qemu-kvm-block-iscsi-5.2.0-11.el8s.x86_64 -qemu-kvm-block-rbd-5.2.0-11.el8s.x86_64 -qemu-kvm-block-ssh-5.2.0-11.el8s.x86_64 -qemu-kvm-common-5.2.0-11.el8s.x86_64 -qemu-kvm-core-5.2.0-11.el8s.x86_64 -quota-4.04-13.el8.x86_64 -quota-nls-4.04-13.el8.noarch +qemu-guest-agent-5.2.0-16.el8s.x86_64 +qemu-img-5.2.0-16.el8s.x86_64 +qemu-kvm-5.2.0-16.el8s.x86_64 +qemu-kvm-block-curl-5.2.0-16.el8s.x86_64 +qemu-kvm-block-gluster-5.2.0-16.el8s.x86_64 +qemu-kvm-block-iscsi-5.2.0-16.el8s.x86_64 +qemu-kvm-block-rbd-5.2.0-16.el8s.x86_64 +qemu-kvm-block-ssh-5.2.0-16.el8s.x86_64 +qemu-kvm-common-5.2.0-16.el8s.x86_64 +qemu-kvm-core-5.2.0-16.el8s.x86_64 +qemu-kvm-ui-opengl-5.2.0-16.el8s.x86_64 +qemu-kvm-ui-spice-5.2.0-16.el8s.x86_64 +quota-4.04-14.el8.x86_64 +quota-nls-4.04-14.el8.noarch @@ -889 +892 @@ -sos-4.0-11.el8.noarch +sos-4.1-1.el8.noarch @@ -903 +906 @@ -subscription-manager-rhsm-certificates-1.28.13-2.el8.x86_64 +subscription-manager-rhsm-certificates-1.28.16-1.el8.x86_64 @@ -960,0 +964 @@ +xkeyboard-config-2.28-1.el8.noarch @@ -963,0 +968,2 @@ +xmlsec1-1.2.25-4.el8.x86_64 +xmlsec1-openssl-1.2.25-4.el8.x86_64 -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

1 0

Re: Changing the ovirtmgmt IP address
by Matthew.Stier＠fujitsu.com 10 May '21

10 May '21

Found the answer: Update /var/lib/vdsm/persistence/netconf/nets/ovritmgmt and reboot. From: Matthew.Stier(a)fujitsu.com <Matthew.Stier(a)fujitsu.com> Sent: Monday, May 10, 2021 3:18 PM To: users(a)ovirt.org Subject: [ovirt-users] Changing the ovirtmgmt IP address Version: 4.3.10 I'm attempting to change the IP address, netmask and gateway of the ovirtmgmt NIC of a host, but everytime I reboot the host, the old address/netmask/gateway re-assert themselves. Where do I need to make the changes, so they will be permanent? I've modified /etc/sysconfig/network-scripts/ifcfg-ovirtmgmt and route-ovirtmgmt, but they don't stick through a reboot.

1 0

Changing the ovirtmgmt IP address
by Matthew.Stier＠fujitsu.com 10 May '21

10 May '21

Version: 4.3.10 I'm attempting to change the IP address, netmask and gateway of the ovirtmgmt NIC of a host, but everytime I reboot the host, the old address/netmask/gateway re-assert themselves. Where do I need to make the changes, so they will be permanent? I've modified /etc/sysconfig/network-scripts/ifcfg-ovirtmgmt and route-ovirtmgmt, but they don't stick through a reboot.

1 0

Re: Unable to provide network acces to second cluster in DC
by Miguel Garcia 10 May '21

10 May '21

Indeed, the network is assigned to the cluster however is not listed at all.

1 0

Changing 1 node Gluster Distributed to replica
by Ernest Clyde Chua 10 May '21

10 May '21

Good day, currently we have a 1 node host that also runs a gluster in 1 node distributed mode and we recently decided to upgrade to a 3 node host which also runs gluster and set a replica count of 3. can someone help me how can i safely change the volume type to replicated

2 5