- Devel - oVirt List Archives

Warnings in ovirt-engine build process
by Dominik Holler 03 Jan '18

03 Jan '18

If a code change adds a warning to ovirt-engine build process, shouldn't CI mark the change as unstable?

3 3

[ovirt-users] cloud-init not working on master/4.2?
by Roy Golan 03 Jan '18

03 Jan '18

I had problems bootstrapping my glance images, cloud init seems to ignore my password changes and then I realized I'm missing the cdrom in the domxml. To solve it I disabled the DomainXML feature(engine preparing the domxml, not vdsm) and it started working. Before I open a bug can anyone try to reproduce on 4.2? The workaround with engine-config: echo DomainXML | engine-config -s DomainXML=false --cver=4.2 -p /dev/stdin

3 5

WFLYCTL0348: Timeout after [300] seconds waiting for service container stability
by Yedidyah Bar David 02 Jan '18

02 Jan '18

Hi all, Can someone please help debug this failure? It happens to me when deploying hosted-engine --ansible using ovirt-system-tests. So far happened to me once when tried manually and once in jenkins [1] (/var/log/ovirt-engine) [2] (server.log): 2018-01-01 08:19:14,375-05 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 57) WFLYCLINF0002: Started timeout-base cache from ovirt-engine container 2018-01-01 08:23:49,407-05 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0348: Timeout after [300] seconds waiting for service container stability. Operation will roll back. Step that first updated the service container was 'add' at address '[ ("core-service" => "management"), ("management-interface" => "native-interface") ]' On my own system, HE-HA-agent gave up, stopped the machine, started it, and then the engine did start well. In jenkins, we do not give it enough time for this. Now pushed a patch [3] to increase the timeout to 20 minutes (from 10), but this is just to see if it works then. For now, at least. Thanks, [1] http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-el7-x86_… [2] http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-el7-x86_… [3] https://gerrit.ovirt.org/85856 -- Didi

2 3

[ OST Failure Report ] [ oVirt master ] [ 24/12/2017 ] [use_ovn_provider]
by Barak Korren 29 Dec '17

29 Dec '17

Test failed: [ 098_ovirt_provider_ovn.use_ovn_provider ] Link to suspected patches: - Linked test failed on: https://gerrit.ovirt.org/#/c/85703/3 - It seems OVN patches had been failing tests ever since: https://gerrit.ovirt.org/#/c/85645/2 Link to Job: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4492/ Link to all logs: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4492/artifact… Error snippet from log: <error> Fault reason is "Operation Failed". Fault detail is "Failed to communicate with the external provider, see log for additional details.". HTTP response code is 400. -------------------- >> begin captured logging << -------------------- requests.packages.urllib3.connectionpool: INFO: * Starting new HTTPS connection (1): 192.168.201.4 py.warnings: WARNING: * Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.org/en/latest/security.html requests.packages.urllib3.connectionpool: DEBUG: "POST /v2.0/tokens/ HTTP/1.1" 200 None requests.packages.urllib3.connectionpool: INFO: * Starting new HTTPS connection (1): 192.168.201.4 requests.packages.urllib3.connectionpool: DEBUG: "GET /v2.0/networks/ HTTP/1.1" 200 None requests.packages.urllib3.connectionpool: INFO: * Starting new HTTPS connection (1): 192.168.201.4 requests.packages.urllib3.connectionpool: DEBUG: "GET /v2.0/ports/ HTTP/1.1" 200 None requests.packages.urllib3.connectionpool: INFO: * Starting new HTTPS connection (1): 192.168.201.4 requests.packages.urllib3.connectionpool: DEBUG: "GET /v2.0/subnets/ HTTP/1.1" 200 None requests.packages.urllib3.connectionpool: INFO: * Starting new HTTPS connection (1): 192.168.201.4 requests.packages.urllib3.connectionpool: DEBUG: "POST /v2.0/networks/ HTTP/1.1" 201 None requests.packages.urllib3.connectionpool: INFO: * Starting new HTTPS connection (1): 192.168.201.4 requests.packages.urllib3.connectionpool: DEBUG: "POST /v2.0/subnets/ HTTP/1.1" 201 None requests.packages.urllib3.connectionpool: INFO: * Starting new HTTPS connection (1): 192.168.201.4 requests.packages.urllib3.connectionpool: DEBUG: "POST /v2.0/ports/ HTTP/1.1" 201 None requests.packages.urllib3.connectionpool: INFO: * Starting new HTTPS connection (1): 192.168.201.4 requests.packages.urllib3.connectionpool: DEBUG: "GET /v2.0/networks/ HTTP/1.1" 200 None requests.packages.urllib3.connectionpool: INFO: * Starting new HTTPS connection (1): 192.168.201.4 requests.packages.urllib3.connectionpool: DEBUG: "GET /v2.0/ports/ HTTP/1.1" 200 None requests.packages.urllib3.connectionpool: INFO: * Starting new HTTPS connection (1): 192.168.201.4 requests.packages.urllib3.connectionpool: DEBUG: "GET /v2.0/subnets/ HTTP/1.1" 200 None --------------------- >> end captured logging << --------------------- </error> -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted

