<?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: Unable to create CML Experiment - how to debug in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/Unable-to-create-CML-Experiment-how-to-debug/m-p/374476#M241998</link>
    <description>&lt;P&gt;we're not certain the cause of it, but we kubectl cordon off the node and rebooted it. This issue happens sporadically. we are also running on 1.5 CML now&lt;/P&gt;</description>
    <pubDate>Wed, 26 Jul 2023 01:50:29 GMT</pubDate>
    <dc:creator>skipme</dc:creator>
    <dc:date>2023-07-26T01:50:29Z</dc:date>
    <item>
      <title>Unable to create CML Experiment - how to debug</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Unable-to-create-CML-Experiment-how-to-debug/m-p/364221#M239131</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I am unable to create a support case for this, as my support license does not appear to cover this ML Experiments.&lt;/P&gt;&lt;P&gt;I am evaluating Cloudera CML on my company's CDP instance. I created several Experiments on a project to test out the feature (it was a simple script generating some random numbers for metrics) and the experiment created and ran ok. However, I tried to create the same experiment later and the UI just timed out. I used the developer's tools in the browser to see the request and "runs" failed with 504 timeout error. I am unable to troubleshoot the issue further in the UI, and am uncertain if ECS would have any useful information. I could get it to run successfully a few hours later. To my knowledge, nobody touched the CDP cluster during in between this period. During the period I cannot create experiments, I looked at my kubernetes namespace &amp;lt;CML workspace name - userXX&amp;gt; inside ECS, and did not see a pod starting. There was also no events being created. We would like to better understand the product before productionizing it.&amp;nbsp;&lt;FONT color="#0000FF"&gt;Could anyone advise where I might look at to debug the issue&lt;/FONT&gt;?&amp;nbsp;Thank you.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The version we're using is CML 1.4 on CDP, in an intranet network.&lt;/P&gt;</description>
      <pubDate>Tue, 21 Apr 2026 07:43:39 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Unable-to-create-CML-Experiment-how-to-debug/m-p/364221#M239131</guid>
      <dc:creator>skipme</dc:creator>
      <dc:date>2026-04-21T07:43:39Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to create CML Experiment - how to debug</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Unable-to-create-CML-Experiment-how-to-debug/m-p/364417#M239168</link>
      <description>&lt;P&gt;Just an update: In ECS, I see that the pods are being assigned to a particular node and they're "stuck" with a message:&lt;/P&gt;&lt;P&gt;"failed to create pod sandbox: rpc error:code= unknown desc = failed to get sandbox image "index.docker.io/rancher/pause:3.6" failed to pull image "index.docker.rancherpause:3.6": failed to pull and unpack image "docker.io/rancher/pause:3.6".....&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 23 Feb 2023 06:17:40 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Unable-to-create-CML-Experiment-how-to-debug/m-p/364417#M239168</guid>
      <dc:creator>skipme</dc:creator>
      <dc:date>2023-02-23T06:17:40Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to create CML Experiment - how to debug</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Unable-to-create-CML-Experiment-how-to-debug/m-p/364491#M239182</link>
      <description>&lt;P&gt;I've raised a support case thread instead, will not be following up on this thread.&lt;/P&gt;</description>
      <pubDate>Fri, 24 Feb 2023 03:35:37 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Unable-to-create-CML-Experiment-how-to-debug/m-p/364491#M239182</guid>
      <dc:creator>skipme</dc:creator>
      <dc:date>2023-02-24T03:35:37Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to create CML Experiment - how to debug</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Unable-to-create-CML-Experiment-how-to-debug/m-p/374349#M241959</link>
      <description>&lt;P&gt;Hello,&lt;BR /&gt;I have the same issue. Have you got a solution?&lt;/P&gt;</description>
      <pubDate>Mon, 24 Jul 2023 14:09:43 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Unable-to-create-CML-Experiment-how-to-debug/m-p/374349#M241959</guid>
      <dc:creator>IvanCe</dc:creator>
      <dc:date>2023-07-24T14:09:43Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to create CML Experiment - how to debug</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Unable-to-create-CML-Experiment-how-to-debug/m-p/374476#M241998</link>
      <description>&lt;P&gt;we're not certain the cause of it, but we kubectl cordon off the node and rebooted it. This issue happens sporadically. we are also running on 1.5 CML now&lt;/P&gt;</description>
      <pubDate>Wed, 26 Jul 2023 01:50:29 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Unable-to-create-CML-Experiment-how-to-debug/m-p/374476#M241998</guid>
      <dc:creator>skipme</dc:creator>
      <dc:date>2023-07-26T01:50:29Z</dc:date>
    </item>
  </channel>
</rss>

