Kodekloud Challenge #1 issue with creating the pod - issue with command

Hi,
After 4 times trying to finish this challenge and always failing on the above bug, I found out that the pvc binding is always failing for me (even if it is shown green) when the storageClassName is not set to local-storage.

This information is missing above and on the GitHub repository.

1 Like

Hello @Sebastian-Fischer,
Thanks for highlighting this to us
I will forward your request to the KK team.

I ran into the same issue today. I tried to delete the pvc and pod and use the solution files from GitHub but then the pv got deleted. Frustrating. Thank you for looking into this, these challenges are great to practise on!

Hi @boy1,

Just testing the lab and it works fine. Can you please try again and follow the instructions step by step?

Bonjour @mmkmou !

Merci for testing.
I tried the lab twice more (once I accidentally got the pvc incorrect and couldn’t delete the pv so got stuck again). The third time was the charm because by then I could do it flawlessly. It seems to work unless you have to try multiple times because, you know, you’re still learning…
Maybe it happens when you delete and recreate the pod and run the command twice?
Anyway, for others trying this out, it’s probably best to stop trying and just reset the environment once you mess up the pvc or you see that ruby error.

Cheers,
Boy

Hi @boy
As the PV is already claimed you have two options :

Regard

Hello! It would be great to “understand” the problem.

I think the real problem is that the /site directory needs to be cleaned, so the solution will be:
1- Delete the full directory on the k8s node with rm -rf /site
2- Delete the pod, pvc and pv
3- Create pv, pvc and pod

2 Likes

This is so damn frustrating.

I have the same issue, with the above yaml

Hi @hpeters,

How did you configure your PVC?

Same issue here as described by OP.

First see if the pv and pvc are properly up and bounded.
I observed even though the command: [ "jekyll", "new", "/site" ] is fine, the check won’t pass until the command is executed.

I had the same issue as above. I waited a good 20 minutes and the pod never finished. As recommended, I reset the lab and tried the git source and it worked! But my yaml’s were the same as the git ones. I am wondering if the issue is caused if you create a pod with something incorrect, then delete the pod, fix the problem and create the pod again. That is the only thing different in me doing it myself and when I did it with the git source after resetting the lab. Just a suggestion for kk to look into to see why so many people are getting this issue, even after waiting 2 minutes for the pod to start up.

@jdomm95 ,

There is NO issue with the lab.

Occasionally this pod does fail to come up. Nobody has determined exactly why yet. Normally reset the lab and try again (copy the manifest you created to a notepad first to save time)

@Alistair_KodeKloud ,

The Pod does take sometime to come up, but NEVER failed to come up in my test run of 30 times of doing the challenge.

All test run have Pod in Ready state within 30s of kubectl -n development wait --for=condition=Ready pod/jekyll, except Test run #29.

I will attribute the issues reported in this thread/post above of the case of,

  1. Incorrect PVC
  2. Incorrect namespace
  3. and any other human errors (which no body acknowledge they had because they are always right)

Rather then attributing to Ghost in the Shell.

A curious case of Occam's Razor?






























I see you’re running my automation script. TBF I haven’t seen it fail with that either.

No, I am not using your automation script. I ran my own script.

At least that verifies the process from two angles.

Hi!
This problem still exists: