- Users - oVirt List Archives

Re: change he vm memoy size
by Strahil 30 May '19

30 May '19

Actually, you need to untar the OVF from the shared storage and check the configuration from the tar. Just keep it like that (running ) and tomorrow power down and then up the HostedEngine. Best Regards, Strahil NikolovOn May 30, 2019 12:06, "Valkov, Alexey" <Valkov.Alexey(a)knauf.ru> wrote: > > Hello, Strahil. I've just tried with engine-config -s OvfUpdateIntervalInMinutes=1 systemctl restart ovirt-engine.service After that, i changed Memory Size in manager UI. And waited about 30 minutes. Then checked memSize in /var/run/ovirt-hosted-engine-ha/vm.conf (which if i right understand syncronized with ovf every minute) and saw memSize have not been changed. And Memory Size property (in manager UI) also remains initial. Thus i think that ovf dont changes. I return OvfUpdateIntervalInMinutes=60 and will wait till tomorrow, may be the setting will be magically aplyed. > > -- > Best regards > Alexey > >> Hi Alexey, >> How much time did you check before rebooting. >> I have noticed ,that despite the default OVF update interval of 1 hour, it takes 5-6 hours for the engine to update the OVF. >> >> Best Regards, >> Strahil Nikolov >> >> On May 30, 2019 10:30, "Valkov, Alexey" <Valkov.Alexey(a)knauf.ru> wrote: >>> >>> I try to increase memory of HE VM (oVirt 4.2.8). If i do it from manager UI, i see that hot plug works - new memory devices appear and corresponding memory increase appeares inside engine guest. But 'Memory Size' property of hosted engine (in manager UI) don't reflect that new amount of memory. Also after reboot of engine vm, memory size changes back to initial value. Is it possible to change memory size of HE vm ( as far as i know the settings stored in ovf on HE domain) and how i can make this change to be persistent. >>> >>> -- >>> Best regards >>> Alexey >>> >> _______________________________________________ >> >> 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/IKID3B2TH3VR2… >> >>

4 3

[ANN] oVirt 4.3.4 Third Release Candidate is now available
by Sandro Bonazzola 30 May '19

30 May '19

The oVirt Project is pleased to announce the availability of the oVirt 4.3.4 Third Release Candidate, as of May 30th, 2019. This update is a release candidate of the fourth in a series of stabilization updates to the 4.3 series. This is pre-release software. This pre-release should not to be used inproduction. 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) Experimental tech preview for x86_64 and s390x architectures for Fedora 28 is also included. 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 already available[2] Additional Resources: * Read more about the oVirt 4.3.4 release highlights: http://www.ovirt.org/release/4.3.4/ * 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.4/ [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://red.ht/sig> <https://redhat.com/summit>

2 1

oVirt 3.6 SLA and QoS algorithm
by m.isaiev＠kwebbl.com 30 May '19

30 May '19

Hello! We are using oVirt 3.6 in our infrastructure and storage QoS in passive state (they are configured but not applie) for some of the servers. Last time we needed to activate QoS on high load servers and it caused storage load decrease. And this situation has raised some questions: 1. What happened to overlimit storage traffic, when QoS applying on high load virtual machine: a) All over traffic is pulling into some queue, where all disk transactions can be successfully finished with QoS throughput? b) All over-limitation data is dropped and opened transactions failed? c) All active transactions finishes on speed beyond QoS, but all new transactions immediately start to work based on configured limits? 2. How QoS mechanism actually works? Does it use some oVirt specific functions or it uses some system features to limit storage, network or CPU usage? If system one, then the QoS are provided by libvirt (using virsh or directly) or system kernel options and which one? Thanks in advance!

2 2

Re: change he vm memoy size
by Strahil 30 May '19

30 May '19

Hi Alexey, How much time did you check before rebooting. I have noticed ,that despite the default OVF update interval of 1 hour, it takes 5-6 hours for the engine to update the OVF. Best Regards, Strahil NikolovOn May 30, 2019 10:30, "Valkov, Alexey" <Valkov.Alexey(a)knauf.ru> wrote: > > I try to increase memory of HE VM (oVirt 4.2.8). If i do it from manager UI, i see that hot plug works - new memory devices appear and corresponding memory increase appeares inside engine guest. But 'Memory Size' property of hosted engine (in manager UI) don't reflect that new amount of memory. Also after reboot of engine vm, memory size changes back to initial value. Is it possible to change memory size of HE vm ( as far as i know the settings stored in ovf on HE domain) and how i can make this change to be persistent. > > -- > Best regards > Alexey >

3 2

change he vm memoy size
by Valkov, Alexey 30 May '19

30 May '19

1 0

Install fresh 4.3 fails with mounting shared storage
by Vrgotic, Marko 30 May '19

30 May '19

Dear oVIrt, We are trying to deploy new setup with Hosted-Engine , oVirt version 4.3. Volume is on the Netapp, protocol NFS v4. Upon populating shared storage information and path: Please specify the storage you would like to use (glusterfs, iscsi, fc, nfs)[nfs]: nfs Please specify the nfs version you would like to use (auto, v3, v4, v4_1)[auto]: auto Please specify the full shared storage connection path to use (example: host:/path): 172.17.28.5:/ovirt_hosted_engine Following is displayed on the screen: [ INFO ] Creating Storage Domain [ INFO ] TASK [ovirt.hosted_engine_setup : Execute just a specific set of steps] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Force facts gathering] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Check local VM dir stat] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Enforce local VM dir existence] [ INFO ] skipping: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : include_tasks] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Obtain SSO token using username/password credentials] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Fetch host facts] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Fetch cluster ID] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Fetch cluster facts] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Fetch Datacenter facts] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Fetch Datacenter ID] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Fetch Datacenter name] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Add NFS storage domain] [ ERROR ] Error: Fault reason is "Operation Failed". Fault detail is "[General Exception]". HTTP response code is 400. [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Fault reason is \"Operation Failed\". Fault detail is \"[General Exception]\". HTTP response code is 400."} Even with this error – storage gets mounted on the Host: 172.17.28.5:/ovirt_hosted_engine on /rhev/data-center/mnt/172.17.28.5:_ovirt__hosted__engine type nfs4 (rw,relatime,vers=4.0,rsize=65536,wsize=65536,namlen=255,soft,nosharecache,proto=tcp,timeo=600,retrans=6,sec=sys,clientaddr=172.17.28.11,local_lock=none,addr=172.17.28.5) But playbook execution fails and we can not proceed with install. Please advise. Kindly awaiting your reply. Marko Vrgotic

2 1

Re: ovirt metrics ansible error
by Jayme 29 May '19

29 May '19

