August 2019 - Users - oVirt List Archives

Problem with cloud-init (metrics install)
by Chris Adams 13 Aug '19

13 Aug '19

I am trying to set up the oVirt Metrics Store, which uses cloud-init for network settings, so I set the info under the "Initial Run" tab. However, it doesn't seem to actually apply the network settings unless I "run once" and enable clout-init there. I haven't used cloud-init before (been on my to-do list to check out) - am I missing something? -- Chris Adams <cma(a)cmadams.net>

4 8

Re: Inconsistent metadata on VM's disks
by Strahil 13 Aug '19

13 Aug '19

I see only inconsistent VG errors... Most probably it is CentOS specific. Best Regards, Strahil NikolovOn Aug 13, 2019 12:03, Nardus Geldenhuys <nardusg(a)gmail.com> wrote: > > Hi There > > Hope you are all well. We got this weird issue at the moment. Let me explain. > > We are on ovirt 4.3.5. We use Centos 7.6 and when we do an update on the VM's the VM's can not boot into multi user mode. It complains that the root mount can't be found. When you boot using ISO and rescue mode you can see the disks. When you chroot into the VM and run pvscan twice your VM can be rebooted and it is fixed. We don't know if this is Centos based or maybe something on ovirt. Screenshots below. Any help would be appreciated. > > > > >

1 0

LDAPS-Config
by Budur Nagaraju 13 Aug '19

13 Aug '19

Hi Can someone help in configuring LDAPs authentication in oVirt3.5 ? Thanks, Nagaraju

1 0

Installing new oVirt node fails
by Winfried de Heiden 12 Aug '19

12 Aug '19

2 3

upgrading ovirt 4.2.8 to 4.3.5
by Cole Johnson 12 Aug '19

12 Aug '19

I am trying to upgrade ovirt on a standalone ovirt node host, and when I run # yum install http://resources.ovirt.org/pub/yum-repo/ovirt-release43.rpm I get: # yum install http://resources.ovirt.o : package_upload, product-id, search-disabled-repos, subscription- : manager, vdsmupgrade This system is not registered with an entitlement server. You can use subscription-manager to register. Repository centos-sclo-rh-release is listed more than once in the configuration Examining /var/tmp/yum-root-sbzUPq/ovirt-release43.rpm: ovirt-release43-4.3.5.1-1.el7.noarch /var/tmp/yum-root-sbzUPq/ovirt-release43.rpm: does not update installed package. Loading mirror speeds from cached hostfile * ovirt-4.2-epel: d2lzkl7pfhq30w.cloudfront.net * ovirt-4.3: resources.ovirt.org * ovirt-4.3-epel: d2lzkl7pfhq30w.cloudfront.net No package ovirt-release43.txt available. Error: Nothing to do Uploading Enabled Repositories Report Loaded plugins: fastestmirror, product-id, subscription-manager This system is not registered with an entitlement server. You can use subscription-manager to register. Repository centos-sclo-rh-release is listed more than once in the configuration Cannot upload enabled repos report, is this client registered? rg/pub/yum-repo/ovirt-release43.rpm and then running # yum update "ovirt-*-setup*" I get: Loaded plugins: enabled_repos_upload, fastestmirror, imgbased-persist, : package_upload, product-id, search-disabled-repos, subscription- : manager, vdsmupgrade This system is not registered with an entitlement server. You can use subscription-manager to register. Repository centos-sclo-rh-release is listed more than once in the configuration Loading mirror speeds from cached hostfile * ovirt-4.2-epel: d2lzkl7pfhq30w.cloudfront.net * ovirt-4.3: resources.ovirt.org * ovirt-4.3-epel: d2lzkl7pfhq30w.cloudfront.net Resolving Dependencies --> Running transaction check ---> Package ovirt-hosted-engine-setup.noarch 0:2.2.33-1.el7 will be updated ---> Package ovirt-hosted-engine-setup.noarch 0:2.3.11-1.el7 will be an update --> Processing Dependency: otopi >= 1.8 for package: ovirt-hosted-engine-setup-2.3.11-1.el7.noarch --> Processing Dependency: ovirt-ansible-engine-setup >= 1.1.9 for package: ovirt-hosted-engine-setup-2.3.11-1.el7.noarc h --> Processing Dependency: ovirt-ansible-hosted-engine-setup >= 1.0.21 for package: ovirt-hosted-engine-setup-2.3.11-1.e l7.noarch --> Processing Dependency: ovirt-ansible-repositories >= 1.1.5 for package: ovirt-hosted-engine-setup-2.3.11-1.el7.noarc h --> Processing Dependency: ovirt-host >= 4.3 for package: ovirt-hosted-engine-setup-2.3.11-1.el7.noarch --> Processing Dependency: ovirt-host-deploy >= 1.8 for package: ovirt-hosted-engine-setup-2.3.11-1.el7.noarch --> Processing Dependency: ovirt-hosted-engine-ha >= 2.3.3 for package: ovirt-hosted-engine-setup-2.3.11-1.el7.noarch --> Processing Dependency: vdsm-python >= 4.30 for package: ovirt-hosted-engine-setup-2.3.11-1.el7.noarch --> Processing Dependency: vdsm-python >= 4.30 for package: ovirt-hosted-engine-setup-2.3.11-1.el7.noarch --> Running transaction check ---> Package otopi.noarch 0:1.7.8-1.el7 will be obsoleted ---> Package ovirt-ansible-engine-setup.noarch 0:1.1.9-1.el7 will be installed ---> Package ovirt-ansible-hosted-engine-setup.noarch 0:1.0.26-1.el7 will be installed ---> Package ovirt-ansible-repositories.noarch 0:1.1.5-1.el7 will be installed ---> Package ovirt-host.x86_64 0:4.2.3-1.el7 will be updated ---> Package ovirt-host.x86_64 0:4.3.4-1.el7 will be an update --> Processing Dependency: ovirt-host-dependencies = 4.3.4-1.el7 for package: ovirt-host-4.3.4-1.el7.x86_64 --> Processing Dependency: aide for package: ovirt-host-4.3.4-1.el7.x86_64 --> Processing Dependency: iperf3 for package: ovirt-host-4.3.4-1.el7.x86_64 --> Processing Dependency: libvirt-admin for package: ovirt-host-4.3.4-1.el7.x86_64 --> Processing Dependency: openscap for package: ovirt-host-4.3.4-1.el7.x86_64 --> Processing Dependency: openscap-utils for package: ovirt-host-4.3.4-1.el7.x86_64 --> Processing Dependency: pam_pkcs11 for package: ovirt-host-4.3.4-1.el7.x86_64 --> Processing Dependency: scap-security-guide for package: ovirt-host-4.3.4-1.el7.x86_64 ---> Package ovirt-host-deploy.noarch 0:1.7.4-1.el7 will be obsoleted ---> Package ovirt-hosted-engine-ha.noarch 0:2.2.19-1.el7 will be updated ---> Package ovirt-hosted-engine-ha.noarch 0:2.3.3-1.el7 will be an update --> Processing Dependency: vdsm >= 4.30.11 for package: ovirt-hosted-engine-ha-2.3.3-1.el7.noarch --> Processing Dependency: vdsm >= 4.30.11 for package: ovirt-hosted-engine-ha-2.3.3-1.el7.noarch --> Processing Dependency: vdsm-client >= 4.30.11 for package: ovirt-hosted-engine-ha-2.3.3-1.el7.noarch ---> Package python2-otopi.noarch 0:1.8.3-1.el7 will be obsoleting --> Processing Dependency: otopi-common = 1.8.3-1.el7 for package: python2-otopi-1.8.3-1.el7.noarch ---> Package python2-ovirt-host-deploy.noarch 0:1.8.0-1.el7 will be obsoleting --> Processing Dependency: ovirt-host-deploy-common = 1.8.0-1.el7 for package: python2-ovirt-host-deploy-1.8.0-1.el7.noa rch ---> Package vdsm-python.noarch 0:4.20.46-1.el7 will be updated --> Processing Dependency: vdsm-python = 4.20.46-1.el7 for package: vdsm-jsonrpc-4.20.46-1.el7.noarch --> Processing Dependency: vdsm-python = 4.20.46-1.el7 for package: vdsm-http-4.20.46-1.el7.noarch ---> Package vdsm-python.noarch 0:4.30.24-1.el7 will be an update --> Processing Dependency: vdsm-api = 4.30.24-1.el7 for package: vdsm-python-4.30.24-1.el7.noarch --> Processing Dependency: vdsm-common = 4.30.24-1.el7 for package: vdsm-python-4.30.24-1.el7.noarch --> Processing Dependency: vdsm-network = 4.30.24-1.el7 for package: vdsm-python-4.30.24-1.el7.noarch --> Running transaction check ---> Package otopi-common.noarch 0:1.8.3-1.el7 will be installed ---> Package ovirt-host.x86_64 0:4.3.4-1.el7 will be an update --> Processing Dependency: aide for package: ovirt-host-4.3.4-1.el7.x86_64 --> Processing Dependency: iperf3 for package: ovirt-host-4.3.4-1.el7.x86_64 --> Processing Dependency: libvirt-admin for package: ovirt-host-4.3.4-1.el7.x86_64 --> Processing Dependency: openscap for package: ovirt-host-4.3.4-1.el7.x86_64 --> Processing Dependency: openscap-utils for package: ovirt-host-4.3.4-1.el7.x86_64 --> Processing Dependency: pam_pkcs11 for package: ovirt-host-4.3.4-1.el7.x86_64 --> Processing Dependency: scap-security-guide for package: ovirt-host-4.3.4-1.el7.x86_64 ---> Package ovirt-host-dependencies.x86_64 0:4.2.3-1.el7 will be updated ---> Package ovirt-host-dependencies.x86_64 0:4.3.4-1.el7 will be an update --> Processing Dependency: collectd-write_syslog for package: ovirt-host-dependencies-4.3.4-1.el7.x86_64 --> Processing Dependency: liblognorm for package: ovirt-host-dependencies-4.3.4-1.el7.x86_64 --> Processing Dependency: rsyslog-elasticsearch for package: ovirt-host-dependencies-4.3.4-1.el7.x86_64 --> Processing Dependency: rsyslog-mmjsonparse for package: ovirt-host-dependencies-4.3.4-1.el7.x86_64 --> Processing Dependency: rsyslog-mmnormalize for package: ovirt-host-dependencies-4.3.4-1.el7.x86_64 --> Processing Dependency: v2v-conversion-host-wrapper for package: ovirt-host-dependencies-4.3.4-1.el7.x86_64 ---> Package ovirt-host-deploy-common.noarch 0:1.8.0-1.el7 will be installed ---> Package vdsm.x86_64 0:4.20.46-1.el7 will be updated --> Processing Dependency: vdsm = 4.20.46-1.el7 for package: vdsm-hook-ethtool-options-4.20.46-1.el7.noarch --> Processing Dependency: vdsm = 4.20.46-1.el7 for package: vdsm-hook-vmfex-dev-4.20.46-1.el7.noarch --> Processing Dependency: vdsm = 4.20.46-1.el7 for package: vdsm-gluster-4.20.46-1.el7.x86_64 --> Processing Dependency: vdsm = 4.20.46-1.el7 for package: vdsm-hook-fcoe-4.20.46-1.el7.noarch ---> Package vdsm.x86_64 0:4.30.24-1.el7 will be an update --> Processing Dependency: kernel >= 3.10.0-957.12.2.el7 for package: vdsm-4.30.24-1.el7.x86_64 --> Processing Dependency: libvirt-daemon-kvm >= 4.5.0-10.el7_6.9 for package: vdsm-4.30.24-1.el7.x86_64 --> Processing Dependency: qemu-kvm-rhev >= 10:2.12.0-18.el7_6.5 for package: vdsm-4.30.24-1.el7.x86_64 ---> Package vdsm-api.noarch 0:4.20.46-1.el7 will be updated ---> Package vdsm-api.noarch 0:4.30.24-1.el7 will be an update ---> Package vdsm-client.noarch 0:4.20.46-1.el7 will be updated ---> Package vdsm-client.noarch 0:4.30.24-1.el7 will be an update --> Processing Dependency: vdsm-yajsonrpc = 4.30.24-1.el7 for package: vdsm-client-4.30.24-1.el7.noarch ---> Package vdsm-common.noarch 0:4.20.46-1.el7 will be updated ---> Package vdsm-common.noarch 0:4.30.24-1.el7 will be an update ---> Package vdsm-http.noarch 0:4.20.46-1.el7 will be updated ---> Package vdsm-http.noarch 0:4.30.24-1.el7 will be an update ---> Package vdsm-jsonrpc.noarch 0:4.20.46-1.el7 will be updated ---> Package vdsm-jsonrpc.noarch 0:4.30.24-1.el7 will be an update ---> Package vdsm-network.x86_64 0:4.20.46-1.el7 will be updated ---> Package vdsm-network.x86_64 0:4.30.24-1.el7 will be an update --> Running transaction check ---> Package collectd-write_syslog.x86_64 0:5.8.1-4.el7 will be installed --> Processing Dependency: collectd(x86-64) = 5.8.1-4.el7 for package: collectd-write_syslog-5.8.1-4.el7.x86_64 ---> Package ovirt-host.x86_64 0:4.3.4-1.el7 will be an update --> Processing Dependency: aide for package: ovirt-host-4.3.4-1.el7.x86_64 --> Processing Dependency: iperf3 for package: ovirt-host-4.3.4-1.el7.x86_64 --> Processing Dependency: libvirt-admin for package: ovirt-host-4.3.4-1.el7.x86_64 --> Processing Dependency: openscap for package: ovirt-host-4.3.4-1.el7.x86_64 --> Processing Dependency: openscap-utils for package: ovirt-host-4.3.4-1.el7.x86_64 --> Processing Dependency: pam_pkcs11 for package: ovirt-host-4.3.4-1.el7.x86_64 --> Processing Dependency: scap-security-guide for package: ovirt-host-4.3.4-1.el7.x86_64 ---> Package ovirt-host-dependencies.x86_64 0:4.3.4-1.el7 will be an update --> Processing Dependency: liblognorm for package: ovirt-host-dependencies-4.3.4-1.el7.x86_64 --> Processing Dependency: rsyslog-elasticsearch for package: ovirt-host-dependencies-4.3.4-1.el7.x86_64 --> Processing Dependency: rsyslog-mmjsonparse for package: ovirt-host-dependencies-4.3.4-1.el7.x86_64 --> Processing Dependency: rsyslog-mmnormalize for package: ovirt-host-dependencies-4.3.4-1.el7.x86_64 ---> Package qemu-kvm-ev.x86_64 10:2.12.0-18.el7_6.3.1 will be updated ---> Package qemu-kvm-ev.x86_64 10:2.12.0-18.el7_6.7.1 will be an update --> Processing Dependency: qemu-kvm-common-ev = 10:2.12.0-18.el7_6.7.1 for package: 10:qemu-kvm-ev-2.12.0-18.el7_6.7.1.x 86_64 --> Processing Dependency: qemu-img-ev = 10:2.12.0-18.el7_6.7.1 for package: 10:qemu-kvm-ev-2.12.0-18.el7_6.7.1.x86_64 ---> Package v2v-conversion-host-wrapper.noarch 0:1.14.2-1.el7 will be installed --> Processing Dependency: libcgroup-tools for package: v2v-conversion-host-wrapper-1.14.2-1.el7.noarch ---> Package vdsm.x86_64 0:4.30.24-1.el7 will be an update --> Processing Dependency: kernel >= 3.10.0-957.12.2.el7 for package: vdsm-4.30.24-1.el7.x86_64 --> Processing Dependency: libvirt-daemon-kvm >= 4.5.0-10.el7_6.9 for package: vdsm-4.30.24-1.el7.x86_64 ---> Package vdsm-gluster.x86_64 0:4.20.46-1.el7 will be updated ---> Package vdsm-gluster.x86_64 0:4.30.24-1.el7 will be an update ---> Package vdsm-hook-ethtool-options.noarch 0:4.20.46-1.el7 will be updated ---> Package vdsm-hook-ethtool-options.noarch 0:4.30.24-1.el7 will be an update ---> Package vdsm-hook-fcoe.noarch 0:4.20.46-1.el7 will be updated ---> Package vdsm-hook-fcoe.noarch 0:4.30.24-1.el7 will be an update ---> Package vdsm-hook-vmfex-dev.noarch 0:4.20.46-1.el7 will be updated ---> Package vdsm-hook-vmfex-dev.noarch 0:4.30.24-1.el7 will be an update ---> Package vdsm-yajsonrpc.noarch 0:4.20.46-1.el7 will be updated ---> Package vdsm-yajsonrpc.noarch 0:4.30.24-1.el7 will be an update --> Running transaction check ---> Package collectd.x86_64 0:5.8.1-2.el7 will be updated --> Processing Dependency: collectd(x86-64) = 5.8.1-2.el7 for package: collectd-virt-5.8.1-2.el7.x86_64 --> Processing Dependency: collectd(x86-64) = 5.8.1-2.el7 for package: collectd-write_http-5.8.1-2.el7.x86_64 --> Processing Dependency: collectd(x86-64) = 5.8.1-2.el7 for package: collectd-disk-5.8.1-2.el7.x86_64 --> Processing Dependency: collectd(x86-64) = 5.8.1-2.el7 for package: collectd-netlink-5.8.1-2.el7.x86_64 ---> Package collectd.x86_64 0:5.8.1-4.el7 will be an update ---> Package ovirt-host.x86_64 0:4.3.4-1.el7 will be an update --> Processing Dependency: aide for package: ovirt-host-4.3.4-1.el7.x86_64 --> Processing Dependency: iperf3 for package: ovirt-host-4.3.4-1.el7.x86_64 --> Processing Dependency: libvirt-admin for package: ovirt-host-4.3.4-1.el7.x86_64 --> Processing Dependency: openscap for package: ovirt-host-4.3.4-1.el7.x86_64 --> Processing Dependency: openscap-utils for package: ovirt-host-4.3.4-1.el7.x86_64 --> Processing Dependency: pam_pkcs11 for package: ovirt-host-4.3.4-1.el7.x86_64 --> Processing Dependency: scap-security-guide for package: ovirt-host-4.3.4-1.el7.x86_64 ---> Package ovirt-host-dependencies.x86_64 0:4.3.4-1.el7 will be an update --> Processing Dependency: liblognorm for package: ovirt-host-dependencies-4.3.4-1.el7.x86_64 --> Processing Dependency: rsyslog-elasticsearch for package: ovirt-host-dependencies-4.3.4-1.el7.x86_64 --> Processing Dependency: rsyslog-mmjsonparse for package: ovirt-host-dependencies-4.3.4-1.el7.x86_64 --> Processing Dependency: rsyslog-mmnormalize for package: ovirt-host-dependencies-4.3.4-1.el7.x86_64 ---> Package qemu-img-ev.x86_64 10:2.12.0-18.el7_6.3.1 will be updated ---> Package qemu-img-ev.x86_64 10:2.12.0-18.el7_6.7.1 will be an update ---> Package qemu-kvm-common-ev.x86_64 10:2.12.0-18.el7_6.3.1 will be updated ---> Package qemu-kvm-common-ev.x86_64 10:2.12.0-18.el7_6.7.1 will be an update ---> Package v2v-conversion-host-wrapper.noarch 0:1.14.2-1.el7 will be installed --> Processing Dependency: libcgroup-tools for package: v2v-conversion-host-wrapper-1.14.2-1.el7.noarch ---> Package vdsm.x86_64 0:4.30.24-1.el7 will be an update --> Processing Dependency: kernel >= 3.10.0-957.12.2.el7 for package: vdsm-4.30.24-1.el7.x86_64 --> Processing Dependency: libvirt-daemon-kvm >= 4.5.0-10.el7_6.9 for package: vdsm-4.30.24-1.el7.x86_64 --> Running transaction check ---> Package collectd-disk.x86_64 0:5.8.1-2.el7 will be updated ---> Package collectd-disk.x86_64 0:5.8.1-4.el7 will be an update ---> Package collectd-netlink.x86_64 0:5.8.1-2.el7 will be updated ---> Package collectd-netlink.x86_64 0:5.8.1-4.el7 will be an update ---> Package collectd-virt.x86_64 0:5.8.1-2.el7 will be updated ---> Package collectd-virt.x86_64 0:5.8.1-4.el7 will be an update ---> Package collectd-write_http.x86_64 0:5.8.1-2.el7 will be updated ---> Package collectd-write_http.x86_64 0:5.8.1-4.el7 will be an update ---> Package ovirt-host.x86_64 0:4.3.4-1.el7 will be an update --> Processing Dependency: aide for package: ovirt-host-4.3.4-1.el7.x86_64 --> Processing Dependency: iperf3 for package: ovirt-host-4.3.4-1.el7.x86_64 --> Processing Dependency: libvirt-admin for package: ovirt-host-4.3.4-1.el7.x86_64 --> Processing Dependency: openscap for package: ovirt-host-4.3.4-1.el7.x86_64 --> Processing Dependency: openscap-utils for package: ovirt-host-4.3.4-1.el7.x86_64 --> Processing Dependency: pam_pkcs11 for package: ovirt-host-4.3.4-1.el7.x86_64 --> Processing Dependency: scap-security-guide for package: ovirt-host-4.3.4-1.el7.x86_64 --> Processing Dependency: liblognorm for package: ovirt-host-dependencies-4.3.4-1.el7.x86_64 --> Processing Dependency: rsyslog-elasticsearch for package: ovirt-host-dependencies-4.3.4-1.el7.x86_64 --> Processing Dependency: rsyslog-mmjsonparse for package: ovirt-host-dependencies-4.3.4-1.el7.x86_64 --> Processing Dependency: rsyslog-mmnormalize for package: ovirt-host-dependencies-4.3.4-1.el7.x86_64 ---> Package v2v-conversion-host-wrapper.noarch 0:1.14.2-1.el7 will be installed --> Processing Dependency: libcgroup-tools for package: v2v-conversion-host-wrapper-1.14.2-1.el7.noarch ---> Package vdsm.x86_64 0:4.30.24-1.el7 will be an update --> Processing Dependency: kernel >= 3.10.0-957.12.2.el7 for package: vdsm-4.30.24-1.el7.x86_64 --> Processing Dependency: libvirt-daemon-kvm >= 4.5.0-10.el7_6.9 for package: vdsm-4.30.24-1.el7.x86_64 --> Finished Dependency Resolution Error: Package: v2v-conversion-host-wrapper-1.14.2-1.el7.noarch (ovirt-4.3) Requires: libcgroup-tools Error: Package: ovirt-host-dependencies-4.3.4-1.el7.x86_64 (ovirt-4.3) Requires: rsyslog-mmjsonparse Error: Package: ovirt-host-dependencies-4.3.4-1.el7.x86_64 (ovirt-4.3) Requires: rsyslog-elasticsearch Error: Package: ovirt-host-4.3.4-1.el7.x86_64 (ovirt-4.3) Requires: openscap Error: Package: ovirt-host-4.3.4-1.el7.x86_64 (ovirt-4.3) Requires: libvirt-admin Error: Package: ovirt-host-4.3.4-1.el7.x86_64 (ovirt-4.3) Requires: scap-security-guide Error: Package: ovirt-host-4.3.4-1.el7.x86_64 (ovirt-4.3) Requires: aide Error: Package: ovirt-host-dependencies-4.3.4-1.el7.x86_64 (ovirt-4.3) Requires: rsyslog-mmnormalize Error: Package: ovirt-host-4.3.4-1.el7.x86_64 (ovirt-4.3) Requires: pam_pkcs11 Error: Package: ovirt-host-dependencies-4.3.4-1.el7.x86_64 (ovirt-4.3) Requires: liblognorm Error: Package: ovirt-host-4.3.4-1.el7.x86_64 (ovirt-4.3) Requires: openscap-utils Error: Package: ovirt-host-4.3.4-1.el7.x86_64 (ovirt-4.3) Requires: iperf3 Error: Package: vdsm-4.30.24-1.el7.x86_64 (ovirt-4.3) Requires: libvirt-daemon-kvm >= 4.5.0-10.el7_6.9 Installed: libvirt-daemon-kvm-4.5.0-10.el7_6.4.x86_64 (installed) libvirt-daemon-kvm = 4.5.0-10.el7_6.4 Error: Package: vdsm-4.30.24-1.el7.x86_64 (ovirt-4.3) Requires: kernel >= 3.10.0-957.12.2.el7 Installed: kernel-3.10.0-957.5.1.el7.x86_64 (installed) kernel = 3.10.0-957.5.1.el7 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest Uploading Enabled Repositories Report Loaded plugins: fastestmirror, product-id, subscription-manager This system is not registered with an entitlement server. You can use subscription-manager to register. Repository centos-sclo-rh-release is listed more than once in the configuration Cannot upload enabled repos report, is this client registered? Is there any idea on the dependencies that are not being found? Thanks for the help

2 1

oVirt 4.3.5 potential issue with NFS storage
by Vrgotic, Marko 11 Aug '19

11 Aug '19

Dear oVIrt, This is my third oVirt platform in the company, but first time I am seeing following logs: “2019-08-07 16:00:16,099Z INFO [org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-51) [1b85e637] Lock freed to object 'EngineLock:{exclusiveLocks='[2350ee82-94ed-4f90-9366-451e0104d1d6=PROVIDER]', sharedLocks=''}' 2019-08-07 16:00:25,618Z WARN [org.ovirt.engine.core.vdsbroker.irsbroker.IrsProxy] (EE-ManagedThreadFactory-engine-Thread-37723) [] domain 'bda97276-a399-448f-9113-017972f6b55a:ovirt_production' in problem 'PROBLEMATIC'. vds: 'ovirt-sj-05.ictv.com' 2019-08-07 16:00:40,630Z INFO [org.ovirt.engine.core.vdsbroker.irsbroker.IrsProxy] (EE-ManagedThreadFactory-engine-Thread-37735) [] Domain 'bda97276-a399-448f-9113-017972f6b55a:ovirt_production' recovered from problem. vds: 'ovirt-sj-05.ictv.com' 2019-08-07 16:00:40,652Z INFO [org.ovirt.engine.core.vdsbroker.irsbroker.IrsProxy] (EE-ManagedThreadFactory-engine-Thread-37737) [] Domain 'bda97276-a399-448f-9113-017972f6b55a:ovirt_production' recovered from problem. vds: 'ovirt-sj-01.ictv.com' 2019-08-07 16:00:40,652Z INFO [org.ovirt.engine.core.vdsbroker.irsbroker.IrsProxy] (EE-ManagedThreadFactory-engine-Thread-37737) [] Domain 'bda97276-a399-448f-9113-017972f6b55a:ovirt_production' has recovered from problem. No active host in the DC is reporting it as problematic, so clearing the domain recovery timer.” Can you help me understanding why is this being reported? This setup is: 5HOSTS, 3 in HA SelfHostedEngine Version 4.3.5 NFS based Netapp storage, version 4.1 “10.210.13.64:/ovirt_hosted_engine on /rhev/data-center/mnt/10.210.13.64:_ovirt__hosted__engine type nfs4 (rw,relatime,vers=4.1,rsize=65536,wsize=65536,namlen=255,soft,nosharecache,proto=tcp,timeo=600,retrans=6,sec=sys,clientaddr=10.210.11.14,local_lock=none,addr=10.210.13.64) 10.210.13.64:/ovirt_production on /rhev/data-center/mnt/10.210.13.64:_ovirt__production type nfs4 (rw,relatime,vers=4.1,rsize=65536,wsize=65536,namlen=255,soft,nosharecache,proto=tcp,timeo=600,retrans=6,sec=sys,clientaddr=10.210.11.14,local_lock=none,addr=10.210.13.64) tmpfs on /run/user/0 type tmpfs (rw,nosuid,nodev,relatime,seclabel,size=9878396k,mode=700)” First mount is SHE dedicated storage. Second mount “ovirt_produciton” is for other VM Guests. Kindly awaiting your reply. Marko Vrgotic

3 7

VM --- is not responding.
by Edoardo Mazza 11 Aug '19

11 Aug '19

Hi all, It is more days that for same vm I received this error, but I don't underdand why. The traffic of the virtual machine is not excessive, cpu and ram to, but for few minutes the vm is not responding. and in the messages log file of the vm I received the error under, yo can help me? thanks Edoardo kernel: NMI watchdog: BUG: soft lockup - CPU#2 stuck for 25s! [kworker/2:0:26227] Aug 8 02:51:11 vmmysql kernel: Modules linked in: binfmt_misc ip6t_rpfilter ipt_REJECT nf_reject_ipv4 ip6t_REJECT nf_reject_ ipv6 xt_conntrack ip_set nfnetlink ebtable_nat ebtable_broute bridge stp llc ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_ nat_ipv6 ip6table_mangle ip6table_security ip6table_raw iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_con ntrack iptable_mangle iptable_security iptable_raw ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter snd_hda_c odec_generic iosf_mbi crc32_pclmul ppdev ghash_clmulni_intel snd_hda_intel snd_hda_codec aesni_intel snd_hda_core lrw gf128mul glue_helper ablk_helper snd_hwdep cryptd snd_seq snd_seq_device snd_pcm snd_timer snd soundcore virtio_rng sg virtio_balloon i2c_piix4 parport_pc parport joydev pcspkr ip_tables xfs libcrc32c sd_mod Aug 8 02:51:14 vmmysql kernel: crc_t10dif crct10dif_generic sr_mod cdrom virtio_net virtio_console virtio_scsi ata_generic p ata_acpi crct10dif_pclmul crct10dif_common crc32c_intel serio_raw qxl floppy drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops ttm drm ata_piix libata virtio_pci drm_panel_orientation_quirks virtio_ring virtio dm_mirror dm_region_hash dm_log dm_mod Aug 8 02:51:14 vmmysql kernel: CPU: 2 PID: 26227 Comm: kworker/2:0 Kdump: loaded Tainted: G L ------------ 3.10.0-957.12.1.el7.x86_64 #1 Aug 8 02:51:14 vmmysql kernel: Hardware name: oVirt oVirt Node, BIOS 1.11.0-2.el7 04/01/2014 Aug 8 02:51:14 vmmysql kernel: Workqueue: events_freezable disk_events_workfn Aug 8 02:51:14 vmmysql kernel: task: ffff9e25b6609040 ti: ffff9e27b1610000 task.ti: ffff9e27b1610000 Aug 8 02:51:14 vmmysql kernel: RIP: 0010:[<ffffffffb8b6b355>] [<ffffffffb8b6b355>] _raw_spin_unlock_irqrestore+0x15/0x20 Aug 8 02:51:14 vmmysql kernel: RSP: 0000:ffff9e27b1613a68 EFLAGS: 00000286 Aug 8 02:51:14 vmmysql kernel: RAX: 0000000000000001 RBX: ffff9e27b1613a10 RCX: ffff9e27b72a3d05 Aug 8 02:51:14 vmmysql kernel: RDX: ffff9e27b729a420 RSI: 0000000000000286 RDI: 0000000000000286 Aug 8 02:51:14 vmmysql kernel: RBP: ffff9e27b1613a68 R08: 0000000000000001 R09: ffff9e25b67fc198 Aug 8 02:51:14 vmmysql kernel: R10: ffff9e27b45bd8d8 R11: 0000000000000000 R12: ffff9e25b67fde80 Aug 8 02:51:14 vmmysql kernel: R13: ffff9e25b67fc000 R14: ffff9e25b67fc158 R15: ffffffffc032f8e0 Aug 8 02:51:14 vmmysql kernel: FS: 0000000000000000(0000) GS:ffff9e27b7280000(0000) knlGS:0000000000000000 Aug 8 02:51:14 vmmysql kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Aug 8 02:51:14 vmmysql kernel: CR2: 00007f0c9e9b6008 CR3: 0000000232480000 CR4: 00000000003606e0 Aug 8 02:51:14 vmmysql kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Aug 8 02:51:14 vmmysql kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Aug 8 02:51:14 vmmysql kernel: Call Trace: Aug 8 02:51:14 vmmysql kernel: [<ffffffffc0323d65>] ata_scsi_queuecmd+0x155/0x450 [libata] Aug 8 02:51:14 vmmysql kernel: [<ffffffffc031fdb0>] ? ata_scsiop_inq_std+0xf0/0xf0 [libata] Aug 8 02:51:14 vmmysql kernel: [<ffffffffb88d14f0>] scsi_dispatch_cmd+0xb0/0x240 Aug 8 02:51:14 vmmysql kernel: [<ffffffffb88daa8c>] scsi_request_fn+0x4cc/0x680 Aug 8 02:51:14 vmmysql kernel: [<ffffffffb8743679>] __blk_run_queue+0x39/0x50 Aug 8 02:51:14 vmmysql kernel: [<ffffffffb874b6d5>] blk_execute_rq_nowait+0xb5/0x170 Aug 8 02:51:14 vmmysql kernel: [<ffffffffb874b81b>] blk_execute_rq+0x8b/0x150 Aug 8 02:51:14 vmmysql kernel: [<ffffffffb867d369>] ? bio_phys_segments+0x19/0x20 Aug 8 02:51:14 vmmysql kernel: [<ffffffffb8746cb1>] ? blk_rq_bio_prep+0x31/0xb0 Aug 8 02:51:14 vmmysql kernel: [<ffffffffb874b537>] ? blk_rq_map_kern+0xc7/0x180 Aug 8 02:51:14 vmmysql kernel: [<ffffffffb88d75b3>] scsi_execute+0xd3/0x170 Aug 8 02:51:14 vmmysql kernel: [<ffffffffb88d929e>] scsi_execute_req_flags+0x8e/0x100 Aug 8 02:51:14 vmmysql kernel: [<ffffffffc041431c>] sr_check_events+0xbc/0x2d0 [sr_mod] Aug 8 02:51:14 vmmysql kernel: [<ffffffffc036905e>] cdrom_check_events+0x1e/0x40 [cdrom] Aug 8 02:51:14 vmmysql kernel: [<ffffffffc04150b1>] sr_block_check_events+0xb1/0x120 [sr_mod] Aug 8 02:51:14 vmmysql kernel: [<ffffffffb8759276>] disk_check_events+0x66/0x190 Aug 8 02:51:14 vmmysql kernel: [<ffffffffb87593b6>] disk_events_workfn+0x16/0x20 Aug 8 02:51:14 vmmysql kernel: [<ffffffffb84b9d8f>] process_one_work+0x17f/0x440 Aug 8 02:51:14 vmmysql kernel: [<ffffffffb84bae26>] worker_thread+0x126/0x3c0 Aug 8 02:51:14 vmmysql kernel: [<ffffffffb84bad00>] ? manage_workers.isra.25+0x2a0/0x2a0 Aug 8 02:51:14 vmmysql kernel: [<ffffffffb84c1c71>] kthread+0xd1/0xe0 Aug 8 02:51:14 vmmysql kernel: [<ffffffffb84c1ba0>] ? insert_kthread_work+0x40/0x40 Aug 8 02:51:14 vmmysql kernel: [<ffffffffb8b75bf7>] ret_from_fork_nospec_begin+0x21/0x21 Aug 8 02:51:14 vmmysql kernel: [<ffffffffb84c1ba0>] ? insert_kthread_work+0x40/0x40 Aug 8 02:51:14 vmmysql kernel: Code: 14 25 10 43 03 b9 5d c3 0f 1f 40 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 ff 14 25 10 43 03 b9 48 89 f7 57 9d <0f> 1f 44 00 00 5d c3 0f 1f 40 00 0f 1f 44 00 00 55 48 89 e5 48

2 2

Re: oVirt 4.3.5.1 failed to configure management network on the host
by Strahil 09 Aug '19

09 Aug '19

You can't bond a bond, nor to layer a teaming device ontop a bond ... There was an article about that. If it worked - most probably it won't as you wish. Lacp can play active-backup based on aggregation group, but you need all NICs in the same LACP. Best Regards, Strahil NikolovOn Aug 9, 2019 10:22, Mitja Pirih <mitja(a)pirih.si> wrote: > > On 08. 08. 2019 11:42, Strahil wrote: > > > > LACP supports works with 2 switches, but if you wish to aggregate all > > links - you need switch support (high-end hardware). > > > > Best Regards, > > Strahil Nikolov > > > > I am aware of that. That's why my idea was to use bond1 (LACP) on eth1+2 > on switch1 and bond2 (LACP) on eth3+4 on switch2 and then team together > bond1 + bond2. With this config theoretically I should get bonding > spanned over two switches. Technically it worked, redundancy and > aggregation. > > The problem was deploying self-hosted engine, because the script was > unable to configure management network. > > If I use bonding spanned over two switches as you suggest, based on > documentation > https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/ht… > my options are: > - Mode 2 (XOR policy) > - Mode 5 (adaptive transmit load-balancing policy): no use of bridges > - Mode 6 (adaptive load-balancing policy): same limitation of mode 5 > > Basically only Mode 2 looks usable for us. > > > Regards, > Mitja > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/CCFVROZHDJ5UP…

1 0

Re: RFE: Add the ability to the engine to serve as a fencing proxy
by Strahil 09 Aug '19

09 Aug '19

I think poison pill-based fencing is easier to implement but it requires either Network-based (iSCSI or NFS) or FC-based shared storage. It is used in corosync/pacemaker clusters and is easier to implement. Best Regards, Strahil Nikolov On Aug 8, 2019 11:29, Sandro Bonazzola <sbonazzo(a)redhat.com> wrote: > > > > Il giorno ven 2 ago 2019 alle ore 10:50 Sandro E <feeds.sandro(a)gmail.com> ha scritto: >> >> Hi, >> >> i hope that this hits the right people i found an RFE (Bug 1373957) which would be a realy nice feature for my company as we have to request firewall rules for every new host and this ends up in a lot of mess and work. Is there any change that this RFE gets implemented ? >> >> Thanks for any help or tips > > > This RFE has been filed in 2016 and didn't got much interest so far. Can you elaborate a bit on the user story for this? > > > >> >> >> BR, >> Sandro >> _______________________________________________ >> Users mailing list -- users(a)ovirt.org >> To unsubscribe send an email to users-leave(a)ovirt.org >> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ >> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/UP7NZWXZBNHM7… > > > > -- > > Sandro Bonazzola > > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > > Red Hat EMEA > > sbonazzo(a)redhat.com > > Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.

2 1

Re: oVirt 4.3.5.1 failed to configure management network on the host
by Strahil 09 Aug '19

09 Aug '19

LACP supports works with 2 switches, but if you wish to aggregate all links - you need switch support (high-end hardware). Best Regards, Strahil NikolovOn Aug 6, 2019 18:08, Vincent Royer <vincent(a)epicenergy.ca> wrote: > > I also am spanned over two switches. You can use bonding, you just can't use 802.3 mode. > > I have MGMT bonded to two gig switches and storage bonded to two 10g switches for Gluster. Each switch has its own fw/router in HA. So we can lose either switch, either router, or any single interface or cable without interruption. > > > On Tue, Aug 6, 2019, 12:33 AM Mitja Pirih <mitja(a)pirih.si> wrote: >> >> On 05. 08. 2019 21:20, Vincent Royer wrote: >> > I tried deployment of 4.3.5.1 using teams and it didn't work. I did >> > get into the engine using the temp url on the host, but the teams >> > showed up as individual nics. Any changes made, like assigning a new >> > logical network to the nic, failed and I lost connectivity. >> > >> > Setup as a bond instead of team before deployment worked as expected, >> > and the bonds showed up properly in the engine. >> > >> > ymmv >> > >> >> I can't use bonding, spanned over two switches. >> Maybe there is another way to do it, but I am burned out, anybody with >> an idea? >> >> The server has 4x 10Gbps nics. I need up to 20Gbps throughput in HA mode. >> >> >> Thanks. >> >> >> >> Br, >> Mitja

2 1

Re: Ovirt 4.3.5.4-1.el7 noVNC keeps disconnecting with 1006
by Strahil 08 Aug '19

08 Aug '19

