[DevOps] libirt error: Cannot set up guest memory 'pc.ram': Cannot allocate memory

[Andrey Sledzinskiy]

http://jenkins-product.srt.mirantis.net:8080/view/5.0_swarm/job/5.0_fuelmain.system_test.ubuntu.services_ha/1/console

All tests failed on step with snapshot resuming

Deploy cluster in ha mode with Ceilometer ... 2014-05-23 05:46:46,412 - INFO environment.py:322 -- We have snapshot with such name ready_with_5_slaves
libvirt: QEMU Driver error : internal error: process exited while connecting to monitor: Cannot set up guest memory 'pc.ram': Cannot allocate memory
libvirt: QEMU Driver error : internal error: process exited while connecting to monitor: Cannot set up guest memory 'pc.ram': Cannot allocate memory
libvirt: QEMU Driver error : internal error: process exited while connecting to monitor: Cannot set up guest memory 'pc.ram': Cannot allocate memory
libvirt: QEMU Driver error : internal error: process exited while connecting to monitor: Cannot set up guest memory 'pc.ram': Cannot allocate memory
libvirt: QEMU Driver error : internal error: process exited while connecting to monitor: Cannot set up guest memory 'pc.ram': Cannot allocate memory
libvirt: QEMU Driver error : internal error: process exited while connecting to monitor: Cannot set up guest memory 'pc.ram': Cannot allocate memory
libvirt: QEMU Driver error : internal error: process exited while connecting to monitor: Cannot set up guest memory 'pc.ram': Cannot allocate memory
libvirt: QEMU Driver error : internal error: process exited while connecting to monitor: Cannot set up guest memory 'pc.ram': Cannot allocate memory
libvirt: QEMU Driver error : internal error: process exited while connecting to monitor: Cannot set up guest memory 'pc.ram': Cannot allocate memory
libvirt: QEMU Driver error : internal error: process exited while connecting to monitor: Cannot set up guest memory 'pc.ram': Cannot allocate memory
ERROR

[Igor Shishkin (teran)]

http://monitor-product.vm.mirantis.net/chart.php?itemid=83342&period=35185&stime=20140523075533&updateProfile=1&profileIdx=web.item.graph&profileIdx2=83342&sid=df97b0e075a64fa3&width=1292&curtime=1401196952348

Looks true. Possibly it was because of running environment in parallel, any way we did had atop at 23rd of May, so currently it's not possible to investigate.

Yeasterday we installed atop on all microclouds.
Please reopen if the same problem will come back.

[Egor Kotko (ykotko)]

{"build_id": "2014-07-15_23-01-44", "mirantis": "yes", "build_number": "129", "ostf_sha": "09b6bccf7d476771ac859bb3c76c9ebec9da9e1f", "nailgun_sha": "1d08d6f80b6514085dd8c0af4d437ef5d37e2802", "production": "docker", "api": "1.0", "fuelmain_sha": "13e7eb64352a90edf1265f672d87fce10fee5093", "astute_sha": "9a74b788be9a7c5682f1c52a892df36e4766ce3f", "release": "5.0.1", "fuellib_sha": "2d1e1369c13bc9771e9473086cb064d257a21fc2"}

http://jenkins-product.srt.mirantis.net:8080/view/5.0_swarm/job/5.0_fuelmain.system_test.ubuntu.bonding_simple/13/testReport/%28root%29/deploy_bonding_active_backup/deploy_bonding_active_backup/
http://jenkins-product.srt.mirantis.net:8080/view/5.0_swarm/job/5.0_fuelmain.system_test.ubuntu.bonding_simple/13/testReport/%28root%29/deploy_bonding_balance_slb/deploy_bonding_balance_slb/

http://jenkins-product.srt.mirantis.net:8080/view/5.0_swarm/job/5.0_fuelmain.system_test.ubuntu.bonding_simple/13/console

Test failed with the same error.

[Igor Shishkin (teran)]

I think this could be related to envs left running. Did it reproduced recently?

[Igor Shishkin (teran)]

Does this issue still reproduces?

[Andrey Sledzinskiy (asledzinskiy)]

No, issue wasn't reproduced on latest runs

[Igor Shishkin (teran)]

No activity for more then month. Setting invalid according to workflow.