<p>I spun up an Openshift 4.6 cluster on AWS, 3 masters, 2 Workers for learning/play. Since it was just for learning, I shut down all nodes at once using the AWS Web Console. When I brought them back up a few days later, the console will not spin up.</p>
<p>So I  followed this doc on <a href="https://docs.openshift.com/container-platform/4.5/backup_and_restore/graceful-cluster-restart.html#graceful-restart-cluster" rel="nofollow noreferrer">restarting the cluster</a>. Didn't work, so I started looking at how the pods were doing for the console itself. I ran <code>oc get pods -n openshift-console -o wide -w</code> and got:</p>
<pre><code>NAME                       READY   STATUS                     RESTARTS   AGE    IP            NODE                                         NOMINATED NODE   READINESS GATES
console-59f557f67d-ks5kq   0/1     Pending                    0          13m    &lt;none&gt;        &lt;none&gt;                                       &lt;none&gt;           &lt;none&gt;
console-59f557f67d-q6zrc   0/1     UnexpectedAdmissionError   0          4d6h   &lt;none&gt;        ip-10-0-139-41.us-west-2.compute.internal    &lt;none&gt;           &lt;none&gt;
console-59f557f67d-w4q7l   0/1     UnexpectedAdmissionError   0          56m    &lt;none&gt;        ip-10-0-131-234.us-west-2.compute.internal   &lt;none&gt;           &lt;none&gt;
console-59f557f67d-zvxzn   0/1     UnexpectedAdmissionError   0          59m    &lt;none&gt;        ip-10-0-131-234.us-west-2.compute.internal   &lt;none&gt;           &lt;none&gt;
downloads-55f4ff79-lqdj7   1/1     Running                    0          59m    10.131.0.4    ip-10-0-208-19.us-west-2.compute.internal    &lt;none&gt;           &lt;none&gt;
downloads-55f4ff79-mrfzn   1/1     Running                    0          59m    10.131.0.13   ip-10-0-208-19.us-west-2.compute.internal    &lt;none&gt;           &lt;none&gt;
</code></pre>
<p>So seeing that there were a few messed up pods, I wanted to look at their logs, but I don't know how to target just a specific pod by the <code>NAME</code> column above. I tried each of these:
<code>oc get pods/console-59f557f67d-q6zrc</code>
<code>oc get podtemplates/console-59f557f67d-q6zrc</code></p>
<p>I consistently get <code>Error from server (NotFound): pods &quot;console-59f557f67d-q6zrc&quot; not found</code>.</p>
<p>I then found the command <code>oc get pods -n openshift-console -o name</code> which reveals:</p>
<pre><code>pod/console-59f557f67d-ks5kq
pod/console-59f557f67d-q6zrc
pod/console-59f557f67d-w4q7l
pod/console-59f557f67d-zvxzn
pod/downloads-55f4ff79-lqdj7
pod/downloads-55f4ff79-mrfzn
</code></pre>
<p>So I was right, it's a &quot;pod&quot;, but then if I try to run anything like <code>oc logs &lt;name&gt;</code> it returns the same error that it can't be found. Is this a bug? Does Openshift think there are Pods around that no longer exist and is routing to those Pods despite not existing?</p>
<p>If not, what resource type is the thing under the <code>NAME</code> column? How do I target it with say an <code>oc logs</code> or <code>oc delete</code> command?</p>

Aaron Chamberlain
<p>I discovered the correct syntax in this <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1753040" rel="nofollow noreferrer">Redhat Bugzilla Issue</a>.</p>
<p>The correct syntax is to place the name as another argument after the namespace declaration.</p>
<p>Examples:</p>
<p><code>oc describe pod -n openshift-console console-59f557f67d-zvxzn</code></p>
<p><code>oc logs pod -n openshift-console console-59f557f67d-zvxzn</code></p>
<p><code>oc delete pod -n openshift-console console-59f557f67d-zvxzn</code></p>
<p>I'll follow up and update when I find this reference in the official docs or command line help.</p>
