- Users - oVirt List Archives

sdk api and follow question / bug
by Peter Hudec 14 May '18

14 May '18

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi, I'm using API to get stats about the VM using the FOLLOW syntax described in http://ovirt.github.io/ovirt-engine-api-model/4.2/#documents/003_common_ concepts/follow In my case I list all VM with FOLLOWING - 'statistics', - 'nics.statistics', - 'disk_attachments.disk.statistics' On my env with about 50 VM the query took about 12s but the paring for the monitoring system is easy. The question is, it's better to split the code and use more queries as the note in the API docs recommends? Not sure it will be faster and less cpu intensive on the engine side. Also the disk_attachments.disk.statistics on VMs seems to be broken, I'm not getting the data on 4.2.2 installation. /using json syntax, not xml/ regards Peter - -- *Peter Hudec* Infraštruktúrny architekt phudec(a)cnc.sk <mailto:phudec@cnc.sk> *CNC, a.s.* Borská 6, 841 04 Bratislava Recepcia: +421 2 35 000 100 Mobil:+421 905 997 203 *www.cnc.sk* <http:///www.cnc.sk> -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEERCwM7E/ZOYb1ejhCbZu8qDuIhFsFAlr0A60ACgkQbZu8qDuI hFuh9RAAxP7o7Ve7tGN2c9ClG5FQcOpUH9Jwa6JiieEauFP3ivIdN1vVwA+YhgVW Ij9iDrXBWdtlVrlQojqInMrWjNUQoeSAiJGTee/LztjeKrxK7Hkbd6JC8GAL0WbK NWjHtzODX98MHhY7tgFoCW0xApUcN4c+jp5E8IuN/Gh19Ml3Nk9okUbbXDAnOxNK 1n5y1wnye2Gjk7hVwHoccY4V74FgjQ/hKbVRwjhDXHsHa9VHBpLJKtRhu1+5JdDj ba79B5KM7w9CYI/QnLDsKeGLHsEylEnw6zY6+seitRAtIGfe7XB+PDddt9dSoC91 bwZfVEx6GCUr6lp+YJsbd/BCFdjLpMhWuI1q3d0A1rzuB4P/9/ehK2fB5ZtE5IDx snkfNOk9sn/+AxuR79GnORdAOL38VFtNg1vZeHBVCg9byQ+mPcIlXdavYmZw9Sn3 lqsuS8xzcVltRw30eF9ne8uIlDETUdLQ84/RI2kxcbXT6naGWH9pbtto5ttY84Oc QLAzIKeSFj9GFQm06b5wCReA7gpApU1eMeBlXEhGfUwwpQ4Ma2QjGVHLM6yyIbHG uqKQcaU2z0gZANmDMw1RSv6AbDiDYvF5UNznCJklrxKycLKgiLVYEfsDcT8+mSKK pFqazDVn6HzEa+SnU+peSQxb0N1oCfnufUqyCumih+8FNmjr1V8= =u7vS -----END PGP SIGNATURE-----

2 2

oVirt 4.2.3 on RHEL/CentOS 7.5
by Stefano Stagnaro 14 May '18

14 May '18

Hello, since oVirt 4.2.3 release notes still indicates the availability for EL 7.4, I would like to know if the release has been tested for EL 7.5 yet and it's safe to install the VDSM on it (instead of oVirt Node). Thank you. -- Stefano Stagnaro Prisma Telecom Testing S.r.l. Via Petrocchi, 4 20127 Milano – Italy Tel. 02 26113507 int 339 e-mail: stefanos(a)prismatelecomtesting.com skype: stefano.stagnaro

2 1

oVirt guest agent on OpenSUSE 42.3 Leap
by Magnus Isaksson 14 May '18

14 May '18

