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

2022-08-29 Thread 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: unable to bring up gluster bricks after 4.5 upgrade

2022-08-29 Thread Jayme 
It appears that I may have resolved the issue after putting host into
maintenance again and rebooting a second time. I'm really not sure why but
all bricks are up now

On Mon, Aug 29, 2022 at 3:45 PM Jayme  wrote:

> A bit more info from the host's brick log
>
> [2022-08-29 18:43:44.251198 +] D [MSGID: 0]
> [options.c:1113:xlator_reconfigure_rec] 0-engine-barrier: reconfigured
> [2022-08-29 18:43:44.251203 +] D [MSGID: 0]
> [options.c:1133:xlator_reconfigure_rec] 0-engine-index: No reconfigure()
> found
> [2022-08-29 18:43:44.251207 +] D [MSGID: 0]
> [options.c:1113:xlator_reconfigure_rec] 0-engine-index: reconfigured
> [2022-08-29 18:43:44.251214 +] I [MSGID: 0]
> [options.c:1251:xlator_option_reconf_bool] 0-engine-quota: option
> deem-statfs using set value off
> [2022-08-29 18:43:44.251221 +] I [MSGID: 0]
> [options.c:1251:xlator_option_reconf_bool] 0-engine-quota: option
> server-quota using set value off
> [2022-08-29 18:43:44.251248 +] D [MSGID: 0]
> [options.c:1113:xlator_reconfigure_rec] 0-engine-quota: reconfigured
> [2022-08-29 18:44:04.899452 +] E [MSGID: 113072]
> [posix-inode-fd-ops.c:2087:posix_writev] 0-engine-posix: write failed:
> offset 0, [Invalid argument]
> [2022-08-29 18:44:04.899542 +] E [MSGID: 115067]
> [server-rpc-fops_v2.c:1324:server4_writev_cbk] 0-engine-server: WRITE info
> [{frame=358765}, {WRITEV_fd_no=5},
> {uuid_utoa=c816cdf3-12e6-45c0-ae0f-2cf03e0f7299},
> {client=CTX_ID:11b78775-07c9-47ff-b426-b44f3f88a3f7-GRAPH_ID:0-PID:25622-HOST:host1.x-PC_NAME:engine-client-0-RECON_NO:-2},
> {error-xlator=engine-posix}, {errno=22}, {error=Invalid argument}]
> [2022-08-29 18:44:14.876436 +] E [MSGID: 113002]
> [posix-entry-ops.c:769:posix_mkdir] 0-engine-posix: gfid is null for (null)
> [Invalid argument]
> [2022-08-29 18:44:14.876503 +] E [MSGID: 115056]
> [server-rpc-fops_v2.c:497:server4_mkdir_cbk] 0-engine-server: MKDIR info
> [{frame=359508}, {MKDIR_path=},
> {uuid_utoa=----0001}, {bname=},
> {client=CTX_ID:37199949-8cf2-4bbe-938e-e9ef3bd98486-GRAPH_ID:3-PID:2473-HOST:host0.x-PC_NAME:engine-client-0-RECON_NO:-0},
> {error-xlator=engine-posix}, {errno=22}, {error=Invalid argument}]
>
> On Mon, Aug 29, 2022 at 3:18 PM Jayme  wrote:
>
>> Hello All,
>>
>> I've been struggling with a few issues upgrading my 3-node HCI custer
>> from 4.4 to 4.5.
>>
>> At present the self hosted engine VM is properly running oVirt 4.5 on
>> CentOS 8x stream.
>>
>> First host node, I set in maintenance and installed new node-ng image. I
>> ran into issue with rescue mode on boot which appears to have been related
>> to LVM devices bug. I was able to work past that and get the node to boot.
>>
>> The node running 4.5.2 image is booting properly and gluster/lvm mounts
>> etc all look good. I am able to activate the host and run VMs on it etc.
>> however, oVirt cli is showing that all bricks on host are DOWN.
>>
>> I was unable to get the bricks back up even after doing a force start of
>> the volumes.
>>
>> Here is the glusterd log from the host in question when I try force start
>> on the engine volume (other volumes are similar:
>>
>> ==> glusterd.log <==
>> The message "I [MSGID: 106568]
>> [glusterd-svc-mgmt.c:266:glusterd_svc_stop] 0-management: bitd service is
>> stopped" repeated 2 times between [2022-08-29 18:09:56.027147 +] and
>> [2022-08-29 18:10:34.694144 +]
>> [2022-08-29 18:10:34.695348 +] I [MSGID: 106618]
>> [glusterd-svc-helper.c:909:glusterd_attach_svc] 0-glusterd: adding svc
>> glustershd (volume=engine) to existing process with pid 2473
>> [2022-08-29 18:10:34.695669 +] I [MSGID: 106131]
>> [glusterd-proc-mgmt.c:84:glusterd_proc_stop] 0-management: scrub already
>> stopped
>> [2022-08-29 18:10:34.695691 +] I [MSGID: 106568]
>> [glusterd-svc-mgmt.c:266:glusterd_svc_stop] 0-management: scrub service is
>> stopped
>> [2022-08-29 18:10:34.695832 +] I [MSGID: 106617]
>> [glusterd-svc-helper.c:698:glusterd_svc_attach_cbk] 0-management: svc
>> glustershd of volume engine attached successfully to pid 2473
>> [2022-08-29 18:10:34.703718 +] E [MSGID: 106115]
>> [glusterd-mgmt.c:119:gd_mgmt_v3_collate_errors] 0-management: Post commit
>> failed on gluster2.x. Please check log file for details.
>> [2022-08-29 18:10:34.703774 +] E [MSGID: 106115]
>> [glusterd-mgmt.c:119:gd_mgmt_v3_collate_errors] 0-management: Post commit
>> failed on gluster1.x. Please check log file for details.
>> [2022-08-29 18:10:34.703797 +] E [MSGID: 106664]
>> [glusterd-mgmt.c:1969:glusterd_mgmt_v3_post_commit] 0-management: Post
>> commit failed on peers
>> [2022-08-29 18:10:34.703800 +] E [MSGID: 106664]
>> [glusterd-mgmt.c:2664:glusterd_mgmt_v3_initiate_all_phases] 0-management:
>> Post commit Op Failed
>>
>> If I run start command manually on host cli:
>>
>>  gluster volume start engine force
>> volume start: engine: failed: Post commit failed on gluster1.. Please
>> check log file for details.

[ovirt-users] Re: unable to bring up gluster bricks after 4.5 upgrade

2022-08-29 Thread Jayme 
A bit more info from the host's brick log

[2022-08-29 18:43:44.251198 +] D [MSGID: 0]
[options.c:1113:xlator_reconfigure_rec] 0-engine-barrier: reconfigured
[2022-08-29 18:43:44.251203 +] D [MSGID: 0]
[options.c:1133:xlator_reconfigure_rec] 0-engine-index: No reconfigure()
found
[2022-08-29 18:43:44.251207 +] D [MSGID: 0]
[options.c:1113:xlator_reconfigure_rec] 0-engine-index: reconfigured
[2022-08-29 18:43:44.251214 +] I [MSGID: 0]
[options.c:1251:xlator_option_reconf_bool] 0-engine-quota: option
deem-statfs using set value off
[2022-08-29 18:43:44.251221 +] I [MSGID: 0]
[options.c:1251:xlator_option_reconf_bool] 0-engine-quota: option
server-quota using set value off
[2022-08-29 18:43:44.251248 +] D [MSGID: 0]
[options.c:1113:xlator_reconfigure_rec] 0-engine-quota: reconfigured
[2022-08-29 18:44:04.899452 +] E [MSGID: 113072]
[posix-inode-fd-ops.c:2087:posix_writev] 0-engine-posix: write failed:
offset 0, [Invalid argument]
[2022-08-29 18:44:04.899542 +] E [MSGID: 115067]
[server-rpc-fops_v2.c:1324:server4_writev_cbk] 0-engine-server: WRITE info
[{frame=358765}, {WRITEV_fd_no=5},
{uuid_utoa=c816cdf3-12e6-45c0-ae0f-2cf03e0f7299},
{client=CTX_ID:11b78775-07c9-47ff-b426-b44f3f88a3f7-GRAPH_ID:0-PID:25622-HOST:host1.x-PC_NAME:engine-client-0-RECON_NO:-2},
{error-xlator=engine-posix}, {errno=22}, {error=Invalid argument}]
[2022-08-29 18:44:14.876436 +] E [MSGID: 113002]
[posix-entry-ops.c:769:posix_mkdir] 0-engine-posix: gfid is null for (null)
[Invalid argument]
[2022-08-29 18:44:14.876503 +] E [MSGID: 115056]
[server-rpc-fops_v2.c:497:server4_mkdir_cbk] 0-engine-server: MKDIR info
[{frame=359508}, {MKDIR_path=},
{uuid_utoa=----0001}, {bname=},
{client=CTX_ID:37199949-8cf2-4bbe-938e-e9ef3bd98486-GRAPH_ID:3-PID:2473-HOST:host0.x-PC_NAME:engine-client-0-RECON_NO:-0},
{error-xlator=engine-posix}, {errno=22}, {error=Invalid argument}]

On Mon, Aug 29, 2022 at 3:18 PM Jayme  wrote:

> Hello All,
>
> I've been struggling with a few issues upgrading my 3-node HCI custer from
> 4.4 to 4.5.
>
> At present the self hosted engine VM is properly running oVirt 4.5 on
> CentOS 8x stream.
>
> First host node, I set in maintenance and installed new node-ng image. I
> ran into issue with rescue mode on boot which appears to have been related
> to LVM devices bug. I was able to work past that and get the node to boot.
>
> The node running 4.5.2 image is booting properly and gluster/lvm mounts
> etc all look good. I am able to activate the host and run VMs on it etc.
> however, oVirt cli is showing that all bricks on host are DOWN.
>
> I was unable to get the bricks back up even after doing a force start of
> the volumes.
>
> Here is the glusterd log from the host in question when I try force start
> on the engine volume (other volumes are similar:
>
> ==> glusterd.log <==
> The message "I [MSGID: 106568] [glusterd-svc-mgmt.c:266:glusterd_svc_stop]
> 0-management: bitd service is stopped" repeated 2 times between [2022-08-29
> 18:09:56.027147 +] and [2022-08-29 18:10:34.694144 +]
> [2022-08-29 18:10:34.695348 +] I [MSGID: 106618]
> [glusterd-svc-helper.c:909:glusterd_attach_svc] 0-glusterd: adding svc
> glustershd (volume=engine) to existing process with pid 2473
> [2022-08-29 18:10:34.695669 +] I [MSGID: 106131]
> [glusterd-proc-mgmt.c:84:glusterd_proc_stop] 0-management: scrub already
> stopped
> [2022-08-29 18:10:34.695691 +] I [MSGID: 106568]
> [glusterd-svc-mgmt.c:266:glusterd_svc_stop] 0-management: scrub service is
> stopped
> [2022-08-29 18:10:34.695832 +] I [MSGID: 106617]
> [glusterd-svc-helper.c:698:glusterd_svc_attach_cbk] 0-management: svc
> glustershd of volume engine attached successfully to pid 2473
> [2022-08-29 18:10:34.703718 +] E [MSGID: 106115]
> [glusterd-mgmt.c:119:gd_mgmt_v3_collate_errors] 0-management: Post commit
> failed on gluster2.x. Please check log file for details.
> [2022-08-29 18:10:34.703774 +] E [MSGID: 106115]
> [glusterd-mgmt.c:119:gd_mgmt_v3_collate_errors] 0-management: Post commit
> failed on gluster1.x. Please check log file for details.
> [2022-08-29 18:10:34.703797 +] E [MSGID: 106664]
> [glusterd-mgmt.c:1969:glusterd_mgmt_v3_post_commit] 0-management: Post
> commit failed on peers
> [2022-08-29 18:10:34.703800 +] E [MSGID: 106664]
> [glusterd-mgmt.c:2664:glusterd_mgmt_v3_initiate_all_phases] 0-management:
> Post commit Op Failed
>
> If I run start command manually on host cli:
>
>  gluster volume start engine force
> volume start: engine: failed: Post commit failed on gluster1.. Please
> check log file for details.
> Post commit failed on gluster2.. Please check log file for details.
>
> I feel like this may be some issue with the difference in major versions
> of GlusterFS on the nodes but I am unsure. The other nodes are running
> ovirt-node-ng-4.4.6.3
>
> At this point I am afraid to bring down any other node to attempt
> upgrading it without the

[ovirt-users] unable to bring up gluster bricks after 4.5 upgrade

2022-08-29 Thread Jayme 
Hello All,

I've been struggling with a few issues upgrading my 3-node HCI custer from
4.4 to 4.5.

At present the self hosted engine VM is properly running oVirt 4.5 on
CentOS 8x stream.

First host node, I set in maintenance and installed new node-ng image. I
ran into issue with rescue mode on boot which appears to have been related
to LVM devices bug. I was able to work past that and get the node to boot.

The node running 4.5.2 image is booting properly and gluster/lvm mounts etc
all look good. I am able to activate the host and run VMs on it etc.
however, oVirt cli is showing that all bricks on host are DOWN.

I was unable to get the bricks back up even after doing a force start of
the volumes.

Here is the glusterd log from the host in question when I try force start
on the engine volume (other volumes are similar:

==> glusterd.log <==
The message "I [MSGID: 106568] [glusterd-svc-mgmt.c:266:glusterd_svc_stop]
0-management: bitd service is stopped" repeated 2 times between [2022-08-29
18:09:56.027147 +] and [2022-08-29 18:10:34.694144 +]
[2022-08-29 18:10:34.695348 +] I [MSGID: 106618]
[glusterd-svc-helper.c:909:glusterd_attach_svc] 0-glusterd: adding svc
glustershd (volume=engine) to existing process with pid 2473
[2022-08-29 18:10:34.695669 +] I [MSGID: 106131]
[glusterd-proc-mgmt.c:84:glusterd_proc_stop] 0-management: scrub already
stopped
[2022-08-29 18:10:34.695691 +] I [MSGID: 106568]
[glusterd-svc-mgmt.c:266:glusterd_svc_stop] 0-management: scrub service is
stopped
[2022-08-29 18:10:34.695832 +] I [MSGID: 106617]
[glusterd-svc-helper.c:698:glusterd_svc_attach_cbk] 0-management: svc
glustershd of volume engine attached successfully to pid 2473
[2022-08-29 18:10:34.703718 +] E [MSGID: 106115]
[glusterd-mgmt.c:119:gd_mgmt_v3_collate_errors] 0-management: Post commit
failed on gluster2.x. Please check log file for details.
[2022-08-29 18:10:34.703774 +] E [MSGID: 106115]
[glusterd-mgmt.c:119:gd_mgmt_v3_collate_errors] 0-management: Post commit
failed on gluster1.x. Please check log file for details.
[2022-08-29 18:10:34.703797 +] E [MSGID: 106664]
[glusterd-mgmt.c:1969:glusterd_mgmt_v3_post_commit] 0-management: Post
commit failed on peers
[2022-08-29 18:10:34.703800 +] E [MSGID: 106664]
[glusterd-mgmt.c:2664:glusterd_mgmt_v3_initiate_all_phases] 0-management:
Post commit Op Failed

If I run start command manually on host cli:

 gluster volume start engine force
volume start: engine: failed: Post commit failed on gluster1.. Please
check log file for details.
Post commit failed on gluster2.. Please check log file for details.

I feel like this may be some issue with the difference in major versions of
GlusterFS on the nodes but I am unsure. The other nodes are running
ovirt-node-ng-4.4.6.3

At this point I am afraid to bring down any other node to attempt upgrading
it without the bricks in UP status on the first host. I do not want to lose
quorum and potentially disrupt running VMs.

Any idea why I can't seem to start the volumes on the upgraded host?

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

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

2022-08-29 Thread vk 
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/

[ovirt-users] Re: oVirt 4.5 self-hosted network not working

2022-08-29 Thread Paul-Erik Törrönen 
On 28/08/2022 11.12, Colin Coe wrote:
> How is networking configured on the hypervisors?  Single NIC (or bond)
> or multi-homed?

The host (a single one) has a single network device. It is a Dell
Latitude laptop, so nothing fancy.

I've run some tcpdumps, and it looks like at least the ICMP and TCP
traffic from another machine on the same subnet does get to the host (as
confirmed by running tcpdump on the host), but then it disappears. It
never gets to the engine VM (running also tcpdump).

Interesting detail is that ARP does seem to get to the engine VM as I
can see the expected "request who-has  tell  is-at " on the engine
VM-side.

FWIW the packages should be the latest from the centos-release-ovirt45,
including ovirt-hosted-engine-setup-2.6.5-1.el8.noarch.

Poltsi
___
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/QQ73WDP5FSZXL5MGIMURMAAMB5ZS6A2J/

[ovirt-users] Re: how kill backup operation

2022-08-29 Thread Arik Hadas 
On Mon, Aug 29, 2022 at 2:20 PM Diego Ercolani 
wrote:

> Thank you for your support,
> I'm councious about the difficulty to keep everything in-line. I currently
> try to find the correct workload to make backup (using CBR) of VMs.
> I tryied both vprotect (with current tecnology preview) and Veeam
> (community using RHV plugin) And I'm currently experiencing very annoying
> problems.
> I can give you the engine-log
> https://cloud.ssis.sm/index.php/s/M9DqFHSaowYqa9H, I currently have two
> machines in an unconsinstent stato from the snapshot point of view:
> SSIS-otobo and SSIS-TPayX2go.

I empied the image_transfer table, last time it helped. This is the sql to
> restore it:
> INSERT INTO public.image_transfers
> (command_id,command_type,phase,last_updated,message,vds_id,disk_id,imaged_ticket_id,proxy_uri,bytes_sent,bytes_total,"type",active,daemon_uri,client_inactivity_timeout,image_format,backend,backup_id,client_type,shallow,timeout_policy)
> VALUES
>  ('54097389-db69-4aa3-a34d-eb6cb2c1fc4b',1024,7,'2022-08-26
> 15:00:46.138+02',NULL,'bac4cca5-b6db-4d66-af65-39b8929262b7','5d18a058-652f-4c94-a9ff-9c15152c61b4','1e1846a1-f9f0-49e5-912e-2f5bf8dd8144','
> https://ovirt-engine.ovirt:54323/images',12307202048,42949640192,1,false,'
> https://ovirt-node3.ovirt:54322/images
> ',3600,5,1,'7e06b6e9-92d9-4f83-ac16-9a06a638fac3',2,false,'legacy');
>

I don't see anything suspicious in that log - I see backups of both of the
aforementioned VMs but they all seem to succeed, including snapshot
removals. But it could be that something that is not covered by this log
went wrong as I can't see the backup 7e06b6e9-92d9-4f83-ac16-9a06a638fac3
there.


>
> I'm currently stuck because I cannot even remove the VMs as they are
> "locked during backup" operation
>

I see two options:
1. To stop ovirt-engine, remove the relevant parts from the
command_entities table and unlock the entities (there's a script for that:
https://github.com/oVirt/ovirt-engine/blob/master/packaging/setup/dbutils/unlock_entity.sh),
and then restart ovirt-engine
2. To finalize ongoing image transfers [1] and then finalize the backup [2]

The second option should be much simpler

[1]
https://github.com/oVirt/ovirt-engine-api-model/blob/4.5.11/src/main/java/services/ImageTransferService.java#L243-L255

[2]
https://github.com/oVirt/ovirt-engine-api-model/blob/4.5.11/src/main/java/services/VmBackupService.java#L69-L86


> ___
> 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/RFMRQ4PDPGHPQKZURHIR2ZYS5HL4FXU7/
>
___
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/HK4SM4BHRLNL2TICHG23QSUABM3NNHW4/

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

2022-08-29 Thread Martin Perina 
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
- 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  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  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/
> ___
> Users mailing list

[ovirt-users] oVirt 4.5.2 /var growing rapidly due to ovirt_engine_history db

2022-08-29 Thread sohail_akhter3 
Hi,

We have recently upgrade our oVirt environment to 4.5.2 version. Environment is 
based on hosted-engine. Since we have upgrade we noticed rapid incrase in /var 
partition in engine VM. It is increasing very rapidly. If we vacuum 
ovirt_engine_history db, /var size reduces but next day size will increase 
again upto 5-10%. We did db vacuuming couple of time but not sure we it is 
increasing so rapidly. 
Here is the partial output of vacuuming that was done on 26-08-22. Table 
"host_interface_hourly_history" had more entries to be removed. Rest of the 
table had not much entries. Previously table "host_interface_samples_history" 
had entries to be removed.
Any Idea what can be the reason for that?

# dwh-vacuum -f -v
SELECT pg_catalog.set_config('search_path', '', false);
vacuumdb: vacuuming database "ovirt_engine_history"
RESET search_path;
SELECT c.relname, ns.nspname FROM pg_catalog.pg_class c
 JOIN pg_catalog.pg_namespace ns ON c.relnamespace OPERATOR(pg_catalog.=) ns.oid
 LEFT JOIN pg_catalog.pg_class t ON c.reltoastrelid OPERATOR(pg_catalog.=) t.oid
 WHERE c.relkind OPERATOR(pg_catalog.=) ANY (array['r', 'm'])
 ORDER BY c.relpages DESC;
SELECT pg_catalog.set_config('search_path', '', false);
VACUUM (FULL, VERBOSE) public.host_interface_samples_history;
INFO:  vacuuming "public.host_interface_samples_history"
INFO:  "host_interface_samples_history": found 3135 removable, 84609901 
nonremovable row versions in 1564960 pages
DETAIL:  0 dead row versions cannot be removed yet.
CPU: user: 41.88 s, system: 14.93 s, elapsed: 422.83 s.
VACUUM (FULL, VERBOSE) public.host_interface_hourly_history;
INFO:  vacuuming "public.host_interface_hourly_history"
INFO:  "host_interface_hourly_history": found 252422 removable, 39904650 
nonremovable row versions in 473269 pages

Please let me know if any further information is required.

Regards
Sohail
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/VD2ROVZY2TOLZHSK4HWHEENRP7BQLRYI/

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

2022-08-29 Thread Jirka Simon 

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

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

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

2022-08-29 Thread 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

2022-08-29 Thread Jirka Simon 

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

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

2022-08-29 Thread Jirka Simon 

Hello 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/W2T2SYZMK4T2VHU2OG3E5I72RAFPT6NN/

[ovirt-users] Re: how kill backup operation

2022-08-29 Thread Diego Ercolani 
Thank you for your support,
I'm councious about the difficulty to keep everything in-line. I currently try 
to find the correct workload to make backup (using CBR) of VMs.
I tryied both vprotect (with current tecnology preview) and Veeam (community 
using RHV plugin) And I'm currently experiencing very annoying problems.
I can give you the engine-log 
https://cloud.ssis.sm/index.php/s/M9DqFHSaowYqa9H, I currently have two 
machines in an unconsinstent stato from the snapshot point of view: SSIS-otobo 
and SSIS-TPayX2go.
I empied the image_transfer table, last time it helped. This is the sql to 
restore it:
INSERT INTO public.image_transfers 
(command_id,command_type,phase,last_updated,message,vds_id,disk_id,imaged_ticket_id,proxy_uri,bytes_sent,bytes_total,"type",active,daemon_uri,client_inactivity_timeout,image_format,backend,backup_id,client_type,shallow,timeout_policy)
 VALUES
 ('54097389-db69-4aa3-a34d-eb6cb2c1fc4b',1024,7,'2022-08-26 
15:00:46.138+02',NULL,'bac4cca5-b6db-4d66-af65-39b8929262b7','5d18a058-652f-4c94-a9ff-9c15152c61b4','1e1846a1-f9f0-49e5-912e-2f5bf8dd8144','https://ovirt-engine.ovirt:54323/images',12307202048,42949640192,1,false,'https://ovirt-node3.ovirt:54322/images',3600,5,1,'7e06b6e9-92d9-4f83-ac16-9a06a638fac3',2,false,'legacy');

I'm currently stuck because I cannot even remove the VMs as they are "locked 
during backup" operation
___
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/RFMRQ4PDPGHPQKZURHIR2ZYS5HL4FXU7/

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

2022-08-29 Thread 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] Re: Q: Engione 4.4.10 and New Host on CentOS Stream 9

2022-08-29 Thread Michal Skrivanek 


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

[ovirt-users] Re: (no subject)

2022-08-29 Thread Michal Skrivanek 


> On 26. 8. 2022, at 17:37, parallax  wrote:
> 
> I need to switch the host into maintenance mode but without stopping VMs

why? you shouldn't do that, it's not that easy to make sure everything picks up 
the new certificates.
in 4.5.1+ you can re-enroll certificates in unresponsive state too, but ^^.

> VM is not checked as "HA available" and selected "manual migration only" in 
> options
> If I do manual fencing to the host (confirm host has been rebooted) will the 
> VM automatically start on another host ?

if they are not HA they won't.

> 
> ср, 24 авг. 2022 г. в 14:15, parallax  >:
> I had to add a new server into the datacenter and the StorageDomains status 
> back to normal and the error is gone
> but I still have hosts that haven't valid certificates
> putting host into maintenance mode is the only way to update the certificate ?
> 
> пн, 22 авг. 2022 г. в 13:31, Strahil Nikolov  >:
> Are you able to set a host into maintenance?
> If yes, then you should be able to Hosts -> select host -> Installation -> 
> Enroll Certificate
> 
> Best Regards,
> Strahil Nikolov 
> 
> On Mon, Aug 22, 2022 at 10:30, parallax
> mailto:dd432...@gmail.com>> wrote:
> no vdsm errors on hosts side 
> but I see vdsmcert.pem has expired on each hosts in the datacenter 
> and there were no warning to me about certs expiration beginning
> 
> it is possible to update the certificate without stopping the server ?
> 
> сб, 20 авг. 2022 г. в 18:27, Strahil Nikolov  >:
> Check the vdsm logs on all hosts to get a clue why this is happening.
> 
> P.S.: Next time consider adding a subject.
> 
> Best Regards,
> Strahil Nikolov 
> 
> On Sat, Aug 20, 2022 at 17:23, parallax
> mailto:dd432...@gmail.com>> wrote:
> oVirt version:4.4.4.7-1.el8
> 
> I have several servers in cluster and I got this error:
> 
> Data Center is being initialized, please wait for initialization to complete.
> VDSM command GetStoragePoolInfoVDS failed: PKIX path validation failed: 
> java.security.cert.CertPathValidatorException: validity check failed
> 
> the SPM role is constantly being transferred to the servers and I can't do 
> anything
> 
> in StorageDomains storages are in inactive status but virtual machines are 
> runnig
> 
> how ti fix it?
> ___
> 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/P6MGHC2NU3BDQ7DJSER2VH757C2Y5YKJ/
>  
> 
> ___
> 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/WOVV6HJLSIRDLUTCYBLJCWCNMBMK73LF/
>  
> 
___
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/EFN27PE3CYWHQAFBY3AJ3NFTAHFJCYUO/

[ovirt-users] Re: Commissioning hew host on centos9

2022-08-29 Thread Sandro Bonazzola 
Il giorno sab 27 ago 2022 alle ore 03:34 David Johnson <
djohn...@maxistechnology.com> ha scritto:

> Good evening all,
>
> I am trying to commission an ovirt host on new hardware using Centos 9.
>
> I followed the pre-install instructions at
> https://www.ovirt.org/download/install_on_rhel.html, and eventually
> figured out that this line was missing from the preparation scripts:
>
> dnf install rdo-openvswitch-2.15
>

Why did you install rdo-openvswitch? The oVirt project uses
ovirt-openvswitch and it should be pulled in automatically as a dependency.


>
> With that, I was able to continue installation.
>
> After completing the instructions, DNF update reports this:
>
> [root@localhost administrator]# dnf update --nobest
> Last metadata expiration check: 0:01:06 ago on Fri 26 Aug 2022 08:20:27 PM
> CDT.
> Dependencies resolved.
>
>  Problem 1: package ovirt-openvswitch-2.15-4.el9.noarch requires
> openvswitch2.15, but none of the providers can be installed
>   - package rdo-openvswitch-2:2.17-2.el9s.noarch obsoletes openvswitch2.15
> < 2.17 provided by openvswitch2.15-2.15.0-99.el9s.x86_64
>   - package rdo-openvswitch-2:2.17-2.el9s.noarch obsoletes openvswitch2.15
> < 2.17 provided by openvswitch2.15-2.15.0-51.el9s.x86_64
>   - package rdo-openvswitch-2:2.17-2.el9s.noarch obsoletes openvswitch2.15
> < 2.17 provided by openvswitch2.15-2.15.0-56.el9s.x86_64
>   - package rdo-openvswitch-2:2.17-2.el9s.noarch obsoletes openvswitch2.15
> < 2.17 provided by openvswitch2.15-2.15.0-81.el9s.x86_64
>   - cannot install the best update candidate for package
> ovirt-openvswitch-2.15-4.el9.noarch
>   - cannot install the best update candidate for package
> openvswitch2.15-2.15.0-99.el9s.x86_64
>  Problem 2: problem with installed package
> ovirt-openvswitch-2.15-4.el9.noarch
>   - package ovirt-openvswitch-2.15-4.el9.noarch requires openvswitch2.15,
> but none of the providers can be installed
>   - package rdo-openvswitch-2:2.17-2.el9s.noarch obsoletes openvswitch2.15
> < 2.17 provided by openvswitch2.15-2.15.0-99.el9s.x86_64
>   - package rdo-openvswitch-2:2.17-2.el9s.noarch obsoletes openvswitch2.15
> < 2.17 provided by openvswitch2.15-2.15.0-51.el9s.x86_64
>   - package rdo-openvswitch-2:2.17-2.el9s.noarch obsoletes openvswitch2.15
> < 2.17 provided by openvswitch2.15-2.15.0-56.el9s.x86_64
>   - package rdo-openvswitch-2:2.17-2.el9s.noarch obsoletes openvswitch2.15
> < 2.17 provided by openvswitch2.15-2.15.0-81.el9s.x86_64
>   - cannot install the best update candidate for package
> rdo-openvswitch-1:2.15-2.el9s.noarch
>
> DNF info lists these
>
> [root@localhost administrator]# dnf list installed |grep openvswitch
> centos-release-nfv-openvswitch.noarch1-4.el9s
> @c9s-extras-common
> network-scripts-openvswitch2.15.x86_64   2.15.0-99.el9s
> @centos-nfv-openvswitch
> openvswitch-selinux-extra-policy.noarch  1.0-31.el9s
>@centos-nfv-openvswitch
>
> *openvswitch2.15.x86_64   2.15.0-99.el9s
> @centos-nfv-openvswitch*ovirt-openvswitch.noarch
> 2.15-4.el9   @centos-ovirt45
> python3-openvswitch2.15.x86_64   2.15.0-99.el9s
> @centos-nfv-openvswitch
> rdo-openvswitch.noarch   1:2.15-2.el9s
>@centos-openstack-yoga
>
> *Questions:*
>
> 1. Is this a problem?
>
> 2. If this is a problem, is there an FAQ sheet or known steps to work
> around/fix this?
>
> 3. Does there need to be an update to the pre-installation instructions?
>
> *David Johnson*
> *Director of Development, Maxis Technology*
> 844.696.2947 ext 702 (o) | 479.531.3590 (c)
> 
> 
> 
>
> *Follow us:*  
> ___
> 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/KKD24ZKCDLQD4SSICGIPKI6VYXCM6VP6/
>


-- 

Sandro Bonazzola

MANAGER, SOFTWARE ENGINEERING, EMEA R PERFORMANCE & SCALE

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