---
name: openshift-ts-worker-dupe-nodes
title: After a worker node updates or reloads, why do duplicate nodes and pods appear?
description: '[Virtual Private Cloud] [Classic infrastructure]'
last-updated: 2026-04-29
---

> ## Documentation Index
> The table of contents for this documentation set is at https://cloud.ibm.com/docs/openshift?format=markdown
> The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt
> Use these files to discover more information as needed.

# After a worker node updates or reloads, why do duplicate nodes and pods appear?
{: #cs_duplicate_nodes}
{: support}

[Virtual Private Cloud]{: tag-vpc} [Classic infrastructure]{: tag-classic-inf}

When you run `oc get nodes`, you see duplicate worker nodes with the status **`NotReady`**. The worker nodes with **`NotReady`** have public IP addresses, while the worker nodes with **`Ready`** have private IP addresses.
{: tsSymptoms}

Older clusters listed worker nodes by the cluster's public IP address. Now, worker nodes are listed by the cluster's private IP address. When you reload or update a node, the IP address changes, but the reference to the public IP address remains.
{: tsCauses}

Service is not disrupted due to these duplicates, but you can remove the old worker node references from the API server.
{: tsResolve}

```sh
oc delete node <node_name1> <node_name2>
```
{: pre}