Oooh, awesome find! Looks like there's something up with our validation logic. Thanks for poking around, we'll look into this! ... View more

What version of CM are you using? ... View more

Oh, huh. This is unusual. Is there anything interesting in the Director logs relating to this? ... View more

Ooof. Looks like this is an issue in the Cloudera manager front. Let me ping the CM devs and they can take a look at this. ... View more

Hi dturner. Just wondering if you had had a chance to test this -- let me know! ... View more

Hi! Sorry for the delay. Director 6.2.1 was released today with this (hopefully) patched. Do you mind testing and letting me know? Thank you! ... View more

One more clarification: in the config file, are you using explicit databases keyword (https://github.com/cloudera/director-scripts/blob/master/configs/azure.reference.conf#L710), or are you using databaseTemplates (https://github.com/cloudera/director-scripts/blob/master/configs/azure.reference.conf#L746)? ... View more

Also, to clarify: we're talking about Azure Database for PostgreSQL (https://azure.microsoft.com/en-us/services/postgresql/) and Azure Database for MySQL (https://azure.microsoft.com/en-us/services/mysql/), correct? ... View more

Thank you -- clearly I'm not as familiar with Postgres. 🙂 I'll keep you informed. ... View more

I'm glad you asked, actually. MySQL seems to work as I'd expect after a fix. I'm having some difficulty replicating the issue in Postgres, though, because I can't seem to progress past a certain point. Is there anything special you have to do to your Postgres instance to get by this error?   ERROR : admin-user@host must be member of role scm_xxxxx   ... View more

For some context, Azure for MySQL requires some username munging in order to get it to work correctly. It looks like this new feature inadvertently stepped on Postgres. On our end it should (hopefully) be simple to fix, I'm just testing it out now. ... View more

You're right, these hacks shouldn't be necessary -- this looks like a bug on our side. We're working on it! ... View more

Unfortunately no, PostgreSQL RDS is not supported. Sorry about that! ... View more

This error is benign -- it won't affect the behavior of your clusters -- but I'm a little curious as to why it's happening. Did you change the admin credentials in Cloudera Manager, by chance? ... View more

Wow! I'm impressed. Thank you for the detailed instructions, and good work! I would like to reiterate that anyone who follows this advice does it at their own risk, just in case you missed jcpuskar's warning . 🙂 ... View more

Hello! Unfortunately, there's no way to do this in Director as you're suggesting. This API call is a placeholder, and doesn't support any actual updates.   Do you have the option of engaging support for this? That would be my recommended path forward.   It is possible to remove the encryption from Director's database (https://www.cloudera.com/documentation/director/2-8-x/topics/director_db_encryption.html), but any sort of DB editing is entirely unsupported. ... View more

What OS are you using for your CDH cluster? Do you have an image ID so that we could try using it ourselves? This could very well be a bug on our end.   You can skip around EnableUnlimitedStrengthJce by adding:   lp.bootstrap.unlimited-jce: false To your server's application.properties. I believe the unlimited strength JCE is bundled into Java after 8u162, so this step may be unnecessary. ... View more

In your first response, it looks as though the SSH credentials aren't correct, and Director is failing attempting to SSH into the instance. Are you sure you've provided the right username and key for this instance? In the second, it looks like Java has not been installed prior to CM being installed. Do you have the javaInstallationStrategy set to none for this config? Let me know. ... View more

Hi Jyo. This section of the log doesn't appear to have the relevant information we need. Could you look for the string BOOTSTRAP_FAILED in your log and see if you see an error above that that could be more edifying? Especailly surrounding the installation of cloudera-manager-daemons, as it seems like this is when it failed. It could be a networking issue.   Does this happen consistently when trying to bootstrap a cluster? ... View more

Could you let us know what kind of table this is? HBase, Impala, etc? Then I can get your post moved to the appropriate forum for this. ... View more

I unfortunately do not see the application log -- is the link missing?   With the cluster in UPDATE_FAILED, Director is no longer able to operate on this cluster. Do you have an earlier DB backup that you would be able to restore to?   Getting out of UPDATE_FAILED is possible, but is currently only supported as a guided process through Cloudera Director Support due to how dangerous it can be. Do you have a support contract with Cloudera at the moment?   While you can add this through CM, Director will be unable to manage this host and it may make growing/shrinking difficult once the UPDATE_FAILED problem is fixed. If you add it through CM and then recover Director, Director will be able to grow and shrink the cluster, but will be otherwise unaware of that new node, and will not be able to modify it if desired.   The extra CDH parcel could be a source of grief, but I'd like to try to get by the UPDATE_FAILED problem first. ... View more

Unfortunately no, there is no way of changing these within Director at the moment. I've filed an internal request to add this feature to Director, but there's no timeframe on that at the moment. ... View more

Sameer, could you post the whole of your Director log? At the minimum, Director shouldn't be entering into UPDATE_FAILED because of this. I'd like to know exactly what went wrong.   It looks like the message " Host must have a single version of CDH installed. " appears when CM can't determine the CDH version on the new host. What's the full version of CDH that's currently running on this cluster, including the patch version? e.g. 5.14.0.24. This should show up in the Director UI, but you should be able to find this in the parcel section on the CM instance itself.   Is this a production cluster? I see the name is "sandbox." Is it possible to create this cluster again? ... View more

The feature that John described above does not provide this functionality, and Director doesn't provide any way to make this work. It would be simple to create a new CM server (deployment) on the EU region and add the cluster to that, of course, but not to add that cluster to the US deployment. It is technically *possible* to create a cluster this way, but this would need to be accomplished outside of Director. It would require some network configuration that may be inadvisable, though I'm not an expert here and it's not something we'd be able to support of help with. ... View more

Sorry for the delay in response. We've been noticing this issue crop up for Director 2.4 lately on AWS. We recommend upgrading to Director 2.5.1, which has not been exhibiting the same problem due to the change in our instance allocation/tagging logic. ... View more

Can you give me the exact AMI IDs that you are using to try out? ... View more

Director installs Java 7 by default and has since version 1.0. Is it possible that Java is unexpectedly installed on the instance type that you're using? Director attempts to remove existing Java versions prior to installing its own version, but occasionally certain images have Java installed in ways that Director isn't anticipating. What version of Director are you using? Assuming that you're using AWS: what region and what AMI are you using to try to bootstrap the cluster? ... View more

Okay, hrm. Are you using the web UI, or a conf file to set up this cluster? If you're using a conf file, would you be able to post it on something like pastebin (being sure to redact anything sensitive like AWS secret keys, access keys, and SSH keys) and link it here? Also would you be able to give me the exact AMI ID that's being used? Are you certain you're using the same private key when trying to set up a cluster that you're using to SSH into raw instances? This error is still consistent with incorrect SSH credentials being supplied -- we just have to figure out exactly what's going on here. ... View more

It looks as though the user authentication is still the problem. Can you try provisioning an instance of the AMI you're trying to use manually and attempting to connect using the credentials you're providing to Director? i.e. Launch an instance using the EC2 console and just attempting to SSH into it. ... View more