You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@jclouds.apache.org by "Ignasi Barrera (JIRA)" <ji...@apache.org> on 2015/05/26 00:29:18 UTC
[jira] [Commented] (JCLOUDS-911) Jclouds cannot create CentOS in
Google Compute Engine
[ https://issues.apache.org/jira/browse/JCLOUDS-911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14558557#comment-14558557 ]
Ignasi Barrera commented on JCLOUDS-911:
----------------------------------------
Could this be related to JCLOUDS-861? If cloud-init configures the ssh daemon, that could explain why the solution for CentOS is to provide the cloud-init configuration in the instance metadata.
[~yaronr], [~broudy] could you confirm this?
> Jclouds cannot create CentOS in Google Compute Engine
> -----------------------------------------------------
>
> Key: JCLOUDS-911
> URL: https://issues.apache.org/jira/browse/JCLOUDS-911
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-compute
> Affects Versions: 2.0.0
> Reporter: Ruben Rubio Rey
> Priority: Critical
>
> Jclouds cannot create CentOS instances in Google Compute Engine.
> By default GCE uses the root user to log into the server, and CentOS instances in GCE does not PermitRootLogin at sshd_config.
> Therefore it fails at org.jclouds.compute.internal.BaseComputeService.createNodesInGroup(BaseComputeService.java:222) because of AuthorizationException.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)