<?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>topic Re: Viya 4 Pods does not start after restart in Administration and Deployment</title>
    <link>https://communities.sas.com/t5/Administration-and-Deployment/Viya-4-Pods-does-not-start-after-restart/m-p/862667#M26172</link>
    <description>This message is saying kubernetes is not receiving a response when trying to connect to cr.sas.com to download images. That you can connect from your bastion host proves the issue is not with cr.sas.com but with your infrastructure. I suspect the firewall configuration needs to be updated to allow these outbound connections from the nodes.</description>
    <pubDate>Tue, 07 Mar 2023 14:43:15 GMT</pubDate>
    <dc:creator>gwootton</dc:creator>
    <dc:date>2023-03-07T14:43:15Z</dc:date>
    <item>
      <title>Viya 4 Pods does not start after restart</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Viya-4-Pods-does-not-start-after-restart/m-p/862629#M26166</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We have restarted our sas viya environment, however after restart alot of pods are not running/completed.&lt;/P&gt;
&lt;P&gt;Some pods contain this type of messages:&lt;/P&gt;
&lt;P&gt;This one is from sas-crunchy-data-postgres-operator describe output&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; Normal&amp;nbsp;&amp;nbsp; Pulling&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 11m (x4 over 16m)&amp;nbsp;&amp;nbsp; kubelet&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Pulling image "cr.sas.com/viya-4-x64_oci_linux_2-docker/sas-certframe:3.25.5-20220408.1649425759549"&lt;/P&gt;
&lt;P&gt;&amp;nbsp; Warning&amp;nbsp; Failed&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 10m (x4 over 15m)&amp;nbsp;&amp;nbsp; kubelet&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Failed to pull image "cr.sas.com/viya-4-x64_oci_linux_2-docker/sas-certframe:3.25.5-20220408.1649425759549": rpc error: code = Unknown desc = pinging container registry cr.sas.com: Get "&lt;A href="https://cr.sas.com/v2/" target="_blank"&gt;https://cr.sas.com/v2/&lt;/A&gt;": dial tcp 149.173.160.155:443: i/o timeout&lt;/P&gt;
&lt;P&gt;&amp;nbsp; Warning&amp;nbsp; Failed&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 10m (x4 over 15m)&amp;nbsp;&amp;nbsp; kubelet&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Error: ErrImagePull&lt;/P&gt;
&lt;P&gt;&amp;nbsp; Warning&amp;nbsp; Failed&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;10m (x5 over 15m)&amp;nbsp;&amp;nbsp; kubelet&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Error: ImagePullBackOff&lt;/P&gt;
&lt;P&gt;&amp;nbsp; Normal&amp;nbsp;&amp;nbsp; BackOff&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 72s (x38 over 15m)&amp;nbsp; kubelet&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Back-off pulling image "cr.sas.com/viya-4-x64_oci_linux_2-docker/sas-certframe:3.25.5-20220408.1649425759549"&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I tried to telnet cr.sas.com 443 from the bastion host and seems fine.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="alko13_0-1678181144031.jpeg" style="width: 400px;"&gt;&lt;img src="https://communities.sas.com/t5/image/serverpage/image-id/81136i457CD2BC755EB8CE/image-size/medium?v=v2&amp;amp;px=400" role="button" title="alko13_0-1678181144031.jpeg" alt="alko13_0-1678181144031.jpeg" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Attaching as well the describe pods, get pods output&lt;/P&gt;
&lt;P&gt;Appreciate&amp;nbsp; any advice,&lt;/P&gt;
&lt;P&gt;Thanks!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 07 Mar 2023 09:32:20 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Viya-4-Pods-does-not-start-after-restart/m-p/862629#M26166</guid>
      <dc:creator>alko13</dc:creator>
      <dc:date>2023-03-07T09:32:20Z</dc:date>
    </item>
    <item>
      <title>Re: Viya 4 Pods does not start after restart</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Viya-4-Pods-does-not-start-after-restart/m-p/862637#M26167</link>
      <description>In cases like this it is always a good idea to contact SAS technical asap. &lt;A href="https://support.sas.com/en/technical-support/contact-sas.lang.html" target="_blank"&gt;https://support.sas.com/en/technical-support/contact-sas.lang.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Provide as much detail as you can about the environment/setup/configuration and complete zipped logfiles. They will ask for them anyway.</description>
      <pubDate>Tue, 07 Mar 2023 11:03:13 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Viya-4-Pods-does-not-start-after-restart/m-p/862637#M26167</guid>
      <dc:creator>JosvanderVelden</dc:creator>
      <dc:date>2023-03-07T11:03:13Z</dc:date>
    </item>
    <item>
      <title>Re: Viya 4 Pods does not start after restart</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Viya-4-Pods-does-not-start-after-restart/m-p/862667#M26172</link>
      <description>This message is saying kubernetes is not receiving a response when trying to connect to cr.sas.com to download images. That you can connect from your bastion host proves the issue is not with cr.sas.com but with your infrastructure. I suspect the firewall configuration needs to be updated to allow these outbound connections from the nodes.</description>
      <pubDate>Tue, 07 Mar 2023 14:43:15 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Viya-4-Pods-does-not-start-after-restart/m-p/862667#M26172</guid>
      <dc:creator>gwootton</dc:creator>
      <dc:date>2023-03-07T14:43:15Z</dc:date>
    </item>
  </channel>
</rss>

