<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Re: &amp;quot;No deployment found matching the config file.&amp;quot; when updating cluster in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/quot-No-deployment-found-matching-the-config-file-quot-when/m-p/45704#M42099</link>
    <description>&lt;P&gt;The &lt;EM&gt;status&lt;/EM&gt; command is meant for clusters that were bootstrapped locally with the client (standalone mode) and won't work for clusters that were bootstrapped on a remote server.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You can refer to&amp;nbsp;&lt;A href="https://www.cloudera.com/documentation/director/latest/topics/director_cli_commands.html" target="_blank"&gt;https://www.cloudera.com/documentation/director/latest/topics/director_cli_commands.html&lt;/A&gt; for additional information on which commands are meant for remote and which are meant for local.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The documentation here may also give a better understanding of the difference between bootstrapping with just the client vs bootstrapping against a server:&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.cloudera.com/documentation/director/latest/topics/director_client_and_server.html" target="_blank"&gt;https://www.cloudera.com/documentation/director/latest/topics/director_client_and_server.html&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 28 Sep 2016 19:45:55 GMT</pubDate>
    <dc:creator>aarman</dc:creator>
    <dc:date>2016-09-28T19:45:55Z</dc:date>
    <item>
      <title>"No deployment found matching the config file." when updating cluster</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/quot-No-deployment-found-matching-the-config-file-quot-when/m-p/45688#M42098</link>
      <description>&lt;P&gt;I created a cluster using bootstrap-remote and Directory auto generated the environment/deployment names. I've added the names myself into the configuration&lt;/P&gt;&lt;PRE&gt;environmentName: drona Environment
deploymentName: drona Deployment
name: drona&lt;/PRE&gt;&lt;P&gt;But I'm still getting the error: "No deployment found matching the config file." when I run:&lt;/P&gt;&lt;PRE&gt;cloudera-director status cluster.conf  --lp.remote.username=admin --lp.remote.password=x&lt;/PRE&gt;&lt;P&gt;The deployment and environment names are correct, I get a good response in the api console for the environments command that tells me the environment exists:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;http://10.12.16.212:7189/api/v5/environments/drona%20Environment/deployments/drona%20Deployment

{
  "name": "drona Deployment",
  "hostname": "10.12.16.62",
  "port": 7180,
  "username": "admin",
  "password": "REDACTED",
  "managerInstance": {
 ...&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What am I doing wrong here?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Tony&lt;/P&gt;</description>
      <pubDate>Wed, 28 Sep 2016 14:10:55 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/quot-No-deployment-found-matching-the-config-file-quot-when/m-p/45688#M42098</guid>
      <dc:creator>afoerster</dc:creator>
      <dc:date>2016-09-28T14:10:55Z</dc:date>
    </item>
    <item>
      <title>Re: "No deployment found matching the config file." when updating cluster</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/quot-No-deployment-found-matching-the-config-file-quot-when/m-p/45704#M42099</link>
      <description>&lt;P&gt;The &lt;EM&gt;status&lt;/EM&gt; command is meant for clusters that were bootstrapped locally with the client (standalone mode) and won't work for clusters that were bootstrapped on a remote server.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You can refer to&amp;nbsp;&lt;A href="https://www.cloudera.com/documentation/director/latest/topics/director_cli_commands.html" target="_blank"&gt;https://www.cloudera.com/documentation/director/latest/topics/director_cli_commands.html&lt;/A&gt; for additional information on which commands are meant for remote and which are meant for local.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The documentation here may also give a better understanding of the difference between bootstrapping with just the client vs bootstrapping against a server:&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.cloudera.com/documentation/director/latest/topics/director_client_and_server.html" target="_blank"&gt;https://www.cloudera.com/documentation/director/latest/topics/director_client_and_server.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 28 Sep 2016 19:45:55 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/quot-No-deployment-found-matching-the-config-file-quot-when/m-p/45704#M42099</guid>
      <dc:creator>aarman</dc:creator>
      <dc:date>2016-09-28T19:45:55Z</dc:date>
    </item>
  </channel>
</rss>

