You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
it was a while since I didn't not update g10k, then I jumped from version 0.6.1 to verions 0.8.1 (and then 0.8.2, without solving the issue) and g10k started throwing the following error:
unTar(): error while creating symlink modules/hieradata/hostgroups/kube-control.yaml pointing to kube-master.yaml Error: symlink kube-master.yaml modules/hieradata/hostgroups/kube-control.yaml: file exists
It throws the error, always on this same file: kube-control.yaml, and on both puppet servers (I have two puppet servers).
To clean the error I had to delete all the file and run g10k again.
To solve the problem I had to roll-back to a working version (for me it's 0.6.1)
Now, I am trying a git diff between tags, to ensure that you're not doing anything around the word "control"
The text was updated successfully, but these errors were encountered:
I can't imagine what it can be wrong with the name, but perhaps you can create a file called kube-master.yaml, and a symlink called kube-control.yaml pointing to kube-master.yaml.
hello @xorpaul
it was a while since I didn't not update
g10k
, then I jumped from version 0.6.1 to verions 0.8.1 (and then 0.8.2, without solving the issue) and g10k started throwing the following error:It throws the error, always on this same file:
kube-control.yaml
, and on both puppet servers (I have two puppet servers).To clean the error I had to delete all the file and run g10k again.
To solve the problem I had to roll-back to a working version (for me it's 0.6.1)
Now, I am trying a git diff between tags, to ensure that you're not doing anything around the word "control"
The text was updated successfully, but these errors were encountered: