# Node does not exist

**URL:** <https://forums.suse.com/t/node-does-not-exist/20666>\
**Category:** SUSE Storage\
**Created:** [July 6, 2021, 11:05pm UTC](https://forums.suse.com/t/node-does-not-exist/20666 "2021-07-06T23:05:23Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![CrankyCoder](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/crankycoder/32/6134_2.png) [@CrankyCoder](https://forums.suse.com/u/CrankyCoder)\
**Post date:** [July 6, 2021, 11:05pm UTC](https://forums.suse.com/t/node-does-not-exist/20666/1 "2021-07-06T23:05:23Z")

</div>

Created a new pvc today. first one since upgrading to 1.1.1. Not sure if it’s related (would lean more to NOT being related but figured i would mention it.)

```auto
Warning FailedAttachVolume <invalid> (x11 over 6m) attachdetach-controller AttachVolume.Attach failed for volume "pvc-22cf1f37-f0f2-4203-9918-904816a80841" : rpc error: code = NotFound desc = ControllerPublishVolume: the node kube-1 does not exist

```

I have tried deleting the pod and tried to get it to run somewhere else. Same thing for kube-2 and kube-5.

The longhorn UI shows all the nodes even the ones it says are not found.

 ![image](https://us1.discourse-cdn.com/flex022/uploads/suse/original/2X/f/f3302cea11c0311728e49b1a421f9be702827b3a.png)

Has anyone seen this?

---

<div class="post-metadata">

**Author:** ![c3y1huang](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/c3y1huang/32/7281_2.png) [@c3y1huang](https://forums.suse.com/u/c3y1huang)\
**Post date:** [July 7, 2021, 2:00am UTC](https://forums.suse.com/t/node-does-not-exist/20666/2 "2021-07-07T02:00:03Z")

</div>

Hmm the error doesn’t look familiar. It could just be temporarily blocked. If you can provide us your support bundle then we can have a better idea of what is happening.

You can attach the support bundle here or send it to [longhorn-support-bundle@Suse.com](mailto:longhorn-support-bundle@Suse.com) with the issue number - 20666.

---

<div class="post-metadata">

**Author:** ![CrankyCoder](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/crankycoder/32/6134_2.png) [@CrankyCoder](https://forums.suse.com/u/CrankyCoder)\
**Post date:** [July 7, 2021, 3:06pm UTC](https://forums.suse.com/t/node-does-not-exist/20666/3 "2021-07-07T15:06:39Z")

</div>

I have sent over support bundle. I saw this happen with a couple nodes. So not sure if I have something SERIOUSLY wrong in the underlying cluster or what. Seems to only be happening with this new storage request. All my existing ones seems to be fine.

---

<div class="post-metadata">

**Author:** ![c3y1huang](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/c3y1huang/32/7281_2.png) [@c3y1huang](https://forums.suse.com/u/c3y1huang)\
**Post date:** [July 8, 2021, 10:38am UTC](https://forums.suse.com/t/node-does-not-exist/20666/4 "2021-07-08T10:38:22Z")

</div>

Thank you @CrankyCoder , we’ve received it. Can you also help to create a [bug report](https://github.com/longhorn/longhorn/issues/new?assignees=&labels=kind%2Fbug&template=bug_report.md&title=%5BBUG%5D) with the `reproducing steps` and `environment info`?

---

<div class="post-metadata">

**Author:** ![CrankyCoder](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/crankycoder/32/6134_2.png) [@CrankyCoder](https://forums.suse.com/u/CrankyCoder)\
**Post date:** [July 8, 2021, 12:44pm UTC](https://forums.suse.com/t/node-does-not-exist/20666/5 "2021-07-08T12:44:44Z")

</div>

I can, but I don’t know how it manifested to begin with. So I am unsure if it’s a bug or something wrong with my cluster or what.

---

<div class="post-metadata">

**Author:** ![c3y1huang](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/c3y1huang/32/7281_2.png) [@c3y1huang](https://forums.suse.com/u/c3y1huang)\
**Post date:** [July 9, 2021, 1:26am UTC](https://forums.suse.com/t/node-does-not-exist/20666/6 "2021-07-09T01:26:05Z")

</div>

Is it reproducible on a new cluster? Are you able to add a new node and a volume to attach to the new node to see if it’s schedulable?

We also saw quite of logs coming from the metrics server. Are you able to disable it and see if that makes a difference?

```auto
2021-07-07T15:02:08.240143213Z time="2021-07-07T15:02:08Z" level=warning msg="error during scrape" collector=node error="the server could not find the requested resource (get nodes.metrics.k8s.io)" node=kube-1

```

---

<div class="post-metadata">

**Author:** ![CrankyCoder](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/crankycoder/32/6134_2.png) [@CrankyCoder](https://forums.suse.com/u/CrankyCoder)\
**Post date:** [July 12, 2021, 6:16pm UTC](https://forums.suse.com/t/node-does-not-exist/20666/7 "2021-07-12T18:16:10Z")

</div>

I am building a new cluster starting today. Longhorn will be the first “workload” to go into it as soon as it’s online.

---

<div class="post-metadata">

**Author:** ![BBBeggar](https://avatars.discourse-cdn.com/v4/letter/b/f6c823/32.png) [@BBBeggar](https://forums.suse.com/u/BBBeggar)\
**Post date:** [February 3, 2023, 8:05am UTC](https://forums.suse.com/t/node-does-not-exist/20666/8 "2023-02-03T08:05:03Z")

</div>

Hello there!  
I encountered the same issue that had been solved by redeploying a bit later. So I cannot provide more information on the topic but just wanted to check if you were able to solve this on your side as well eventually ?  
Cheers

---

<div class="post-metadata">

**Author:** ![weizhe0422](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/weizhe0422/32/9516_2.png) [@weizhe0422](https://forums.suse.com/u/weizhe0422)\
**Post date:** [February 21, 2023, 5:31pm UTC](https://forums.suse.com/t/node-does-not-exist/20666/9 "2023-02-21T17:31:53Z")

</div>

> [@BBBeggar](#):
>
> ed the same issue that had been solved by redeploying a bit later. So I cannot provide more information on the topic but just wanted to check if you were able to solve this on your side as well eventually

What version of Longhorn are you using?

The `ControllerPublishVolume` means sends the actual attach request to the longhorn api.

Could you run `kubectl get csinodes` to see if the target node is in the list?

---

<div class="post-metadata">

**Author:** ![allenf](https://avatars.discourse-cdn.com/v4/letter/a/47e85d/32.png) [@allenf](https://forums.suse.com/u/allenf)\
**Post date:** [December 13, 2023, 10:04pm UTC](https://forums.suse.com/t/node-does-not-exist/20666/10 "2023-12-13T22:04:41Z")

</div>

Im having the same issues  
 ![image](https://us1.discourse-cdn.com/flex022/uploads/suse/original/2X/c/cbd0c832a6bc73c687b02eae7452c34eb30034e5.png)

I Created a new bug here [[BUG] LongHorn is not detecting any nodes after 16 · Issue #7329 · longhorn/longhorn · GitHub](https://github.com/longhorn/longhorn/issues/7329)

i can not afford to recreate a new cluster as most of my pods in this are Production… But i really need answers as i can not complete the setup

---

<div class="post-metadata">

**Author:** ![PhanLe0110](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/phanle0110/32/7022_2.png) [@PhanLe0110](https://forums.suse.com/u/PhanLe0110)\
**Post date:** [December 19, 2023, 3:34am UTC](https://forums.suse.com/t/node-does-not-exist/20666/11 "2023-12-19T03:34:04Z")

</div>

we are follow up your report in the github ticket
