- Users - oVirt List Archives

Can't shut down VM
by Peter Calum 16 Jan '17

16 Jan '17

Hi, I have a VM hanging in powering down state, the same VM has at snapshot hanging in state locked. - How do i solve this ? vmId='6d820a57-efef-431d-b98f-99e8fe13b6ac', oVirt Engine Version: 4.0.5.5-1.el7.centos engine log attached. -- Venlig hilsen / Kind regards Peter Calum

3 6

VDSM service won't start
by paul.greene.va 16 Jan '17

16 Jan '17

All, I'm having an issue with the vdsmd service refusing to start on a fresh install of RHEL 7.2, RHEV version 4.0. It initially came up correctly, and the command "ip a" showed a "vdsmdummy" interface and a "ovirtmgmt" interface. However after a couple of reboots, those interfaces disappeared, and running "systemctl status vdsmd" generated the message "Dependency failed for Virtual Desktop Service Manager/Job vdsmd.service/start failed with result 'dependency'". Didn't say what dependency though I have 3 hosts where this happening on 2 out of 3 hosts. For some odd reason, the one host isn't having any problems. In a Google search I found an instance where system clock timing was out of sync, and that messed it up. I checked all three hosts, as well as the RHEV manager and they all had chronyd running and the clocks appeared to be in sync. After a reboot the virtual interfaces usually initially come up, but go down again within a few minutes. Running journalctl -xe gives these three messages: "failed to start Virtual Desktop Server Manager network restoration" "Dependency failed for Virtual Desktop Server Manager" (but it doesn't say which dependency failed" "Dependency failed for MOM instance configured for VDSM purposes" (again, doesn't way which dependency) Any suggestions? Paul

4 6

Reminder: we have Wildfly's web mgmt console (with auth)
by Roy Golan 16 Jan '17

16 Jan '17

For quite some time now we can access Wildfly's web console on https://127.0.0.1:8706 It's the UI equivalent of jboss.cli but much more convenient. Example of tasks you can perform there: - Change logging settings, live - Tweak the managed thread pool (will send a different thread about it) - Shutdown/reload the service - Tweak db connection details - Get info/stats on the running setup EE components and more One of the main advantages over the old jmx method is that it uses a plugin to authenticate the engine user so your credentials should be admin@internal or any superuser for that matter. The default is to expose it to localhost and that could be change in services/ovirt-engine/ovirt-engine.xml.in.For firewalled setups, you can ssh tunnel your machine to overcome that as always. R

1 0

DWH URL in 4.0.6 ??
by Devin Acosta 15 Jan '17

15 Jan '17

I upgraded to the latest 4.0.6 and show that the Data Ware House process is running, did they change how you access the GUI for it? Going to: https://{fqdn}/ovirt-engine-reports/ no longer functions on any of my deployments? -- Devin Acosta Red Hat Certified Architect, LinuxStack 602-354-1220 || devin(a)linuxguru.co

3 2

[ANN] oVirt 4.0.6 Release is now available
by Sandro Bonazzola 15 Jan '17

15 Jan '17

The oVirt Project is pleased to announce the general availability of oVirt 4.0.6, as of January 10th, 2016. This release is available now for: * Red Hat Enterprise Linux 7.3 or later * CentOS Linux (or similar) 7.3 or later * Fedora 23 (tech preview) This release supports Hypervisor Hosts running: * Red Hat Enterprise Linux 7.3 or later * CentOS Linux (or similar) 7.3 or later * Fedora 23 (tech preview) * oVirt Next Generation Node 4.0 This update is the sixth in a series of stabilization updates to the 4.0 series. 4.0.6 brings 4 enhancements and 59 bugfixes, including 24 high or urgent severity fixes, on top of oVirt 4.0 series See the release notes [1] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: * A new oVirt Live ISO is already available. [2] * A new oVirt Next Generation Node will be available soon [2] * A new oVirt Engine Appliance is already available for Red Hat Enterprise Linux and CentOS Linux (or similar) * Mirrors[3] might need up to one day to synchronize. Additional Resources: * Read more about the oVirt 4.0.6 release highlights: http://www.ovirt.org/release/4.0.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.0.6/ [2] http://resources.ovirt.org/pub/ovirt-4.0-pre/iso/ [3] http://www.ovirt.org/Repository_mirrors#Current_mirrors -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

7 13

Ovirt Host Error while executing action: Cannot add Host. Host with the same address already exists
by Jeramy Johnson 14 Jan '17

14 Jan '17

Hey guys I wanted to know if anyone ever recieved this error before "Error while executing action: Cannot add Host. Host with the same address already exists" when trying to re-add a Host that you deleted? I think the host maybe partially deleted or have records somewhere. Let me know if anyone can help? Thanks,

2 1

question regarding fencing proxies
by cmc 14 Jan '17

14 Jan '17

Hi, Can someone tell me how the engine decides which power management proxy/proxies to use (using default cluster/dc config)? I am using drac 7 for a fence agent in my two host cluster, and have noticed that one of the hosts cannot contact the drac. My guess is that the engine is using one host to as a power management proxy and hosts cannot reach their own drac as they are on the same interface + vlan. Example scenario: Engine uses host 2 as power management proxy. It can contact host 1’s drac, but cannot contact its own drac. In the case of host 2 being unreachable/kdumping etc, would the engine switch to use host 1 as the proxy to contact host 2’s drac? Thanks, Cam PS: I'd like to use the APC as an additional fencing agent, each host has two PSUs connected to two different APCs. Is there a guide on how to specify two ports on two different PDUs to control power on a host?

3 3

vdsm IOProcessClient WARNING Timeout waiting for communication thread for client
by Bill James 13 Jan '17

13 Jan '17

We have an ovirt system with 3 clusters, all running centos7. ovirt engine is running on separate host, ovirt-engine-3.6.4.1-1.el7.centos.noarch 2 of the clusters are running newer version of ovirt, 3 nodes each, ovirt-engine-4.0.3-1.el7.centos.noarch, glusterfs-3.7.16-1.el7.x86_64, vdsm-4.18.11-1.el7.centos.x86_64. 1 cluster is still running the older version, ovirt-engine-3.6.4.1-1.el7.centos.noarch. Yes we are in the process of upgrading the whole system to ovirt4.0, but takes time.... One of the 2 clusters running ovirt4 is complaining of timeouts, vdsm talking to gluster. No warnings on the 2 other clusters. Thread-720062::DEBUG::2017-01-13 07:29:46,814::outOfProcess::87::Storage.oop::(getProcessPool) Creating ioprocess /rhev/data-center/mnt/glusterSD/ovirt1-gl.dmz.p rod.j2noc.com:_gv1 Thread-720062::INFO::2017-01-13 07:29:46,814::__init__::325::IOProcessClient::(__init__) Starting client ioprocess-5874 Thread-720062::DEBUG::2017-01-13 07:29:46,814::__init__::334::IOProcessClient::(_run) Starting ioprocess for client ioprocess-5874 Thread-720062::DEBUG::2017-01-13 07:29:46,832::__init__::386::IOProcessClient::(_startCommunication) Starting communication thread for client ioprocess-5874 *Thread-720062::WARNING::2017-01-13 07:29:46,847::__init__::401::IOProcessClient::(_startCommunication) Timeout waiting for communication thread for client ioproc**ess-5874* [2017-01-12 07:27:58.685680] I [MSGID: 106488] [glusterd-handler.c:1533:__glusterd_handle_cli_get_volume] 0-glusterd: Received get vol req The message "I [MSGID: 106488] [glusterd-handler.c:1533:__glusterd_handle_cli_get_volume] 0-glusterd: Received get vol req" repeated 31 times between [2017-01-12 07:27:58.685680] and [2017-01-12 07:29:46.971939] attached logs: engine.log supervdsm.log vdsm.log etc-glusterfs-glusterd.vol.log cli.log

2 2

OVirt 4 / Migration issue
by Devin Acosta 13 Jan '17

13 Jan '17

I have a cluster that is running OVirt 4.0.5-2, and I notice in the vdsm.log when I try to migrate I keep seeing this error: Thread-54::ERROR::2017-01-10 16:42:31,465::migration::254::virt.vm::(_recover) vmId=`e2390382-ee5b-4552-a980-487143885802`::migration destination error: Destination hook failed: Hook Error: ('openstacknet hook: [unexpected error]: Traceback (most recent call last):\n File "/usr/libexec/vdsm/hooks/before_device_migrate_destination/50_openstacknet", line 75, in <module>\n main()\n File "/usr/libexec/vdsm/hooks/before_device_migrate_destination/50_openstacknet", line 47, in main\n pluginType = os.environ[PLUGIN_TYPE_KEY]\n File "/usr/lib64/python2.7/UserDict.py", line 23, in __getitem__\n raise KeyError(key)\nKeyError: \'plugin_type\'\n\n\n',) Any idea how to fix this? -- Devin Acosta Red Hat Certified Architect, LinuxStack 602-354-1220 || devin(a)linuxguru.co

1 1

Unable to delete VM disk
by cmc 13 Jan '17

13 Jan '17

Hi, I'm trying to delete a disk from a host I have shut down, as I need to provision a larger one. When I try to delete it, it gives me an exception on the UI. I've tried removing the bootable flag, and creating another disk, but it still won't allow the deletion of the disk. I can't see a relevant error in the engine log, though there are errors in the UI log, but I expect that is just as result of the underlying issue with deleting the disk. Thanks, Cam

4 20