Bug 781312

Summary: cannot pass rhc-chk with the additional ssh key
Product: OKD Reporter: Meng Bo <bmeng>
Component: ContainersAssignee: Abhishek Gupta <abhgupta>
Status: CLOSED CURRENTRELEASE QA Contact: libra bugs <libra-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 1.x   
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rhc-0.84.13-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-02-02 23:55:33 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Meng Bo 2012-01-13 09:35:59 UTC
Description of problem:
rhc-chk cannot pass with the additional ssh key pair.

Version-Release number of selected component (if applicable):
rhc-node-0.84.23-1.el6_2.noarch 
rhc-broker-0.84.40-1.el6_2.noarch 

How reproducible:
always

Steps to Reproduce:
1.create domain with existed ssh key pair
# rhc-create-domain -n domain1 -l bmeng 
2.generate new ssh key pair and add the public key to domain above
# ssh-keygen 
# rhc-ctl-domain -a key1 -k libra_id_rsa_2.pub 
3.change the ssh key path and do rhc-chk
# vi ~/.openshift/express.config
ssh_key_file = 'libra_id_rsa_2'
# rhc-chk
  
Actual results:
rhc-chk failed due to ssh key unmatched.

Expected results:
rhc-chk should pass since the additional key pair matched.

Additional info:
[mengbo@localhost .ssh]$ rhc-domain-info -i
Password: 
User Info
=========
Namespace: bmeng4s
  RHLogin: bmeng+4
Primary SSH key: AAAAB3NzaC1yc2EAAAADAQABAAABAQCvk6aI6mJplA2BqfLaf6XheT26VQvvVhToSWGEl09+tZ/pVLBiZf+tDX0duGj5y+ATlMKAZ/urahO4nliQ1Kjs8ZO/xHYiIrZPm9jTgLEOd5c/wQh8Nof4E/FVqQEpcqq3ZhIk3a0bODE5nHfYPUphWjgLawFqVr0eoEbXUSc4QZ8Pubet2km6/sGtaEusF4ThERBq9jLjA5q4Gt/856lCa1SXPKCBtMBRLvMt4H7RYWwLG7ahzzuxygVNUVrIdLzW+WEWWJdI5SSpBXCDsJbPwBxmJhRqkyNNzPbq5u8DY7g2eoAthtDS3wE3rWKFFNFMTScK9ANwvh3Tn+DEwBuX
Primary SSH key type: ssh-rsa

Additional SSH keys
===================
Name: key1
 Key: AAAAB3NzaC1yc2EAAAABIwAAAQEArKlvv4vJBBUimp63II0/EbXI5Q5iTAfKuR+sdeg/uovu3Zkyz2S69DHv5BPEvheVz7Da9ebLeDemzWcXtYm+XR7+LfC5adWoXLQ/uy6yluogKt4hejYyHeEaOKgqR0s6MBtYWQitveFw+jLfjIiycofYWQIEXyp7PxvPeq4YJPtshEBUrqDNpdKnZLNN845VwRI8FB7x8mYLRy2rFciQGbjOR+SKvJ8CDryE9dTOJXtP2arrvznUVAYLGaEUOuiCQJOg8fRt5KFwjEFAbZ5fcTBmqjmJSx+P/a1LFMJPNXbyCuJOllZmqj93F8MPHteBxFqRooGFI+vMW/X68L7Y0w==
Type: ssh-rsa

Use rhc-ctl-domain for managing additional ssh keys


[mengbo@localhost .ssh]$ rhc-chk
Password: 
Analyzing system
..FF...
=================================================
||  Your system did not pass all of the tests  ||
=================================================
1) Local /home/mengbo/.ssh/libra_id_rsa_2 does not match remote pub key, SSH auth will not work FIX: Perhaps you should regenerate your public key, or run rhc-create-domain with -a to alter the remote key.
2) Local /home/mengbo/.ssh/libra_id_rsa_2 does not match remote pub key, SSH auth will not work FIX: Perhaps you should regenerate your public key, or run rhc-create-domain with -a to alter the remote key.

Comment 1 Abhishek Gupta 2012-01-13 22:17:45 UTC
The response structure change (ssh key value was changed from a string to a dictionary) was not carried over to the rhc-chk command.

This has been fixed now and will be part of the current release.

Comment 2 Meng Bo 2012-01-16 04:18:11 UTC
verified on devenv_217 with rhc-0.85.1-1.el6_2.noarch.
bug fixed

Comment 3 Mrunal Patel 2012-02-02 23:55:33 UTC
Closing verified bugs.