Description of problem:

Satellite using wrong/invalid/deleted ssh keypair and failing EC2 provisioning with following error:

----
Unable to save
Failed to create a compute aws+cr2 (us-west-2-EC2) instance carla-hritz: The key pair 'foreman-20b156c25-b77a-4534-9c9e-da60c1695849' does not exist
----

REASON:
 Satellite use ssh-key name "foreman-xxx" which was created by Satellite upon creating EC2 compute resource. key contents are available in satellite DB and AWS>Keypairs


If above keypair is deleted from AWS Console, Satellite fails with this error.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Create AWS compute resource: 
  
          WebUI: Compute Resources > aws CR > SSH Keys > you can find associated ssh keypair.(foreman-xxx)

2. Goto AWS Console (AWS > EC2 > Key Pairs) and delete mentioned keypair(foreman-xxx) and try to provision Ec2 instance.

3. 

Actual results:

Satellite will still look for DELETED KeyPair and fail.

Expected results:

Satellite Should give us option to CREATE NEW keypair. OR 
Give OPTION to choose NEW/Different keypair.

Additional info:


WORKAROUND:

-------
# hammer compute-resource list
                - Copy exact NAME of the compute resource from the list  Example: aws_cr


# foreman-rake console
# ComputeResource.find_by(:name =>'aws_cr').send(:destroy_key_pair)
# ComputeResource.find_by(:name =>'aws_cr').send(:create_key_pair)
-------

Goto: Satellite WebUI: Compute Resource > Select AWS compute resource > SSH_Keys > Now here you will have the option to create new SSH Key.