I just tried again from scratch this time making sure a proper wildcard DNS entry existed and without using the set /etc/hosts option and am still running in to the pods issue. Can anyone confirm if this requires a public external IP to work? I am working on an internal DNS zone here and natted ips. On Tue, May 28, 2019 at 3:28 PM Edward Berger <edwberger(a)gmail.com> wrote: > In my case it was a single bare metal host, so that would be equivalent to > disabling iptables on the master0 VM you're installing to, in your ovirt > scenario. > > On Tue, May 28, 2019 at 1:25 PM Jayme <jaymef(a)gmail.com> wrote: > >> Do you mean the iptables firewall on the server being installed to i.e. >> master0 or the actual oVirt host that the master0 VM is running on? I did >> try flushing iptables rules on master0 VM then ran plays again from >> installer VM but fail at the same point. >> >> Does this log message have anything to do with the issue, /etc/cni >> directory does not even exist on master0 VM. >> >> May 28 17:23:35 master0 origin-node: W0528 17:23:35.012902 10434 >> cni.go:172] Unable to update cni config: No networks found in /etc/cni/net.d >> May 28 17:23:35 master0 origin-node: E0528 17:23:35.013398 10434 >> kubelet.go:2101] Container runtime network not ready: NetworkReady=false >> reason:NetworkPluginNotReady message:docker: network plugin is not ready: >> cni config uninitialized >> >> >> >> On Tue, May 28, 2019 at 1:19 PM Edward Berger <edwberger(a)gmail.com> >> wrote: >> >>> > TASK [openshift_control_plane : Wait for control plane pods to appear] >>> ********* >>> > Monday 27 May 2019 13:31:54 +0000 (0:00:00.180) 0:14:33.857 >>> ************ >>> > FAILED - RETRYING: Wait for control plane pods to appear (60 retries >>> left). >>> > FAILED - RETRYING: Wait for control plane pods to appear (59 retries >>> left). >>> > It eventually counts all the way down to zero and fails. >>> >>> This looks a lot like the issues I saw when the host firewall (iptables) >>> was blocking another OKD all-in-one-host install script [1]. >>> Disabling iptables allowed the installation to continue for my proof of >>> concept "cluster". >>> >>> [1]https://github.com/gshipley/installcentos >>> >>> The other error I had with [1] was it was trying to install a couple of >>> packages (zile and python2-pip) from EPEL with the repo disabled. >>> >>> >>> >>> On Tue, May 28, 2019 at 10:41 AM Jayme <jaymef(a)gmail.com> wrote: >>> >>>> Shirly, >>>> >>>> Oh and I should mention that I did verify that NetworkManager was >>>> installed on the master0 VM and enabled/started the second go around. So >>>> that service is there and running. >>>> >>>> # systemctl list-unit-files | grep Network >>>> dbus-org.freedesktop.NetworkManager.service >>>> enabled >>>> NetworkManager-dispatcher.service >>>> enabled >>>> NetworkManager-wait-online.service >>>> enabled >>>> NetworkManager.service >>>> enabled >>>> >>>> On Tue, May 28, 2019 at 11:13 AM Jayme <jaymef(a)gmail.com> wrote: >>>> >>>>> Shirly, >>>>> >>>>> I appreciate the help with this. Unfortunately I am still running in >>>>> to the same problem. So far I've tried to install/enable/start >>>>> NetworkManager on the existing "master0" server and re-ran the plans from >>>>> the installer VM. I ran in to the same problem waiting for control plane >>>>> pods and same errors in syslog. >>>>> >>>>> So I wiped everything out, killed the template along with the >>>>> installer and master VMs. On oVirt engine (I am running 4.3.3.7-1 stable) >>>>> I did have ovirt-engine-metrics-1.3.0x rpm installed, no yum updates >>>>> available on an update check. So I installed >>>>> http://resources.ovirt.org/pub/yum-repo/ovirt-release43-pre.rpm then >>>>> proceeded to install the latest version of ovirt-engine-metrics which gave >>>>> me: ovirt-engine-metrics-1.3.1-1.el7.noarch on hosted engine. >>>>> >>>>> After that package was installed I proceeded to follow steps from >>>>> beginning outlined at: >>>>> https://ovirt.org/documentation/metrics-install-guide/Installing_Metrics_St… -- >>>>> I ran in to the docker check issue again (same as my initial email) so I >>>>> disabled that and again got as far as starting control plane pods before >>>>> failure. >>>>> >>>>> Not sure where to go from here at this point. The only thing I can >>>>> think of that I did differently vs the instructions outlined above is that >>>>> I have not crated the wildcard DNS record, however I did set configs to >>>>> create /etc/hosts entries and they /etc/hosts on the machines have the >>>>> proper IPs assigned for all hostnames (automatically added by the ansible >>>>> plays). >>>>> >>>>> Any ideas how I can get past the plane pods issue? >>>>> >>>>> Thanks! >>>>> >>>>> On Tue, May 28, 2019 at 4:23 AM Shirly Radco <sradco(a)redhat.com> >>>>> wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> The latest release of 4.3.z should already include a fix for this >>>>>> issue, ovirt-engine-metrics-1.3.1 rpm. >>>>>> >>>>>> The issue is that it requires the NetworkManagar to be installed, >>>>>> running and enabled for it to work. >>>>>> >>>>>> You can install it manually on the master0 vm , start and enable it >>>>>> or you can also install the updated rpm from the nightly builds if your >>>>>> environment is oVirt 4.2.z: >>>>>> >>>>>> https://resources.ovirt.org/pub/ovirt-4.2-snapshot/rpm/el7/noarch/ovirt-eng… >>>>>> >>>>>> Relevant patches are: >>>>>> https://gerrit.ovirt.org/#/c/99959/ >>>>>> https://gerrit.ovirt.org/#/c/99718/ >>>>>> >>>>>> Best regards, >>>>>> >>>>>> -- >>>>>> >>>>>> Shirly Radco >>>>>> >>>>>> BI Senior Software Engineer >>>>>> >>>>>> Red Hat <https://www.redhat.com/> >>>>>> >>>>>> <https://www.redhat.com/> >>>>>> >>>>>> >>>>>> On Mon, May 27, 2019 at 4:41 PM Jayme <jaymef(a)gmail.com> wrote: >>>>>> >>>>>>> I managed to get past that but am running in to another problem >>>>>>> later in the process on the control plane pods to appear task. I thought >>>>>>> perhaps a glitch in the process from the failed docker step previously so >>>>>>> after a few more runs I tried killing everything and restarting the metrics >>>>>>> process again from the very beginning and end up hitting the same issue >>>>>>> with control plane pods even though all other steps/tasks seem to be >>>>>>> working. >>>>>>> >>>>>>> I'm just getting this: >>>>>>> >>>>>>> TASK [openshift_control_plane : Wait for control plane pods to >>>>>>> appear] ********* >>>>>>> Monday 27 May 2019 13:31:54 +0000 (0:00:00.180) 0:14:33.857 >>>>>>> ************ >>>>>>> FAILED - RETRYING: Wait for control plane pods to appear (60 retries >>>>>>> left). >>>>>>> FAILED - RETRYING: Wait for control plane pods to appear (59 retries >>>>>>> left). >>>>>>> FAILED - RETRYING: Wait for control plane pods to appear (58 retries >>>>>>> left). >>>>>>> FAILED - RETRYING: Wait for control plane pods to appear (57 retries >>>>>>> left). >>>>>>> FAILED - RETRYING: Wait for control plane pods to appear (56 retries >>>>>>> left). >>>>>>> >>>>>>> It eventually counts all the way down to zero and fails. >>>>>>> >>>>>>> In syslog of the master0 server I'm seeing some errors related to >>>>>>> cni config >>>>>>> >>>>>>> May 27 13:39:07 master0 ansible-oc_obj: Invoked with files=None >>>>>>> kind=pod force=False all_namespaces=None field_selector=None >>>>>>> namespace=kube-system delete_after=False >>>>>>> kubeconfig=/etc/origin/master/admin.kubeconfig content=None state=list >>>>>>> debug=False selector=None name=master-api-master0.xxxxxx.com >>>>>>> May 27 13:39:09 master0 origin-node: W0527 13:39:09.064230 20150 >>>>>>> cni.go:172] Unable to update cni config: No networks found in /etc/cni/net.d >>>>>>> May 27 13:39:09 master0 origin-node: E0527 13:39:09.064670 20150 >>>>>>> kubelet.go:2101] Container runtime network not ready: NetworkReady=false >>>>>>> reason:NetworkPluginNotReady message:docker: network plugin is not ready: >>>>>>> cni config uninitialized >>>>>>> May 27 13:39:13 master0 ansible-oc_obj: Invoked with files=None >>>>>>> kind=pod force=False all_namespaces=None field_selector=None >>>>>>> namespace=kube-system delete_after=False >>>>>>> kubeconfig=/etc/origin/master/admin.kubeconfig content=None state=list >>>>>>> debug=False selector=None name=master-api-master0.xxxxxx.com >>>>>>> May 27 13:39:14 master0 origin-node: W0527 13:39:14.066911 20150 >>>>>>> cni.go:172] Unable to update cni config: No networks found in /etc/cni/net.d >>>>>>> May 27 13:39:14 master0 origin-node: E0527 13:39:14.067321 20150 >>>>>>> kubelet.go:2101] Container runtime network not ready: NetworkReady=false >>>>>>> reason:NetworkPluginNotReady message:docker: network plugin is not ready: >>>>>>> cni config uninitialized >>>>>>> May 27 13:39:14 master0 origin-node: E0527 13:39:14.814705 20150 >>>>>>> summary.go:102] Failed to get system container stats for >>>>>>> "/system.slice/origin-node.service": failed to get cgroup stats for >>>>>>> "/system.slice/origin-node.service": failed to get container info for >>>>>>> "/system.slice/origin-node.service": unknown container >>>>>>> "/system.slice/origin-node.service" >>>>>>> May 27 13:39:19 master0 origin-node: W0527 13:39:19.069450 20150 >>>>>>> cni.go:172] Unable to update cni config: No networks found in /etc/cni/net.d >>>>>>> May 27 13:39:19 master0 origin-node: E0527 13:39:19.069850 20150 >>>>>>> kubelet.go:2101] Container runtime network not ready: NetworkReady=false >>>>>>> reason:NetworkPluginNotReady message:docker: network plugin is not ready: >>>>>>> cni config uninitialized >>>>>>> >>>>>>> On Mon, May 27, 2019 at 9:35 AM Shirly Radco <sradco(a)redhat.com> >>>>>>> wrote: >>>>>>> >>>>>>>> Hi Jayme, >>>>>>>> >>>>>>>> Thank you for reaching out. >>>>>>>> Please try rerunning the ansible playbook. >>>>>>>> If this doesn't work, try adding to the integ.ini in the metrics vm >>>>>>>> openshift_disable_check=docker_storage >>>>>>>> and rerun the ansible playbook again. >>>>>>>> >>>>>>>> Please update how it goes. >>>>>>>> >>>>>>>> Best regards, >>>>>>>> >>>>>>>> -- >>>>>>>> >>>>>>>> Shirly Radco >>>>>>>> >>>>>>>> BI Senior Software Engineer >>>>>>>> >>>>>>>> Red Hat <https://www.redhat.com/> >>>>>>>> >>>>>>>> <https://www.redhat.com/> >>>>>>>> >>>>>>>> >>>>>>>> On Sun, May 26, 2019 at 9:34 PM Jayme <jaymef(a)gmail.com> wrote: >>>>>>>> >>>>>>>>> I'm running in to this ansible error during oVirt metrics >>>>>>>>> installation (following procedures at: >>>>>>>>> https://ovirt.org/documentation/metrics-install-guide/Installing_Metrics_St… >>>>>>>>> ) >>>>>>>>> >>>>>>>>> This is happening late in the process, after successfully >>>>>>>>> deploying the installation VM and then running second step from the metrics >>>>>>>>> VM. >>>>>>>>> >>>>>>>>> CHECK [memory_availability : master0.xxxxxx.com] >>>>>>>>> ************************************************************************************************* >>>>>>>>> fatal: [master0.xxxxxxx.com] FAILED! => {"changed": true, >>>>>>>>> "checks": {"disk_availability": {}, "docker_image_availability": >>>>>>>>> {"changed": true}, "docker_storage": {"failed": true, "failures": >>>>>>>>> [["OpenShiftCheckException", "Could not find imported module support code >>>>>>>>> for docker_info. Looked for either AnsibleDockerClient.py or >>>>>>>>> docker_common.py\nTraceback (most recent call last):\n File >>>>>>>>> \"/usr/share/ansible/openshift-ansible/roles/openshift_health_checker/action_plugins/openshift_health_check.py\", >>>>>>>>> line 225, in run_check\n result = check.run()\n File >>>>>>>>> \"/usr/share/ansible/openshift-ansible/roles/openshift_health_checker/openshift_checks/docker_storage.py\", >>>>>>>>> line 53, in run\n docker_info = self.execute_module(\"docker_info\", >>>>>>>>> {})\n File >>>>>>>>> \"/usr/share/ansible/openshift-ansible/roles/openshift_health_checker/openshift_checks/__init__.py\", >>>>>>>>> line 211, in execute_module\n result = self._execute_module(module_name, >>>>>>>>> module_args, self.tmp, self.task_vars)\n File >>>>>>>>> \"/usr/lib/python2.7/site-packages/ansible/plugins/action/__init__.py\", >>>>>>>>> line 809, in _execute_module\n (module_style, shebang, module_data, >>>>>>>>> module_path) = self._configure_module(module_name=module_name, >>>>>>>>> module_args=module_args, task_vars=task_vars)\n File >>>>>>>>> \"/usr/lib/python2.7/site-packages/ansible/plugins/action/__init__.py\", >>>>>>>>> line 203, in _configure_module\n environment=final_environment)\n File >>>>>>>>> \"/usr/lib/python2.7/site-packages/ansible/executor/module_common.py\", >>>>>>>>> line 1023, in modify_module\n environment=environment)\n File >>>>>>>>> \"/usr/lib/python2.7/site-packages/ansible/executor/module_common.py\", >>>>>>>>> line 859, in _find_module_utils\n recursive_finder(module_name, >>>>>>>>> b_module_data, py_module_names, py_module_cache, zf)\n File >>>>>>>>> \"/usr/lib/python2.7/site-packages/ansible/executor/module_common.py\", >>>>>>>>> line 621, in recursive_finder\n raise AnsibleError(' >>>>>>>>> '.join(msg))\nAnsibleError: Could not find imported module support code for >>>>>>>>> docker_info. Looked for either AnsibleDockerClient.py or >>>>>>>>> docker_common.py\n"]], "msg": "Could not find imported module support code >>>>>>>>> for docker_info. Looked for either AnsibleDockerClient.py or >>>>>>>>> docker_common.py\nTraceback (most recent call last):\n File >>>>>>>>> \"/usr/share/ansible/openshift-ansible/roles/openshift_health_checker/action_plugins/openshift_health_check.py\", >>>>>>>>> line 225, in run_check\n result = check.run()\n File >>>>>>>>> \"/usr/share/ansible/openshift-ansible/roles/openshift_health_checker/openshift_checks/docker_storage.py\", >>>>>>>>> line 53, in run\n docker_info = self.execute_module(\"docker_info\", >>>>>>>>> {})\n File >>>>>>>>> \"/usr/share/ansible/openshift-ansible/roles/openshift_health_checker/openshift_checks/__init__.py\", >>>>>>>>> line 211, in execute_module\n result = self._execute_module(module_name, >>>>>>>>> module_args, self.tmp, self.task_vars)\n File >>>>>>>>> \"/usr/lib/python2.7/site-packages/ansible/plugins/action/__init__.py\", >>>>>>>>> line 809, in _execute_module\n (module_style, shebang, module_data, >>>>>>>>> module_path) = self._configure_module(module_name=module_name, >>>>>>>>> module_args=module_args, task_vars=task_vars)\n File >>>>>>>>> \"/usr/lib/python2.7/site-packages/ansible/plugins/action/__init__.py\", >>>>>>>>> line 203, in _configure_module\n environment=final_environment)\n File >>>>>>>>> \"/usr/lib/python2.7/site-packages/ansible/executor/module_common.py\", >>>>>>>>> line 1023, in modify_module\n environment=environment)\n File >>>>>>>>> \"/usr/lib/python2.7/site-packages/ansible/executor/module_common.py\", >>>>>>>>> line 859, in _find_module_utils\n recursive_finder(module_name, >>>>>>>>> b_module_data, py_module_names, py_module_cache, zf)\n File >>>>>>>>> \"/usr/lib/python2.7/site-packages/ansible/executor/module_common.py\", >>>>>>>>> line 621, in recursive_finder\n raise AnsibleError(' >>>>>>>>> '.join(msg))\nAnsibleError: Could not find imported module support code for >>>>>>>>> docker_info. Looked for either AnsibleDockerClient.py or >>>>>>>>> docker_common.py\n"}, "memory_availability": {}, "package_availability": >>>>>>>>> {"changed": false, "invocation": {"module_args": {"packages": ["PyYAML", >>>>>>>>> "bash-completion", "bind", "ceph-common", "dnsmasq", "docker", "firewalld", >>>>>>>>> "flannel", "glusterfs-fuse", "httpd-tools", "iptables", >>>>>>>>> "iptables-services", "iscsi-initiator-utils", "libselinux-python", >>>>>>>>> "nfs-utils", "ntp", "openssl", "origin", "origin-clients", >>>>>>>>> "origin-hyperkube", "origin-node", "pyparted", "python-httplib2", >>>>>>>>> "yum-utils"]}}}, "package_version": {"changed": false, "invocation": >>>>>>>>> {"module_args": {"package_list": [{"check_multi": false, "name": "origin", >>>>>>>>> "version": ""}, {"check_multi": false, "name": "origin-master", "version": >>>>>>>>> ""}, {"check_multi": false, "name": "origin-node", "version": ""}], >>>>>>>>> "package_mgr": "yum"}}}}, "msg": "One or more checks failed", >>>>>>>>> "playbook_context": "install"} >>>>>>>>> >>>>>>>>> NO MORE HOSTS LEFT >>>>>>>>> ******************************************************************************************************************************************* >>>>>>>>> >>>>>>>>> PLAY RECAP >>>>>>>>> *************************************************************************************************************************************************** >>>>>>>>> localhost : ok=35 changed=1 unreachable=0 >>>>>>>>> failed=0 skipped=16 rescued=0 ignored=0 >>>>>>>>> master0.xxxxxxx.com : ok=96 changed=6 unreachable=0 >>>>>>>>> failed=1 skipped=165 rescued=0 ignored=0 >>>>>>>>> >>>>>>>>> >>>>>>>>> INSTALLER STATUS >>>>>>>>> ********************************************************************************************************************************************* >>>>>>>>> Initialization : Complete (0:00:16) >>>>>>>>> Health Check : In Progress (0:00:36) >>>>>>>>> This phase can be restarted by running: >>>>>>>>> playbooks/openshift-checks/pre-install.yml >>>>>>>>> Sunday 26 May 2019 16:36:25 +0000 (0:00:36.151) 0:01:56.339 >>>>>>>>> ************ >>>>>>>>> >>>>>>>>> =============================================================================== >>>>>>>>> Run health checks (install) - EL >>>>>>>>> --------------------------------------------------------------------------------------------------------------------- >>>>>>>>> 36.15s >>>>>>>>> os_firewall : Ensure iptables services are not enabled >>>>>>>>> ------------------------------------------------------------------------------------------------ >>>>>>>>> 2.74s >>>>>>>>> openshift_repos : Ensure libselinux-python is installed >>>>>>>>> ----------------------------------------------------------------------------------------------- >>>>>>>>> 1.77s >>>>>>>>> openshift_repos : refresh cache >>>>>>>>> ----------------------------------------------------------------------------------------------------------------------- >>>>>>>>> 1.60s >>>>>>>>> Gather Cluster facts >>>>>>>>> ---------------------------------------------------------------------------------------------------------------------------------- >>>>>>>>> 1.51s >>>>>>>>> container_runtime : Fixup SELinux permissions for docker >>>>>>>>> ---------------------------------------------------------------------------------------------- >>>>>>>>> 1.33s >>>>>>>>> container_runtime : Place additional/blocked/insecure registries >>>>>>>>> in /etc/containers/registries.conf >>>>>>>>> --------------------------------------------------- 1.30s >>>>>>>>> Ensure openshift-ansible installer package deps are installed >>>>>>>>> ----------------------------------------------------------------------------------------- >>>>>>>>> 1.29s >>>>>>>>> container_runtime : Install Docker >>>>>>>>> -------------------------------------------------------------------------------------------------------------------- >>>>>>>>> 1.17s >>>>>>>>> Initialize openshift.node.sdn_mtu >>>>>>>>> --------------------------------------------------------------------------------------------------------------------- >>>>>>>>> 1.13s >>>>>>>>> os_firewall : Install firewalld packages >>>>>>>>> -------------------------------------------------------------------------------------------------------------- >>>>>>>>> 1.13s >>>>>>>>> container_runtime : Set various Docker options >>>>>>>>> -------------------------------------------------------------------------------------------------------- >>>>>>>>> 1.11s >>>>>>>>> install NetworkManager >>>>>>>>> -------------------------------------------------------------------------------------------------------------------------------- >>>>>>>>> 1.10s >>>>>>>>> openshift_repos : Configure correct origin release repository >>>>>>>>> ----------------------------------------------------------------------------------------- >>>>>>>>> 1.05s >>>>>>>>> container_runtime : Get current installed Docker version >>>>>>>>> ---------------------------------------------------------------------------------------------- >>>>>>>>> 1.04s >>>>>>>>> openshift_repos : Configure origin gpg keys >>>>>>>>> ----------------------------------------------------------------------------------------------------------- >>>>>>>>> 1.04s >>>>>>>>> openshift_repos : Remove openshift_additional.repo file >>>>>>>>> ----------------------------------------------------------------------------------------------- >>>>>>>>> 0.99s >>>>>>>>> container_runtime : Setup the docker-storage for overlay >>>>>>>>> ---------------------------------------------------------------------------------------------- >>>>>>>>> 0.96s >>>>>>>>> Detecting Operating System from ostree_booted >>>>>>>>> --------------------------------------------------------------------------------------------------------- >>>>>>>>> 0.95s >>>>>>>>> Gather Cluster facts >>>>>>>>> ---------------------------------------------------------------------------------------------------------------------------------- >>>>>>>>> 0.92s >>>>>>>>> >>>>>>>>> >>>>>>>>> Failure summary: >>>>>>>>> >>>>>>>>> >>>>>>>>> 1. Hosts: master0.xxxxxxx.com >>>>>>>>> Play: OpenShift Health Checks >>>>>>>>> Task: Run health checks (install) - EL >>>>>>>>> Message: One or more checks failed >>>>>>>>> Details: check "docker_storage": >>>>>>>>> Could not find imported module support code for >>>>>>>>> docker_info. Looked for either AnsibleDockerClient.py or docker_common.py >>>>>>>>> Traceback (most recent call last): >>>>>>>>> File >>>>>>>>> "/usr/share/ansible/openshift-ansible/roles/openshift_health_checker/action_plugins/openshift_health_check.py", >>>>>>>>> line 225, in run_check >>>>>>>>> result = check.run() >>>>>>>>> File >>>>>>>>> "/usr/share/ansible/openshift-ansible/roles/openshift_health_checker/openshift_checks/docker_storage.py", >>>>>>>>> line 53, in run >>>>>>>>> docker_info = >>>>>>>>> self.execute_module("docker_info", {}) >>>>>>>>> File >>>>>>>>> "/usr/share/ansible/openshift-ansible/roles/openshift_health_checker/openshift_checks/__init__.py", >>>>>>>>> line 211, in execute_module >>>>>>>>> result = self._execute_module(module_name, >>>>>>>>> module_args, self.tmp, self.task_vars) >>>>>>>>> File >>>>>>>>> "/usr/lib/python2.7/site-packages/ansible/plugins/action/__init__.py", line >>>>>>>>> 809, in _execute_module >>>>>>>>> (module_style, shebang, module_data, >>>>>>>>> module_path) = self._configure_module(module_name=module_name, >>>>>>>>> module_args=module_args, task_vars=task_vars) >>>>>>>>> File >>>>>>>>> "/usr/lib/python2.7/site-packages/ansible/plugins/action/__init__.py", line >>>>>>>>> 203, in _configure_module >>>>>>>>> environment=final_environment) >>>>>>>>> File >>>>>>>>> "/usr/lib/python2.7/site-packages/ansible/executor/module_common.py", line >>>>>>>>> 1023, in modify_module >>>>>>>>> environment=environment) >>>>>>>>> File >>>>>>>>> "/usr/lib/python2.7/site-packages/ansible/executor/module_common.py", line >>>>>>>>> 859, in _find_module_utils >>>>>>>>> recursive_finder(module_name, b_module_data, >>>>>>>>> py_module_names, py_module_cache, zf) >>>>>>>>> File >>>>>>>>> "/usr/lib/python2.7/site-packages/ansible/executor/module_common.py", line >>>>>>>>> 621, in recursive_finder >>>>>>>>> raise AnsibleError(' '.join(msg)) >>>>>>>>> AnsibleError: Could not find imported module >>>>>>>>> support code for docker_info. Looked for either AnsibleDockerClient.py or >>>>>>>>> docker_common.py >>>>>>>>> >>>>>>>>> >>>>>>>>> The execution of "install_okd.yaml" includes checks designed to >>>>>>>>> fail early if the requirements of the playbook are not met. One or more of >>>>>>>>> these checks failed. To disregard these results,explicitly disable checks >>>>>>>>> by setting an Ansible variable: >>>>>>>>> openshift_disable_check=docker_storage >>>>>>>>> Failing check names are shown in the failure details above. Some >>>>>>>>> checks may be configurable by variables if your requirements are different >>>>>>>>> from the defaults; consult check documentation. >>>>>>>>> Variables can be set in the inventory or passed on the command >>>>>>>>> line using the -e flag to ansible-playbook. >>>>>>>>> _______________________________________________ >>>>>>>>> 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/SEFPOF36T7G4G… >>>>>>>>> >>>>>>>> _______________________________________________ >>>> 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/CN6G76Z7MVNK6… >>>> >>>

