This message was deleted.
# atlantis-community
s
This message was deleted.
r
I've never seen this
Does that directory exist?
s
yep…so does the workspace
r
Did you supply the workspace too?
atlantis plan -d dir -w workspace
s
Supply the workspace??
yea…its in my command above
r
Oh missed that
Did you ssh into the container and see if that dir exists?
Maybe it ran out of space?
s
plenty of space…and yes the dir is there
p
k8s?
is and external volume? permissions?
s
yea…in eks….other PRs are working ok
p
ohhh, only one PR? that is very extrange
s
My dev has a LOT of changes going on across multiple workspaces and is touching different statefiles because of it. Pretty unusual PR compared to what we normally push. Im wondering if it has something to do with that
Ill keep poking…if I find anything interesting ill report back
thx
p
maybe set atlantis to debug to see of there is any leads?
just to capture a few runs to see
👍 1
s
So it looks like im out of disk space…If I change this from 5Gi to 50Gi I get the following…`The StatefulSet "atlantis" is invalid: spec: Forbidden: updates to statefulset spec for fields other than 'replicas', 'template', 'updateStrategy', 'persistentVolumeClaimRetentionPolicy' and 'minReadySeconds' are forbidden` What am I missing here?
Copy code
volumeClaim:
  enabled: true
  ## Disk space for to check out repositories
  dataStorage: 5Gi
nm…think i figured it out but i broke something else now 🙄
Ok…all fixed. I did figure out something else though when I was fixing things. You will break existing PRs if you kill off your statefulset, pods, and pvc. 🙂 But ill come back tomorrow with my writeup of how i fixed them tomorrow in case someone else runs into the same issue. I need a beer.
👍 2
🍻 1
m
In case it helps someone in the future, I have seen this error when I do
atlantis unlock
and later come back to the PR and run
atlantis plan
against a specific project. It seems I need to run a plan on all projects after unlock….only then i can start targeting a specific project.