neutron's 7.0.mos-new.deploy-deb failures

[Alexey Stupnikov]

neutron 7.0.mos-new.deploy-deb tests are failing with the following error output:

libvirt: error : uuidstr in virDomainLookupByUUIDString must be a valid UUID
2016-06-27 09:24:26,674 - ERROR decorators.py:108 -- Error making the environment snapshot: Traceback (most recent call last):
  File "/home/jenkins/workspace/7.0.mos-new.deploy-deb/fuel-qa/fuelweb_test/helpers/decorators.py", line 105, in wrapper
    is_make=True)
  File "/home/jenkins/workspace/7.0.mos-new.deploy-deb/fuel-qa/fuelweb_test/models/environment.py", line 259, in make_snapshot
    self.d_env.suspend(verbose=False)
  File "/home/jenkins/venv-nailgun-tests-2.9/local/lib/python2.7/site-packages/devops/models/environment.py", line 144, in suspend
    node.suspend(verbose)
  File "/home/jenkins/venv-nailgun-tests-2.9/local/lib/python2.7/site-packages/devops/models/node.py", line 205, in suspend
    if verbose or self.driver.node_active(self):
  File "/home/jenkins/venv-nailgun-tests-2.9/local/lib/python2.7/site-packages/devops/helpers/retry.py", line 27, in wrapper
    return func(*args, **kwargs)
  File "/home/jenkins/venv-nailgun-tests-2.9/local/lib/python2.7/site-packages/devops/driver/libvirt/libvirt_driver.py", line 135, in node_active
    return self.conn.lookupByUUIDString(node.uuid).isActive()
  File "/home/jenkins/venv-nailgun-tests-2.9/local/lib/python2.7/site-packages/libvirt.py", line 3639, in lookupByUUIDString
    if ret is None:raise libvirtError('virDomainLookupByUUIDString() failed', conn=self)
libvirtError: uuidstr in virDomainLookupByUUIDString must be a valid UUID

Dmitry Burmistrov and Olesya Novaselskaya told me that I should ask devops to investigate this bug.

Example review: https://review.fuel-infra.org/#/c/22596/
Example job: http://osci-jenkins.srt.mirantis.net:8080/job/7.0.mos-new.deploy-deb/1560/

[Pawel Brzozowski (pbrzozowski)]

I have cleaned up both devops environments and libvirt setup. Now it's possible to create environments. I am not sure if that's required but be aware, that the node state is "fresh" currently.

[Alexey Stupnikov (astupnikov)]

The problem is not fixed, I will ask CI team to continue investigation.

[Dmitry Burmistrov (dburmistrov)]

Fixed by total cleanup of test slave