yahoo-eng-team team mailing list archive

[Loganathan Parthipan <1260301@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

If an expired vnc token is used, I'd expect an appropriate HTTP
response. However, currently novnc just hangs at "Starting VNC
handshake".

To reproduce

1. nova get-vnc-console <uuid> novnc => returns a URI with the token
2. point browser to the returned URI after the expiry
3. page hangs at "Starting VNC handshake"

Expected response

An appropriate HTTP response

** Affects: nova
     Importance: Undecided
         Status: New

** Summary changed:

- Expired vnc token doesn't result in an HTTP 401
+ Expired vnc token doesn't fail fast

** Description changed:

- If an expired vnc token is used, I'd expect an HTTP 401. However,
- currently novnc just hangs at "Starting VNC handshake".
+ If an expired vnc token is used, I'd expect an appropriate HTTP
+ response. However, currently novnc just hangs at "Starting VNC
+ handshake".
  
  To reproduce
  
  1. nova get-vnc-console <uuid> novnc => returns a URI with the token
  2. point browser to the returned URI after the expiry
  3. page hangs at "Starting VNC handshake"
  
  Expected response
  
- HTTP 401
+ An appropriate HTTP response

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1260301

Title:
  Expired vnc token doesn't fail fast

Status in OpenStack Compute (Nova):
  New

Bug description:
  If an expired vnc token is used, I'd expect an appropriate HTTP
  response. However, currently novnc just hangs at "Starting VNC
  handshake".

  To reproduce

  1. nova get-vnc-console <uuid> novnc => returns a URI with the token
  2. point browser to the returned URI after the expiry
  3. page hangs at "Starting VNC handshake"

  Expected response

  An appropriate HTTP response

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1260301/+subscriptions