Replies: 1 comment
-
I think I had an outdated or misconfigured playbook. I am currently trying to redo it with a newly copied version and hope it will be successfull. In case everything works I will just close this discussion and appologize for unnecessary opening it. The new playbook is executing the post folder. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Good evening everybody,
I have been trying to troubleshoot my install for a while now so I thought I'd come here to try and solve this together with you. I didn't feel comfortable opening an Issue with the things I found so far since this is pretty much my first time working with Ansible so I don't have the knowledge nor experience to state anything more than educated guesses.
I used my playbook with the -vvvv flag and used tee to write the output into a file so I could comfortably search through the >10k lines. Please excuse my likely missuse of the terminology. Not once have I found "Copy metallb CRs manifest to first master" which would be the name of one of the functions in "roles/k3s/post/tasks/metallb.yml". This leads me to believe that the "post" folder is never executed. I didn't dig for too long but I also couldn't find when it would be included from following the other files and what they were including. This theory would also be compatible with my observation that my cluster would start working and get an Ingress IP when I would manually apply a configuration to metallb.
I would delighted if somebody were to help me figure this out. Thank you very much.
Best,
Gabgobie
Beta Was this translation helpful? Give feedback.
All reactions