Reply
Highlighted
Explorer
Posts: 12
Registered: ‎11-05-2018

Cloudera Director API Creating Kerberized cluster - Role is missing Kerberos keytab error

[ Edited ]

Hi All,

 

   I'm trying to create kerberos enabled cluster using cloudera director API. I can create deployment with Kerberos, but when I'm creating cluster via API in this Kerberized deployment I have an error as below:

 

[2019-01-16 11:23:08.144 +0000] ERROR [p-ffd58d681d66-DefaultBootstrapClusterJob] 4906ac24-006f-4526-a8c1-b9f2c6e29893 POST /api/v12/environments/devd/deployments/devd-deployment/clusters com.cloudera.launchpad.bootstrap.UnboundedWaitForApiCommand - c.c.l.b.UnboundedWaitForApiCommand: Command First Run with ID 81 failed. Details: ApiCommand{id=81, name=First Run, startTime=Wed Jan 16 11:22:52 UTC 2019, endTime=Wed Jan 16 11:23:03 UTC 2019, active=false, success=false, resultMessage=Failed to perform First Run of services., serviceRef=null, roleRef=null, hostRef=null, parent=null}
[2019-01-16 11:23:08.145 +0000] ERROR [p-ffd58d681d66-DefaultBootstrapClusterJob] 4906ac24-006f-4526-a8c1-b9f2c6e29893 POST /api/v12/environments/devd/deployments/devd-deployment/clusters com.cloudera.launchpad.bootstrap.UnboundedWaitForApiCommand - c.c.l.b.UnboundedWaitForApiCommand: Command Start with ID 87 failed. Details: ApiCommand{id=87, name=Start, startTime=Wed Jan 16 11:22:55 UTC 2019, endTime=Wed Jan 16 11:22:55 UTC 2019, active=false, success=false, resultMessage=Failed to start service., serviceRef=ApiServiceRef{peerName=null, clusterName=devd-cluster, serviceName=CD-HUE-uZsbrabQ}, roleRef=null, hostRef=null, parent=null}
[2019-01-16 11:23:08.145 +0000] ERROR [p-ffd58d681d66-DefaultBootstrapClusterJob] 4906ac24-006f-4526-a8c1-b9f2c6e29893 POST /api/v12/environments/devd/deployments/devd-deployment/clusters com.cloudera.launchpad.bootstrap.UnboundedWaitForApiCommand - c.c.l.b.UnboundedWaitForApiCommand: Command Format with ID 84 failed. Details: ApiCommand{id=84, name=Format, startTime=Wed Jan 16 11:22:53 UTC 2019, endTime=Wed Jan 16 11:22:53 UTC 2019, active=false, success=false, resultMessage=Command failed to run because this role has an invalid configuration. Review and correct its configuration. First error: Role is missing Kerberos keytab. Go to the Kerberos Credentials page and click the Generate Missing Credentials button., serviceRef=ApiServiceRef{peerName=null, clusterName=devd-cluster, serviceName=CD-HDFS-aUFIUBlr}, roleRef=ApiRoleRef{clusterName=devd-cluster, serviceName=CD-HDFS-aUFIUBlr, roleName=CD-HDFS-aUFIUBlr-NAMENODE-8323ef85de11982fad50916c90a09289}, hostRef=null, parent=null}
[2019-01-16 11:23:08.145 +0000] ERROR [p-ffd58d681d66-DefaultBootstrapClusterJob] 4906ac24-006f-4526-a8c1-b9f2c6e29893 POST /api/v12/environments/devd/deployments/devd-deployment/clusters com.cloudera.launchpad.bootstrap.UnboundedWaitForApiCommand - c.c.l.b.UnboundedWaitForApiCommand: Command ZkInit with ID 95 failed. Details: ApiCommand{id=95, name=ZkInit, startTime=Wed Jan 16 11:22:58 UTC 2019, endTime=Wed Jan 16 11:22:58 UTC 2019, active=false, success=false, resultMessage=Command failed to run because this role has an invalid configuration. Review and correct its configuration. First error: Role is missing Kerberos keytab. Go to the Kerberos Credentials page and click the Generate Missing Credentials button., serviceRef=ApiServiceRef{peerName=null, clusterName=devd-cluster, serviceName=CD-ZOOKEEPER-omDPdQXw}, roleRef=ApiRoleRef{clusterName=devd-cluster, serviceName=CD-ZOOKEEPER-omDPdQXw, roleName=CD-ZOOKEEPER-omDPdQXw-SERVER-8323ef85de11982fad50916c90a09289}, hostRef=null, parent=null}
[2019-01-16 11:23:08.145 +0000] ERROR [p-ffd58d681d66-DefaultBootstrapClusterJob] 4906ac24-006f-4526-a8c1-b9f2c6e29893 POST /api/v12/environments/devd/deployments/devd-deployment/clusters com.cloudera.launchpad.bootstrap.UnboundedWaitForApiCommand - c.c.l.b.UnboundedWaitForApiCommand: Command HiveCreateMetastoreTables with ID 85 failed. Details: ApiCommand{id=85, name=HiveCreateMetastoreTables, startTime=Wed Jan 16 11:22:53 UTC 2019, endTime=Wed Jan 16 11:22:53 UTC 2019, active=false, success=false, resultMessage=Command failed to run because this role has an invalid configuration. Review and correct its configuration. First error: Role is missing Kerberos keytab. Go to the Kerberos Credentials page and click the Generate Missing Credentials button., serviceRef=ApiServiceRef{peerName=null, clusterName=devd-cluster, serviceName=CD-HIVE-HQkdfQXY}, roleRef=ApiRoleRef{clusterName=devd-cluster, serviceName=CD-HIVE-HQkdfQXY, roleName=CD-HIVE-HQkdfQXY-HIVEMETASTORE-8323ef85de11982fad50916c90a09289}, hostRef=null, parent=null}
[2019-01-16 11:23:08.145 +0000] ERROR [p-ffd58d681d66-DefaultBootstrapClusterJob] 4906ac24-006f-4526-a8c1-b9f2c6e29893 POST /api/v12/environments/devd/deployments/devd-deployment/clusters com.cloudera.launchpad.bootstrap.UnboundedWaitForApiCommand - c.c.l.pipeline.util.PipelineRunner: Attempt to execute job failed

 

 

KDC looks good, because I can enable Kerberos via Cloudera Manager and it works.

 

Thanks for any help in advance.

 

Cheers,

 

Bart

Explorer
Posts: 12
Registered: ‎11-05-2018

Re: Cloudera Director API Creating Kerberized cluster - Role is missing Kerberos keytab error

KDC_TYPE was not set. Parameter value in json was escaped and despite Cloudera Director did not return any error this parameter was not set. I modified this parameter to "MIT KDC" and it works.
Announcements