VMware: unable to access VNC console of rescue VM

Bug #1356389 reported by Gary Kotton
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Fix Released
High
Gary Kotton

Bug Description

When doing a rescue VM the user is unable to access the VNC console of that VM
In addition the state of the rescue VM is also 'SHUTDOWN'

Gary Kotton (garyk)
Changed in nova:
milestone: none → juno-3
assignee: nobody → Gary Kotton (garyk)
importance: Undecided → Critical
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to nova (master)

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

Changed in nova:
status: New → In Progress
Gary Kotton (garyk)
tags: added: icehouse-backport-potential vmware
Revision history for this message
Tracy Jones (tjones-i) wrote : Re: VMware: unable to access VNC console of resuce VM

as this only affects 1 hypervisor by definition it cannot be critical

Changed in nova:
importance: Critical → High
Thierry Carrez (ttx)
Changed in nova:
milestone: juno-3 → juno-rc1
Revision history for this message
Michael Still (mikal) wrote :

Is anyone working on this bug? We might need to drop if from rc1 if there isn't a fix proposed soon.

summary: - VMware: unable to access VNC console of resuce VM
+ VMware: unable to access VNC console of rescue VM
Michael Still (mikal)
Changed in nova:
milestone: juno-rc1 → none
description: updated
Gary Kotton (garyk)
tags: added: juno-backport-potential
Revision history for this message
Gary Kotton (garyk) wrote :
Changed in nova:
milestone: none → kilo-3
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to nova (master)

Reviewed: https://review.openstack.org/113908
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=cd1765459a24e52e1b933c8e05517fed75ac9d41
Submitter: Jenkins
Branch: master

commit cd1765459a24e52e1b933c8e05517fed75ac9d41
Author: Gary Kotton <email address hidden>
Date: Wed Aug 13 07:11:55 2014 -0700

    VMware: fix VM rescue problem with VNC console

    The user was unable to access the VNC console after a VM was rescued.

    This is solved by refactoring the rescue/unrescue operations. We
    no longer spawn a new VM on rescue but attach the original image and
    boot from it. On unrescue detach the original (rescue) image.

    Co-authored-by: Radoslav Gerganov <email address hidden>

    UpgradeImpact

    Prior to this patch a rescue operation would create a new VM and the
    rescue would take place on the new VM. This is prone to an endless
    amount of problems. Some of the issues found are:
     - unable to access the VNC console of a rescued instance
     - unstable to suspend or resume a rescued instance
     - rescue with ephemeral disks does not work
    This patch now uses an inplace rescue on the same
    VM. It is suggested that when upgrading to the latest version to ensure
    that users are aware that a rescue during the upgrade may be problematic.
    It is suggested that in the upgrade window that the admin prevent instances
    being rescued and give sufficient notice to users.

    Change-Id: I3218e7edfe0f71626b2930c39dea0fba4d2e69ca
    Closes-bug: #1356389

Changed in nova:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in nova:
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in nova:
milestone: kilo-3 → 2015.1.0
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.