There is an existing persistent volume called orange-pv-cka13-trb. A persistent volume claim called orange-pvc-cka13-trb is created to claim storage from orange-pv-cka13-trb.However, this PVC is stuck in a Pending state. As of now, there is no data in the volume.Troubleshoot and fix this issue, making sure that orange-pvc-cka13-trb PVC is in Bound state.|
Troubleshooting:
There was a mismatch of request in pv(100mi) and pvc(150mi). I updated pvc to 150mi and pvc was in bound state also.|
But still my answer is wrong. Why?|
We need additional information to debug the issue. Please provide us the link to the Mock exam and also check the solution provided at the end of the mock.
I checked the answer but still have doubt because they made changes in PVC(changed value from 150MI to 100MI) and i made changes in PV (changed value from 100MI to 150MI).
I also faced this every time with this question. For change requested volume i recreated PVC with asked Mi volume then I create it. It correctly created and shown in bound state. I change nothing else this problem is might be from result evaluation.
I am also receiving an unexpected failure for this question. I captured the pvc yaml in a file, edited the storage request from 150Mi to 100Mi, deleted the pvc and recreated it. The status changes to bound to the expected PV. So far I’ve encountered this question, with an unexpected failure, in Mock Exams 3 and 4.
Hi Alistair, this is one the questions where it’s not clear if we have to change PV or PVC.
If we change the PVC to 100Mi the question is marked as correct.
If we change PV to 150Mi which also fixes the issue the question is marked as incorrect.
There’s another one involving crashed pods where it’s the other way around. Changing the PV the question is marked as correct, changing PVC to fix the issue gets an incorrect answer
It seems that there are some glitches in the Mock Exam sandboxes.
I got this issue with PVC too, even if I did everything right - resized and recreated pvc, without touching pv.
In the same time I also get reported that another question was not correct (which was also not true). However after couple re-checks of exam results, finally all questions got green.