7 17

[VDSM] upgrading pylint - new errors
by Nir Soffer 28 Dec '17

28 Dec '17

I'm trying to upgrade pylint to latest so we can enjoy latest fixes like this: https://github.com/PyCQA/pylint/issues/1736 Now we have some new errors, please check. ************* Module vdsm.clientIF*00:06:53.857* *E*:588,16: *Possible unbalanced tuple unpacking with sequence: left side has 2 label(s), right side has 0 value(s)* (*unbalanced-tuple-unpacking*) 587 if eventid == libvirt.VIR_DOMAIN_EVENT_ID_LIFECYCLE: 588 event, detail = args[:-1] 589 v.onLibvirtLifecycleEvent(event, detail, None) Code is indeed incorrect, should be: event, detail = args[:2] *00:06:53.859* *E*:593,16: *Possible unbalanced tuple unpacking with sequence: left side has 1 label(s), right side has 0 value(s)* (*unbalanced-tuple-unpacking*)*00:06:53.861* *E*:596,16: *Possible unbalanced tuple unpacking with sequence: left side has 4 label(s), right side has 0 value(s)* (*unbalanced-tuple-unpacking*)*00:06:53.863* *E*:599,16: *Possible unbalanced tuple unpacking with sequence: left side has 5 label(s), right side has 0 value(s)* (*unbalanced-tuple-unpacking*)*00:06:53.867* *E*:610,16: *Possible unbalanced tuple unpacking with sequence: left side has 1 label(s), right side has 0 value(s)* (*unbalanced-tuple-unpacking*)*00:06:53.869* *E*:615,16: *Possible unbalanced tuple unpacking with sequence: left side has 1 label(s), right side has 0 value(s)* (*unbalanced-tuple-unpacking*)*00:06:53.872* *E*:618,16: *Possible unbalanced tuple unpacking with sequence: left side has 4 label(s), right side has 0 value(s)* (*unbalanced-tuple-unpacking*)*00:06:53.873* ************* Module vdsm.v2v*00:06:53.874* *E*:1368,27: *Instance of 'closing' has no 'read' member* (*no-member*)*00:06:53.876* ************* Module vdsm.tool.configurator*00:06:53.878* *E*:118,12: *No value for argument 'action' in function call* (*no-value-for-parameter*)*00:06:53.880* *E*:158,12: *No value for argument 'action' in function call* (*no-value-for-parameter*)*00:06:53.881* *E*:193,12: *No value for argument 'action' in function call* (*no-value-for-parameter*)*00:06:53.883* *E*:215,12: *No value for argument 'action' in function call* (*no-value-for-parameter*)*00:06:53.885* ************* Module vdsm.virt.vm_migrate_hook*00:06:53.886* *E*:199, 4: *No value for argument 'domain' in function call* (*no-value-for-parameter*)*00:06:53.888* *E*:199, 4: *No value for argument 'event' in function call* (*no-value-for-parameter*)*00:06:53.890* *E*:199, 4: *No value for argument 'phase' in function call* (*no-value-for-parameter*)*00:06:53.892* ************* Module vdsm.network.netlink.monitor*00:06:53.893* *E*:172,58: *Instance of 'closing' has no 'poll' member* (*no-member*)

3 7

vdsm: AttributeError: 'NoneType' object has no attribute 'wrap_command'
by Yaniv Kaul 28 Dec '17

28 Dec '17

Just saw this on[1]: 2017-12-28 10:09:24,980-0500 INFO (MainThread) [vdsm.api] FINISH prepareForShutdown return=None from=internal, task_id=1a83a4d3-43e3-4833-883b-dfd2fe4d76be (api:52) 2017-12-28 10:09:24,980-0500 INFO (MainThread) [vds] Stopping threads (vdsmd:159) 2017-12-28 10:09:24,980-0500 INFO (MainThread) [vds] Exiting (vdsmd:170) 2017-12-28 10:09:25,011-0500 INFO (mailbox-hsm) [storage.MailBox.HsmMailMonitor] HSM_MailboxMonitor - Incoming mail monitoring thread stopped, clearing outgoing mail (mailbox:511) 2017-12-28 10:09:25,011-0500 INFO (mailbox-hsm) [storage.MailBox.HsmMailMonitor] HSM_MailMonitor sending mail to SPM - ['/usr/bin/dd', 'of=/rhev/data-center/9b97451a-0312-4c69-85e2-f86d6d273636/mastersd/dom_md/inbox', 'iflag=fullblock', 'oflag=direct', 'conv=notrunc', 'bs=4096', 'count=1', 'seek=1'] (mailbox:387) 2017-12-28 10:09:25,012-0500 ERROR (mailbox-hsm) [storage.MailBox.HsmMailMonitor] FINISH thread <Thread(mailbox-hsm, started daemon 139968009594624)> failed (concurrent:201) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/common/concurrent.py", line 194, in run ret = func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/storage/mailbox.py", line 514, in _run self._sendMail() # Clear outgoing mailbox File "/usr/lib/python2.7/site-packages/vdsm/storage/mailbox.py", line 394, in _sendMail _mboxExecCmd(self._outCmd, data=self._outgoingMail) File "/usr/lib/python2.7/site-packages/vdsm/storage/mailbox.py", line 84, in _mboxExecCmd return misc.execCmd(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/common/commands.py", line 53, in execCmd command = cmdutils.wrap_command(command, with_ioclass=ioclass, AttributeError: 'NoneType' object has no attribute 'wrap_command' 2017-12-28 10:09:28,965-0500 INFO (MainThread) [vds] (PID: 23232) I am the actual vdsm 4.20.9-84.git615770f.el7.centos lago-basic-suite-master-host-0 (3.10.0-693.2.2.el7.x86_64) (vdsmd:148) 2017-12-28 10:09:28,966-0500 INFO (MainThread) [vds] VDSM will run with cpu affinity: frozenset([1]) (vdsmd:254) 2017-12-28 10:09:28,970-0500 INFO (MainThread) [storage.HSM] START HSM init (hsm:366) [1] http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-el7-x86_…

3 2

User is not authorized to perform this action. - trying to add SSH Public Key for a user
by Yaniv Kaul 28 Dec '17

28 Dec '17

I'm following the example[1] and getting an error: User is not authorized to perform this action. What permission do I need (I'm using admin@internal) in order to do this? Engine.log: 2017-12-28 07:25:35,571-05 WARN [org.ovirt.engine.core.bll.AddUserProfileCommand] (default task-13) [5af96d04-f81d-4c76-9f06-ee03a12e2f71] Validation of action 'AddUserProfile' failed for user admin@internal-authz. Reasons: VAR__ACTION__ADD,VAR__TYPE__USER_PROFILE,USER_NOT_AUTHORIZED_TO_PERFORM_ACTION 2017-12-28 07:25:35,572-05 DEBUG [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor] (default task-13) [5af96d04-f81d-4c76-9f06-ee03a12e2f71] method: runAction, params: [AddUserProfile, UserProfileParameters:{commandId='a57680f0-3926-4808-8452-ea8d67b076a3', user='null', commandType='Unknown'}], timeElapsed: 41ms 2017-12-28 07:25:35,577-05 ERROR [org.ovirt.engine.api.restapi.resource.AbstractBackendResource] (default task-13) [] Operation Failed: [User is not authorized to perform this action.] TIA, Y. [1] https://github.com/oVirt/ovirt-engine-sdk/blob/master/sdk/examples/add_user…

