System tests 7.0 doesn't worked because of problem with libvirt

Bug #1538182 reported by Vadim Rovachev on 2016-01-26
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Medium
Andrey Nikitin

Bug Description

https://patching-ci.infra.mirantis.net/view/All/job/7.0.system_test.ubuntu.bonding_ha/11/console

+ python fuelweb_test/run_tests.py -q --nologcapture --with-xunit --group=bonding_ha
Create environment and set up master node ... libvirt: Storage Driver error : Storage pool not found: no storage pool with matching name 'default'
libvirt: Storage Driver error : Storage pool not found: no storage pool with matching name 'default'
libvirt: Storage Driver error : Storage pool not found: no storage pool with matching name 'default'
libvirt: Storage Driver error : Storage pool not found: no storage pool with matching name 'default'
libvirt: Storage Driver error : Storage pool not found: no storage pool with matching name 'default'
libvirt: Storage Driver error : Storage pool not found: no storage pool with matching name 'default'
libvirt: Storage Driver error : Storage pool not found: no storage pool with matching name 'default'
libvirt: Storage Driver error : Storage pool not found: no storage pool with matching name 'default'
libvirt: Storage Driver error : Storage pool not found: no storage pool with matching name 'default'
libvirt: Storage Driver error : Storage pool not found: no storage pool with matching name 'default'

Changed in fuel:
assignee: nobody → Fuel DevOps (fuel-devops)
summary: - System tests 7.0 doesn't worked because of problem w\ libvirt
+ System tests 7.0 doesn't worked because of problem with libvirt
Igor Shishkin (teran) wrote :

Jan 18 10:18:58 srv031-scc puppet-agent[10975]: Prefetching virsh resources for libvirt_pool
Jan 18 10:18:58 srv031-scc puppet-agent[10975]: Executing '/usr/bin/virsh -q pool-list --all'
Jan 18 10:18:58 srv031-scc puppet-agent[10975]: (/Stage[main]/Fuel_project::Jenkins::Slave/Libvirt_pool[default]) Dependency File[/etc/sysconfig/libvirtd] has failures: true
Jan 18 10:18:58 srv031-scc puppet-agent[10975]: (/Stage[main]/Fuel_project::Jenkins::Slave/Libvirt_pool[default]) Skipping because of failed dependencies

tags: added: area-devops
Igor Shishkin (teran) on 2016-01-26
Changed in fuel:
assignee: Fuel DevOps (fuel-devops) → Igor Shishkin (teran)
importance: Undecided → High
status: New → Confirmed
status: Confirmed → In Progress
milestone: none → 8.0
Igor Shishkin (teran) wrote :

The issue is fixed on those servers, but we still need to check why it wasn't passed from the first time(second puppet pass created the pool).
Decreasing priority to medium.

Changed in fuel:
assignee: Igor Shishkin (teran) → Fuel DevOps (fuel-devops)
status: In Progress → Triaged
importance: High → Medium
Vadim Rovachev (vrovachev) wrote :

Thank you so much, Igor.

Andrey Nikitin (heos) wrote :

CI-team, please provide a server to test deployement of jenkins slave by manifests.

Changed in fuel:
status: Triaged → New
assignee: Fuel DevOps (fuel-devops) → Fuel CI (fuel-ci)
Aleksandra Fedorova (bookwar) wrote :

mc0n1-msk provided

Changed in fuel:
assignee: Fuel CI (fuel-ci) → Andrey Nikitin (heos)
milestone: 8.0 → 7.0-updates
Andrey Nikitin (heos) on 2016-02-12
Changed in fuel:
status: New → In Progress
Andrey Nikitin (heos) wrote :

As I can see, the target pool was created:

virsh # pool-list
 Name State Autostart
-------------------------------------------
 default active yes

Moreover, I can't find related errors in the log files. So, I think, that problem was happeden once.

Andrey Nikitin (heos) wrote :

I've tried to deploy clean server with our puppet manifests and I see, that the problem doesn't repeat.

Related job on jenkins sandbox:
https://jenkins-sandbox.infra.mirantis.net/job/7.0.system_test.ubuntu.bonding_ha_one_controller/5/console

Changed in fuel:
status: In Progress → Fix Committed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers