Common lab errors and how to fix them

Fixes for the errors members hit most: wrong folder, clone conflicts, and the Lab 4.3 OIDC error.

"No such file or directory" when running a script

You are in the wrong folder. Lab scripts use paths relative to where they live. Run pwd to see where you are, cd into the folder the guide names, then run the script again. When a step says "from the repo root", that means the top of your cgep-labs repo.

"destination path already exists" on git clone

You already cloned that repo. Either cd into the existing folder and run git pull, or clone into a new folder name. Do not clone a repo inside another repo.

Lab 4.3: "Not authorized to perform sts:AssumeRoleWithWebIdentity"

GitHub changed the format of the OIDC token for repositories created after July 15, 2026, so older trust policies stopped matching. The Lab 4.3 guide was updated on September 26, 2026 with a trust policy that accepts both formats.

  1. Re-open the Lab 4.3 guide from the Labs page.
  2. Replace the role's trust policy with the one in the guide.
  3. Apply, then re-run the GitHub Actions workflow.

Something else is failing

Post in #studygroup_cge_certs with the lab number, the exact command you ran, and the full error text (a screenshot of the terminal works). Include your OS, and on Windows say whether you are in Git Bash.

Last updated 2026-10-18

More in Courses and labs

Still stuck?

Email hello@grcengclub.com with the email address you use for the Academy and a screenshot of what you see. For lab and study questions, the #studygroup_cge_certs channel in the Club Slack is the fastest place to get an answer.