2 3

Dashboard error after upgrade to 4.3.2
by Mikhail Krasnobaev 29 May '19

29 May '19

3 3

Re: nested attributes of structs
by Nathanaël Blanchet 29 May '19

29 May '19

Hello Lucie, Can you give me the BZ number so I can follow the ticket? I'd like to test the ansible patch as soon as it's available. De: "Lucie Leistnerova" <lleistne(a)redhat.com> À: "Nathanaël Blanchet" <blanchet(a)abes.fr>, "users" <users(a)ovirt.org> Envoyé: Mercredi 29 Mai 2019 08:31:16 Objet: Re: [ovirt-users] nested attributes of structs Hi Nathanaël, On 5/28/19 5:21 PM, Nathanaël Blanchet wrote: Hello, Considering: https://bugzilla.redhat.com/show_bug.cgi?id=1653743 and https://github.com/ansible/ansible/issues/30624 I installed latest 4.3 sdk and ansible 2.8 but I still can't get the name of the href link doing this: - name : disk facts ovirt_disk_facts : auth : "{{ ovirt_auth }}" fetch_nested: true it still gives: "storage_domains": [ { "href": "/ovirt-engine/api/storagedomains/0dc2941a-bdc2-4ce4-8ad7-43fa9c944f88", "id": "0dc2941a-bdc2-4ce4-8ad7-43fa9c944f88" } If I understand, I should get the storage_domain name instead of its id, shouldn't I? The change seems to not work perfectly. When I run playbook with fetch_nested: True nested_attributes: - name I get "quota": { "href": "/ovirt-engine/api/datacenters/87bc2e30-f3b1-11e8-aa7d-001a4a013f36/quotas/96f2a2e4-f3b1-11e8-82b6-001a4a013f36", "id": "96f2a2e4-f3b1-11e8-82b6-001a4a013f36", "name": "Default" }, "disk_profile": { "href": "/ovirt-engine/api/storagedomains/82ceb4c9-e844-4fc7-b0ff-559052e6301f/diskprofiles/30cc8a74-4b99-4aab-8193-28826bbecbb9", "id": "30cc8a74-4b99-4aab-8193-28826bbecbb9", "name": "ll-03s1-43-3" }, So for direct link <quota href="/ovirt-engine/api/datacenters/87bc2e30-f3b1-11e8-aa7d-001a4a013f36/quotas/96f2a2e4-f3b1-11e8-82b6-001a4a013f36" id="96f2a2e4-f3b1-11e8-82b6-001a4a013f36"/> it works fine. But storage domains are different, it is a list of links. <storage_domains> <storage_domain href="/ovirt-engine/api/storagedomains/82ceb4c9-e844-4fc7-b0ff-559052e6301f" id="82ceb4c9-e844-4fc7-b0ff-559052e6301f"/> </storage_domains> I'll check it with developer and update by verifying the BZ. Thanks for catching that issue. BQ_BEGIN -- Nathanaël Blanchet Supervision réseau Pôle Infrastrutures Informatiques 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 Tél. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 blanchet(a)abes.fr _______________________________________________ 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/L4ZHNR6YWLBQH… BQ_END Best regards, -- Lucie Leistnerova Senior Quality Engineer, QE Cloud, RHVM Red Hat EMEA IRC: lleistne @ #rhev-qe

1 0

Administration Portal "Uncaught Exception" Issue
by Zachary Winter 29 May '19

29 May '19

I am consistently receiving error warnings in the Administration Portal the read as follows: /"Uncaught exception occurred. Please try reloading the page. Details: (TypeError) : Cannot read property 'a' of null/ // /Please have your administrator check the UI logs"/ / / My questions are: 1) Where/What are the UI logs? 2) Is this a known issue, and how do I fix it? //

4 6

nested attributes of structs
by Nathanaël Blanchet 29 May '19

29 May '19

Hello, Considering: https://bugzilla.redhat.com/show_bug.cgi?id=1653743 and https://github.com/ansible/ansible/issues/30624 I installed latest 4.3 sdk and ansible 2.8 but I still can't get the name of the href link doing this: - name: disk facts ovirt_disk_facts: auth: "{{ ovirt_auth }}" fetch_nested: true it still gives: "storage_domains": [ { "href": "/ovirt-engine/api/storagedomains/0dc2941a-bdc2-4ce4-8ad7-43fa9c944f88", "id": "0dc2941a-bdc2-4ce4-8ad7-43fa9c944f88" } If I understand, I should get the storage_domain name instead of its id, shouldn't I? -- Nathanaël Blanchet Supervision réseau Pôle Infrastrutures Informatiques 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 Tél. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 blanchet(a)abes.fr