Hi Ryan, I'm using noVNC and not regular VNC. Last login: Thu Aug 8 16:40:50 2019 from ovirt1.localdomain [root@engine ~]# firewall-cmd --list-all public (active) target: default icmp-block-inversion: no interfaces: eth0 sources: services: ssh dhcpv6-client ovirt-postgres ovirt-https ovn-central-firewall-service ovirt-fence-kdump-listener ovirt-imageio-proxy ovirt-websocket-proxy ovirt-http ovirt-vmconsole-proxy ovirt-provider-ovn smtp ports: protocols: masquerade: no forward-ports: source-ports: icmp-blocks: rich rules: Best Regards, Strahil Nikolov On Aug 8, 2019 14:13, Ryan Barry wrote: > > On Thu, Aug 8, 2019 at 4:26 AM Sandro Bonazzola wrote: > > > > > > > > Il giorno dom 4 ago 2019 alle ore 16:11 Strahil Nikolov ha scritto: > >> > >> Hello Community, > >> > >> did anyone experience disconnects after a minute or 2 (seems random ,but I will check it out) with error code 1006 ? > >> Can someone with noVNC reproduce that behaviour ? > >> > >> As I manage to connect, it seems strange to me to loose connection like that. The VM was not migrated - so it should be something else. > > > > Can you please post firewall details and console.vv file? It should > not be possible to connect with the firewall in the way, but I would > wonder if something is changing it from behind > > > > > @Ryan Barry , @Michal Skrivanek any clue? > > > >> > >> > >> Best Regards, > >> Strahil Nikolov > >> _______________________________________________ > >> Users mailing list -- users(a)ovirt.org > >> To unsubscribe send an email to users-leave(a)ovirt.org > >> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > >> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > >> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/UVBK5NWKAHXH2… > > > > > > > > -- > > > > Sandro Bonazzola > > > > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > > > > Red Hat EMEA > > > > sbonazzo(a)redhat.com > > > > Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours. > > > > -- > > Ryan Barry > > Associate Manager - RHV Virt/SLA > > rbarry(a)redhat.com M: +16518159306 IM: rbarry > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/YONQ3MYAIGPKF…

1 0

Error creating local storage domain: Internal Engine Error.
by christian_barr＠hotmail.com 08 Aug '19

08 Aug '19

Hello. I'm new to ovirt and trying to set up a sandbox on an old Dell workstation I have. Any help greatly appreciated. I have created a 4.2 Compatible DC and Cluster. I'm able to add the host and that checks in OK. Its an older system hence going with 4.2 for processor support. When I try to a local storage domain, it fails. The error returned to the screen is : Error while executing action New Local Storage Domain: Internal Engine Error The process gets as far as creating some files and directories in the directory I'm trying to configure as a local storage domain. I notice in the UI, the format of the domain is specified as v4. (This option is greyed out and I cannot modify it). This is an excerpt of the engine.log, with the error the first line of which seems to be indicating its trying to use a v5 format ..... 019-08-07 23:21:24,618+01 WARN [org.ovirt.engine.core.bll.storage.domain.AttachStorageDomainToPoolCommand] (default task-56) [67e87701] Validation of action 'AttachStorageDomainToPool' failed for user SYSTEM. Reasons: VAR__TYPE__STORAGE__DOMAIN,VAR__ACTION__ATTACH,ACTION_TYPE_FAILED_STORAGE_DOMAIN_FORMAT_ILLEGAL,$storageFormat V5 2019-08-07 23:21:24,620+01 INFO [org.ovirt.engine.core.bll.storage.domain.AttachStorageDomainToPoolCommand] (default task-56) [67e87701] Lock freed to object 'EngineLock:{exclusiveLocks='[f2858a80-4730-40f8-b417-50d65503dcae=STORAGE]', sharedLocks=''}' 2019-08-07 23:21:24,623+01 INFO [org.ovirt.engine.core.bll.CommandCompensator] (default task-56) [67e87701] Command [id=abb92524-f71a-48fa-bf49-bae1f8a80989]: Compensating DELETED_OR_UPDATED_ENTITY of org.ovirt.engine.core.common.businessentities.StorageDomainDynamic; snapshot: id=f2858a80-4730-40f8-b417-50d65503dcae. 2019-08-07 23:21:24,626+01 INFO [org.ovirt.engine.core.bll.CommandCompensator] (default task-56) [67e87701] Command [id=abb92524-f71a-48fa-bf49-bae1f8a80989]: Compensating NEW_ENTITY_ID of org.ovirt.engine.core.common.businessentities.profiles.DiskProfile; snapshot: 94c8fb2e-e17a-46dd-a859-f3e18d9b3de7. 2019-08-07 23:21:24,627+01 INFO [org.ovirt.engine.core.bll.CommandCompensator] (default task-56) [67e87701] Command [id=abb92524-f71a-48fa-bf49-bae1f8a80989]: Compensating NEW_ENTITY_ID of org.ovirt.engine.core.common.businessentities.StorageDomainDynamic; snapshot: f2858a80-4730-40f8-b417-50d65503dcae. 2019-08-07 23:21:24,627+01 INFO [org.ovirt.engine.core.bll.CommandCompensator] (default task-56) [67e87701] Command [id=abb92524-f71a-48fa-bf49-bae1f8a80989]: Compensating NEW_ENTITY_ID of org.ovirt.engine.core.common.businessentities.StorageDomainStatic; snapshot: f2858a80-4730-40f8-b417-50d65503dcae. 2019-08-07 23:21:24,635+01 ERROR [org.ovirt.engine.core.bll.storage.domain.AddLocalStorageDomainCommand] (default task-56) [67e87701] Transaction rolled-back for command 'org.ovirt.engine.core.bll.storage.domain.AddLocalStorageDomainCommand'. 2019-08-07 23:21:24,639+01 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-56) [67e87701] EVENT_ID: USER_ADD_STORAGE_DOMAIN_FAILED(957), Failed to add Storage Domain STG01. (User: admin@internal-authz) Thanks all. Barman.

3 4

ovirt-web-ui-1.5.3: immediate logout in VM portal
by Matthias Leopold 08 Aug '19

08 Aug '19

Hi, after upgrading to oVirt 4.3.5 yesterday (which also brought ovirt-web-ui-1.5.3) users are immediately logged out after login to the "VM Portal" with "You have been logged out due to inactivity" displayed in the browser. The "Administration Portal" works as expected. This happens - for existing UserRole users/new UserRole users/Administrator users - with different browsers (Chrome/Firefox/IE) - also when creating new browser profiles Logs in engine.log are unsuspicious IMHO (see below for Administrator user login). /var/log/ovirt-engine/ui.log is completely quiet. Downgrade to 1.5.2 resolves the situation. Reading about "Added check for inactivity during session and logout after expiration" in 1.5.3 changelog suggests that something might have gone wrong. Has anybody seen this? Shall I file a bug report? thx matthias 2019-08-07 12:51:45,556+02 INFO [org.ovirt.engine.core.sso.utils.AuthenticationUtils] (default task-8) [] User admin@internal successfully logged in with scopes: ovirt-app-admin ovirt-app-api ovirt-app-portal ovirt-ext=auth:sequence-priority=~ ovirt-ext=revoke:revoke-all ovirt-ext=token-info:authz-search ovirt-ext=token-info:public-authz-search ovirt-ext=token-info:validate ovirt-ext=token:password-access 2019-08-07 12:51:45,728+02 INFO [org.ovirt.engine.core.bll.aaa.CreateUserSessionCommand] (default task-8) [2cb53d8d] Running command: CreateUserSessionCommand internal: false. 2019-08-07 12:51:45,768+02 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-8) [2cb53d8d] EVENT_ID: USER_VDC_LOGIN(30), User admin@internal-authz connecting from 'xxx.yyy.zzz.63' using session '+DY5GdQK35zrApbt971Df0nACY2o5qpT0ebX7zFnYj/SNnJACyH7nKKd5iJSshJZZo0TgkJUoSixB7StGq10VA==' logged in. 2019-08-07 12:51:48,385+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetFileStatsVDSCommand] (default task-11) [92c5e178-324e-4407-a844-7d1cb67e71b0] START, GetFileStatsVDSCommand( GetFileStatsParameters:{storagePoolId='1285d24b-53d1-4b4d-bba4-4aa6264f0c4a', ignoreFailoverLimit='false'}), log id: cd6a0e4 2019-08-07 12:51:48,394+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetFileStatsVDSCommand] (default task-11) [92c5e178-324e-4407-a844-7d1cb67e71b0] FINISH, GetFileStatsVDSCommand, return: {grml64-full_2018.12.iso={status=0, ctime=1553615947.0, size=704905216}, CentOS-7-x86_64-Minimal-1810.iso={status=0, ctime=1555410499.0, size=962592768}}, log id: cd6a0e4 2019-08-07 12:51:48,419+02 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-11) [92c5e178-324e-4407-a844-7d1cb67e71b0] EVENT_ID: REFRESH_REPOSITORY_IMAGE_LIST_SUCCEEDED(998), Refresh image list succeeded for domain(s): ISOstar-DEV (All file type) 2019-08-07 12:51:49,478+02 INFO [org.ovirt.engine.core.bll.aaa.LogoutSessionCommand] (default task-8) [4f195583] Running command: LogoutSessionCommand internal: false. 2019-08-07 12:51:49,524+02 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-8) [4f195583] EVENT_ID: USER_VDC_LOGOUT(31), User admin@internal-authz connected from 'xxx.yyy.zzz.63' using session '+DY5GdQK35zrApbt971Df0nACY2o5qpT0ebX7zFnYj/SNnJACyH7nKKd5iJSshJZZo0TgkJUoSixB7StGq10VA==' logged out. 2019-08-07 12:51:49,581+02 INFO [org.ovirt.engine.core.sso.servlets.OAuthRevokeServlet] (default task-14) [] User admin@internal successfully logged out 2019-08-07 12:51:49,675+02 INFO [org.ovirt.engine.core.bll.aaa.TerminateSessionsForTokenCommand] (default task-11) [37daeccc] Running command: TerminateSessionsForTokenCommand internal: true.

4 6

Re: Error creating local storage domain: Internal Engine Error.
by christian barr 08 Aug '19

08 Aug '19

