virsh call from tests uses default configured connection

Bug #1518878 reported by Aleksei Stepanov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
Low
Unassigned

Bug Description

Call like:
    virsh dumpxml
not defines, which connection to use. As result, possible situations, when virsh will not find any active VM anyway as active VM presents.
Solution: add connection string to all requests:
    virsh -c qemu:///system dumpxml

Fuel-web: not actual due to start virsh as root

Tags: area-qa
description: updated
Maciej Relewicz (rlu)
Changed in fuel:
assignee: nobody → Fuel Library Team (fuel-library)
Revision history for this message
Alexandr Kostrikov (akostrikov-mirantis) wrote :

Move to invalid due to no information about what system affected.
If it is about shell usage, it is highlighted in libvirt docs.

Changed in fuel:
status: New → Invalid
Revision history for this message
Aleksei Stepanov (penguinolog) wrote :

Places of hardcode:
1. fuelweb_test/helpers/os_actions.py: 504
2. fuelweb_test/teststest_by_temptest.py: 98

Changed in fuel:
assignee: Fuel Library Team (fuel-library) → nobody
Revision history for this message
Dennis Dmitriev (ddmitriev) wrote :

No system tests are affected. 'virsh dumpxml' is executed by system tests on cluster compute nodes always under user 'root'. Compute nodes have correct defaults for libvirt, so this bug is invalid.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.