vm_state and power_state are inconsistent after creating a VM which is not power-on.

[javeme]

vm_state and power_state are inconsistent after creating a VM which is not power-on, until periodic task _sync_power_states().
It's need to set the vm_state to the state decided by the power_state(such as STOPPED) instead of ACTIVE, after it is created.

[master] nova/compute/manager.py class ComputeManager._update_instance_after_spawn():
    def _update_instance_after_spawn(self, context, instance):
        instance.power_state = self._get_power_state(context, instance)
        instance.vm_state = vm_states.ACTIVE # todo: decided by the power_state(such as STOPPED) instead of ACTIVE
        instance.task_state = None
        instance.launched_at = timeutils.utcnow()
        configdrive.update_instance(instance)

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/181661

[melanie witt (melwitt)]

Can you elaborate about what you mean by "creating a VM which is not powered on?" When an instance is created, it should be powered on. What behavior have you observed?

[OpenStack Infra (hudson-openstack)]

Change abandoned by javeme (<email address hidden>) on branch: master
Review: https://review.openstack.org/181661

[Sean Dague (sdague)]

This bug does not have enough information to be actionable, it would have auto expired, except it was assigned to a user.