"Instance directory already exists. Reusing existing files." logged at every spawn
Bug #1747961 reported by
Claudiu Belu
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| compute-hyperv |
Fix Released
|
Low
|
Unassigned | ||
Bug Description
A recent patch in compute-hyperv allowed instances to be evacuated. It is checking if the instance's dir already exists (typically the case on shared storage), and if so, reuse it.
But, PathUtils' get_instance_dir always returns a path, which means that the mentioned message is always logged.
| Changed in compute-hyperv: | |
| importance: | Undecided → Low |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to compute-hyperv (master) | #1 |
| Changed in compute-hyperv: | |
| status: | New → Fix Released |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Zuul
Branch: master
commit c4c65971d366deb
Author: Lucian Petrut <email address hidden>
Date: Thu Feb 8 17:12:46 2018 +0200
Fix instance dir check when spawning
When spawning instances, we're checking if the instance dir
already exists, in which case we're logging a message, stating
that existing instance files will be reused.
Well, at least that's what we thought we were doing. Actually,
we're always logging this message as the check is wrong.
This change fixes this issue.
Change-Id: I6cf52ae23d90e6
Closes-Bug: #1747961