0/3 nodes are available: pod has unbound immediate PersistentVolumeClaims. preemption: 0/3 nodes are available: 3 No preemption victims found for incoming pod

[nishit93-hub]

Hi,

I created a new Java project using the odo init command. After initializing new components, I ran the command odo dev However it is giving me the following error

0/3 nodes are available: pod has unbound immediate PersistentVolumeClaims. preemption: 0/3 nodes are available: 3 No preemption victims found for the incoming pod.

I want to know do I need to create PersistentVolumeClaims first and define that in generated devfile.yaml

[rm3l]

Hi @nishit93-hub,

I created a new Java project using the odo init command. After initializing new components, I ran the command odo dev However it is giving me the following error

0/3 nodes are available: pod has unbound immediate PersistentVolumeClaims. preemption: 0/3 nodes are available: 3 No preemption victims found for the incoming pod.

I want to know do I need to create PersistentVolumeClaims first and define that in generated devfile.yaml

You shouldn't need to create PVCs first. There are some PVCs that odo might request to sync the project sources and, if the devfile contains a volume component, odo would automatically create the PVCs for you (depending on whether the volume component is marked as ephemeral or not). See How odo works for more details.

To help investigate, can you please share your devfile.yaml file?
Also, can you tell us what type of cluster you are connected to? If possible, can you also share the output of the following command (<component-name> is the metadata.namefield in thedevfile.yamlfile, and can also be extracted withyq '.metadata.name' devfile.yaml`)?

kubectl describe pod --selector "app.kubernetes.io/instance=<component-name>"

[rm3l]

FYI, I'll convert this issue into a discussion, since this is more of a support question (for now maybe).