2 1

oVirt Simple Backup support?
by michael＠wanderingmad.com 29 May '19

29 May '19

I just started using oVirt Simpe backup and I see that the maintainer is no longer going to maintain it. So far it seems like the most elegant solution to backing up VMs, is someone else going to maintain it? will it be "adopted" by the oVirt team?

3 2

ovirt metrics ansible error
by Jayme 28 May '19

28 May '19

I'm running in to this ansible error during oVirt metrics installation (following procedures at: https://ovirt.org/documentation/metrics-install-guide/Installing_Metrics_St… ) This is happening late in the process, after successfully deploying the installation VM and then running second step from the metrics VM. CHECK [memory_availability : master0.xxxxxx.com] ************************************************************************************************* fatal: [master0.xxxxxxx.com] FAILED! => {"changed": true, "checks": {"disk_availability": {}, "docker_image_availability": {"changed": true}, "docker_storage": {"failed": true, "failures": [["OpenShiftCheckException", "Could not find imported module support code for docker_info. Looked for either AnsibleDockerClient.py or docker_common.py\nTraceback (most recent call last):\n File \"/usr/share/ansible/openshift-ansible/roles/openshift_health_checker/action_plugins/openshift_health_check.py\", line 225, in run_check\n result = check.run()\n File \"/usr/share/ansible/openshift-ansible/roles/openshift_health_checker/openshift_checks/docker_storage.py\", line 53, in run\n docker_info = self.execute_module(\"docker_info\", {})\n File \"/usr/share/ansible/openshift-ansible/roles/openshift_health_checker/openshift_checks/__init__.py\", line 211, in execute_module\n result = self._execute_module(module_name, module_args, self.tmp, self.task_vars)\n File \"/usr/lib/python2.7/site-packages/ansible/plugins/action/__init__.py\", line 809, in _execute_module\n (module_style, shebang, module_data, module_path) = self._configure_module(module_name=module_name, module_args=module_args, task_vars=task_vars)\n File \"/usr/lib/python2.7/site-packages/ansible/plugins/action/__init__.py\", line 203, in _configure_module\n environment=final_environment)\n File \"/usr/lib/python2.7/site-packages/ansible/executor/module_common.py\", line 1023, in modify_module\n environment=environment)\n File \"/usr/lib/python2.7/site-packages/ansible/executor/module_common.py\", line 859, in _find_module_utils\n recursive_finder(module_name, b_module_data, py_module_names, py_module_cache, zf)\n File \"/usr/lib/python2.7/site-packages/ansible/executor/module_common.py\", line 621, in recursive_finder\n raise AnsibleError(' '.join(msg))\nAnsibleError: Could not find imported module support code for docker_info. Looked for either AnsibleDockerClient.py or docker_common.py\n"]], "msg": "Could not find imported module support code for docker_info. Looked for either AnsibleDockerClient.py or docker_common.py\nTraceback (most recent call last):\n File \"/usr/share/ansible/openshift-ansible/roles/openshift_health_checker/action_plugins/openshift_health_check.py\", line 225, in run_check\n result = check.run()\n File \"/usr/share/ansible/openshift-ansible/roles/openshift_health_checker/openshift_checks/docker_storage.py\", line 53, in run\n docker_info = self.execute_module(\"docker_info\", {})\n File \"/usr/share/ansible/openshift-ansible/roles/openshift_health_checker/openshift_checks/__init__.py\", line 211, in execute_module\n result = self._execute_module(module_name, module_args, self.tmp, self.task_vars)\n File \"/usr/lib/python2.7/site-packages/ansible/plugins/action/__init__.py\", line 809, in _execute_module\n (module_style, shebang, module_data, module_path) = self._configure_module(module_name=module_name, module_args=module_args, task_vars=task_vars)\n File \"/usr/lib/python2.7/site-packages/ansible/plugins/action/__init__.py\", line 203, in _configure_module\n environment=final_environment)\n File \"/usr/lib/python2.7/site-packages/ansible/executor/module_common.py\", line 1023, in modify_module\n environment=environment)\n File \"/usr/lib/python2.7/site-packages/ansible/executor/module_common.py\", line 859, in _find_module_utils\n recursive_finder(module_name, b_module_data, py_module_names, py_module_cache, zf)\n File \"/usr/lib/python2.7/site-packages/ansible/executor/module_common.py\", line 621, in recursive_finder\n raise AnsibleError(' '.join(msg))\nAnsibleError: Could not find imported module support code for docker_info. Looked for either AnsibleDockerClient.py or docker_common.py\n"}, "memory_availability": {}, "package_availability": {"changed": false, "invocation": {"module_args": {"packages": ["PyYAML", "bash-completion", "bind", "ceph-common", "dnsmasq", "docker", "firewalld", "flannel", "glusterfs-fuse", "httpd-tools", "iptables", "iptables-services", "iscsi-initiator-utils", "libselinux-python", "nfs-utils", "ntp", "openssl", "origin", "origin-clients", "origin-hyperkube", "origin-node", "pyparted", "python-httplib2", "yum-utils"]}}}, "package_version": {"changed": false, "invocation": {"module_args": {"package_list": [{"check_multi": false, "name": "origin", "version": ""}, {"check_multi": false, "name": "origin-master", "version": ""}, {"check_multi": false, "name": "origin-node", "version": ""}], "package_mgr": "yum"}}}}, "msg": "One or more checks failed", "playbook_context": "install"} NO MORE HOSTS LEFT ******************************************************************************************************************************************* PLAY RECAP *************************************************************************************************************************************************** localhost : ok=35 changed=1 unreachable=0 failed=0 skipped=16 rescued=0 ignored=0 master0.xxxxxxx.com : ok=96 changed=6 unreachable=0 failed=1 skipped=165 rescued=0 ignored=0 INSTALLER STATUS ********************************************************************************************************************************************* Initialization : Complete (0:00:16) Health Check : In Progress (0:00:36) This phase can be restarted by running: playbooks/openshift-checks/pre-install.yml Sunday 26 May 2019 16:36:25 +0000 (0:00:36.151) 0:01:56.339 ************ =============================================================================== Run health checks (install) - EL --------------------------------------------------------------------------------------------------------------------- 36.15s os_firewall : Ensure iptables services are not enabled ------------------------------------------------------------------------------------------------ 2.74s openshift_repos : Ensure libselinux-python is installed ----------------------------------------------------------------------------------------------- 1.77s openshift_repos : refresh cache ----------------------------------------------------------------------------------------------------------------------- 1.60s Gather Cluster facts ---------------------------------------------------------------------------------------------------------------------------------- 1.51s container_runtime : Fixup SELinux permissions for docker ---------------------------------------------------------------------------------------------- 1.33s container_runtime : Place additional/blocked/insecure registries in /etc/containers/registries.conf --------------------------------------------------- 1.30s Ensure openshift-ansible installer package deps are installed ----------------------------------------------------------------------------------------- 1.29s container_runtime : Install Docker -------------------------------------------------------------------------------------------------------------------- 1.17s Initialize openshift.node.sdn_mtu --------------------------------------------------------------------------------------------------------------------- 1.13s os_firewall : Install firewalld packages -------------------------------------------------------------------------------------------------------------- 1.13s container_runtime : Set various Docker options -------------------------------------------------------------------------------------------------------- 1.11s install NetworkManager -------------------------------------------------------------------------------------------------------------------------------- 1.10s openshift_repos : Configure correct origin release repository ----------------------------------------------------------------------------------------- 1.05s container_runtime : Get current installed Docker version ---------------------------------------------------------------------------------------------- 1.04s openshift_repos : Configure origin gpg keys ----------------------------------------------------------------------------------------------------------- 1.04s openshift_repos : Remove openshift_additional.repo file ----------------------------------------------------------------------------------------------- 0.99s container_runtime : Setup the docker-storage for overlay ---------------------------------------------------------------------------------------------- 0.96s Detecting Operating System from ostree_booted --------------------------------------------------------------------------------------------------------- 0.95s Gather Cluster facts ---------------------------------------------------------------------------------------------------------------------------------- 0.92s Failure summary: 1. Hosts: master0.xxxxxxx.com Play: OpenShift Health Checks Task: Run health checks (install) - EL Message: One or more checks failed Details: check "docker_storage": Could not find imported module support code for docker_info. Looked for either AnsibleDockerClient.py or docker_common.py Traceback (most recent call last): File "/usr/share/ansible/openshift-ansible/roles/openshift_health_checker/action_plugins/openshift_health_check.py", line 225, in run_check result = check.run() File "/usr/share/ansible/openshift-ansible/roles/openshift_health_checker/openshift_checks/docker_storage.py", line 53, in run docker_info = self.execute_module("docker_info", {}) File "/usr/share/ansible/openshift-ansible/roles/openshift_health_checker/openshift_checks/__init__.py", line 211, in execute_module result = self._execute_module(module_name, module_args, self.tmp, self.task_vars) File "/usr/lib/python2.7/site-packages/ansible/plugins/action/__init__.py", line 809, in _execute_module (module_style, shebang, module_data, module_path) = self._configure_module(module_name=module_name, module_args=module_args, task_vars=task_vars) File "/usr/lib/python2.7/site-packages/ansible/plugins/action/__init__.py", line 203, in _configure_module environment=final_environment) File "/usr/lib/python2.7/site-packages/ansible/executor/module_common.py", line 1023, in modify_module environment=environment) File "/usr/lib/python2.7/site-packages/ansible/executor/module_common.py", line 859, in _find_module_utils recursive_finder(module_name, b_module_data, py_module_names, py_module_cache, zf) File "/usr/lib/python2.7/site-packages/ansible/executor/module_common.py", line 621, in recursive_finder raise AnsibleError(' '.join(msg)) AnsibleError: Could not find imported module support code for docker_info. Looked for either AnsibleDockerClient.py or docker_common.py The execution of "install_okd.yaml" includes checks designed to fail early if the requirements of the playbook are not met. One or more of these checks failed. To disregard these results,explicitly disable checks by setting an Ansible variable: openshift_disable_check=docker_storage Failing check names are shown in the failure details above. Some checks may be configurable by variables if your requirements are different from the defaults; consult check documentation. Variables can be set in the inventory or passed on the command line using the -e flag to ansible-playbook.

