Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Missing become for k3s_state=restarted (possibly others) #89

Closed
Diaoul opened this issue Jan 25, 2021 · 2 comments
Closed

Missing become for k3s_state=restarted (possibly others) #89

Diaoul opened this issue Jan 25, 2021 · 2 comments
Assignees
@xanmanning
Labels
bug Something isn't working

Comments

@Diaoul
Copy link
Contributor

Diaoul commented Jan 25, 2021

Not sure if this is a bug or the expected behavior but there is no become in start/stop it seems. I would've expected one since I use k3s_become_for_all. Maybe add k3s_become_for_control for start/stop/restart?
@xanmanning xanmanning self-assigned this Jan 26, 2021
@xanmanning xanmanning added the bug Something isn't working label Jan 26, 2021
xanmanning added a commit that referenced this issue Jan 30, 2021
@xanmanning
Bugfixes
2c12436 
  - Added uninstall task to remove hard-linked files #88
  - Fixed missing become for `systemd` operations tasks. #89
  - Added `k3s_start_on_boot` to control `systemd.enabled`.
@xanmanning
Copy link
Member

Hi @Diaoul - Should now be fixed in v2.5.1 🙂

@Diaoul
Copy link
Contributor Author

Diaoul commented Jan 30, 2021 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@xanmanning xanmanning

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@xanmanning @Diaoul