- Users - oVirt List Archives

Re: Fwd: FreeBSD after 10.3 could not boot (Freeze)
by Karli Sjöberg 26 May '18

26 May '18

1 0

hosted engine deploy failed , engine vm is shudown
by dhy336＠sina.com 26 May '18

26 May '18

Hi I deploy hosted engine face some errors.[ INFO ] TASK [Get ovirtmgmt route table id][ ERROR ] fatal: [localhost]: FAILED! => {"attempts": 50, "changed": true, "cmd": "ip rule list | grep ovirtmgmt | sed s/\\\\[.*\\\\]\\ //g | awk '{ print $9 }'", "delta": "0:00:00.004175", "end": "2018-05-26 17:41:11.892218", "rc": 0, "start": "2018-05-26 17:41:11.888043", "stderr": "", "stderr_lines": [], "stdout": "", "stdout_lines": []}[ ERROR ] Failed to execute stage 'Closing up': Failed executing ansible-playbook[ INFO ] Stage: Clean up[ INFO ] Cleaning temporary resources[ INFO ] TASK [Gathering Facts][ INFO ] ok: [localhost][ INFO ] TASK [Remove local vm dir] I find when hosted-engine -deloy run [Get ovirtmgmt route table id], my enginen VM is shutdown,and /var/log/message show my engine vm is powered down by guest-shutdown, May 26 09:32:23 engine systemd: Reloading.May 26 09:32:24 engine python: ansible-file Invoked with directory_mode=None force=False remote_src=None path=/root/heanswers.conf owner=None follow=False group=None unsafe_writes=None state=absent content=NOT_LOGGING_PARAMETER serole=None diff_peek=None setype=None selevel=None original_basename=None regexp=None validate=None src=None seuser=None recurse=False delimiter=None mode=None attributes=None backup=NoneMay 26 09:32:38 engine systemd-logind: Removed session 3.May 26 09:32:48 engine qemu-ga: info: guest-shutdown called, mode: powerdownMay 26 09:32:48 engine systemd: Started Delayed Shutdown Service.May 26 09:32:48 engine systemd: Starting Delayed Shutdown Service...May 26 09:32:48 engine systemd-shutdownd: Shutting down at Sat 2018-05-26 17:32:48 CST (poweroff)...May 26 09:32:48 engine systemd-shutdownd: Creating /run/nologin, blocking further logins...May 26 09:32:48 engine systemd: Stopping QEMU Guest Agent...May 26 09:32:48 engine systemd: Stopping Session 1 of user root.May 26 09:32:48 engine systemd: Stopped target Multi-User System.May 26 09:32:48 engine systemd: Stopping Multi-User System.May 26 09:32:48 engine systemd: Stopped Execute cloud user/final scripts.May 26 09:32:48 engine systemd: Stopping Execute cloud user/final scripts...May 26 09:32:48 engine systemd: Stopping oVirt Engine...May 26 09:32:48 engine sshd[24523]: Received signal 15; terminating.May 26 09:32:48 engine systemd: Stopping OpenSSH server daemon...May 26 09:32:48 engine systemd: Stopping The Apache HTTP Server...

1 0

Problems with configuring ovirt and neotron network integration
by Pym 25 May '18

25 May '18

Hi: Environmental information： 4.2.0 ovirt version, according to "https://www.ovirt.org/documentation/how-to/networking/overlay-networks-with…" document of it services. Both services are accessible from the browser. After the above environment is configured according to the document, I need to execute the following command "engine-config --set keyauthstoneurl =http://< host-fqdn >:35357/v2.0" on the ovirt-engine side. The following information appears: "Error setting KeystoneAuthUrl's value. No such entry." When I execute "engine-config-a | grep-i 'KeystoneAuthUrl'", there is no return value, and there is no such configuration item in the current version of ovirt. Now how do I proceed next? Thanks！

1 0

hosted-engine 4.2.3.7-1 "engine-setup"
by femi adegoke 25 May '18

25 May '18

This is oVirt 4.2.3 + Gluster. I ran yum -y update on the hosted engine. It installed 1 package & upgraded 16. Is it necessary to run "engine-setup" again after the yum update?

2 1

Hosted Engine failed
by shamilkpm＠gmail.com 25 May '18

25 May '18

I am hosting ovirt node as VM under VMware. when try to run engine setup, it getting fails and error [ INFO ] TASK [Create cloud init user-data and meta-data files] [ INFO ] TASK [Create ISO disk] [ INFO ] changed: [localhost] [ INFO ] TASK [Create local VM] [ INFO ] changed: [localhost] [ INFO ] TASK [Get local VM IP] [ ERROR ] fatal: [localhost]: FAILED! => {"attempts": 50, "changed": true, "cmd": "virsh -r net-dhcp-leases default | grep -i 00:16:3E:6A:7A:F9 | awk '{ print $5 }' | cut -f1 -d'/'", "delta": "0:00:00.095336", "end": "2018-05-25 00:52:21.390980", "rc": 0, "start": "2018-05-25 00:52:21.295644", "stderr": "", "stderr_lines": [], "stdout": "", "stdout_lines": []} [ INFO ] TASK [include_tasks] [ INFO ] ok: [localhost] [ INFO ] TASK [Remove local vm dir] [ INFO ] changed: [localhost] [ INFO ] TASK [Notify the user about a failure] [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "The system may not be provisioned according to the playbook results: please check the logs for the issue, fix accordingly or re-deploy from scratch.\n"} ANYONE CAN HELP ME ?? -SHAMZ