________________________________ Hi. I have attached logs and screens Thanks. Barman. ________________________________ From: Shani Leviim <sleviim(a)redhat.com> Sent: 08 August 2019 12:36 To: christian_barr(a)hotmail.com <christian_barr(a)hotmail.com> Cc: users <users(a)ovirt.org> Subject: Re: [ovirt-users] Error creating local storage domain: Internal Engine Error. Hi Barman, Can you please attach a full engine log? Also attaching a screenshot would be great. Regards, Shani Leviim On Thu, Aug 8, 2019 at 2:44 PM <christian_barr(a)hotmail.com<mailto:christian_barr@hotmail.com>> wrote: Hello. I'm new to ovirt and trying to set up a sandbox on an old Dell workstation I have. Any help greatly appreciated. I have created a 4.2 Compatible DC and Cluster. I'm able to add the host and that checks in OK. Its an older system hence going with 4.2 for processor support. When I try to a local storage domain, it fails. The error returned to the screen is : Error while executing action New Local Storage Domain: Internal Engine Error The process gets as far as creating some files and directories in the directory I'm trying to configure as a local storage domain. I notice in the UI, the format of the domain is specified as v4. (This option is greyed out and I cannot modify it). This is an excerpt of the engine.log, with the error the first line of which seems to be indicating its trying to use a v5 format ..... 019-08-07 23:21:24,618+01 WARN [org.ovirt.engine.core.bll.storage.domain.AttachStorageDomainToPoolCommand] (default task-56) [67e87701] Validation of action 'AttachStorageDomainToPool' failed for user SYSTEM. Reasons: VAR__TYPE__STORAGE__DOMAIN,VAR__ACTION__ATTACH,ACTION_TYPE_FAILED_STORAGE_DOMAIN_FORMAT_ILLEGAL,$storageFormat V5 2019-08-07 23:21:24,620+01 INFO [org.ovirt.engine.core.bll.storage.domain.AttachStorageDomainToPoolCommand] (default task-56) [67e87701] Lock freed to object 'EngineLock:{exclusiveLocks='[f2858a80-4730-40f8-b417-50d65503dcae=STORAGE]', sharedLocks=''}' 2019-08-07 23:21:24,623+01 INFO [org.ovirt.engine.core.bll.CommandCompensator] (default task-56) [67e87701] Command [id=abb92524-f71a-48fa-bf49-bae1f8a80989]: Compensating DELETED_OR_UPDATED_ENTITY of org.ovirt.engine.core.common.businessentities.StorageDomainDynamic; snapshot: id=f2858a80-4730-40f8-b417-50d65503dcae. 2019-08-07 23:21:24,626+01 INFO [org.ovirt.engine.core.bll.CommandCompensator] (default task-56) [67e87701] Command [id=abb92524-f71a-48fa-bf49-bae1f8a80989]: Compensating NEW_ENTITY_ID of org.ovirt.engine.core.common.businessentities.profiles.DiskProfile; snapshot: 94c8fb2e-e17a-46dd-a859-f3e18d9b3de7. 2019-08-07 23:21:24,627+01 INFO [org.ovirt.engine.core.bll.CommandCompensator] (default task-56) [67e87701] Command [id=abb92524-f71a-48fa-bf49-bae1f8a80989]: Compensating NEW_ENTITY_ID of org.ovirt.engine.core.common.businessentities.StorageDomainDynamic; snapshot: f2858a80-4730-40f8-b417-50d65503dcae. 2019-08-07 23:21:24,627+01 INFO [org.ovirt.engine.core.bll.CommandCompensator] (default task-56) [67e87701] Command [id=abb92524-f71a-48fa-bf49-bae1f8a80989]: Compensating NEW_ENTITY_ID of org.ovirt.engine.core.common.businessentities.StorageDomainStatic; snapshot: f2858a80-4730-40f8-b417-50d65503dcae. 2019-08-07 23:21:24,635+01 ERROR [org.ovirt.engine.core.bll.storage.domain.AddLocalStorageDomainCommand] (default task-56) [67e87701] Transaction rolled-back for command 'org.ovirt.engine.core.bll.storage.domain.AddLocalStorageDomainCommand'. 2019-08-07 23:21:24,639+01 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-56) [67e87701] EVENT_ID: USER_ADD_STORAGE_DOMAIN_FAILED(957), Failed to add Storage Domain STG01. (User: admin@internal-authz) Thanks all. Barman. _______________________________________________ Users mailing list -- users(a)ovirt.org<mailto:users@ovirt.org> To unsubscribe send an email to users-leave(a)ovirt.org<mailto:users-leave@ovirt.org> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/EMNQLWPQ2BVV2…

1 0

Re: Agentless backup solutions
by Strahil 08 Aug '19

08 Aug '19

I had corruption of the Hosted Engine due to a power failiure of all hosts (Gluster). My lab has no UPS. You can create a snapshot via API , backup the snapshot and then delete it via the API while the VM is working (no downtime). Still, this approach won't work for Databases as you can create the snapahot in the middle of a transaction. Best Regards, Strahil NikolovOn Aug 7, 2019 20:33, Douglas Duckworth <dod2014(a)med.cornell.edu> wrote: > > Hi > > > We are running oVirt 4.2.8.2-1.el7. Should probably upgrade but it works. > > > We are backing up the engine every day with dump going to external NFS file system then onto the cloud. For VMs we are doing backups within Linux itself using a program called Restic which then sends data to cloud S3 service. That runs daily as well. > > > We also save all configuration data, for applications running on our VMs such as Apache, etc, within Ansible. So we can quickly recreate the VM using Ansible, along with any applications, then restore any data, not saved in Ansible, such as private PKI keys or PostgreSQL dump, for example, from Restic. Dockerized applications even easier. There would be some downtime to redeploy a new VM but this is acceptable given the constrains of our environment. > > > I am wondering under what situations has anyone experienced VM corruption? This would help me determine if more effort should be invested in snapshotting VMs and possibly exporting their disks. Though as I recall removing snapshots from my storage domain would require shutting down the VM, right? > > > -- > Thanks, > > Douglas Duckworth, MSc, LFCS > HPC System Administrator > Scientific Computing Unithttps://github.com/restic/restic

1 0

Ovirt 4.3.5.4-1.el7 noVNC keeps disconnecting with 1006
by Strahil Nikolov 08 Aug '19

08 Aug '19

Hello Community, did anyone experience disconnects after a minute or 2 (seems random ,but I will check it out) with error code 1006 ?Can someone with noVNC reproduce that behaviour ? As I manage to connect, it seems strange to me to loose connection like that. The VM was not migrated - so it should be something else. Best Regards,Strahil Nikolov

3 2

[ANN] oVirt 4.3.6 Second Release Candidate is now available for testing
by Sandro Bonazzola 08 Aug '19

08 Aug '19

The oVirt Project is pleased to announce the availability of the oVirt 4.3.6 Second Release Candidate for testing, as of August 8th, 2019. This update is a release candidate of the sixth in a series of stabilization updates to the 4.3 series. This is pre-release software. This pre-release should not to be used in production. This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 7.7 or later (but <8) * CentOS Linux (or similar) 7.7 or later (but <8) This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 7.7 or later (but <8) * CentOS Linux (or similar) 7.7 or later (but <8) * oVirt Node 4.3 (available for x86_64 only) See the release notes [1] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available - oVirt Node is not yet available, pending CentOS 7.7 release to be available Additional Resources: * Read more about the oVirt 4.3.6 release highlights: http://www.ovirt.org/release/4.3.6/ * Get more oVirt Project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] http://www.ovirt.org/release/4.3.6/ -- 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.*

2 7

RFE: Add the ability to the engine to serve as a fencing proxy
by Sandro E 08 Aug '19

08 Aug '19

Hi, i hope that this hits the right people i found an RFE (Bug 1373957) which would be a realy nice feature for my company as we have to request firewall rules for every new host and this ends up in a lot of mess and work. Is there any change that this RFE gets implemented ? Thanks for any help or tips BR, Sandro

2 1

Removing VDSM dependency on multipath driver.
by amit1.kumar＠intel.com 08 Aug '19

08 Aug '19

Hi All, I observed that for FCP storage domain only mpath enabled drives are getting listed, for e.g. if we have local nvme drives attached to the VDSM host, only mpath enabled nvme drives are getting listed in the ovirt engine for FCP storage domain. Actually I am creating a RAID (using mdadm tool, software raid) on two local nvme drives and wanted to expose it to the Ovirt engine through FCP storage domain, is it possible? or can we bypass multipath in FCP storage domain so that all the block device can be listed in the ovirt engine for FCP storage domain? Thanks, Amit

2 1

Agentless backup solutions
by femi adegoke 07 Aug '19

07 Aug '19

What backup solutions are people using? I'm only interested in host-level backups (no agents in the vm's) I am aware of the following products: https://storware.eu/en/storware-vprotect/ https://github.com/zipurman/oVIRT_Simple_Backup https://www.sepusa.com/ Any others?

9 16

oVirt 4.3.5.1 failed to configure management network on the host
by Mitja Pirih 07 Aug '19

07 Aug '19

Hi, I am trying to deploy hosted engine on Ovirt Node 4.3.5.1 and I am getting: ovirt failed to configure management network on the host. I am pretty sure the problem lies in my network config that is actually working quite nice. My current network config is: team0: - Switch1: bond0 (LACP): eno1,eno3 - Switch2: bond1 (LACP): eno2,eno4 Switch1 and switch2 are interconnected by a different LAG group. Current network config was tested against all kinds of failures, nic port failure, switch failure...etc...and it works. Although I am open to suggestions how to implement high availability with high throughput. By default on hosted engine deployment team0 is selected as bridge interface. Br, Mitja Logs: === supervdsm.log: https://pastebin.com/raw/bijW7uhi === vdsm.log part1: https://pastebin.com/raw/BYGsieCw === vdsm.log part2: https://pastebin.com/raw/rgzQCDjw

2 5

distribute storage domains
by Jason M. Stallings 07 Aug '19

07 Aug '19

Hello I'm trying to figure out a way to automatically distribute our storage domain occupation evenly or at least avoid them getting full. We have a lot of users creating vms and they seem to select the first available storage domain, thus one is nearly full and the rest are barely used. Is there a way to accomplish that? Thank you Jason

4 7

Not able to import vm from kvm host
by Crazy Ayansh 07 Aug '19

07 Aug '19

Hi Team, I am trying to convert/import few vm from KVM to ovirt but i am getting below error message. Aug 7 15:56:11 IONDELSVR46 journal: authentication failed: Failed to start SASL negotiation: -20 (SASL(-13): user not found: unable to canonify user and get auxprops) Aug 7 15:56:11 IONDELSVR46 journal: authentication failed: authentication failed Please help! Thanks Shashank

1 0

(no subject)
by Crazy Ayansh 07 Aug '19

07 Aug '19

Hi Team, I am trying to convert/import few vm from KVM to ovirt but i am getting below error message. Aug 7 15:56:11 IONDELSVR46 journal: authentication failed: Failed to start SASL negotiation: -20 (SASL(-13): user not found: unable to canonify user and get auxprops) Aug 7 15:56:11 IONDELSVR46 journal: authentication failed: authentication failed Please help! Thanks Shashank

1 0

port_security in external networks-API
by ada per 07 Aug '19

07 Aug '19

Hello everyone, I have the following python script that creates an external network, but now after updating ovirt a new option "network port security" exists that is set as enabled by default. How can i disable the network port security? thanks!! :) networks_service = connection.system_service().networks_service() # Use the "add" method to create new VM logical network in data center network = networks_service.add( network=types.Network( name= ext_net_name, description='Network for testing API', data_center=types.DataCenter( name='Default' ), usages=[types.NetworkUsage.VM], external_provider=types.OpenStackNetworkProvider( id=provider.id ) ),

2 3

hosted engine installation / multipath / iscsi
by Michael Frank 07 Aug '19

07 Aug '19

Hi, since several days i try to install the hosted engine initially to an iscsi multipath device without success. Some information on the environment: - Version 4.3.3 - using two 10gbe interfaces as single bond for the ovirtmgmt interface - using two 10gbe storage interfaces on each hypervisor for iscsi storage -- each storage interface is configured without any bonding, etc -- each storage interface lives in a separate vlan were also the iscsi Portals/target are available, the iscsi portals have 4x10ge interfaces each, (2 in vlan xx and 2 interfaces in vlan yy ) -- so; each storage interface is connected to two iscsi Portals via 4 interfaces The documentation here is for me unclear: https://ovirt.org/documentation/self-hosted/chap-Deploying_Self-Hosted_Engi… >Note: To specify more than one iSCSI target, you must enable multipathing before deploying the self-hosted engine. There is also a Multipath >Helper tool that generates a script to install and configure multipath with different options. This indicates for me that it should be possbile to install the HE directly on the /dev/mapper/mpath device which is availibale when I have prepared the host accordingly before installing the HE (log in to multiple iscsi targets, create proper multipath,conf, etc) - right ? I login to the two iscsi portals and get in sum 8 pathes, 4 from each interface and iscsi target. Basically I have then the mpath device on the hypervisor available and i can mount the mpath device and put data on it. In the cockpit interface the mount can also be activated and is recognized correctly. multipathd -ll and lsblk looks good. Everything seems to be fine. But when I run the "hosted-engine" --deploy, the last option while running the assistant is to enter the iscsi data. So, basically i just want to define my mpath device - when entering the data (ip, port)for the iscsi Portal I can see the 4 pathes of the single hosted Engine target, and when i choose the path where the "lun" is finally available it fails. I think in general this option is not that what i want to have here for using the multipath device. I' m lost - what is the usual way to install the HE on a multipath device ? Do i have to change the configuration of the storage interfaces or the iscsi network design? Did I missed something obvious ? Can I put in my multipath data into the answerfile to get rid of the last step of the assistant ? Can I use the related ansible role for specify the Mpath device which is available when activating the multipath service ? Is it not possible in general ?? : https://bugzilla.redhat.com/show_bug.cgi?id=1193961 Sorry in advance for the long mail .... 1!^^ br, michael Sent from a mobile device

3 2

Re: Linux VM keeps crashing on copying files "with lost communication with qemu"
by Strahil 07 Aug '19

07 Aug '19

Maybe the libvirtd < - > libgfapi communication is somehow broken. I'm using FUSE and I have no issues, but my lab is not I/O intensive . Have you noticed if the issue happens during I/O (for example - full backup) intensive load? You can even try to stop using libgfapi and check if it happens again. Best Regards, Strahil NikolovOn Aug 3, 2019 00:39, Darrell Budic <budic(a)onholyground.com> wrote: > > I’ve been seeing similar issues lately (since upgrading to 4.3.4 and later) with gluster storage (and libgfapi), but haven’t pinned to anything particular yet. But libvirt seems to have some issues and vdsmd stops being able to poll disk usage. My VMs don’t crash or stop working, but they do report as ? in the management interface and can’t be migrated. Current work around is to restart libvirtd then vdsmd, occasionally restarting libvirtd restarts a VM (presumably the one that had broken some disk something…). > > Sorry I don’t have more info to go on, but I’ll update here if I get more on anything similar. > > -Darrell > > > On Aug 2, 2019, at 9:23 AM, kevin.doyle(a)manchester.ac.uk wrote: > > > > HI > > I think it is a bug with qemu, and isci disks. Has anyone else seen this issue VM crashes and lost communication with qemu Can I update qemu ? if so what is the latest support version to use on Ovirt 4.3.2.1-1.el7 Current versions of qemu installed > > > > Installed Packages > > qemu-img-ev.x86_64 10:2.12.0-18.el7_6.3.1 > > qemu-kvm-common-ev.x86_64 10:2.12.0-18.el7_6.3.1 > > qemu-kvm-ev.x86_64 10:2.12.0-18.el7_6.3.1 > > > > Many thanks > > Kevin > > _______________________________________________ > > Users mailing list -- users(a)ovirt.org > > To unsubscribe send an email to users-leave(a)ovirt.org > > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/FDMHYEJXRG6IG… > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/ZAOILBQRM7XPY…

3 3

oVirt- UX Research Study Participation
by Laura Wright 06 Aug '19

06 Aug '19

Hello! The UX Research team at Red Hat is conducting a new oVirt study and is looking to test out the usability of a few features in oVirt. We are currently recruiting participants located in the United States and internationally. If you are interested, please use this calendar to sign up for a spot: https://calendar.google.com/calendar/selfsched?sstoken=UUhJcjBDd09oOXg5fGRl… The study is open to international participants but getting compensated is only available to US based participants currently. For this study, you will be required to use FireFox and allow your screen and audio to be recorded. This study should only take about 45 minutes to complete and will be conducted via Bluejeans. All data will be totally anonymous and viewed only by the UX research team. As a token of our gratitude, we will be providing you with an Amazon gift card to compensate you for your time. Your feedback will help us make the project better! Thank you in advance for your time! Please let me know if you have any questions. Thank you, Sara Chizari & Laura Wright --Red Hat UXD Laura Wright She/Her/Hers UXD Team Red Hat Massachusetts <https://www.redhat.com/> 314 Littleton Rd lwright(a)redhat.com <https://www.redhat.com/>

1 0

4.3.5.1 failed deployment SSL ovn errors
by Vincent Royer 06 Aug '19

06 Aug '19

I had a failed HCI replica 3 deployment, a fresh 4.3.5.1 install. I fixed some things, ran the cleanup script and rebooted. The first host's logs are now full of: ovs|00330|stream_ssl|ERR|Certificate must be configured to use SSL ovn-controller ovs|00329|stream_ssl|ERR|Private key must be configured to use SSL ovn-controller ovs|00328|stream_ssl|ERR|Certificate must be configured to use SSL ovn-controller ovs|00327|stream_ssl|ERR|Private key must be configured to use SSL ovn-controller how do I fix that?

3 3

bond for vm interfaces
by Edoardo Mazza 06 Aug '19

06 Aug '19

Hello everyone, I need to create a bond for vm interfaces but I don't kown what is the best solution, you can help me? Thanks Edoardo

3 2

Data Center Compatibility version
by Rick A 06 Aug '19

06 Aug '19

So I updated our environment a bit ago during a scheduled down time from 4.2 to 4.3. Everything went smoothly, but it looks like I forgot to update the Data Center Compatibility (See alert message below). My question is, can I just change the Data Center compatibility to 4.3 while the environment is running without causing issues, or do i need to shutdown all my VM's and put the hosts into maintenance mode? The compatibility version for everything else is already set to 4.3. Thanks Alert Message: "Data Center compatibility version is 4.2, which is lower than latest engine version 4.3. Please upgrade your Data Center to latest version to successfully finish upgrade of your setup"

2 1

[ANN] oVirt 4.3.5 Fifth Release Candidate is now available for testing
by Sandro Bonazzola 06 Aug '19

06 Aug '19

The oVirt Project is pleased to announce the availability of the oVirt 4.3.5 Fifth Release Candidate for testing, as of July 11th, 2019. While testing this release candidate please consider deeper testing on gluster upgrade since with this release we are switching from Gluster 5 to Gluster 6. This update is a release candidate of the fifth in a series of stabilization updates to the 4.3 series. This is pre-release software. This pre-release should not to be used in production. This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 7.6 or later * CentOS Linux (or similar) 7.6 or later This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 7.6 or later * CentOS Linux (or similar) 7.6 or later * oVirt Node 4.3 (available for x86_64 only) See the release notes [1] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is laready available - oVirt Node is already available[2] Additional Resources: * Read more about the oVirt 4.3.5 release highlights: http://www.ovirt.org/release/4.3.5/ * Get more oVirt Project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] http://www.ovirt.org/release/4.3.5/ [2] http://resources.ovirt.org/pub/ovirt-4.3-pre/iso/ -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/>

3 7

ovirt-release43-pre-4.3.6-0.1 - python-ioprocess RPM version
by Maton, Brett 06 Aug '19

06 Aug '19

Hi, I just ran yum update on my test cluster and ran into the following issue: I did notice that the python2-ioprocess is currently installed from the ovirt-4.2 repo... Any suggestions? Thanks, Brett Repo RPM: ovirt-release43-pre-4.3.6-0.1.rc1.el7.noarch yum -y upgrade ... Error: Package: vdsm-python-4.30.25-1.el7.noarch (ovirt-4.3-pre) Requires: python-ioprocess >= 1.2.1 Installed: python2-ioprocess-1.1.2-1.el7.x86_64 (@ovirt-4.2) python-ioprocess = 1.1.2 Available: python-ioprocess-0.16.1-1.el7.noarch (ovirt-4.3-centos-ovirt43) python-ioprocess = 0.16.1-1.el7 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest

2 1

4.3.5 update error
by Kapetanakis Giannis 06 Aug '19

06 Aug '19

Hi, Trying today engine-setup to update from 4.3.3 -> 4.3.5 I got this error: [ ERROR ] Failed to execute stage 'Setup validation': local variable 'snapshot_cl' referenced before assignment In log file I see: 2019-07-31 10:43:00,375+0300 DEBUG otopi.context context._executeMethod:145 method exception Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/otopi/context.py", line 132, in _executeMethod method['method']() File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/db/schema.py", line 437, in _validation self._checkSnapshotCompatibilityVersion() File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/db/schema.py", line 212, in _checkSnapshotCompatibilityVersion 'v': snapshot_cl, UnboundLocalError: local variable 'snapshot_cl' referenced before assignment 2019-07-31 10:43:00,381+0300 ERROR otopi.context context._executeMethod:154 Failed to execute stage 'Setup validation': local variable 'snapshot_cl' referenced before assignment Any hints? thanks Giannis

