-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Need to add become: root to ubuntu.yml? #8
Comments
Hi there! Thanks! 😃 Regarding "become": What I normally do is setting
in ether The Ansible Hope this helps a bit. BTW: I'm currently updating the role to Longhorn 1.5.3. Should be ready the next days. I'm currently testing the changes. |
Hi, I hit two other issues that I'd thought I'd mention:
Thank you again, I realise I'm just dumping in this issue, but if you want me to work on something I will make a separate issue/pull request. I've now got everything working on my cluster and you've made it so much easier and declarative so thank you! |
I was already thinking about re-factoring the role as you suggested so that
You're right.
Of course. As long as it works reliable I'm fine with it. I also want to implement a change where one can specify the location of |
First, thank you for a wonderful ansible role, just trying out deploying it now.
Installing longhorn to a single-node remote Ubuntu 22.04 server with microk8s I had some issues. In particular I needed to modify
tasks/ubuntu.yml to add become: yes to the multipathd tasks, otherwise I have permission errors.
If I try adding become: yes to when the role is invoked, then I get other issues as my root user doesn't have a kubeconf setup.
Can you suggest the best way to handle permissions for the multipath? Is this something needed more generally?
Thank you again for all your hard work.
The text was updated successfully, but these errors were encountered: