You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whirr.apache.org by "Andrew Bayer (JIRA)" <ji...@apache.org> on 2012/08/22 00:28:38 UTC
[jira] [Created] (WHIRR-641) No longer possible to hardcode
password for bootstrap user
Andrew Bayer created WHIRR-641:
----------------------------------
Summary: No longer possible to hardcode password for bootstrap user
Key: WHIRR-641
URL: https://issues.apache.org/jira/browse/WHIRR-641
Project: Whirr
Issue Type: Bug
Components: core
Affects Versions: 0.8.0
Reporter: Andrew Bayer
Assignee: Andrew Bayer
Priority: Critical
Fix For: 0.9.0
(debating whether to fix this in 0.8.0 with another RC or shrug and accept that it's an edge case and fix it in 0.8.1...)
With the whirr.template changes added in WHIRR-593, it's no longer possible to specify whirr.bootstrap-user=user:password (or whirr.template=loginUser=user:password, for that matter) to specify login creds for the bootstrap user. This is generally not a problem, since most providers will either use SSH keys or return a generated password, which jclouds picks up. But if for some reason your provider has hard-coded passwords on the images, you're kinda screwed here. The specific change that broke this is https://github.com/apache/whirr/commit/d7865344354b602ad59146afc6eadd7df4b7d344#L9L274.
--
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-641) No longer possible to hardcode
password for bootstrap user
Posted by "Adrian Cole (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13439245#comment-13439245 ]
Adrian Cole commented on WHIRR-641:
-----------------------------------
I offer to write tests for this, and if there's a less dangerous approach to fixing, I'll add that in a revision.
> No longer possible to hardcode password for bootstrap user
> ----------------------------------------------------------
>
> Key: WHIRR-641
> URL: https://issues.apache.org/jira/browse/WHIRR-641
> Project: Whirr
> Issue Type: Bug
> Components: core
> Affects Versions: 0.8.0
> Reporter: Andrew Bayer
> Assignee: Andrew Bayer
> Priority: Critical
> Fix For: 0.9.0
>
> Attachments: WHIRR-641.patch
>
>
> (debating whether to fix this in 0.8.0 with another RC or shrug and accept that it's an edge case and fix it in 0.8.1...)
> With the whirr.template changes added in WHIRR-593, it's no longer possible to specify whirr.bootstrap-user=user:password (or whirr.template=loginUser=user:password, for that matter) to specify login creds for the bootstrap user. This is generally not a problem, since most providers will either use SSH keys or return a generated password, which jclouds picks up. But if for some reason your provider has hard-coded passwords on the images, you're kinda screwed here. The specific change that broke this is https://github.com/apache/whirr/commit/d7865344354b602ad59146afc6eadd7df4b7d344#L9L274.
--
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-641) No longer possible to hardcode
password for bootstrap user
Posted by "Andrew Bayer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Bayer updated WHIRR-641:
-------------------------------
Fix Version/s: 0.8.1
Committed to branch-0.8 as well.
> No longer possible to hardcode password for bootstrap user
> ----------------------------------------------------------
>
> Key: WHIRR-641
> URL: https://issues.apache.org/jira/browse/WHIRR-641
> Project: Whirr
> Issue Type: Bug
> Components: core
> Affects Versions: 0.8.0
> Reporter: Andrew Bayer
> Assignee: Adrian Cole
> Priority: Critical
> Fix For: 0.8.1, 0.9.0
>
> Attachments: WHIRR-641.patch, WHIRR-641.patch, WHIRR-641-pt2.patch
>
>
> (debating whether to fix this in 0.8.0 with another RC or shrug and accept that it's an edge case and fix it in 0.8.1...)
> With the whirr.template changes added in WHIRR-593, it's no longer possible to specify whirr.bootstrap-user=user:password (or whirr.template=loginUser=user:password, for that matter) to specify login creds for the bootstrap user. This is generally not a problem, since most providers will either use SSH keys or return a generated password, which jclouds picks up. But if for some reason your provider has hard-coded passwords on the images, you're kinda screwed here. The specific change that broke this is https://github.com/apache/whirr/commit/d7865344354b602ad59146afc6eadd7df4b7d344#L9L274.
--
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-641) No longer possible to hardcode
password for bootstrap user
Posted by "Andrew Bayer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13440599#comment-13440599 ]
Andrew Bayer commented on WHIRR-641:
------------------------------------
Committing to trunk now.
> No longer possible to hardcode password for bootstrap user
> ----------------------------------------------------------
>
> Key: WHIRR-641
> URL: https://issues.apache.org/jira/browse/WHIRR-641
> Project: Whirr
> Issue Type: Bug
> Components: core
> Affects Versions: 0.8.0
> Reporter: Andrew Bayer
> Assignee: Adrian Cole
> Priority: Critical
> Fix For: 0.9.0
>
> Attachments: WHIRR-641.patch, WHIRR-641.patch
>
>
> (debating whether to fix this in 0.8.0 with another RC or shrug and accept that it's an edge case and fix it in 0.8.1...)
> With the whirr.template changes added in WHIRR-593, it's no longer possible to specify whirr.bootstrap-user=user:password (or whirr.template=loginUser=user:password, for that matter) to specify login creds for the bootstrap user. This is generally not a problem, since most providers will either use SSH keys or return a generated password, which jclouds picks up. But if for some reason your provider has hard-coded passwords on the images, you're kinda screwed here. The specific change that broke this is https://github.com/apache/whirr/commit/d7865344354b602ad59146afc6eadd7df4b7d344#L9L274.
--
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-641) No longer possible to hardcode
password for bootstrap user
Posted by "Andrew Bayer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13440572#comment-13440572 ]
Andrew Bayer commented on WHIRR-641:
------------------------------------
So the actual problem here is in jclouds and is fixed in beta.11, but I think we should go ahead with this patch on trunk (and branch-0.8 once I push the 0.8.0 release this afternoon) anyway. +1.
> No longer possible to hardcode password for bootstrap user
> ----------------------------------------------------------
>
> Key: WHIRR-641
> URL: https://issues.apache.org/jira/browse/WHIRR-641
> Project: Whirr
> Issue Type: Bug
> Components: core
> Affects Versions: 0.8.0
> Reporter: Andrew Bayer
> Assignee: Adrian Cole
> Priority: Critical
> Fix For: 0.9.0
>
> Attachments: WHIRR-641.patch, WHIRR-641.patch
>
>
> (debating whether to fix this in 0.8.0 with another RC or shrug and accept that it's an edge case and fix it in 0.8.1...)
> With the whirr.template changes added in WHIRR-593, it's no longer possible to specify whirr.bootstrap-user=user:password (or whirr.template=loginUser=user:password, for that matter) to specify login creds for the bootstrap user. This is generally not a problem, since most providers will either use SSH keys or return a generated password, which jclouds picks up. But if for some reason your provider has hard-coded passwords on the images, you're kinda screwed here. The specific change that broke this is https://github.com/apache/whirr/commit/d7865344354b602ad59146afc6eadd7df4b7d344#L9L274.
--
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-641) No longer possible to hardcode
password for bootstrap user
Posted by "Andrew Bayer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Bayer updated WHIRR-641:
-------------------------------
Attachment: WHIRR-641.patch
This patch adds back in the (provider).image.login-user override if the TemplateBuilderSpec in ClusterSpec returns non-null getLoginUser() - that gets set to what, historically, has been spec.getBootstrapUser(). I've tested this against our internal cloud setup, which happens to be that edge case where passwords are hardcoded, and it didn't work without this patch...and it does with it.
So the question is whether this is significant enough to merit a new RC. I'm tending to think it isn't.
> No longer possible to hardcode password for bootstrap user
> ----------------------------------------------------------
>
> Key: WHIRR-641
> URL: https://issues.apache.org/jira/browse/WHIRR-641
> Project: Whirr
> Issue Type: Bug
> Components: core
> Affects Versions: 0.8.0
> Reporter: Andrew Bayer
> Assignee: Andrew Bayer
> Priority: Critical
> Fix For: 0.9.0
>
> Attachments: WHIRR-641.patch
>
>
> (debating whether to fix this in 0.8.0 with another RC or shrug and accept that it's an edge case and fix it in 0.8.1...)
> With the whirr.template changes added in WHIRR-593, it's no longer possible to specify whirr.bootstrap-user=user:password (or whirr.template=loginUser=user:password, for that matter) to specify login creds for the bootstrap user. This is generally not a problem, since most providers will either use SSH keys or return a generated password, which jclouds picks up. But if for some reason your provider has hard-coded passwords on the images, you're kinda screwed here. The specific change that broke this is https://github.com/apache/whirr/commit/d7865344354b602ad59146afc6eadd7df4b7d344#L9L274.
--
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-641) No longer possible to hardcode
password for bootstrap user
Posted by "Adrian Cole (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adrian Cole updated WHIRR-641:
------------------------------
Attachment: WHIRR-641.patch
adds newline per checkstyle
> No longer possible to hardcode password for bootstrap user
> ----------------------------------------------------------
>
> Key: WHIRR-641
> URL: https://issues.apache.org/jira/browse/WHIRR-641
> Project: Whirr
> Issue Type: Bug
> Components: core
> Affects Versions: 0.8.0
> Reporter: Andrew Bayer
> Assignee: Adrian Cole
> Priority: Critical
> Fix For: 0.9.0
>
> Attachments: WHIRR-641.patch, WHIRR-641.patch
>
>
> (debating whether to fix this in 0.8.0 with another RC or shrug and accept that it's an edge case and fix it in 0.8.1...)
> With the whirr.template changes added in WHIRR-593, it's no longer possible to specify whirr.bootstrap-user=user:password (or whirr.template=loginUser=user:password, for that matter) to specify login creds for the bootstrap user. This is generally not a problem, since most providers will either use SSH keys or return a generated password, which jclouds picks up. But if for some reason your provider has hard-coded passwords on the images, you're kinda screwed here. The specific change that broke this is https://github.com/apache/whirr/commit/d7865344354b602ad59146afc6eadd7df4b7d344#L9L274.
--
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-641) No longer possible to hardcode
password for bootstrap user
Posted by "Adrian Cole (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adrian Cole updated WHIRR-641:
------------------------------
Attachment: (was: WHIRR-641.patch)
> No longer possible to hardcode password for bootstrap user
> ----------------------------------------------------------
>
> Key: WHIRR-641
> URL: https://issues.apache.org/jira/browse/WHIRR-641
> Project: Whirr
> Issue Type: Bug
> Components: core
> Affects Versions: 0.8.0
> Reporter: Andrew Bayer
> Assignee: Adrian Cole
> Priority: Critical
> Fix For: 0.9.0
>
> Attachments: WHIRR-641.patch, WHIRR-641.patch
>
>
> (debating whether to fix this in 0.8.0 with another RC or shrug and accept that it's an edge case and fix it in 0.8.1...)
> With the whirr.template changes added in WHIRR-593, it's no longer possible to specify whirr.bootstrap-user=user:password (or whirr.template=loginUser=user:password, for that matter) to specify login creds for the bootstrap user. This is generally not a problem, since most providers will either use SSH keys or return a generated password, which jclouds picks up. But if for some reason your provider has hard-coded passwords on the images, you're kinda screwed here. The specific change that broke this is https://github.com/apache/whirr/commit/d7865344354b602ad59146afc6eadd7df4b7d344#L9L274.
--
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-641) No longer possible to hardcode
password for bootstrap user
Posted by "Andrew Bayer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Bayer updated WHIRR-641:
-------------------------------
Attachment: WHIRR-641-pt2.patch
Whoops - forgot my additional local tweak. With this, I'm all good.
> No longer possible to hardcode password for bootstrap user
> ----------------------------------------------------------
>
> Key: WHIRR-641
> URL: https://issues.apache.org/jira/browse/WHIRR-641
> Project: Whirr
> Issue Type: Bug
> Components: core
> Affects Versions: 0.8.0
> Reporter: Andrew Bayer
> Assignee: Adrian Cole
> Priority: Critical
> Fix For: 0.9.0
>
> Attachments: WHIRR-641.patch, WHIRR-641.patch, WHIRR-641-pt2.patch
>
>
> (debating whether to fix this in 0.8.0 with another RC or shrug and accept that it's an edge case and fix it in 0.8.1...)
> With the whirr.template changes added in WHIRR-593, it's no longer possible to specify whirr.bootstrap-user=user:password (or whirr.template=loginUser=user:password, for that matter) to specify login creds for the bootstrap user. This is generally not a problem, since most providers will either use SSH keys or return a generated password, which jclouds picks up. But if for some reason your provider has hard-coded passwords on the images, you're kinda screwed here. The specific change that broke this is https://github.com/apache/whirr/commit/d7865344354b602ad59146afc6eadd7df4b7d344#L9L274.
--
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-641) No longer possible to hardcode
password for bootstrap user
Posted by "Adrian Cole (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13439239#comment-13439239 ]
Adrian Cole commented on WHIRR-641:
-----------------------------------
like so many things in whirr. this issue smells of many missing test cases.
> No longer possible to hardcode password for bootstrap user
> ----------------------------------------------------------
>
> Key: WHIRR-641
> URL: https://issues.apache.org/jira/browse/WHIRR-641
> Project: Whirr
> Issue Type: Bug
> Components: core
> Affects Versions: 0.8.0
> Reporter: Andrew Bayer
> Assignee: Andrew Bayer
> Priority: Critical
> Fix For: 0.9.0
>
> Attachments: WHIRR-641.patch
>
>
> (debating whether to fix this in 0.8.0 with another RC or shrug and accept that it's an edge case and fix it in 0.8.1...)
> With the whirr.template changes added in WHIRR-593, it's no longer possible to specify whirr.bootstrap-user=user:password (or whirr.template=loginUser=user:password, for that matter) to specify login creds for the bootstrap user. This is generally not a problem, since most providers will either use SSH keys or return a generated password, which jclouds picks up. But if for some reason your provider has hard-coded passwords on the images, you're kinda screwed here. The specific change that broke this is https://github.com/apache/whirr/commit/d7865344354b602ad59146afc6eadd7df4b7d344#L9L274.
--
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-641) No longer possible to hardcode
password for bootstrap user
Posted by "Andrew Bayer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13440590#comment-13440590 ]
Andrew Bayer commented on WHIRR-641:
------------------------------------
beta.11 + this patch seems to suffice in my testing, so let's go forward with this patch on trunk.
> No longer possible to hardcode password for bootstrap user
> ----------------------------------------------------------
>
> Key: WHIRR-641
> URL: https://issues.apache.org/jira/browse/WHIRR-641
> Project: Whirr
> Issue Type: Bug
> Components: core
> Affects Versions: 0.8.0
> Reporter: Andrew Bayer
> Assignee: Adrian Cole
> Priority: Critical
> Fix For: 0.9.0
>
> Attachments: WHIRR-641.patch, WHIRR-641.patch
>
>
> (debating whether to fix this in 0.8.0 with another RC or shrug and accept that it's an edge case and fix it in 0.8.1...)
> With the whirr.template changes added in WHIRR-593, it's no longer possible to specify whirr.bootstrap-user=user:password (or whirr.template=loginUser=user:password, for that matter) to specify login creds for the bootstrap user. This is generally not a problem, since most providers will either use SSH keys or return a generated password, which jclouds picks up. But if for some reason your provider has hard-coded passwords on the images, you're kinda screwed here. The specific change that broke this is https://github.com/apache/whirr/commit/d7865344354b602ad59146afc6eadd7df4b7d344#L9L274.
--
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-641) No longer possible to hardcode
password for bootstrap user
Posted by "Adrian Cole (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adrian Cole updated WHIRR-641:
------------------------------
Attachment: WHIRR-641.patch
isolated change to where config is parsed. isolated code related to change and backfilled tests
> No longer possible to hardcode password for bootstrap user
> ----------------------------------------------------------
>
> Key: WHIRR-641
> URL: https://issues.apache.org/jira/browse/WHIRR-641
> Project: Whirr
> Issue Type: Bug
> Components: core
> Affects Versions: 0.8.0
> Reporter: Andrew Bayer
> Assignee: Adrian Cole
> Priority: Critical
> Fix For: 0.9.0
>
> Attachments: WHIRR-641.patch, WHIRR-641.patch
>
>
> (debating whether to fix this in 0.8.0 with another RC or shrug and accept that it's an edge case and fix it in 0.8.1...)
> With the whirr.template changes added in WHIRR-593, it's no longer possible to specify whirr.bootstrap-user=user:password (or whirr.template=loginUser=user:password, for that matter) to specify login creds for the bootstrap user. This is generally not a problem, since most providers will either use SSH keys or return a generated password, which jclouds picks up. But if for some reason your provider has hard-coded passwords on the images, you're kinda screwed here. The specific change that broke this is https://github.com/apache/whirr/commit/d7865344354b602ad59146afc6eadd7df4b7d344#L9L274.
--
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-641) No longer possible to hardcode
password for bootstrap user
Posted by "Adrian Cole (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13440588#comment-13440588 ]
Adrian Cole commented on WHIRR-641:
-----------------------------------
I'd say more correctly "actual problem here is [also] in jclouds". There are syntax errors we've identified and test gaps that are definitely issues. That said, once you clear them out, you are hung until the upstream fixes apply (those in jclouds 1.5.0-beta.11)
> No longer possible to hardcode password for bootstrap user
> ----------------------------------------------------------
>
> Key: WHIRR-641
> URL: https://issues.apache.org/jira/browse/WHIRR-641
> Project: Whirr
> Issue Type: Bug
> Components: core
> Affects Versions: 0.8.0
> Reporter: Andrew Bayer
> Assignee: Adrian Cole
> Priority: Critical
> Fix For: 0.9.0
>
> Attachments: WHIRR-641.patch, WHIRR-641.patch
>
>
> (debating whether to fix this in 0.8.0 with another RC or shrug and accept that it's an edge case and fix it in 0.8.1...)
> With the whirr.template changes added in WHIRR-593, it's no longer possible to specify whirr.bootstrap-user=user:password (or whirr.template=loginUser=user:password, for that matter) to specify login creds for the bootstrap user. This is generally not a problem, since most providers will either use SSH keys or return a generated password, which jclouds picks up. But if for some reason your provider has hard-coded passwords on the images, you're kinda screwed here. The specific change that broke this is https://github.com/apache/whirr/commit/d7865344354b602ad59146afc6eadd7df4b7d344#L9L274.
--
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] [Assigned] (WHIRR-641) No longer possible to hardcode
password for bootstrap user
Posted by "Adrian Cole (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adrian Cole reassigned WHIRR-641:
---------------------------------
Assignee: Adrian Cole (was: Andrew Bayer)
> No longer possible to hardcode password for bootstrap user
> ----------------------------------------------------------
>
> Key: WHIRR-641
> URL: https://issues.apache.org/jira/browse/WHIRR-641
> Project: Whirr
> Issue Type: Bug
> Components: core
> Affects Versions: 0.8.0
> Reporter: Andrew Bayer
> Assignee: Adrian Cole
> Priority: Critical
> Fix For: 0.9.0
>
> Attachments: WHIRR-641.patch
>
>
> (debating whether to fix this in 0.8.0 with another RC or shrug and accept that it's an edge case and fix it in 0.8.1...)
> With the whirr.template changes added in WHIRR-593, it's no longer possible to specify whirr.bootstrap-user=user:password (or whirr.template=loginUser=user:password, for that matter) to specify login creds for the bootstrap user. This is generally not a problem, since most providers will either use SSH keys or return a generated password, which jclouds picks up. But if for some reason your provider has hard-coded passwords on the images, you're kinda screwed here. The specific change that broke this is https://github.com/apache/whirr/commit/d7865344354b602ad59146afc6eadd7df4b7d344#L9L274.
--
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-641) No longer possible to hardcode
password for bootstrap user
Posted by "Adrian Cole (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13440592#comment-13440592 ]
Adrian Cole commented on WHIRR-641:
-----------------------------------
+1
> No longer possible to hardcode password for bootstrap user
> ----------------------------------------------------------
>
> Key: WHIRR-641
> URL: https://issues.apache.org/jira/browse/WHIRR-641
> Project: Whirr
> Issue Type: Bug
> Components: core
> Affects Versions: 0.8.0
> Reporter: Andrew Bayer
> Assignee: Adrian Cole
> Priority: Critical
> Fix For: 0.9.0
>
> Attachments: WHIRR-641.patch, WHIRR-641.patch
>
>
> (debating whether to fix this in 0.8.0 with another RC or shrug and accept that it's an edge case and fix it in 0.8.1...)
> With the whirr.template changes added in WHIRR-593, it's no longer possible to specify whirr.bootstrap-user=user:password (or whirr.template=loginUser=user:password, for that matter) to specify login creds for the bootstrap user. This is generally not a problem, since most providers will either use SSH keys or return a generated password, which jclouds picks up. But if for some reason your provider has hard-coded passwords on the images, you're kinda screwed here. The specific change that broke this is https://github.com/apache/whirr/commit/d7865344354b602ad59146afc6eadd7df4b7d344#L9L274.
--
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