[ovirt-users] OVirt VM's not getting DHCP address

[mikejhathaway]

Hi Folks,

None of my VM's are ablt to get an IP from my DHCP server, the management 
network interface and an additional interface are both set to DHCP and are able 
to get addresses, but I am not able to see any VM's obtain an address, is there 
anything by way of trouble shooting someone can point me to please?

TIA

Mike
___
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/PLORGJ6KVD4N4XYQXA47YBBFVKJQGV6E/

[ovirt-users] Re: OS moves after reboot to different device

[simon]

I should clarify that the OS remains on the BOSS card (originally /dev/sda) but 
following a reboot the device name has changed to /dev/sdc
___
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/4I7ENXMS7LPQO66IX6YSGBTMPSJIONYF/

[ovirt-users] OS moves after reboot to different device

[simon]

Hi All,

I just built a 3 node cluster (4.5.2) with 3 Virtual Disks on identical Dell 
Servers.
First Virtual Disk /dev/sda - BOSS Card - 450GB
Second Virtual Disk /dev/sdb - SSD 14TB
Third Virtual Disk /dev/sdc - HDD 72TB
All OS disks were /dev/sda before reboot
Following reboot only first Node is still /dev/sda - other 2 nodes are now 
/dev/sdc
This obviously makes it impossible to create VG groups and create Gluster 
storage volumes.
Can anyone shed any light on why this is happening and how to prevent it.

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

[ovirt-users] Re: OS moves after reboot to different device

[simon]

Thanks Jean-Louis,

I've never had an issue with them changing in the past.

Do you have some documentation/links that would help me in the oVirt 
enviroments please?

Regards

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

[ovirt-users] Re: OS moves after reboot to different device

[Jean-Louis Dupond via Users]

This is just normal. The /dev/sdX names are never stable, as they are 
assigned during boot time.

And it depends which device module is loaded first, so names might change.

If you need stable naming, then use /dev/disk/by-xxx/ symlinks.

On 7/02/2023 15:14, si...@justconnect.ie wrote:

I should clarify that the OS remains on the BOSS card (originally /dev/sda) but 
following a reboot the device name has changed to /dev/sdc
___
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/4I7ENXMS7LPQO66IX6YSGBTMPSJIONYF/

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

[ovirt-users] Problem with update 4.4.3

[scrik787]

Good afternoon,
I have version 4.4.3 and want to upgrade to at least 4.4.10
but I am facing this error:
[root@ovirt1 ~]# yum update
Failed to set locale, defaulting to C.UTF-8
Last metadata expiration check: 2:05:22 ago on Tue Feb  7 12:31:28 2023.
Error: 
 Problem 1: package libgfapi0-8.6-2.el8s.x86_64 requires 
glusterfs-client-xlators(x86-64) = 8.6-2.el8s, but none of the providers can be 
installed
  - cannot install the best update candidate for package 
glusterfs-api-7.8-1.el8.x86_64
  - package glusterfs-client-xlators-8.6-2.el8s.x86_64 is filtered out by 
exclude filtering
 Problem 2: package libglusterfs0-8.6-2.el8s.x86_64 obsoletes glusterfs-libs <= 
8.6-2.el8s provided by glusterfs-libs-7.8-1.el8.x86_64
  - package glusterfs-7.8-1.el8.x86_64 requires glusterfs-libs = 7.8-1.el8, but 
none of the providers can be installed
  - cannot install the best update candidate for package 
glusterfs-libs-7.8-1.el8.x86_64
  - problem with installed package glusterfs-7.8-1.el8.x86_64
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use 
not only best candidate packages)

I tried these options, but the error did not go away. How can I update? I don't 
use GlusterFS. I use ISCSI:

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

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

dnf distro-sync —nobest
yum install https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm
yum update
yum update --skip-broken --nobest
___
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/LDH6K6ICRDDQ3YLEIH2IWZX3EG6LXVVC/

[ovirt-users] oVirt 4.6 planning

[Sandro Bonazzola]

oVirt developers community, I see there are a few enhancements submitted in
GitHub:
engine: Add amt_ws fence agent support

Notification emails merging and localization


And also some rebase proposal:
Rebase on WildFly 26 
Which would probably make more sense to be targeted to an oVirt 4.6 than a
4.5.z.

There are now about three hundreds Untargeted issues(no milestone set)

to
be triaged and about sixty Untargeted PRs (no milestone set)

to
be reviewed.
Some of them might be ready for a 4.5.z bugfix release while others can
wait for a 4.6.

Anyone willing to step in to lead the oVirt 4.6 development?

A year has passed since my blog post about the future of the oVirt project
 but the
concept is the same: oVirt future depends on how you, the community! Come
help contribute to this new future !
CC users community in case someone wants to jump into development as well.

Regards,
-- 

Sandro Bonazzola

MANAGER, SOFTWARE ENGINEERING - Red Hat In-Vehicle Operating System

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

[ovirt-users] Ovirt provider OVN

[scrik787]

Good afternoon,
Since installing ovirt, there have been problems with OVN Provider. But we 
didn't do it, and we didn't have to. Now we need to create virtual networks, 
but nothing works for us. Please help with thoughts. I updated the Ovirt OVN 
Provider certificate, previously there was a problem with them after 2 years.

all host install with ovirt node:
software:
OS Version:RHEL - 8 - 2.2004.0.2.el8
OS Description:oVirt Node 4.4.3
Kernel Version:4.18.0 - 193.28.1.el8_2.x86_64
KVM Version:4.2.0 - 29.el8.6
LIBVIRT Version:libvirt-6.0.0-25.2.el8
VDSM Version:vdsm-4.40.35.1-1.el8
SPICE Version:0.14.2 - 1.el8_2.1
GlusterFS Version:glusterfs-7.8-1.el8
CEPH Version:librbd1-12.2.7-9.el8
Open vSwitch Version:[N/A]
Nmstate Version:nmstate-0.3.6-2.el8
Kernel Features:MDS: (Not affected), L1TF: (Not affected), SRBDS: (Not 
affected), MELTDOWN: (Not affected), SPECTRE_V1: (Mitigation: usercopy/swapgs 
barriers and __user pointer sanitization), SPECTRE_V2: (Mitigation: Enhanced 
IBRS, IBPB: conditional, RSB filling), ITLB_MULTIHIT: (KVM: Mitigation: Split 
huge pages), TSX_ASYNC_ABORT: (Mitigation: Clear CPU buffers; SMT vulnerable), 
SPEC_STORE_BYPASS: (Mitigation: Speculative Store Bypass disabled via prctl and 
seccomp)
VNC Encryption:Disabled
FIPS mode enabled:Disabled

Logs /var/log/ovirt-provider-ovn.log
2023-02-07 12:32:18,629 root Starting server
2023-02-07 12:32:18,630 root Version: 1.2.32-1
2023-02-07 12:32:18,630 root Build date: 20200929061233
2023-02-07 12:32:18,630 root Githash: 44a7426
2023-02-07 12:34:17,362 ovsdbapp.backend.ovs_idl.idlutils Unable to open stream 
to ssl:127.0.0.1:6641 to retrieve schema: Connection reset by peer
2023-02-07 12:34:17,362 root From: :::10.0.120.11:43288 Request: GET 
/v2.0/networks
2023-02-07 12:34:17,362 root Could not retrieve schema from ssl:127.0.0.1:6641
Traceback (most recent call last):
  File "/usr/share/ovirt-provider-ovn/handlers/base_handler.py", line 138, in 
_handle_request
method, path_parts, content
  File "/usr/share/ovirt-provider-ovn/handlers/selecting_handler.py", line 175, 
in handle_request
return self.call_response_handler(handler, content, parameters)
  File "/usr/share/ovirt-provider-ovn/handlers/neutron.py", line 35, in 
call_response_handler
with NeutronApi() as ovn_north:
  File "/usr/share/ovirt-provider-ovn/neutron/neutron_api.py", line 95, in 
__init__
self.ovsidl, self.idl = ovn_connection.connect()
  File "/usr/share/ovirt-provider-ovn/ovn_connection.py", line 46, in connect
ovnconst.OVN_NORTHBOUND
  File 
"/usr/lib/python3.6/site-packages/ovsdbapp/backend/ovs_idl/connection.py", line 
154, in from_server
helper = idlutils.get_schema_helper(connection_string, schema_name)
  File "/usr/lib/python3.6/site-packages/ovsdbapp/backend/ovs_idl/idlutils.py", 
line 144, in get_schema_helper
raise Exception("Could not retrieve schema from %s" % connection)
Exception: Could not retrieve schema from ssl:127.0.0.1:6641

Test in Ovirt Engine OVN Provider
Error:Failed to communicate with the external provider, see log for additional 
details.

[root@ovirtengine ~]# cat 
/etc/ovirt-provider-ovn/conf.d/10-setup-ovirt-provider-ovn.conf
# This file is automatically generated by engine-setup. Please do not edit 
manually
[PROVIDER]
provider-host=ovirt.test.test.org
[SSL]
ssl-cert-file=/etc/pki/ovirt-engine/certs/ovirt-provider-ovn.cer
ssl-key-file=/etc/pki/ovirt-engine/keys/ovirt-provider-ovn.key.nopass
ssl-cacert-file=/etc/pki/ovirt-engine/ca.pem
https-enabled=true
[OVN REMOTE]
ovn-remote=ssl:127.0.0.1:6641
[OVIRT]
ovirt-sso-client-id=ovirt-provider-ovn
ovirt-sso-client-secret=SECRET KEY
ovirt-host=https://ovirt.test.test.org:443
ovirt-ca-file=/etc/pki/ovirt-engine/apache-ca.pem
[NETWORK]
port-security-enabled-default=True

Reinstall Ovirt OVN with engine-setup did not solve the problem

[root@vovirtengine ~]# ovn-nbctl get-ssl
Private key: /etc/pki/ovirt-engine/keys/ovn-ndb.key.nopass
Certificate: /etc/pki/ovirt-engine/certs/ovn-ndb.cer
CA Certificate: /etc/pki/ovirt-engine/ca.pem
Bootstrap: false
[root@vovirtengine ~]# ovn-nbctl get-connection
pssl:6641:[::]
[root@vovirtengine ~]# ovn-sbctl get-ssl
Private key: /etc/pki/ovirt-engine/keys/ovn-sdb.key.nopass
Certificate: /etc/pki/ovirt-engine/certs/ovn-sdb.cer
CA Certificate: /etc/pki/ovirt-engine/ca.pem
Bootstrap: false
[root@vovirtengine ~]# ovn-sbctl get-connection
read-write role="" pssl:6642:[::]
[root@vovirtengine ~]# 

Ovirt-ENgine Config
Name ovirt-provider-ovn
Description oVirt network provider for OVN
Networking Plugin oVirt Network Provider for OVN
Automatic Synchronization YES
Unmanaged NO
Read-Only NO
Provider URL https://ovirt.test.test.org:9696
Requires Authentication YES
Username admin@internal
Password PASWORD
Protocol HTTPS
Host Name ovirt.test.test.org
API Port 35357
API Version v2.0
Tenant Name


on host in cluster logs /var/log/openvswitch/ovn-controller.log
<...>
2023-02-07T09:11:58.903Z|303247|stream_ssl|WARN|SSL_connect: system error 
(Success)