Nova compute - misleading warning message
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Confirmed
|
Undecided
|
Brin Zhang |
Bug Description
Minor issue, but logged by our QA team
Its on a Live Migration operation
Probably too late to make Stein release as it is a warning log change.
07/22/2018 10:18:55 AM
We are moving instance from hostB ---- > hostA
LM operation is successful, but when we see below logs from node hostA, it is
giving wrong info
Jul 12 15:44:52 dldv0031 nova-compute[
When the instance is moved from hostB --> to hostA,
Why does nova-compute log "Instance d459e746-
I did a little investigating of _remove_
1. It is logged as a WARNING and not as an INFO as you would expect for a status update and it is not at the end of LM operation(not a final status)
2. It is part of the _remove_
3. The corner case where the WARNING gets logged is described as:
# The instance has been moved to another host either via a
# migration, evacuation or unshelve in between the time when we
# ran InstanceList.
# instances to RT.tracked_
# allocations that reference this compute host if the VM is in
# a stable terminal state (i.e. it isn't in a state of waiting
# for resize to confirm/revert), however if the destination
# host is an Ocata compute host, it will delete the allocation
# that contains this source compute host information anyway and
# recreate an allocation that only refers to itself. So we
# don't need to do anything in that case. Just log the
# situation here for information but don't attempt to delete or
# change the allocation.
The code condition is:
if instance.host != cn.host:
LOG.
My conclusion is that the warning message could be changed to something different, perhaps something like
LOG.
Changed in nova: | |
status: | In Progress → Confirmed |
Fix proposed to branch: master /review. opendev. org/657916
Review: https:/