2 1

oVirt 4.2 host actions dropdown truncated
by Gianluca Cecchi 25 May '18

25 May '18

example of full list in oVirt 4.2.3.5 with only one host https://drive.google.com/file/d/12fj3uorno9UjBL_aNQOG0mUSqEFn-Ol4/view?usp=… example of truncated list in oVirt 4.2.3.7 with 3 hosts https://drive.google.com/file/d/1Es3YSAhcB_L-feaHdkAvwZz8BTB3sYiS/view?usp=… if I select with the mouse into the column and then scroll with mouse, I can see also the items below in the list: STOP, SSH MANAGEMENT, ecc. but all in all it seems counter-intuitive to me... I think the .5 vs the .7 in version is not the culprit. Anyone can reproduce? BTW: I reproduced the same strange behavior also in an RHV environment with latest 4.2 (updated yesterday), with two hosts. Any comments? Gianluca

2 1

[ANN] oVirt 4.2.4 First Release Candidate is now available
by Sandro Bonazzola 24 May '18

24 May '18

The oVirt Project is pleased to announce the availability of the oVirt 4.2.4 First Release Candidate, as of May 24th, 2018 This update is a release candidate of the fourth in a series of stabilization updates to the 4.2 series. This is pre-release software. This pre-release should not to be used in production. This release is available now for: * Red Hat Enterprise Linux 7.5 or later * CentOS Linux (or similar) 7.5 or later This release supports Hypervisor Hosts running: * Red Hat Enterprise Linux 7.5 or later * CentOS Linux (or similar) 7.5 or later Due to an issue with CentOS mirrors oVirt Node has not been built. We'll build and release oVirt Node as soon as the updated qemu-kvm-ev will be available on CentOS mirrors. See the release notes [1] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is available - oVirt Node is not yet available, will be provided soon[2] Additional Resources: * Read more about the oVirt 4.2.4 release highlights: http://www.ovirt.org/release/4.2.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.2.4/ [2] http://resources.ovirt.org/pub/ovirt-4.2-pre/iso/ -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> <https://redhat.com/summit>

2 3

Support for openstack keystone v3 API?
by Bernhard Dick 24 May '18

24 May '18

Hi, I wanted to try ceph with oVirt and so I've installed an openstack queens (current stable) environment containing cinder and keystone. But when I tried to add the storage provider I ended up with 404 errors in the engine log files. They are because oVirt tries using the v2.0 API, and http://HOST:5000/v2.0/tokens does not exist. If I understand the release notes of openstack correctly the section https://blueprints.launchpad.net/keystone/+spec/removed-as-of-queens includes all v2.0 API being removed from keystone. So I'm asking whether there is support for the v3 API in sight? Regards Bernhard

2 3

Error setting cluster level to 4.2
by Gianluca Cecchi 24 May '18

24 May '18

Hello, after upgrading engine (external) and the 3 hosts composing the cluster, I try to set its level to 4.2 but I receive this kind of message " Error while executing action: Update of cluster compatibility version failed because there are VMs/Templates [ov42, ovlive3, ovlive4, ovlive1, ovlive2] with incorrect configuration. To fix the issue, please go to each of them, edit, change the Custom Compatibility Version of the VM/Template to the cluster level you want to update the cluster to and press OK. If the save does not pass, fix the dialog validation. After successful cluster update, you can revert your Custom Compatibility Version change. " The ovliveN VMs are diskless where I boto from the oVirt live iso for testing and ov42 a nested single VM where I tested the oVirt 4.2 environment before upgrade of the real cluster. I suspect that the problem could be related with macspoof custom property set to true. Is this? In case how can I manage this sort of problem? Can't I have macspoof in 4.2? Thanks, Gianluca

3 3

Need advice using pacemaker on VMs for application HA
by wodel youchi 24 May '18

24 May '18

Hi, Excuse the English :) Need some advice regarding the use of high availability software on VMs on oVirt. We are migrating a physical high available application to oVirt. The HA platform uses pacemaker, it contains two nodes and a shared storage, fence (stonith) is configured to use ILO. I know that oVirt offers HA for VM, but this HA is not application aware, if a service crashes on the VM, it will not be detected. Fencing could be achieved by fence agent rhev. My questions are about the best way to migrate this platform to oVirt. - Is it a good idea to make both VMs (formally nodes) Highly-Available VMs? or may be pin each one of them to a particular hypervisor and/or use VM-Affinity? - I am thinking about the situation where the hypervisor containing one of the VMs crashes, what will be the behavior of the the fence agent on the application? - if the crashed VM is not HA, it will not start on another hypervisor, so the fence agent will try to fence a VM that does not exist anymore, and it will stuck. - if the crashed VM is HA, it will be started on another hypervisor, but what will happen with the fence agent? I think that one VM will fence the other one, and the application will still be unreachable for a longer period. - What about the shared storage, we will use a shared disk on oVirt which does not support snapshot - What are the things to avoid? Any suggestions will be appreciated. Regards.

3 2