On Thu, Jul 5, 2018 at 3:06 AM, <[email protected]> wrote:
> Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic- > ansible-suite-4.2/ > Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic- > ansible-suite-4.2/346/ > Build Number: 346 > Build Status: Still Failing > Triggered By: Started by timer > > ------------------------------------- > Changes Since Last Success: > ------------------------------------- > Changes for Build #345 > [Marcin Mirecki] network: Add ping check for networks connected via > multiple routers > > [Yuval Turgeman] add ovirt-node-ng to stdci-v2 > > [Barak Korren] Fix YAML issue preventing upgrade to JJB >= 2.0.0 > > [Barak Korren] Upgrade JJB to 2.0.0 > > [Barak Korren] Upgrade JJB to 2.0.10 > > [Emil Natan] Add .pytest_cache/ to .gitignore > > > Changes for Build #346 > [Marcin Mirecki] network: Add ping check for networks connected via > multiple routers > > [Barak Korren] Revert "Upgrade JJB to 2.0.10" > > > > > ----------------- > Failed Tests: > ----------------- > 1 tests failed. > FAILED: 004_basic_sanity.vm_run > > Error Message: > > status: 409 > reason: Conflict > detail: Cannot run VM. There is no host that satisfies current scheduling > constraints. See below for details:, The host > lago-he-basic-ansible-suite-4-2-host-0 > did not satisfy internal filter Memory because its available memory is too > low (656 MB) to run the VM. > > Stack Trace: > Traceback (most recent call last): > File "/usr/lib64/python2.7/unittest/case.py", line 369, in run > testMethod() > File "/usr/lib/python2.7/site-packages/nose/case.py", line 197, in > runTest > self.test(*self.arg) > File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 129, > in wrapped_test > test() > File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 59, > in wrapper > return func(get_test_prefix(), *args, **kwargs) > File "/home/jenkins/workspace/ovirt-system-tests_he-basic- > ansible-suite-4.2/ovirt-system-tests/he-basic-ansible- > suite-4.2/test-scenarios/004_basic_sanity.py", line 265, in vm_run > api.vms.get(VM0_NAME).start(start_params) > File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/brokers.py", > line 31193, in start > headers={"Correlation-Id":correlation_id} > File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py", > line 122, in request > persistent_auth=self.__persistent_auth > File > "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/connectionspool.py", > line 79, in do_request > persistent_auth) > File > "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/connectionspool.py", > line 162, in __do_request > raise errors.RequestError(response_code, response_reason, > response_body) > RequestError: > status: 409 > reason: Conflict > detail: Cannot run VM. There is no host that satisfies current scheduling > constraints. See below for details:, The host > lago-he-basic-ansible-suite-4-2-host-0 > did not satisfy internal filter Memory because its available memory is too > low (656 MB) to run the VM. OST specifically asks to run the vm on host-0, which likely also runs the engine vm. Since this usually passes, I assume either something on the engine vm (engine itself or something else) uses more memory now, or something else on host-0 does. I briefly looked at var/log/messages and didn't find anything relevant. Do we collect anything else to help debug this? If not, perhaps we should. Not sure what - ideally we should use ovirt-engine-metrics... -- Didi
_______________________________________________ Infra mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected]/message/5CA25KDW7TN3F4ECTGKW5VI5E7JUA4YB/
