You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whirr.apache.org by "Pavel Vozdvizhenskiy (JIRA)" <ji...@apache.org> on 2012/04/23 19:23:36 UTC
[jira] [Created] (WHIRR-584) Change confusing ssh login help
message at the end of deployment
Pavel Vozdvizhenskiy created WHIRR-584:
------------------------------------------
Summary: Change confusing ssh login help message at the end of deployment
Key: WHIRR-584
URL: https://issues.apache.org/jira/browse/WHIRR-584
Project: Whirr
Issue Type: Bug
Components: core
Affects Versions: 0.7.1
Environment: Amazon EC2
Reporter: Pavel Vozdvizhenskiy
Priority: Trivial
Hello.
I have following properties file:
whirr.cluster-name=vpv-hadoop
whirr.cluster-user=persona
whirr.instance-templates=1 hadoop-namenode+hadoop-jobtracker+hadoop-datanode+hadoop-tasktracker
whirr.hadoop.install-function=install_cdh_hadoop
whirr.hadoop.configure-function=configure_cdh_hadoop
whirr.provider=aws-ec2
whirr.identity=XXXXXXXXXXXXXXXX
whirr.credential=YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY
whirr.hardware-id=m1.large
# This is custom AMI based on Ubuntu 10.04 LTS (lucid) ami-8fac75e6
whirr.image-id=us-east-1/ami-e005de89
# jclouds.ec2.ami-query=owner-id=215688387811;state=available;image-type=machine
whirr.location-id=us-east-1
# This property is required since I use custom AMI
whirr.login-user=ubuntu
At the end of deployment I got following message:
You can log into instances using the following ssh commands:
'ssh -i /home/vpv/.ssh/id_rsa -o "UserKnownHostsFile /dev/null" -o StrictHostKeyChecking=no ubuntu@50.17.168.40'
However, this command is incorrect:
$ ssh -i /home/vpv/.ssh/id_rsa -o "UserKnownHostsFile /dev/null" -o StrictHostKeyChecking=no ubuntu@50.17.168.40
Warning: Permanently added '50.17.168.40' (RSA) to the list of known hosts.
Permission denied (publickey).
The correct one is using value of whirr.cluster-user property:
$ ssh -i /home/vpv/.ssh/id_rsa -o "UserKnownHostsFile /dev/null" -o StrictHostKeyChecking=no persona@50.17.168.40 hostname
Warning: Permanently added '50.17.168.40' (RSA) to the list of known hosts.
ip-10-34-83-52
$
That is because jclouds creates new keypair based on cluster name and injects it for 'login-user' account. While key specified in whirr.private-key-file is used for 'cluster-user' account
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (WHIRR-584) Change confusing ssh login help
message at the end of deployment
Posted by "Andrei Savu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13259809#comment-13259809 ]
Andrei Savu commented on WHIRR-584:
-----------------------------------
Good catch! Thanks for reporting.
> Change confusing ssh login help message at the end of deployment
> ----------------------------------------------------------------
>
> Key: WHIRR-584
> URL: https://issues.apache.org/jira/browse/WHIRR-584
> Project: Whirr
> Issue Type: Bug
> Components: core
> Affects Versions: 0.7.1
> Environment: Amazon EC2
> Reporter: Pavel Vozdvizhenskiy
> Priority: Trivial
> Labels: deployment, ec2, login, ssh
>
> Hello.
> I have following properties file:
> whirr.cluster-name=vpv-hadoop
> whirr.cluster-user=persona
> whirr.instance-templates=1 hadoop-namenode+hadoop-jobtracker+hadoop-datanode+hadoop-tasktracker
> whirr.hadoop.install-function=install_cdh_hadoop
> whirr.hadoop.configure-function=configure_cdh_hadoop
> whirr.provider=aws-ec2
> whirr.identity=XXXXXXXXXXXXXXXX
> whirr.credential=YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY
> whirr.hardware-id=m1.large
> # This is custom AMI based on Ubuntu 10.04 LTS (lucid) ami-8fac75e6
> whirr.image-id=us-east-1/ami-e005de89
> # jclouds.ec2.ami-query=owner-id=215688387811;state=available;image-type=machine
> whirr.location-id=us-east-1
> # This property is required since I use custom AMI
> whirr.login-user=ubuntu
> At the end of deployment I got following message:
> You can log into instances using the following ssh commands:
> 'ssh -i /home/vpv/.ssh/id_rsa -o "UserKnownHostsFile /dev/null" -o StrictHostKeyChecking=no ubuntu@50.17.168.40'
> However, this command is incorrect:
> $ ssh -i /home/vpv/.ssh/id_rsa -o "UserKnownHostsFile /dev/null" -o StrictHostKeyChecking=no ubuntu@50.17.168.40
> Warning: Permanently added '50.17.168.40' (RSA) to the list of known hosts.
> Permission denied (publickey).
> The correct one is using value of whirr.cluster-user property:
> $ ssh -i /home/vpv/.ssh/id_rsa -o "UserKnownHostsFile /dev/null" -o StrictHostKeyChecking=no persona@50.17.168.40 hostname
> Warning: Permanently added '50.17.168.40' (RSA) to the list of known hosts.
> ip-10-34-83-52
> $
> That is because jclouds creates new keypair based on cluster name and injects it for 'login-user' account. While key specified in whirr.private-key-file is used for 'cluster-user' account
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (WHIRR-584) Change confusing ssh login help
message at the end of deployment
Posted by "Andrew Bayer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Bayer updated WHIRR-584:
-------------------------------
Attachment: WHIRR-584.diff.txt
I think this patch should do the trick - it flips the check to use cluster user if that's set and falls back to bootstrap user, rather than the current setup (which is the opposite).
> Change confusing ssh login help message at the end of deployment
> ----------------------------------------------------------------
>
> Key: WHIRR-584
> URL: https://issues.apache.org/jira/browse/WHIRR-584
> Project: Whirr
> Issue Type: Bug
> Components: core
> Affects Versions: 0.7.1
> Environment: Amazon EC2
> Reporter: Pavel Vozdvizhenskiy
> Priority: Trivial
> Labels: deployment, ec2, login, ssh
> Attachments: WHIRR-584.diff.txt
>
>
> Hello.
> I have following properties file:
> {code}
> whirr.cluster-name=vpv-hadoop
> whirr.cluster-user=persona
> whirr.instance-templates=1 hadoop-namenode+hadoop-jobtracker+hadoop-datanode+hadoop-tasktracker
> whirr.hadoop.install-function=install_cdh_hadoop
> whirr.hadoop.configure-function=configure_cdh_hadoop
> whirr.provider=aws-ec2
> whirr.identity=XXXXXXXXXXXXXXXX
> whirr.credential=YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY
> whirr.hardware-id=m1.large
> # This is custom AMI based on Ubuntu 10.04 LTS (lucid) ami-8fac75e6
> whirr.image-id=us-east-1/ami-e005de89
> # jclouds.ec2.ami-query=owner-id=215688387811;state=available;image-type=machine
> whirr.location-id=us-east-1
> # This property is required since I use custom AMI
> whirr.login-user=ubuntu
> {code}
> At the end of deployment I got following message:
> You can log into instances using the following ssh commands:
> 'ssh -i /home/vpv/.ssh/id_rsa -o "UserKnownHostsFile /dev/null" -o StrictHostKeyChecking=no ubuntu@50.17.168.40'
> However, this command is incorrect:
> $ ssh -i /home/vpv/.ssh/id_rsa -o "UserKnownHostsFile /dev/null" -o StrictHostKeyChecking=no ubuntu@50.17.168.40
> Warning: Permanently added '50.17.168.40' (RSA) to the list of known hosts.
> Permission denied (publickey).
> The correct one is using value of whirr.cluster-user property:
> $ ssh -i /home/vpv/.ssh/id_rsa -o "UserKnownHostsFile /dev/null" -o StrictHostKeyChecking=no persona@50.17.168.40 hostname
> Warning: Permanently added '50.17.168.40' (RSA) to the list of known hosts.
> ip-10-34-83-52
> $
> That is because jclouds creates new keypair based on cluster name and injects it for 'login-user' account. While key specified in whirr.private-key-file is used for 'cluster-user' account
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (WHIRR-584) Change confusing ssh login help
message at the end of deployment
Posted by "Pavel Vozdvizhenskiy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pavel Vozdvizhenskiy updated WHIRR-584:
---------------------------------------
Description:
Hello.
I have following properties file:
{code}
whirr.cluster-name=vpv-hadoop
whirr.cluster-user=persona
whirr.instance-templates=1 hadoop-namenode+hadoop-jobtracker+hadoop-datanode+hadoop-tasktracker
whirr.hadoop.install-function=install_cdh_hadoop
whirr.hadoop.configure-function=configure_cdh_hadoop
whirr.provider=aws-ec2
whirr.identity=XXXXXXXXXXXXXXXX
whirr.credential=YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY
whirr.hardware-id=m1.large
# This is custom AMI based on Ubuntu 10.04 LTS (lucid) ami-8fac75e6
whirr.image-id=us-east-1/ami-e005de89
# jclouds.ec2.ami-query=owner-id=215688387811;state=available;image-type=machine
whirr.location-id=us-east-1
# This property is required since I use custom AMI
whirr.login-user=ubuntu
{code}
At the end of deployment I got following message:
You can log into instances using the following ssh commands:
'ssh -i /home/vpv/.ssh/id_rsa -o "UserKnownHostsFile /dev/null" -o StrictHostKeyChecking=no ubuntu@50.17.168.40'
However, this command is incorrect:
$ ssh -i /home/vpv/.ssh/id_rsa -o "UserKnownHostsFile /dev/null" -o StrictHostKeyChecking=no ubuntu@50.17.168.40
Warning: Permanently added '50.17.168.40' (RSA) to the list of known hosts.
Permission denied (publickey).
The correct one is using value of whirr.cluster-user property:
$ ssh -i /home/vpv/.ssh/id_rsa -o "UserKnownHostsFile /dev/null" -o StrictHostKeyChecking=no persona@50.17.168.40 hostname
Warning: Permanently added '50.17.168.40' (RSA) to the list of known hosts.
ip-10-34-83-52
$
That is because jclouds creates new keypair based on cluster name and injects it for 'login-user' account. While key specified in whirr.private-key-file is used for 'cluster-user' account
was:
Hello.
I have following properties file:
whirr.cluster-name=vpv-hadoop
whirr.cluster-user=persona
whirr.instance-templates=1 hadoop-namenode+hadoop-jobtracker+hadoop-datanode+hadoop-tasktracker
whirr.hadoop.install-function=install_cdh_hadoop
whirr.hadoop.configure-function=configure_cdh_hadoop
whirr.provider=aws-ec2
whirr.identity=XXXXXXXXXXXXXXXX
whirr.credential=YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY
whirr.hardware-id=m1.large
# This is custom AMI based on Ubuntu 10.04 LTS (lucid) ami-8fac75e6
whirr.image-id=us-east-1/ami-e005de89
# jclouds.ec2.ami-query=owner-id=215688387811;state=available;image-type=machine
whirr.location-id=us-east-1
# This property is required since I use custom AMI
whirr.login-user=ubuntu
At the end of deployment I got following message:
You can log into instances using the following ssh commands:
'ssh -i /home/vpv/.ssh/id_rsa -o "UserKnownHostsFile /dev/null" -o StrictHostKeyChecking=no ubuntu@50.17.168.40'
However, this command is incorrect:
$ ssh -i /home/vpv/.ssh/id_rsa -o "UserKnownHostsFile /dev/null" -o StrictHostKeyChecking=no ubuntu@50.17.168.40
Warning: Permanently added '50.17.168.40' (RSA) to the list of known hosts.
Permission denied (publickey).
The correct one is using value of whirr.cluster-user property:
$ ssh -i /home/vpv/.ssh/id_rsa -o "UserKnownHostsFile /dev/null" -o StrictHostKeyChecking=no persona@50.17.168.40 hostname
Warning: Permanently added '50.17.168.40' (RSA) to the list of known hosts.
ip-10-34-83-52
$
That is because jclouds creates new keypair based on cluster name and injects it for 'login-user' account. While key specified in whirr.private-key-file is used for 'cluster-user' account
fixed formatting
> Change confusing ssh login help message at the end of deployment
> ----------------------------------------------------------------
>
> Key: WHIRR-584
> URL: https://issues.apache.org/jira/browse/WHIRR-584
> Project: Whirr
> Issue Type: Bug
> Components: core
> Affects Versions: 0.7.1
> Environment: Amazon EC2
> Reporter: Pavel Vozdvizhenskiy
> Priority: Trivial
> Labels: deployment, ec2, login, ssh
>
> Hello.
> I have following properties file:
> {code}
> whirr.cluster-name=vpv-hadoop
> whirr.cluster-user=persona
> whirr.instance-templates=1 hadoop-namenode+hadoop-jobtracker+hadoop-datanode+hadoop-tasktracker
> whirr.hadoop.install-function=install_cdh_hadoop
> whirr.hadoop.configure-function=configure_cdh_hadoop
> whirr.provider=aws-ec2
> whirr.identity=XXXXXXXXXXXXXXXX
> whirr.credential=YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY
> whirr.hardware-id=m1.large
> # This is custom AMI based on Ubuntu 10.04 LTS (lucid) ami-8fac75e6
> whirr.image-id=us-east-1/ami-e005de89
> # jclouds.ec2.ami-query=owner-id=215688387811;state=available;image-type=machine
> whirr.location-id=us-east-1
> # This property is required since I use custom AMI
> whirr.login-user=ubuntu
> {code}
> At the end of deployment I got following message:
> You can log into instances using the following ssh commands:
> 'ssh -i /home/vpv/.ssh/id_rsa -o "UserKnownHostsFile /dev/null" -o StrictHostKeyChecking=no ubuntu@50.17.168.40'
> However, this command is incorrect:
> $ ssh -i /home/vpv/.ssh/id_rsa -o "UserKnownHostsFile /dev/null" -o StrictHostKeyChecking=no ubuntu@50.17.168.40
> Warning: Permanently added '50.17.168.40' (RSA) to the list of known hosts.
> Permission denied (publickey).
> The correct one is using value of whirr.cluster-user property:
> $ ssh -i /home/vpv/.ssh/id_rsa -o "UserKnownHostsFile /dev/null" -o StrictHostKeyChecking=no persona@50.17.168.40 hostname
> Warning: Permanently added '50.17.168.40' (RSA) to the list of known hosts.
> ip-10-34-83-52
> $
> That is because jclouds creates new keypair based on cluster name and injects it for 'login-user' account. While key specified in whirr.private-key-file is used for 'cluster-user' account
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira