test_get_vnc_console doesn't get the console

Bug #1554460 reported by Joseph Lanoux
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tempest
Fix Released
Low
Jordan Pittier

Bug Description

The test_get_vnc_console test doesn't get the VNC console nor verifies the Nova VNC proxy. It just calls the Nova API to get the URL of the console and checks it has the correct format.
Adding a 'wget' or curl command of some sort would probe the feature properly.

Changed in tempest:
assignee: nobody → Joshua White (joshua-l-white)
Changed in tempest:
status: New → In Progress
Revision history for this message
Joshua White (joshua-l-white) wrote :

I noticed that test_get_vnc_console tests 2 console types: novnc & xvpvnc. The first, novnc, can be tested with a curl request. However, xvpvnc, relies on a java client and would require adding dependencies to the testers system. I don't think it would be a good idea to move forward with adding it. Any thoughts?

Changed in tempest:
status: In Progress → Confirmed
Changed in tempest:
assignee: Joshua White (joshua-l-white) → nobody
Changed in tempest:
status: Confirmed → Opinion
Changed in tempest:
assignee: nobody → Michelle Mandel (mmandel)
status: Opinion → In Progress
Changed in tempest:
assignee: Michelle Mandel (mmandel) → Jordan Pittier (jordan-pittier)
Changed in tempest:
importance: Undecided → Low
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tempest (master)

Reviewed: https://review.openstack.org/343078
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=1f87a5611a983acac2208c3e0ba07eee75fe9a51
Submitter: Jenkins
Branch: master

commit 1f87a5611a983acac2208c3e0ba07eee75fe9a51
Author: Michelle Mandel <email address hidden>
Date: Fri Jul 15 17:11:33 2016 -0400

    Add tempest test to test NoVNC support

    Currently there exists support within tempest to make sure that the
    VNC Console URL can be generated, but there is no support to test out
    the actual NoVNC code through the novncproxy. This will add support
    to verify that the novncproxy will return the proper NoVNC JavaScript
    HTML, that the authentication token is validated, and that the basic
    exchange of the RFB protocol from the client through the novncproxy
    is a valid VNC session.

    This test requires that the tempest configuration specifies that the
    VNC Console feature is enabled, otherwise the test will be skipped.
    Additional integration test environments can be switched to enable
    this feature to take advantage of this test.

    This support is being added in conjunction with change set 115484 to
    further test the NoVNC TLS Support, but this test case will work
    whether or not the communication between the novncproxy and VNC
    session is using TLS or is unencrypted.

    Change-Id: Ic7e149f79705cbb910c5b6524dac5cdb73d69710
    Closes-Bug: 1554460
    Depends-On: Idb38a3b11e2f61f23adf1ec23c04ddccd72e7539

Changed in tempest:
status: In Progress → Fix Released
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.