2 1

node zero Networking
by Yedidyah Bar David 28 Dec '17

28 Dec '17

Hi all, I spent quite some time trying to deploy node zero, trying to look at https://bugzilla.redhat.com/show_bug.cgi?id=1528253 , and always fail around the end, with: ERROR fatal: [localhost]: FAILED! => {"attempts": 50, "changed": true, "cmd": "ip rule list | grep ovirtmgmt | sed s/\\\\[.*\\\\]\\ //g | awk '{ print $9 }'", "delta": "0:00:00.008292", "end": "2017-12-25 11:51:39.146800", "rc": 0, "start": "2017-12-25 11:51:39.138508", "stderr": "", "stderr_lines": [], "stdout": "", "stdout_lines": []} ERROR Failed to execute stage 'Closing up': Failed executing ansible-playbook ERROR Hosted Engine deployment failed: this system is not reliable, please check the issue,fix and redeploy I use the following setup: I have a libvirt vm on my laptop, with a single virtual nic eth0. This nic is connected to a bridge called intbr on my laptop. This bridge has no access to outside, and VMs on it have no default route. There is a local dhcp+dns serving this bridge, using the address range 192.168.3.0/24. The vm serves as a nested-kvm hosted-engine host. eth0 gets a static IP address 192.168.3.42 from dhcpd. There is also (didn't check who/what exactly creates it, I think it's libvirt's default) a bridge there called virbr0. virbr0 has IP address 192.168.122.1/24 . When I deploy HE, the engine machine gets also a single virtual nic, which is connected to virbr0, and gets an IP address in that range (192.168.122.85, currently). deploy fails when running the task: - name: Get ovirtmgmt route table id shell: ip rule list | grep ovirtmgmt | sed s/\\[.*\\]\ //g | awk '{ print $9 }' register: ovirtmgmt_table_id until: ovirtmgmt_table_id.stdout_lines|length >= 1 retries: 50 delay: 10 changed_when: True The output of 'ip rule list' is: 0: from all lookup local 32766: from all lookup main 32767: from all lookup default So does not include 'ovirtmgmt'. I do have: # brctl show bridge name bridge id STP enabled interfaces ;vdsmdummy; 8000.000000000000 no ovirtmgmt 8000.06d1bd012412 no eth0 virbr0 8000.525400012499 yes virbr0-nic vnet0 And: # ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master ovirtmgmt state UP qlen 1000 link/ether 06:d1:bd:01:24:12 brd ff:ff:ff:ff:ff:ff 18: virbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP qlen 1000 link/ether 52:54:00:01:24:99 brd ff:ff:ff:ff:ff:ff inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0 valid_lft forever preferred_lft forever 19: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast master virbr0 state DOWN qlen 1000 link/ether 52:54:00:01:24:99 brd ff:ff:ff:ff:ff:ff 20: vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master virbr0 state UNKNOWN qlen 1000 link/ether fe:d1:bd:01:24:04 brd ff:ff:ff:ff:ff:ff inet6 fe80::fcd1:bdff:fe01:2404/64 scope link valid_lft forever preferred_lft forever 21: ;vdsmdummy;: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000 link/ether 1e:1b:84:c2:51:ff brd ff:ff:ff:ff:ff:ff 22: ovirtmgmt: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP qlen 1000 link/ether 06:d1:bd:01:24:12 brd ff:ff:ff:ff:ff:ff inet 192.168.3.42/24 brd 192.168.3.255 scope global dynamic ovirtmgmt valid_lft 70927sec preferred_lft 70927sec inet6 fe80::4d1:bdff:fe01:2412/64 scope link valid_lft forever preferred_lft forever (And of course told deploy that I want to use eth0). Questions: 1. Did this already work for anyone at all? If so, can you please share details? Specifically, how was networking configured? 2. It might be that my problems are due to not having a (default) route for ovirtmgmt bridge/network. If so, then I consider this a bug, but do not mind configuring one for now. 3. All of the relevant section of the playbook has a comment preceding it: # all of the next is a workaroud for the network issue, vdsm installation breaks the routing and it needs to be fixed # once we'll fix the host installation it could be removed Do we have specific details/bug/whatever about the problem we are working around? Perhaps it's already solved and I can try to remove this part? 4. Both now (with (3.) being worked around) and eventually (when it's (what?) fixed), how should this work? Should the engine local vm indeed start connected to virbr0, and then move to ovirtmgmt? Or only the new engine vm (residing on the shared storage) should be in ovirtmgmt? 5. In particular, what should I supply for the "engine fqdn", and what should it resolve to, both in the beginning an eventually? Thanks, -- Didi

