Reply
Master
Posts: 305
Registered: ‎07-01-2015

Missing endpoint address string for publicIpAddress on instance

[ Edited ]

Hi,

 I am running ClouderaDirector 2.8 and after a sucesfull deployment the Director cannot connect to the CM. 

The error messages in the logs are:

 

2018-07-24 10:39:24.664 +0200] INFO  [task-thread-8] - - - - - c.c.launchpad.task.RefreshClusters: Refreshing Cluster models
[2018-07-24 10:39:24.860 +0200] INFO  [task-thread-8] - - - - - c.c.launchpad.task.RefreshClusters: Refreshing Cluster CDHRUN2 Environment:CDHRUN2 Deployment:CDHRUN2.
[2018-07-24 10:39:24.997 +0200] ERROR [task-thread-8] - - - - - c.c.l.b.c.util.ClusterRefresher: Exception while trying to fetch cluster details.
[2018-07-24 10:39:25.093 +0200] INFO  [task-thread-8] - - - - - c.c.director.aws.ec2.EC2Provider: Found EC2 key name aws_cloudera_test for fingerprint
[2018-07-24 10:39:25.315 +0200] WARN  [task-thread-8] - - - - - c.c.l.p.c.PluggableComputeProvider: Missing endpoint address string for publicIpAddress on instance 74ff1afd-9599-4be2-87dd-ba9dd75eced8
[2018-07-24 10:39:25.315 +0200] WARN  [task-thread-8] - - - - - c.c.l.p.c.PluggableComputeProvider: Missing endpoint address string for publicDnsName on instance 74ff1afd-9599-4be2-87dd-ba9dd75eced8
[2018-07-24 10:39:25.423 +0200] INFO  [task-thread-8] - - - - - c.c.director.aws.ec2.EC2Provider: Found EC2 key name aws_cloudera_test for fingerprint
[2018-07-24 10:39:25.758 +0200] WARN  [task-thread-8] - - - - - c.c.l.p.c.PluggableComputeProvider: Missing endpoint address string for publicIpAddress on instance 37e0ebee-e023-45b1-b698-c9a3341cdb72
[2018-07-24 10:39:25.758 +0200] WARN  [task-thread-8] - - - - - c.c.l.p.c.PluggableComputeProvider: Missing endpoint address string for publicDnsName on instance 37e0ebee-e023-45b1-b698-c9a3341cdb72
[2018-07-24 10:39:25.758 +0200] WARN  [task-thread-8] - - - - - c.c.l.p.c.PluggableComputeProvider: Missing endpoint address string for publicIpAddress on instance 68893a60-a82c-462b-abf1-cc220b2248e6
[2018-07-24 10:39:25.758 +0200] WARN  [task-thread-8] - - - - - c.c.l.p.c.PluggableComputeProvider: Missing endpoint address string for publicDnsName on instance 68893a60-a82c-462b-abf1-cc220b2248e6
[2018-07-24 10:39:25.759 +0200] WARN  [task-thread-8] - - - - - c.c.l.p.c.PluggableComputeProvider: Missing endpoint address string for publicIpAddress on instance 6099cff4-3182-495f-8d08-d187c4a593e1
[2018-07-24 10:39:25.759 +0200] WARN  [task-thread-8] - - - - - c.c.l.p.c.PluggableComputeProvider: Missing endpoint address string for publicDnsName on instance 6099cff4-3182-495f-8d08-d187c4a593e1
[2018-07-24 10:39:25.807 +0200] INFO  [task-thread-8] - - - - - c.c.director.aws.ec2.EC2Provider: Found EC2 key name aws_cloudera_test for fingerprint
[2018-07-24 10:39:25.989 +0200] WARN  [task-thread-8] - - - - - c.c.l.p.c.PluggableComputeProvider: Missing endpoint address string for publicIpAddress on instance 9f8acdd7-46ef-4c89-870f-a2753d2107bc
[2018-07-24 10:39:25.989 +0200] WARN  [task-thread-8] - - - - - c.c.l.p.c.PluggableComputeProvider: Missing endpoint address string for publicDnsName on instance 9f8acdd7-46ef-4c89-870f-a2753d2107bc
[2018-07-24 10:39:26.036 +0200] INFO  [task-thread-8] - - - - - c.c.director.aws.ec2.EC2Provider: Found EC2 key name aws_cloudera_test for fingerprint
[2018-07-24 10:39:26.213 +0200] WARN  [task-thread-8] - - - - - c.c.l.p.c.PluggableComputeProvider: Missing endpoint address string for publicIpAddress on instance 35fb2e27-083d-4784-b2ff-cad1b03973ee
[2018-07-24 10:39:26.213 +0200] WARN  [task-thread-8] - - - - - c.c.l.p.c.PluggableComputeProvider: Missing endpoint address string for publicDnsName on instance 35fb2e27-083d-4784-b2ff-cad1b03973ee
[2018-07-24 10:39:26.425 +0200] WARN  [task-thread-8] - - - - - c.c.launchpad.task.RefreshClusters: Failed to refresh all Clusters. Clusters with error = [CDHRUN2 Environment:CDHRUN2 Deployment:CDHRUN2]
[2018-07-24 10:39:33.197 +0200] INFO  [task-thread-3] - - - - - c.c.l.task.RefreshDeployments: Refreshing pre-existing Deployments
[2018-07-24 10:39:33.228 +0200] INFO  [task-thread-3] - - - - - c.c.l.task.RefreshDeployments: Refreshing deployment CDHRUN2 Environment:CDHRUN2 Deployment.
[2018-07-24 10:39:33.299 +0200] INFO  [task-thread-3] - - - - - c.c.director.aws.ec2.EC2Provider: Found EC2 key name aws_cloudera_test for fingerprint
[2018-07-24 10:39:33.483 +0200] WARN  [task-thread-3] - - - - - c.c.l.p.c.PluggableComputeProvider: Missing endpoint address string for publicIpAddress on instance d54dd53f-9d4d-4071-9137-f8251148e367
[2018-07-24 10:39:33.484 +0200] WARN  [task-thread-3] - - - - - c.c.l.p.c.PluggableComputeProvider: Missing endpoint address string for publicDnsName on instance d54dd53f-9d4d-4071-9137-f8251148e367
[2018-07-24 10:39:33.617 +0200] ERROR [task-thread-3] - - - - - c.c.l.b.d.util.DeploymentRefresher: Exception while trying to populate CM versi

