Keypair name lost after launch

[Ken Pepple]

After launching an instance via Horizon, Horizon correctly shows the keypair that you used to launch the instance. However, after it has finished launching and you navigate away from the instances screen and then back to it, the "Keypair" field is set to "Not available".

I am unsure if this is a security "feature" or a bug. If it is as designed, the text should be changed to something more descriptive such as "set" or otherwise obscured to let the user know that there was a keypair set for the instance at launch.

I run into this error repeatedly with Devstack (single server) on trunk (#b177299).

[Gabriel Hurley (gabriel-hurley)]

This is an inconsistency in the Nova API. Under some calls there is a "key_name" attribute returned with the server data, under others there is not...

[Vish Ishaya (vishvananda)]

key_name is added to show and detail. It is not added to the list view. If Horizon wants to show data about the keypair it just needs to be converted to use GET /server/detail instead of GET /server

[Vish Ishaya (vishvananda)]

I was incorrect. There is a bug preventing key_name from appearing in detail

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/12895
Committed: http://github.com/openstack/nova/commit/e06d8bc8cd2b9cc98b0105d036479cb3773b30ac
Submitter: Jenkins
Branch: master

commit e06d8bc8cd2b9cc98b0105d036479cb3773b30ac
Author: Vishvananda Ishaya <email address hidden>
Date: Wed Sep 12 10:37:29 2012 -0700

    Makes key_name show in details view of servers

    The wrong authorizor was being used in the details view and the test
    for details was broken. This fixes the test and makes sure that
    key_name shows up in details like it is supposed to.

    Fixes bug 1043584

    Change-Id: I4ff01bbd32759f30e7a31ef2eac9f58922843037

[Gabriel Hurley (gabriel-hurley)]

Needs verification in Horizon