1 1

oVirt System Test configuration
by Sandro Bonazzola 27 Dec '17

27 Dec '17

Hi, I'd like to discuss what's being tested by oVirt System Test. I'm investigating on a sanlock issue that affects hosted engine hc suite. I installed a CentOS minimal VM and set repositories as in http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/128/a… Upgrade from CentOS 1708 (7.4) minimal is: Aggiornamento: bind-libs-lite x86_64 32:9.9.4-51.el7_4.1 centos-updates-el7 733 k bind-license noarch 32:9.9.4-51.el7_4.1 centos-updates-el7 84 k nss x86_64 3.28.4-15.el7_4 centos-updates-el7 849 k nss-softokn x86_64 3.28.3-8.el7_4 centos-updates-el7 310 k nss-softokn-freebl x86_64 3.28.3-8.el7_4 centos-updates-el7 214 k nss-sysinit x86_64 3.28.4-15.el7_4 centos-updates-el7 60 k nss-tools x86_64 3.28.4-15.el7_4 centos-updates-el7 501 k selinux-policy noarch 3.13.1-166.el7_4.7 centos-updates-el7 437 k selinux-policy-targeted noarch 3.13.1-166.el7_4.7 centos-updates-el7 6.5 M systemd x86_64 219-42.el7_4.4 centos-updates-el7 5.2 M systemd-libs x86_64 219-42.el7_4.4 centos-updates-el7 376 k systemd-sysv x86_64 219-42.el7_4.4 centos-updates-el7 70 k Enabling the CentOS repos: grub2 x86_64 1:2.02-0.65.el7.centos.2 updates 29 k in sostituzione di grub2.x86_64 1:2.02-0.64.el7.centos grub2-tools x86_64 1:2.02-0.65.el7.centos.2 updates 1.8 M in sostituzione di grub2-tools.x86_64 1:2.02-0.64.el7.centos grub2-tools-extra x86_64 1:2.02-0.65.el7.centos.2 updates 993 k in sostituzione di grub2-tools.x86_64 1:2.02-0.64.el7.centos grub2-tools-minimal x86_64 1:2.02-0.65.el7.centos.2 updates 170 k in sostituzione di grub2-tools.x86_64 1:2.02-0.64.el7.centos kernel x86_64 3.10.0-693.11.1.el7 updates 43 M Aggiornamento: NetworkManager x86_64 1:1.8.0-11.el7_4 updates 1.6 M NetworkManager-libnm x86_64 1:1.8.0-11.el7_4 updates 1.2 M NetworkManager-team x86_64 1:1.8.0-11.el7_4 updates 156 k NetworkManager-tui x86_64 1:1.8.0-11.el7_4 updates 224 k NetworkManager-wifi x86_64 1:1.8.0-11.el7_4 updates 184 k bash x86_64 4.2.46-29.el7_4 updates 1.0 M bind-libs-lite x86_64 32:9.9.4-51.el7_4.1 centos-updates-el7 733 k bind-license noarch 32:9.9.4-51.el7_4.1 centos-updates-el7 84 k binutils x86_64 2.25.1-32.base.el7_4.1 updates 5.4 M cpio x86_64 2.11-25.el7_4 updates 210 k cryptsetup-libs x86_64 1.7.4-3.el7_4.1 updates 223 k curl x86_64 7.29.0-42.el7_4.1 updates 267 k glibc x86_64 2.17-196.el7_4.2 updates 3.6 M glibc-common x86_64 2.17-196.el7_4.2 updates 11 M grub2-common noarch 1:2.02-0.65.el7.centos.2 updates 726 k grub2-pc x86_64 1:2.02-0.65.el7.centos.2 updates 29 k grub2-pc-modules noarch 1:2.02-0.65.el7.centos.2 updates 845 k iptables x86_64 1.4.21-18.2.el7_4 updates 428 k kernel-tools x86_64 3.10.0-693.11.1.el7 updates 5.1 M kernel-tools-libs x86_64 3.10.0-693.11.1.el7 updates 5.0 M kexec-tools x86_64 2.0.14-17.2.el7 updates 333 k kmod x86_64 20-15.el7_4.6 updates 120 k kmod-libs x86_64 20-15.el7_4.6 updates 50 k libblkid x86_64 2.23.2-43.el7_4.2 updates 176 k libcurl x86_64 7.29.0-42.el7_4.1 updates 219 k libgcc x86_64 4.8.5-16.el7_4.1 updates 98 k libgomp x86_64 4.8.5-16.el7_4.1 updates 154 k libmount x86_64 2.23.2-43.el7_4.2 updates 178 k libpciaccess x86_64 0.13.4-3.1.el7_4 updates 26 k libstdc++ x86_64 4.8.5-16.el7_4.1 updates 301 k libuuid x86_64 2.23.2-43.el7_4.2 updates 79 k ncurses x86_64 5.9-14.20130511.el7_4 updates 304 k ncurses-base noarch 5.9-14.20130511.el7_4 updates 68 k ncurses-libs x86_64 5.9-14.20130511.el7_4 updates 316 k nss x86_64 3.28.4-15.el7_4 centos-updates-el7 849 k nss-softokn x86_64 3.28.3-8.el7_4 centos-updates-el7 310 k nss-softokn-freebl x86_64 3.28.3-8.el7_4 centos-updates-el7 214 k nss-sysinit x86_64 3.28.4-15.el7_4 centos-updates-el7 60 k nss-tools x86_64 3.28.4-15.el7_4 centos-updates-el7 501 k openssh x86_64 7.4p1-13.el7_4 updates 509 k openssh-clients x86_64 7.4p1-13.el7_4 updates 654 k openssh-server x86_64 7.4p1-13.el7_4 updates 458 k python-gobject-base x86_64 3.22.0-1.el7_4.1 updates 294 k python-perf x86_64 3.10.0-693.11.1.el7 updates 5.1 M selinux-policy noarch 3.13.1-166.el7_4.7 centos-updates-el7 437 k selinux-policy-targeted noarch 3.13.1-166.el7_4.7 centos-updates-el7 6.5 M sudo x86_64 1.8.19p2-11.el7_4 updates 1.1 M systemd x86_64 219-42.el7_4.4 centos-updates-el7 5.2 M systemd-libs x86_64 219-42.el7_4.4 centos-updates-el7 376 k systemd-sysv x86_64 219-42.el7_4.4 centos-updates-el7 70 k tzdata noarch 2017c-1.el7 updates 468 k util-linux x86_64 2.23.2-43.el7_4.2 updates 2.0 M wpa_supplicant x86_64 1:2.6-5.el7_4.1 updates 1.2 M meaning this environement is not receiving updates to core packages like the kernel. Restricting to libvirt, with the repos used in the job libvirt packages doesn't even exists, making yum install libvirt just fail. I think you already know I'm against filtering packages from the repos even if I understand it saves a huge amount of space and download time. I may be wrong, but I tend to not trust OST results since it's not testing real life environments. Any chance we can improve OST to match what users are going to have on their systems? -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

6 14

upgrade_check and upgrade API calls (v4)
by Yaniv Kaul 26 Dec '17

26 Dec '17

I'm trying to check if a certain host can be upgraded. 1. I'm calling it through the host_service, something like: host_service = connection.system_service().hosts_service().host_service( host.id) is_upgrade = host_service.upgrade_check() To my surprise, is_upgrade is None. I expected a Boolean. 2. In addition, when trying to upgrade via: host_service.upgrade() I'm getting Operation Failed - and it complains there are no upgrades available. Alas, in the UI it shows that upgrades available and upgrade does work through the UI. Am I misusing the functions? (The host is a regular host, not ovirt-node btw). TIA, Y.

3 3