libvirt pool path is wrong when it is not default

[Jooho]

Even though I use custom path for storagePool(/home/jooho/KVM), the actuator try to use wrong path.

E0112 03:54:03.202553       1 actuator.go:107] Machine error: error creating volume Can't retrieve volume /var/lib/libvirt/images/tbd-base
E0112 03:54:03.203245       1 actuator.go:51] tbd/tbd-worker-0-nhzvf: error creating libvirt machine: error creating volume Can't retrieve volume /var/lib/libvirt/images/tbd-base
E0112 03:54:04.259706       1 actuator.go:107] Machine error: error creating volume Can't retrieve volume /var/lib/libvirt/images/tbd-base
E0112 03:54:04.259734       1 actuator.go:51] tbd/tbd-worker-0-d554w: error creating libvirt machine: error creating volume Can't retrieve volume /var/lib/libvirt/images/tbd-base

The worker storage files are generated under /home/jooho/KVM but it failed to retrieve the files because it tried to load them under /var/lib/libvirt/images.

Expected result

it should search right path where the image files are generated.

[wking]

#45 should fix this.

[cfergeau]

#45 was superseded by #144 which is merged, so hopefully this no longer is an issue?

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci-robot]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.