The ec2 instances are deployed in private subnet, so it is expected they dont have a publicIpAddress and publicDnsName.

Is there a way how to fix it?

Thanks

Cloudera Employee
Posts: 62
Registered: ‎10-28-2014

Re: Missing endpoint address string for publicIpAddress on instance

You can safely ignore the "missing endpoint address string" warning.

 

Do you have a stack trace or additional error message about the failure to reach Cloudera Manager? Cloudera Director must have SSH access to the CM instance and each of the cluster instances. You can achieve this by running Cloudera Director in the same subnet as the instances, by configuring some sort of VPN, or by configuring the instances to have public IP addresses.

 

Master
Posts: 305
Registered: ‎07-01-2015

Re: Missing endpoint address string for publicIpAddress on instance

Hi, in the meantime realized that the problem is in the changed password for admin in CM. Is it possible to change it on the Director side? 

Thanks

Cloudera Employee
Posts: 62
Registered: ‎10-28-2014

Re: Missing endpoint address string for publicIpAddress on instance

The Cloudera Manager password can be updated in Cloudera Director in a variety of ways, which are not currently well-documented in the Cloudera Director User Guide.

 

If you are using the Cloudera Director UI, you can use the "Update Cloudera Manager Credentials" option in the dropdown on the deployment page.

A deployment update (PUT) through the API (using the API console or Java/Python SDKs) can also do it, since username and password are among the legal template fields to change.

 

Announcements