3 8

Windows Server 2019 Drivers
by racevedo＠lenovo.com 28 May '19

28 May '19

We have updated to oVirt 4.3.3.1 and I'm trying to create a Windows Server 2019 VM. When It's time to select the drivers so the windows installer can detect the hard disk, I am unable to find working drivers. I've tried using virtio-win-0.1.141.iso, oVirt-toolsSetup_4.3-2.el7.iso as well as attaching virtio-0.1.141_amd64.fvd and virtio-0.1.141_x86.fvd as a floppy disk. I've eventually tried every directory manually in those iso's. Can someone link proper documentation on how to get Windows Server 2019 to work or point to the correct drivers? Thanks

5 4

Intermittent packet loss after VM startup. 4.3.3
by Jacob Green 28 May '19

28 May '19

I have an oVirt dev environment, and I have one host and the engine as well as VMs running on a network that looks something like this 172.16.12.0/24 when I start a Windows 10 VM, 1903 or 1809 I start getting issues all across that sub-net. It happens to be my server subnet. Now we have not had any catastrophic interruptions because of it but the behavior is weird. But its weird, this dev environment when I bring up a windows 10 VM on the ovirtmgmt network riding on the same vlan I experience this insane packet loss when I am pinging from my desktop machine to my dhcp server which is also on the 172.16.12.0/24 subnet. The reason I am emailing the mailing lists is we had planned on moving to 4.3.3 tonight, but I cannot confirm if this weird network issue is some how related to 4.3.3 and the way its handling networking. Or if we have something wrong in our network. Just wanted to know if anyone else experience weird issues with VMs windows or otherwise on the ovirtmgmt network in 4.3.3. All the VMs in this dev environment are brand new installations of their respective base OS. Windows and CentOS7 Thank you. -- Jacob Green Systems Admin American Alloy Steel 713-300-5690

2 2

Re: oVirt 4.3.4 RC1 to RC2 - Dashboard error / VM/Host/Gluster Volumes OK
by Strahil 28 May '19

28 May '19

Hi Sandro, Should I open a bug or you can do it based on this thread? Best Regards, Strahil NikolovOn May 28, 2019 10:47, "Maton, Brett" <matonb(a)ltresources.co.uk> wrote: > > I've just upgraded to 4.3.4 RC2 and have the same issue, logs attached. > > Regards, > Brett > > On Mon, 27 May 2019 at 07:47, Sandro Bonazzola <sbonazzo(a)redhat.com> wrote: >> >> >> >> Il giorno dom 26 mag 2019 alle ore 12:46 Strahil Nikolov <hunter86_bg(a)yahoo.com> ha scritto: >>> >>> Hello All, >>> >>> Just upgraded my engine from 4.3.4 RC1 to RC2 and my Dashboard is giving an error (see attached screenshot) despite everything seem to end well: >>> Error! >>> Could not fetch dashboard data. Please ensure that data warehouse is properly installed and configured. >>> >>> I have checked and the VMs and Hosts + Gluster Volumes arep roperly detected (yet all my VMs are powered off since before RC2 upgrade). >>> >>> Any clues that might help you solve that before I roll back (I have a gluster snapshot on 4.3.3-7) ? >>> >>> Best Regards, >>> Strahil Nikolov >> >> >> >> Looks like DWH service is not feeding data to the dashboard, can you please sahre your engine and dwh logs? >> Adding Shirly and Sharon. >> >> >> -- >> >> Sandro Bonazzola >> >> MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV >> >> Red Hat EMEA >> >> sbonazzo(a)redhat.com >> >> _______________________________________________ >> 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

3 2

Group Consumer on Quota not trickling down to Users in Group?
by Brian T 28 May '19

28 May '19

Good morning all, I have a problem with how Groups are handled with Quotas. Currently, when you assign a Group to a Quota, it does not make all the Users in that Group a Consumer in that Quota. As the documentation states, one would have to add each individual User in that Quota. Is this the intended design? I figure, much like how Groups are handled with other oVirt functions, that the Users in a Group assigned to a Quota should also inherit being a Consumer in that Quota. Thank you.

2 3

Can't run nested virtualization
by nicolas＠devels.es 28 May '19

28 May '19

Hi, We're running oVirt version 4.3.3, and trying to configure one of the hosts to support Nested Virtualization, but when installing the nested host it claims it doesn't support hardware virtualization. On the physical host, we've enabled nested virtualization: # cat /sys/module/kvm_intel/parameters/nested Y Content of /etc/modprobe.d/kvm.conf: options kvm_intel nested=1 options kvm_intel enable_shadow_vmcs=1 options kvm_intel enable_apicv=1 options kvm_intel ept=1 I created a VM to run on that host, which will be the nested host. I try to deploy it but the engine will show it failed because: 2019-05-10 09:11:32,006+01 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) [6381e662] EVENT_ID: VDS_INSTALL_IN_PROGRESS_ERROR(511), An error has occurred during installation of Host host1: Failed to execute stage 'Setup validation': Hardware does not support virtualization. Am I missing something here? Thanks.

4 15

How to assign 1 VM to one user in ovirt 4.3
by Harry Conings 28 May '19

28 May '19

Hi I can not seem to find how to assign 1 VM to one user. So that the user only sees one vm in his VM portal Can anyone help ? Ovirt 4.3 thks Harry

4 3

oVirt 4.3.4 RC1 to RC2 - Dashboard error / VM/Host/Gluster Volumes OK
by Strahil Nikolov 28 May '19

28 May '19

Hello All, Just upgraded my engine from 4.3.4 RC1 to RC2 and my Dashboard is giving an error (see attached screenshot) despite everything seem to end well: Error! Could not fetch dashboard data. Please ensure that data warehouse is properly installed and configured. I have checked and the VMs and Hosts + Gluster Volumes arep roperly detected (yet all my VMs are powered off since before RC2 upgrade). Any clues that might help you solve that before I roll back (I have a gluster snapshot on 4.3.3-7) ? Best Regards,Strahil Nikolov

4 4

oVirt Node 4.3.2 Activation/Deactivation Loop
by zachary.winter＠witsconsult.com 28 May '19

28 May '19

I have a two-node cluster with one host (ovirt1) running the oVirt engine and the other running the most recent oVirt Node (4.3.2 from March 2019) software. The engine host has the following information: OS Version: RHEL - 7 - 6.1810.2.el7.centos OS Description: CentOS Linux 7 (Core) Kernel Version: 3.10.0 - 957.12.2.el7.x86_64 KVM Version: 2.12.0 - 18.el7_6.5.1 LIBVIRT Version: libvirt-4.5.0-10.el7_6.9 VDSM Version: vdsm-4.30.13-1.el7 SPICE Version: 0.14.0 - 6.el7_6.1 GlusterFS Version: [N/A] CEPH Version: librbd1-10.2.5-4.el7 Open vSwitch Version: openvswitch-2.10.1-3.el7 Kernel Features: PTI: 1, IBRS: 0, RETP: 1, SSBD: 3 VNC Encryption: Enabled Aside from the other issue I raised of seeing the "Uncaught exception occurred. Please try reloading the page. Details: (TypeError) : Cannot read property 'a' of null Please have your administrator check the UI logs" error on the main host, ovirt1 appears to functioning normally. The node (ovirt2) however is having consistent problems. The follow sequence of events is reproducible and is causing the host to enter a "NonOperational" state on the cluster: * Host ovirt2 installed * VDSM ovirt2 command ConnectStorageServerVDS failed: Message timeout which can be caused by communication issues * Host ovirt2 is not responding. Host cannot be fenced automatically because power management for the host is disabled. * Host ovirt2 cannot access the Storage Domain(s) <UNKNOWN> attached to the Data Center DataCenter1. Setting Host state to Non-Operational. (5/27/1912:43:22 PM) * (Banner appears in GUI) Failed Activating Host ovirt2.witsconsult.com * Failed to connect Host ovirt2 to Storage Pool DataCenter1 (5/27/1912:47:07 PM) * Host ovirt2 cannot access the Storage Domain(s) <UNKNOWN> attached to the Data Center DataCenter1. Setting Host state to Non-Operational. (5/27/1912:47:07 PM) * Host ovirt2 is not responding. Host cannot be fenced automatically because power management for the host is disabled. (5/27/1912:47:07 PM) * VDSM ovirt2 command ConnectStorageServerVDS failed: Message timeout which can be caused by communication issues (5/27/1912:47:07 PM) I can then re-activate ovirt2, which appears as green for approximately 5 minutes and then repeats all of the above issues. What can I do to troubleshoot this?

2 1

oVirt & Grafana
by michael＠wanderingmad.com 27 May '19

27 May '19

I have ovirt connected to my grafana and I can make some rudimentary dashboards, does anyone have any they've already made?

2 1

Donating hardware to the oVirt project - a great opportunity to contribute
by Evgheni Dereveanchin 27 May '19

27 May '19

Hi everyone, My name is Evgheni and I'm in charge of the infrastructure used by oVirt to host the code, test it and serve packages to users. Currently we heavily rely on our PHX data center [1] for these tasks. It consists of several dozen bare metal servers that work as hypervisors, storage servers and bare metal CI hosts. We use them quite effectively yet the amount of workload is always growing so now is a good time to ask our community for help. If you happen to have physical servers or VMs that could be used as part of oVirt infra - please let us know. We created a page [2] describing hardware specs that would allow us make the infra more stable and grow its capacity. If you have any other ideas or input about the oVirt infra - feel free to reach out to me or start a discussion on the Infra list [3]. Regards, Evgheni [1] https://ovirt-infra-docs.readthedocs.io/en/latest/Phoenix_Lab/Overview/inde… [2] https://ovirt.org/community/get-involved/donate-hardware.html [3] https://lists.ovirt.org/

2 1

[Ovirt 4.3] Deploy engine with OVS bridge
by s.natoli＠siinfo.eu 27 May '19

27 May '19

Hi to all! I'm trying to deploy a new hosted-engine (via CLI, hosted-engine --deploy), in a fresh installation of ovirt 4.3, with OVS bridge but there are no option to make the OVS choice instead of the linux bridge. There are some documentation of how to do ovn installation? Thank you for the support

2 1

oVirt node loses gluster volume UUID after reboot, goes to emergency mode every time I reboot.
by michael＠wanderingmad.com 27 May '19

27 May '19

This only started to happen with oVirt node 4.3, 4.2 didn't have issue. Since I updated to 4.3, every reboot the host goes into emergency mode. First few times this happened I re-installed O/S from scratch, but after some digging I found out that the drives it mounts in /etc/fstab cause the problem, specifically these mounts. All three are single drives, one is an SSD and the other 2 are individual NVME drives. UUID=732f939c-f133-4e48-8dc8-c9d21dbc0853 /gluster_bricks/storage_nvme1 auto defaults 0 0 UUID=5bb67f61-9d14-4d0b-8aa4-ae3905276797 /gluster_bricks/storage_ssd auto defaults 0 0 UUID=f55082ca-1269-4477-9bf8-7190f1add9ef /gluster_bricks/storage_nvme2 auto defaults 0 0 In order to get the host to actually boot, I have to go to console, delete those mounts, reboot, and then re-add them, and they end up with new UUIDs. all of these hosts reliably rebooted in 4.2 and earlier, but all the versions of 4.3 have this same problem (I keep updating to hope issue is fixed).

4 8