5 5

[ANN] oVirt Engine 4.3.5 async update is now available
by Sandro Bonazzola 06 Aug '19

06 Aug '19

The oVirt Team has just released a new version of ovirt-engine package that fixes one upgrade related issue.[1] We recommend to users experiencing upgrade issues to try again with this new release. Thanks, [1] https://bugzilla.redhat.com/1734699 -- 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

oVirt tools
by old.good.mail＠gmail.com 06 Aug '19

06 Aug '19

Greetings, After installing oVirt tools on my w2016 virtual server I've noticed that all devices (nic, disks, etc.) are connected as USB devices and I have option available to eject those devices. Is there any way to prvent those devices being ejected on behalf of VM user? (e.g. make sure noone inside the VM can actually eject nic, disk or something)

4 4

[ANN] oVirt 4.3.5 second async is now available
by Sandro Bonazzola 05 Aug '19

05 Aug '19

The oVirt Team has just released a new version of the following packages: - ovirt-ansible-hosted-engine-setup-1.0.26 - ovirt-release43-4.3.5.2 The async release includes additional fixes: - Bug 1734171 <https://bugzilla.redhat.com/show_bug.cgi?id=1734171> - RHV-M 4.3.4 does not boot with fips=1 when OpenSCAP profile used resulting in non FIPS compliant certificates Notes: - oVirt Node is already available[2] oVirt Node has been updated including above packages and: - Latest CentOS Virt SIG update: - CESA-2019:1968 - Important qemu-kvm-ev Security Update Upstream details at https://access.redhat.com/errata/RHSA-2019:1968 - Latest CentOS 7.6 updates including: - CEBA-2019:1899 CentOS 7 bind BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-July/023376.html> - CESA-2019:1880 Low CentOS 7 curl Security Update <https://lists.centos.org/pipermail/centos-announce/2019-July/023377.html> - CEBA-2019:1889 CentOS 7 ipa BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-July/023380.html> - CESA-2019:1873 Important CentOS 7 kernel Security Update <https://lists.centos.org/pipermail/centos-announce/2019-July/023374.html> - CEBA-2019:1895 CentOS 7 systemd BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-July/023393.html> - CEBA-2019:1875 CentOS 7 samba BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-July/023397.html> - CESA-2019:1884 Moderate CentOS 7 libssh2 Security Update <https://lists.centos.org/pipermail/centos-announce/2019-July/023383.html> - CEBA-2019:1874 CentOS 7 net-snmp BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-July/023386.html> - CEBA-2019:1878 CentOS 7 selinux-policy BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-July/023391.html> - CEBA-2019:1885 CentOS 7 sos BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-July/023392.html> - CEEA-2019:1887 CentOS 7 sysstat Enhancement Update <https://lists.centos.org/pipermail/centos-announce/2019-July/023396.html> - CEBA-2019:1901 CentOS 7 tuned BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-July/023394.html> Additional Resources: * Read more about the oVirt 4.3.5 release highlights: http://www.ovirt.org/release/4.3.5/ * Get more oVirt Project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] http://www.ovirt.org/release/4.3.5/ [2] http://resources.ovirt.org/pub/ovirt-4.3/iso/ -- 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

Linux VM keeps crashing on copying files "with lost communication with qemu"
by kevin.doyle＠manchester.ac.uk 02 Aug '19

02 Aug '19

HI I think it is a bug with qemu, and isci disks. Has anyone else seen this issue VM crashes and lost communication with qemu Can I update qemu ? if so what is the latest support version to use on Ovirt 4.3.2.1-1.el7 Current versions of qemu installed Installed Packages qemu-img-ev.x86_64 10:2.12.0-18.el7_6.3.1 qemu-kvm-common-ev.x86_64 10:2.12.0-18.el7_6.3.1 qemu-kvm-ev.x86_64 10:2.12.0-18.el7_6.3.1 Many thanks Kevin

2 1

Use public-signed SSL certs?
by Chris Adams 02 Aug '19

02 Aug '19

I installed an SSL cert from a public CA (Let's Encrypt) on my engine, following this: https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/ht… That gets the regular web UI working, but I can't upload an ISO. I assume that I need to do something with the imageio-proxy service on the engine, but not sure what... I tried replacing imageio-proxy.cer and imageio-proxy.key.nopass, but that didn't work. I'm trying to avoid ever needing to install a special CA cert in browsers. -- Chris Adams <cma(a)cmadams.net>

6 19

Re: Manual Migration not working and Dashboard broken after 4.3.4 update
by Strahil 02 Aug '19

02 Aug '19

I'm not sure, but I always thought that you need an agent for live migrations. You can always try installing either qemu-guest-agent or ovirt-guest-agent and check if live migration between hosts is possible. Have you set the new cluster/dc version ? Best Regards Strahil NikolovOn Jul 9, 2019 17:42, Neil <nwilson123(a)gmail.com> wrote: > > I remember seeing the bug earlier but because it was closed thought it was unrelated, this appears to be it.... > > https://bugzilla.redhat.com/show_bug.cgi?id=1670701 > > Perhaps I'm not understanding your question about the VM guest agent, but I don't have any guest agent currently installed on the VM, not sure if the output of my qemu-kvm process maybe answers this question?.... > > /usr/libexec/qemu-kvm -name guest=Headoffice.cbl-ho.local,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-1-Headoffice.cbl-ho.lo/master-key.aes -machine pc-i440fx-rhel7.3.0,accel=kvm,usb=off,dump-guest-core=off -cpu Broadwell,vme=on,f16c=on,rdrand=on,hypervisor=on,arat=on,xsaveopt=on,abm=on,rtm=on,hle=on -m 8192 -realtime mlock=off -smp 8,maxcpus=64,sockets=16,cores=4,threads=1 -numa node,nodeid=0,cpus=0-7,mem=8192 -uuid 9a6561b8-5702-43dc-9e92-1dc5dfed4eef -smbios type=1,manufacturer=oVirt,product=oVirt Node,version=7-3.1611.el7.centos,serial=4C4C4544-0034-5810-8033-C2C04F4E4B32,uuid=9a6561b8-5702-43dc-9e92-1dc5dfed4eef -no-user-config -nodefaults -chardev socket,id=charmonitor,fd=31,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=2019-07-09T10:26:53,driftfix=slew -global kvm-pit.lost_tick_policy=delay -no-hpet -no-shutdown -boot strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x4 -device virtio-serial-pci,id=virtio-serial0,max_ports=16,bus=pci.0,addr=0x5 -drive if=none,id=drive-ide0-1-0,readonly=on -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -drive file=/rhev/data-center/59831b91-00a5-01e4-0294-000000000018/8a607f8a-542a-473c-bb18-25c05fe2a3d4/images/56e8240c-a172-4f52-b0c1-2bddc4f34f93/9f245467-d31d-4f5a-8037-7c5012a4aa84,format=qcow2,if=none,id=drive-virtio-disk0,serial=56e8240c-a172-4f52-b0c1-2bddc4f34f93,werror=stop,rerror=stop,cache=none,aio=native -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1,write-cache=on -netdev tap,fd=33,id=hostnet0,vhost=on,vhostfd=34 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=00:1a:4a:16:01:5b,bus=pci.0,addr=0x3 -chardev socket,id=charchannel0,fd=35,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.rhevm.vdsm -chardev socket,id=charchannel1,fd=36,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=channel1,name=org.qemu.guest_agent.0 -chardev spicevmc,id=charchannel2,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=3,chardev=charchannel2,id=channel2,name=com.redhat.spice.0 -spice tls-port=5900,addr=10.0.1.11,x509-dir=/etc/pki/vdsm/libvirt-spice,tls-channel=default,tls-channel=main,tls-channel=display,tls-channel=inputs,tls-channel=cursor,tls-channel=playback,tls-channel=record,tls-channel=smartcard,tls-channel=usbredir,seamless-migration=on -device qxl-vga,id=video0,ram_size=67108864,vram_size=8388608,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pci.0,addr=0x2 -incoming defer -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 -object rng-random,id=objrng0,filename=/dev/urandom -device virtio-rng-pci,rng=objrng0,id=rng0,bus=pci.0,addr=0x8 -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny -msg timestamp=on > > Please shout if you need further info. > > Thanks. > > > > > > > On Tue, Jul 9, 2019 at 4:17 PM Strahil Nikolov <hunter86_bg(a)yahoo.com> wrote: >> >> Shouldn't cause that problem. >> >> You have to find the bug in bugzilla and report a regression (if it's not closed) , or open a new one and report the regression. >> As far as I remember , only the dashboard was affected due to new features about vdo disk savings. >>

5 13

no network interface
by A S 01 Aug '19

01 Aug '19

Hi. I had ovirt running with a VM but it suddenly broke. I wiped it all and did a reinstall but now I am not able to connect my host to the network. the host is always saying status='unassigned'. in the network page where I would drag and drop a connection, there is no interface to connect to. its this page https://ovirt.org/images/wiki/SetupNetworksNew.png?1478101462 but there is nothing in the interfaces column on the left Can anyone point me in the right direction to fix this? Thanks I have only one machine with the engine and host on it.

3 2

[ANN] oVirt 4.3.6 First Release Candidate is now available for testing
by Sandro Bonazzola 01 Aug '19

01 Aug '19

The oVirt Project is pleased to announce the availability of the oVirt 4.3.6 First Release Candidate for testing, as of August 1st, 2019. This update is a release candidate of the sixth in a series of stabilization updates to the 4.3 series. This is pre-release software. This pre-release should not to be used in production. This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 7.6 or later (but <8) * CentOS Linux (or similar) 7.6 or later (but <8) This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 7.6 or later (but <8) * CentOS Linux (or similar) 7.6 or later (but <8) * oVirt Node 4.3 (available for x86_64 only) See the release notes [1] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is laready available - oVirt Node is already available[2] Additional Resources: * Read more about the oVirt 4.3.6 release highlights: http://www.ovirt.org/release/4.3.6/ * Get more oVirt Project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] http://www.ovirt.org/release/4.3.6/ [2] http://resources.ovirt.org/pub/ovirt-4.3-pre/iso/ -- 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