[ovirt-users] gluster service on the cluster is unchecked on hci cluster
Hi, I would like to change CPU Type in my oVirt 4.4.10 HCI cluster (based on 3 glusterfs/virt hosts). When I try to I got this error Error while executing action: Cannot disable gluster service on the cluster as it contains volumes. As I remember I had Gluster Service enabled on this cluster but now both (Enable Virt Services and Enable Gluster Service) checkboxes are grayed out and Gluster Service is unchecked. Also Storage / Volumes displays my volumes... well, displays one brick on particular host in unknown state (? mark) which is new situation. As I can see from command line all bricks are online, no healing in progress, all looks good... I am not sure if the second issue is relevant to first one so main question is how can I (re)enable gluster service in my cluster? Thanks in advance, Jiri smime.p7s Description: Elektronicky podpis S/MIME ___ 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/S4NVCQ33ZSJSHR7P7K7OICSA5F253BVA/
[ovirt-users] Re: How to set static IP when creating VM?
Hello Minseok,
You can use some base image and templates with coud-init and set both there.
Or you can use ansible or so.
- name: Create VM "{{ hostname }}" from template
ovirt_vm:
auth: "{{ ovirt_auth }}"
name: "{{ hostname }}"
comment: "{{ ovirt_comment }}"
description: "{{ ovirt_description }}"
template: "{{ ovirt_template }}"
cluster: "{{ ovirt_cluster }}"
memory: "{{ ovirt_vm_memory }}"
memory_max: "{{ ovirt_vm_memory_max }}"
memory_guaranteed: "{{ ovirt_vm_memory }}"
cpu_cores: "{{ ovirt_vm_cores }}"
cpu_sockets: "{{ ovirt_vm_sockets }}"
operating_system: "{{ ovirt_operating_system }}"
clone: true
nics:
- name: "{{ ovirt_nic_name }}"
profile_name: "{{ ovirt_nic_profile }}"
cloud_init_persist: True
cloud_init:
host_name: "{{ hostname }}"
timezone: "GMT+01:00"
dns_servers: "{{ ovirt_dns_servers }}"
authorized_ssh_keys: "{{ ovirt_default_ssh_keys }}"
cloud_init_nics:
- nic_name: "{{ ovirt_nic_name }}"
nic_boot_protocol: static
nic_ip_address: "{{ ovirt_nic_ip_address }}"
nic_netmask: "{{ ovirt_nic_netmask }}"
nic_gateway: "{{ ovirt_nic_gateway }}"
nic_on_boot: True
wait: yes
Jirka
On 7/4/22 06:52, msj...@kisti.re.kr wrote:
Hi, all.
I've used cockpit-machine, qemu-kvm for 2 years for my services, and I tried to
use ovirt for a month. I've use virt-edit to configure ifcfg-eth0 for static IP
as my company does not allow DHCP. I've use virt-customize to set default root
password.
How can I set static IP and root password when creating VM? Currently, I use
virt-edit, virt-customize after I set saslpasswd2 on image files of oVirt, and
it seems not best practice.
Best Regards.
Minseok Jang
___
Users mailing list --users@ovirt.org
To unsubscribe send an email tousers-le...@ovirt.org
Privacy Statement:https://www.ovirt.org/privacy-policy.html
oVirt Code of
Conduct:https://www.ovirt.org/community/about/community-guidelines/
List
Archives:https://lists.ovirt.org/archives/list/users@ovirt.org/message/5B4KZKEOD6JHE5L6T7E4775F4SST3QBI/___
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/NDAIGGTO4I3PGHBLI6JTNXRFVKIE6R5G/
[ovirt-users] virtio-net name enp1s0 and not expected ens3
Hallo, looking for some hint where one can change the guest network name (not with udev rules) but rather is there somewhere a code in ovirt/libvirt? We have one from scratch installed ovirt engine (4.4.10.4-1.el8), where all guests have enp*s* network name, all others engines (like 13 upgraded recently from 4.3.10 to 4.4.10) have ens* network name. In redhat KB https://access.redhat.com/solutions/3709641 is explained how is the naming of virtio-net working What is also different, there is missing ID_NET_NAME_SLOT in udevadm output: ~]$ udevadm info /sys/class/net/enp1s0/ P: /devices/pci:00/:00:02.0/:01:00.0/virtio0/net/enp1s0 E: DEVPATH=/devices/pci:00/:00:02.0/:01:00.0/virtio0/net/enp1s0 E: ID_BUS=pci E: ID_MODEL_FROM_DATABASE=Virtio network device E: ID_MODEL_ID=0x1041 E: ID_NET_DRIVER=virtio_net E: ID_NET_LINK_FILE=/usr/lib/systemd/network/99-default.link E: ID_NET_NAME=enp1s0 E: ID_NET_NAME_MAC=enx001a4a08000e E: ID_NET_NAME_PATH=enp1s0 E: ID_NET_NAMING_SCHEME=rhel-8.0 E: ID_OUI_FROM_DATABASE=Qumranet Inc. E: ID_PATH=pci-:01:00.0 E: ID_PATH_TAG=pci-_01_00_0 E: ID_PCI_CLASS_FROM_DATABASE=Network controller E: ID_PCI_SUBCLASS_FROM_DATABASE=Ethernet controller E: ID_VENDOR_FROM_DATABASE=Red Hat, Inc. E: ID_VENDOR_ID=0x1af4 E: IFINDEX=2 E: INTERFACE=enp1s0 E: SUBSYSTEM=net E: SYSTEMD_ALIAS=/sys/subsystem/net/devices/enp1s0 E: TAGS=:systemd: E: USEC_INITIALIZED=3826556 Expected output of udeavm would be: ~]$ udevadm info /sys/class/net/ens3 P: /devices/pci:00/:00:03.0/virtio0/net/ens3 E: DEVPATH=/devices/pci:00/:00:03.0/virtio0/net/ens3 E: ID_BUS=pci E: ID_MODEL_FROM_DATABASE=Virtio network device E: ID_MODEL_ID=0x1000 E: ID_NET_DRIVER=virtio_net E: ID_NET_LINK_FILE=/usr/lib/systemd/network/99-default.link E: ID_NET_NAME=ens3 E: ID_NET_NAME_MAC=enx001a4a070167 E: ID_NET_NAME_PATH=enp0s3 E: ID_NET_NAME_SLOT=ens3 E: ID_NET_NAMING_SCHEME=rhel-8.0 E: ID_OUI_FROM_DATABASE=Qumranet Inc. E: ID_PATH=pci-:00:03.0 E: ID_PATH_TAG=pci-_00_03_0 E: ID_PCI_CLASS_FROM_DATABASE=Network controller E: ID_PCI_SUBCLASS_FROM_DATABASE=Ethernet controller E: ID_VENDOR_FROM_DATABASE=Red Hat, Inc. E: ID_VENDOR_ID=0x1af4 E: IFINDEX=2 E: INTERFACE=ens3 E: SUBSYSTEM=net E: SYSTEMD_ALIAS=/sys/subsystem/net/devices/ens3 E: TAGS=:systemd: E: USEC_INITIALIZED=3487875 Tested with different OSes like centos/debian, always the same output. -- Ladislav Humenik ___ 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/RXC6B7YBJABFQBNVSQMNANCOB7KPJGWL/
[ovirt-users] virtio-net name enp1s0 and not expected ens3
Hallo, looking for some hint where one can change the guest network name (not with udev rules) but rather is there somewhere a code in ovirt/libvirt? We have one from scratch installed ovirt engine (4.4.10.4-1.el8), where all guests have enp*s* network name, all others engines (like 13 upgraded recently from 4.3.10 to 4.4.10) have ens* network name. In redhat KB https://access.redhat.com/solutions/3709641 is explained how is the naming of virtio-net working What is also different, there is missing ID_NET_NAME_SLOT in udevadm output: ~]$ udevadm info /sys/class/net/enp1s0/ P: /devices/pci:00/:00:02.0/:01:00.0/virtio0/net/enp1s0 E: DEVPATH=/devices/pci:00/:00:02.0/:01:00.0/virtio0/net/enp1s0 E: ID_BUS=pci E: ID_MODEL_FROM_DATABASE=Virtio network device E: ID_MODEL_ID=0x1041 E: ID_NET_DRIVER=virtio_net E: ID_NET_LINK_FILE=/usr/lib/systemd/network/99-default.link E: ID_NET_NAME=enp1s0 E: ID_NET_NAME_MAC=enx001a4a08000e E: ID_NET_NAME_PATH=enp1s0 E: ID_NET_NAMING_SCHEME=rhel-8.0 E: ID_OUI_FROM_DATABASE=Qumranet Inc. E: ID_PATH=pci-:01:00.0 E: ID_PATH_TAG=pci-_01_00_0 E: ID_PCI_CLASS_FROM_DATABASE=Network controller E: ID_PCI_SUBCLASS_FROM_DATABASE=Ethernet controller E: ID_VENDOR_FROM_DATABASE=Red Hat, Inc. E: ID_VENDOR_ID=0x1af4 E: IFINDEX=2 E: INTERFACE=enp1s0 E: SUBSYSTEM=net E: SYSTEMD_ALIAS=/sys/subsystem/net/devices/enp1s0 E: TAGS=:systemd: E: USEC_INITIALIZED=3826556 Expected output of udeavm would be: ~]$ udevadm info /sys/class/net/ens3 P: /devices/pci:00/:00:03.0/virtio0/net/ens3 E: DEVPATH=/devices/pci:00/:00:03.0/virtio0/net/ens3 E: ID_BUS=pci E: ID_MODEL_FROM_DATABASE=Virtio network device E: ID_MODEL_ID=0x1000 E: ID_NET_DRIVER=virtio_net E: ID_NET_LINK_FILE=/usr/lib/systemd/network/99-default.link E: ID_NET_NAME=ens3 E: ID_NET_NAME_MAC=enx001a4a070167 E: ID_NET_NAME_PATH=enp0s3 E: ID_NET_NAME_SLOT=ens3 E: ID_NET_NAMING_SCHEME=rhel-8.0 E: ID_OUI_FROM_DATABASE=Qumranet Inc. E: ID_PATH=pci-:00:03.0 E: ID_PATH_TAG=pci-_00_03_0 E: ID_PCI_CLASS_FROM_DATABASE=Network controller E: ID_PCI_SUBCLASS_FROM_DATABASE=Ethernet controller E: ID_VENDOR_FROM_DATABASE=Red Hat, Inc. E: ID_VENDOR_ID=0x1af4 E: IFINDEX=2 E: INTERFACE=ens3 E: SUBSYSTEM=net E: SYSTEMD_ALIAS=/sys/subsystem/net/devices/ens3 E: TAGS=:systemd: E: USEC_INITIALIZED=3487875 Tested with different OSes like centos/debian, always the same output. -- Ladislav Humenik Systemadministrator / VI IT Operations Hosting Infrastructure IONOS SE | Hinterm Hauptbahnhof 5 | 76137 Karlsruhe | Deutschland ___ 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/7PG34SHGCR22QUR3YMUUSRO22J7JQGSC/
[ovirt-users] SSO error during hosted engine deployment with 4.5.1
On the final setup of using the cockpit ovirt wizard to install the hosted
engine with 4.5.1, this occurs:
[ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Obtain SSO token using
username/password credentials]
[ ERROR ] fatal: [localhost]: FAILED! => {"msg": "The field 'environment'
has an invalid value, which includes an undefined variable. The error was:
'he_admin_username' is undefined\n\nThe error appears to be in
'/usr/share/ansible/collections/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/auth_sso.yml':
line 2, column 3, but may\nbe elsewhere in the file depending on the exact
syntax problem.\n\nThe offending line appears to be:\n\n---\n- name: Obtain
SSO token using username/password credentials\n ^ here\n"}
___
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/UHEK3DEX46R57BF6WJF3UKXXLUKYGEAY/
[ovirt-users] Re: 4.5.1 hyperconverged install failure "No valid network interface has been found"
I figured it out: I noticed that the cockpit was running this command: /usr/bin/python3.8 /usr/bin/ansible-playbook /usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml --tags=get_network_interfaces --skip-tags=always -e he_just_collect_network_interfaces=True --module-path=/usr/share/ovirt-hosted-engine-setup/ansible --inventory=localhost ERROR! the playbook: /usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml could not be found The directory "/usr/share/ovirt-hosted-engine-setup/ansible" doesn't exist. It looks like it was renamed to "/usr/share/ovirt-hosted-engine-setup/he_ansible" This command that I ran on all three nodes worked around the bug: ln -s /usr/share/ovirt-hosted-engine-setup/he_ansible/ /usr/share/ovirt-hosted-engine-setup/ansible I created a pull request https://github.com/oVirt/cockpit-ovirt/pull/27/commits Thanks, Dax Kelson On Wed, Jul 6, 2022 at 3:03 PM Dax Kelson wrote: > TL;DR hyperconverged install. Gluster install works, hosted engine fails > with "no valid network interface has ben found" > > I have a three node hyperconverged cluster that had previously been > running oVirt 4.4 successfully. > > A fully wipe and clean install of 4.5.1 was attempted with: > > ovirt-node-ng-installer-4.5.1-2022062306.el8.iso > > On each node, there are two statically configured 10Gb ethernet interfaces > (and some unused 1Gb interfaces) > > enp5s0f0 - ovirt management/VM network (default gateway is on this network) > enp5s0f1 - gluster network (isolated network) > > Name resolution is done via /etc/hosts on each node: > > 100.64.0.7 node1-ovirt node1-ovirt.local > 100.64.0.8 node2-ovirt node2-ovirt.local > 100.64.0.9 node3-ovirt node3-ovirt.local > 100.79.192.1 node1-ovirt-storage node1-ovirt-storage.local > 100.79.192.2 node2-ovirt-storage node2-ovirt-storage.local > 100.79.192.3 node3-ovirt-storage node3-ovirt-storage.local > > Attempting to install the hosted engine fails with: > > *System data could not be retrieved!* > *No valid network interface has been found* > *If you are using Bonds or VLANs Use the following naming conventions:* > - VLAN interfaces: physical_device.VLAN_ID (for example, eth0.23, > eth1.128, enp3s0.50) > - Bond interfaces: bond*number* (for example, bond0, bond1) > - VLANs on bond interfaces: bond*number*.VLAN_ID (for example, bond0.50, > bond1.128) > * Supported bond modes: active-backup, balance-xor, broadcast, 802.3ad > * Networking teaming is not supported and will cause errors > Here is the network setup on node1: > > [root@node1-ovirt ovirt]# ip -4 addr ls > 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group > default qlen 1000 > inet 127.0.0.1/8 scope host lo >valid_lft forever preferred_lft forever > 6: enp5s0f0: mtu 1500 qdisc mq state UP > group default qlen 1000 > inet 100.64.0.7/20 brd 100.64.15.255 scope global noprefixroute > enp5s0f0 >valid_lft forever preferred_lft forever > 7: enp5s0f1: mtu 1500 qdisc mq state UP > group default qlen 1000 > inet 100.79.192.1/24 brd 100.79.192.255 scope global noprefixroute > enp5s0f1 >valid_lft forever preferred_lft forever > 8: virbr0: mtu 1500 qdisc noqueue > state DOWN group default qlen 1000 > inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0 >valid_lft forever preferred_lft forever > [root@node1-ovirt ovirt]# > > My troubleshooting is that the failure is /probably/ coming from this > file, but I'm not sure why: > > > /usr/share/ansible/collections/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/pre_checks/001_validate_network_interfaces.yml > > Help? > > Thanks! > Dax Kelson > ___ 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/HCCTIEBCG5MHIPR4QUXQBZN7QOW3FV4B/
[ovirt-users] 4.5.1 hyperconverged install failure "No valid network interface has been found"
TL;DR hyperconverged install. Gluster install works, hosted engine fails with "no valid network interface has ben found" I have a three node hyperconverged cluster that had previously been running oVirt 4.4 successfully. A fully wipe and clean install of 4.5.1 was attempted with: ovirt-node-ng-installer-4.5.1-2022062306.el8.iso On each node, there are two statically configured 10Gb ethernet interfaces (and some unused 1Gb interfaces) enp5s0f0 - ovirt management/VM network (default gateway is on this network) enp5s0f1 - gluster network (isolated network) Name resolution is done via /etc/hosts on each node: 100.64.0.7 node1-ovirt node1-ovirt.local 100.64.0.8 node2-ovirt node2-ovirt.local 100.64.0.9 node3-ovirt node3-ovirt.local 100.79.192.1 node1-ovirt-storage node1-ovirt-storage.local 100.79.192.2 node2-ovirt-storage node2-ovirt-storage.local 100.79.192.3 node3-ovirt-storage node3-ovirt-storage.local Attempting to install the hosted engine fails with: *System data could not be retrieved!* *No valid network interface has been found* *If you are using Bonds or VLANs Use the following naming conventions:* - VLAN interfaces: physical_device.VLAN_ID (for example, eth0.23, eth1.128, enp3s0.50) - Bond interfaces: bond*number* (for example, bond0, bond1) - VLANs on bond interfaces: bond*number*.VLAN_ID (for example, bond0.50, bond1.128) * Supported bond modes: active-backup, balance-xor, broadcast, 802.3ad * Networking teaming is not supported and will cause errors Here is the network setup on node1: [root@node1-ovirt ovirt]# ip -4 addr ls 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever 6: enp5s0f0: mtu 1500 qdisc mq state UP group default qlen 1000 inet 100.64.0.7/20 brd 100.64.15.255 scope global noprefixroute enp5s0f0 valid_lft forever preferred_lft forever 7: enp5s0f1: mtu 1500 qdisc mq state UP group default qlen 1000 inet 100.79.192.1/24 brd 100.79.192.255 scope global noprefixroute enp5s0f1 valid_lft forever preferred_lft forever 8: virbr0: mtu 1500 qdisc noqueue state DOWN group default qlen 1000 inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0 valid_lft forever preferred_lft forever [root@node1-ovirt ovirt]# My troubleshooting is that the failure is /probably/ coming from this file, but I'm not sure why: /usr/share/ansible/collections/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/pre_checks/001_validate_network_interfaces.yml Help? Thanks! Dax Kelson ___ 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/XFAEMTNJBX3VOQ4NOPCEV52ETXBSLSMS/
[ovirt-users] vm backup, vprotect, user permissions
Hi, I would like to ask about thepermission for ht e vPortect to backup the VMs. We have got 4 hypervisors in 1 DC for production and use admin account for backup. Recently we added 3 more hypervisors for TEST/DEV. These new hypervisors are in separate DC. As the vProtect got licence only for 4 hosts, we would like to create new user for taking backup only for the production DC. We added vprotect user. Add the DatacenterAdmin toe that users only for production DC, but this do not works, the problems are - the vprotect user see all hosts ;( - the backup are not able to finish, seems that some permission is still missing Does anyone let me help with such a setup? regards Peter ___ 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/3OVKRLHLXIMUOSYAOC7DY22SAYCDIQYF/