Hi all I have some trouble with guest agent for OpenSUSE 42.3 Leap, short version, it don’t start. I have followed instructions that I could find about this error, but all I could find was for Debian 8 (http://lists.ovirt.org/pipermail/users/2018-January/086102.html) Still same problem. Anyone who can help me get this right? # cat /etc/os-release NAME="openSUSE Leap" VERSION="42.3" -------- # systemctl status ovirt-guest-agent ● ovirt-guest-agent.service - oVirt Guest Agent Loaded: loaded (/usr/lib/systemd/system/ovirt-guest-agent.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Mon 2018-05-07 17:25:40 CEST; 17h ago Process: 1167 ExecStart=/usr/bin/python /usr/share/ovirt-guest-agent/ovirt-guest-agent.py (code=exited, status=1/FAILURE) Process: 1156 ExecStartPre=/bin/chown ovirtagent:ovirtagent /run/ovirt-guest-agent.pid (code=exited, status=0/SUCCESS) Process: 1141 ExecStartPre=/bin/touch /run/ovirt-guest-agent.pid (code=exited, status=0/SUCCESS) Process: 1132 ExecStartPre=/sbin/modprobe virtio_console (code=exited, status=0/SUCCESS) Main PID: 1167 (code=exited, status=1/FAILURE) May 07 17:25:39 seweb03 systemd[1]: Starting oVirt Guest Agent... May 07 17:25:39 seweb03 systemd[1]: Started oVirt Guest Agent. May 07 17:25:40 seweb03 systemd[1]: ovirt-guest-agent.service: Main process exited, code=exited, status=1/FAILURE May 07 17:25:40 seweb03 systemd[1]: ovirt-guest-agent.service: Unit entered failed state. May 07 17:25:40 seweb03 systemd[1]: ovirt-guest-agent.service: Failed with result 'exit-code'. ------ From /var/log/ovirt-guest-agent/ovirt-guest-agent.log MainThread::INFO::2018-05-08 10:47:48,782::ovirt-guest-agent::59::root::Starting oVirt guest agent MainThread::ERROR::2018-05-08 10:47:48,783::ovirt-guest-agent::140::root::Unhandled exception in oVirt guest agent! Traceback (most recent call last): File "/usr/share/ovirt-guest-agent/ovirt-guest-agent.py", line 134, in <module> agent.run(daemon, pidfile) File "/usr/share/ovirt-guest-agent/ovirt-guest-agent.py", line 65, in run self.agent = LinuxVdsAgent(config) File "/usr/share/ovirt-guest-agent/GuestAgentLinux2.py", line 466, in __init__ AgentLogicBase.__init__(self, config) File "/usr/share/ovirt-guest-agent/OVirtAgentLogic.py", line 188, in __init__ self.vio = VirtIoChannel(config.get("virtio", "device")) File "/usr/share/ovirt-guest-agent/VirtIoChannel.py", line 151, in __init__ self._stream = VirtIoStream(vport_name) File "/usr/share/ovirt-guest-agent/VirtIoChannel.py", line 132, in __init__ self._vport = os.open(vport_name, os.O_RDWR) OSError: [Errno 13] Permission denied: '/dev/virtio-ports/ovirt-guest-agent.0' ----- # zypper info ovirt-guest-agent-common Loading repository data... Reading installed packages... Information for package ovirt-guest-agent-common: ------------------------------------------------- Repository : openSUSE-Leap-42.3-0 Name : ovirt-guest-agent-common Version : 1.0.12-3.1 Arch : noarch Vendor : openSUSE Installed Size : 140.0 KiB Installed : Yes Status : up-to-date Source package : ovirt-guest-agent-1.0.12-3.1.src Summary : Commonly used files of the oVirt Guest Agent Description : This is the oVirt management agent running inside the guest. The agent interfaces with the oVirt manager, supplying heart-beat info as well as run-time data from within the guest itself. The agent also accepts control commands to be run executed within the OS (like: shutdown and restart). ----- # zypper lr Repository priorities are without effect. All enabled repositories share the same priority. # | Alias | Name | Enabled | GPG Check | Refresh ---+---------------------------+-----------------------------------------+---------+-----------+-------- 1 | Virtualization_oVirt | oVirt (openSUSE_Leap_42.3) | Yes | (r ) Yes | No Regards Magnus

2 2

ovirt-error spm
by Арслан 14 May '18

14 May '18

Hello. There are hosts on which the OS centos7.3 Ovirt 4.1 service is deployed on hosts Hosts have been added to the ovirt cluster. SPM can not be assigned to any host. In logs such error: VDSM node2.exmple.local command HSMGetAllTasksStatusesVDS failed: Not SPM: () Can you tell me what could be the problem? If necessary, I will provide more voluminous logs. -- С уважением, Кубанов Арслан Инженер Департамент сетевой интеграции ЛАНИТ 129075, г. Москва, Мурманский проезд, д. 14, корп. 1 Тел.: +7 (495) 967-6650 #18287 www.lanit.ru

1 0

Package conflicts with release of oVirt 4.2.3 and CentOS 7.5 (cockpit packages required by ovirt)
by Sam McLeod 14 May '18

14 May '18

Howdy all, I've again been hit by packaging conflicts with the release of oVirt 4.2.3 and CentOS 7.5. The error I'm getting when running yum upgrade then accepting the list of packages to upgrade is: Transaction check error: file /usr/share/cockpit/networkmanager/manifest.json from install of cockpit-system-160-3.el7.centos.noarch conflicts with file from package cockpit-networkmanager-160-1.el7.centos.noarch * Both these packages are provided as part of centos extras, this leaves me wondering if this repo is expected to be disabled when oVirt is installed? * If that is the case, there should probably be some clear documentation on what yum repos should not ever be enabled when using oVirt as it seems package conflicts are very common - thoughts? The two packages: # yum info cockpit-system-160-3.el7.centos.noarch Loaded plugins: fastestmirror, package_upload, priorities, product-id, protectbase, rpm-warm-cache, search-disabled-repos, subscription-manager, versionlock This system is not registered with an entitlement server. You can use subscription-manager to register. Loading mirror speeds from cached hostfile 0 packages excluded due to repository protections Available Packages Name : cockpit-system Arch : noarch Version : 160 Release : 3.el7.centos Size : 1.1 M Repo : extras/7/x86_64 Summary : Cockpit admin interface package for configuring and troubleshooting a system URL : http://cockpit-project.org/ License : LGPLv2+ Description : This package contains the Cockpit shell and system configuration interfaces. # yum info cockpit-networkmanager-160-1.el7.centos.noarch Loaded plugins: fastestmirror, package_upload, priorities, product-id, protectbase, rpm-warm-cache, search-disabled-repos, subscription-manager, versionlock This system is not registered with an entitlement server. You can use subscription-manager to register. Loading mirror speeds from cached hostfile 0 packages excluded due to repository protections Installed Packages Name : cockpit-networkmanager Arch : noarch Version : 160 Release : 1.el7.centos Size : 114 k Repo : installed From repo : extras Summary : Cockpit user interface for networking, using NetworkManager URL : http://cockpit-project.org/ License : LGPLv2+ Description : The Cockpit component for managing networking. This package uses NetworkManager. -- Sam McLeod (protoporpoise on IRC) https://smcleod.net https://twitter.com/s_mcleod Words are my own opinions and do not necessarily represent those of my employer or partners.

4 7

oVirt 4.2.3 on RHEL/CentOS 7.5
by Stefano Stagnaro 14 May '18

14 May '18

Hello, since oVirt 4.2.3 release notes still indicates the availability for EL 7.4, I would like to know if the release has been tested for EL 7.5 yet and it's safe to install the VDSM on it (instead of oVirt Node). Thank you. -- Stefano Stagnaro Prisma Telecom Testing S.r.l. Via Petrocchi, 4 20127 Milano – Italy Tel. 02 26113507 int 339 e-mail: stefanos(a)prismatelecomtesting.com skype: stefano.stagnaro

1 0

Re: Ovirt Self Hosted engine deploy fails
by Simone Tiraboschi 14 May '18

14 May '18

Adding back the list as it could also help others. Can you please try manually starting ovn-controller checking where it's failing? On Mon, May 14, 2018 at 10:27 AM, Sumit Bharadia <03ce007(a)gmail.com> wrote: > the service has failed to start. Any suggestions? > > -- Logs begin at Mon 2018-05-14 06:51:03 BST, end at Mon 2018-05-14 > 09:21:48 BST. -- > May 14 06:51:28 ovirt systemd[1]: Dependency failed for OVN controller > daemon. > -- Subject: Unit ovn-controller.service has failed > -- Defined-By: systemd > -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel > -- > -- Unit ovn-controller.service has failed. > -- > -- The result is dependency. > May 14 06:51:28 ovirt systemd[1]: Job ovn-controller.service/start failed > with result 'dependency'. > May 14 07:02:40 ovirt systemd[1]: Dependency failed for OVN controller > daemon. > -- Subject: Unit ovn-controller.service has failed > -- Defined-By: systemd > -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel > -- > -- Unit ovn-controller.service has failed. > -- > -- The result is dependency. > May 14 07:02:40 ovirt systemd[1]: Job ovn-controller.service/start failed > with result 'dependency'. > May 14 08:04:51 ovirt systemd[1]: Dependency failed for OVN controller > daemon. > -- Subject: Unit ovn-controller.service has failed > -- Defined-By: systemd > -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel > -- > -- Unit ovn-controller.service has failed. > -- > -- The result is dependency. > May 14 08:04:51 ovirt systemd[1]: Job ovn-controller.service/start failed > with result 'dependency'. > > > > > On 14 May 2018 at 09:12, Simone Tiraboschi <stirabos(a)redhat.com> wrote: > >> >> >> On Mon, May 14, 2018 at 10:03 AM, Sumit Bharadia <03ce007(a)gmail.com> >> wrote: >> >>> attached from engine VM. >>> >> >> >> The issue is here: >> >> 2018-05-14 08:04:50,596 p=26024 u=ovirt | TASK >> [ovirt-provider-ovn-driver : Ensure ovn-controller is started] ************ >> 2018-05-14 08:04:51,991 p=26024 u=ovirt | fatal: [ovirt]: FAILED! => { >> "changed": false >> } >> >> MSG: >> >> Unable to start service ovn-controller: A dependency job for >> ovn-controller.service failed. See 'journalctl -xe' for details. >> >> >> Can you please double check the output of: >> journalctl -xe -u ovn-controller >> >> >> >>> >>> Thank you. >>> >>> On 14 May 2018 at 08:46, Simone Tiraboschi <stirabos(a)redhat.com> wrote: >>> >>>> Hi, >>>> can you please attach host-deploy logs? >>>> You can find them under /var/log/ovirt-engine/host-deploy on the >>>> engine VM (you can reach it with ssh from the host you tried to deploy). >>>> >>>> On Mon, May 14, 2018 at 9:27 AM, <03ce007(a)gmail.com> wrote: >>>> >>>>> I am trying to setup self hosted ovirt engine (4.2) on centos 7.4, but >>>>> the setup fails after 'Add host' task on 'wait for the host to be up'. The >>>>> log doesn't seem to give clear indication where the issue might be. But I >>>>> got below when ssh manually into ovirt appliance where the engine-deploy >>>>> runs and I see the host status as'install_failed'. >>>>> >>>>> Where the issue might be, and where can i find detailed log on failure? >>>>> >>>>> "ovirt_hosts": [ >>>>> { >>>>> "address": "ovirt", >>>>> "affinity_labels": [], >>>>> "auto_numa_status": "unknown", >>>>> "certificate": { >>>>> "organization": "ovirt", >>>>> "subject": "O=ovirt,CN=ovirt" >>>>> }, >>>>> "cluster": { >>>>> "href": "/ovirt-engine/api/clusters/ba >>>>> 170b8e-5744-11e8-8676-00163e3c9a32", >>>>> "id": "ba170b8e-5744-11e8-8676-00163e3c9a32" >>>>> }, >>>>> "comment": "", >>>>> "cpu": { >>>>> "speed": 0.0, >>>>> "topology": {} >>>>> }, >>>>> "device_passthrough": { >>>>> "enabled": false >>>>> }, >>>>> "devices": [], >>>>> "external_network_provider_configurations": [], >>>>> "external_status": "ok", >>>>> "hardware_information": { >>>>> "supported_rng_sources": [] >>>>> }, >>>>> "hooks": [], >>>>> "href": "/ovirt-engine/api/hosts/aad0f >>>>> e84-2a9b-446d-ac02-82a8f6eb2a3c", >>>>> "id": "aad0fe84-2a9b-446d-ac02-82a8f6eb2a3c", >>>>> "katello_errata": [], >>>>> "kdump_status": "unknown", >>>>> "ksm": { >>>>> "enabled": false >>>>> }, >>>>> "max_scheduling_memory": 0, >>>>> "memory": 0, >>>>> "name": "ovirt", >>>>> "network_attachments": [], >>>>> "nics": [], >>>>> "numa_nodes": [], >>>>> "numa_supported": false, >>>>> "os": { >>>>> "custom_kernel_cmdline": "" >>>>> }, >>>>> "permissions": [], >>>>> "port": 54321, >>>>> "power_management": { >>>>> "automatic_pm_enabled": true, >>>>> "enabled": false, >>>>> "kdump_detection": true, >>>>> "pm_proxies": [] >>>>> }, >>>>> "protocol": "stomp", >>>>> "se_linux": {}, >>>>> "spm": { >>>>> "priority": 5, >>>>> "status": "none" >>>>> }, >>>>> "ssh": { >>>>> "fingerprint": "SHA256:o98ZOygBK0jcfY+l5nfi0E >>>>> GV9v3A4zjclG9d+C3U0WA", >>>>> "port": 22 >>>>> }, >>>>> "statistics": [], >>>>> "status": "install_failed", >>>>> "storage_connection_extensions": [], >>>>> "summary": { >>>>> "total": 0 >>>>> }, >>>>> "tags": [], >>>>> "transparent_huge_pages": { >>>>> "enabled": false >>>>> }, >>>>> "type": "rhel", >>>>> "unmanaged_networks": [], >>>>> "update_available": false >>>>> } >>>>> _______________________________________________ >>>>> Users mailing list -- users(a)ovirt.org >>>>> To unsubscribe send an email to users-leave(a)ovirt.org >>>>> >>>> >>>> >>> >> >

1 0

Ovirt Self Hosted engine deploy fails
by 03ce007＠gmail.com 14 May '18

14 May '18

I am trying to setup self hosted ovirt engine (4.2) on centos 7.4, but the setup fails after 'Add host' task on 'wait for the host to be up'. The log doesn't seem to give clear indication where the issue might be. But I got below when ssh manually into ovirt appliance where the engine-deploy runs and I see the host status as'install_failed'. Where the issue might be, and where can i find detailed log on failure? "ovirt_hosts": [ { "address": "ovirt", "affinity_labels": [], "auto_numa_status": "unknown", "certificate": { "organization": "ovirt", "subject": "O=ovirt,CN=ovirt" }, "cluster": { "href": "/ovirt-engine/api/clusters/ba170b8e-5744-11e8-8676-00163e3c9a32", "id": "ba170b8e-5744-11e8-8676-00163e3c9a32" }, "comment": "", "cpu": { "speed": 0.0, "topology": {} }, "device_passthrough": { "enabled": false }, "devices": [], "external_network_provider_configurations": [], "external_status": "ok", "hardware_information": { "supported_rng_sources": [] }, "hooks": [], "href": "/ovirt-engine/api/hosts/aad0fe84-2a9b-446d-ac02-82a8f6eb2a3c", "id": "aad0fe84-2a9b-446d-ac02-82a8f6eb2a3c", "katello_errata": [], "kdump_status": "unknown", "ksm": { "enabled": false }, "max_scheduling_memory": 0, "memory": 0, "name": "ovirt", "network_attachments": [], "nics": [], "numa_nodes": [], "numa_supported": false, "os": { "custom_kernel_cmdline": "" }, "permissions": [], "port": 54321, "power_management": { "automatic_pm_enabled": true, "enabled": false, "kdump_detection": true, "pm_proxies": [] }, "protocol": "stomp", "se_linux": {}, "spm": { "priority": 5, "status": "none" }, "ssh": { "fingerprint": "SHA256:o98ZOygBK0jcfY+l5nfi0EGV9v3A4zjclG9d+C3U0WA", "port": 22 }, "statistics": [], "status": "install_failed", "storage_connection_extensions": [], "summary": { "total": 0 }, "tags": [], "transparent_huge_pages": { "enabled": false }, "type": "rhel", "unmanaged_networks": [], "update_available": false }

3 2

how to attach an export domain to a new datacenter with an export domain not very well unattached from an obsolete datacenter
by n.vaye＠free.fr 14 May '18

14 May '18

Hi Ovirt Team, how to attach an export domain to a new datacenter with an export domain not very well unattached from an obsolete datacenter ? My old platform with ovirt 4.1 was deleted ans reinstalled with ovirt 4.2.3. It's ok but i have a problem with an export domain which has not been unattached before the extinction of the old platform. When i try to attach this export domain, i have the error message in the gui : Failed to attach Storage Domain oVirtNFS_EXPORT to Data Center xxx. How can i reinitialize the export domain without erase the data ? just the manager who own the domain. Thanks for all. Nicolas VAYE

2 2

ovirt host upgrade 4.2.2 -> 4.2.3
by Artem Tambovskiy 13 May '18

13 May '18

Hello, I'm upgrading my cluster from 4.2.2 to 4.2.3, HE upgrade went well, but having some issues with hosts upgrade: for some reason yum complaining about conflicts during transaction check: Transaction check error: file /usr/share/cockpit/networkmanager/manifest.json from install of cockpit-system-160-3.el7.centos.noarch conflicts with file from package cockpit-networkmanager-160-1.el7.centos.noarch Any ideas about the reason for this? Regards, Artem

2 1