Login to a Nova Compute Instance using an SSL Key FAILS if the Key File Name contains dashes and numbers

[Bruce Basil Mathews]

Customer reported information on a Fuel 6.0 deployed cloud hosting a RHEL 6.6 Virtual Machine:

I ran a few tests, and here’s the results:

Lower-case key-pair name with no dash and no number in the name: success

Lower-case key-pair name with dash and no number in the name: success

Lower-case key-pair name with dash and number in the name: success

Upper-case key-pair name with no dash and no number in the name: success

Upper-case key-pair name with dash and no number in the name: success

Upper-case key-pair name with dash and number in the name: fail

Combinations tested: keytest, key-test, key-test1, KeyTest, Key-Test, Key-Test1, Intel-Test2

Looks like I ran across the only combination that fails reliably.

This may be a bug in the parser on the cloud-init side living in the RHEL image, or in the Nova metadata engine, but since it was discovered on a Fuel deployed cloud, I wanted to register the bug here. Can you please try to reproduce this issue on an actual Fuel deployment with a RHEL 6.6 image? It has been attempted with DevStack but cannot be reproduced.

[Eugeniya Kudryashova (ekudryashova)]

Tried to reproduce on Fuel 6.0 and Centos image (as we don't have RHEL image)

Keypair was successfully created, assigned to instanse. Also I successfully connect via SSH with this key. Tried upper-case key name with dash and number.

Could you describe in which moment such key fails? Left status "Incoplete" for a while, waiting for answer.

[Dmitry Mescheryakov (dmitrymex)]

The bug is hanging in incomplete state for more than a month, hence moving it to invalid.