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

salt 2014.7 doesn't support systemd services #18201

Closed
brendandburns opened this issue Dec 4, 2015 · 5 comments
Closed

salt 2014.7 doesn't support systemd services #18201

brendandburns opened this issue Dec 4, 2015 · 5 comments
Assignees
@justinsb @zmerlynn
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. sig/node Categorizes an issue or PR as relevant to SIG Node.

Comments

@brendandburns
Copy link
Contributor

(at least as far as I can tell)

We rely on systemd on ubuntu on AWS (and possibly elsewhere) which means that these installs don't work properly (e.g. #18037)

We can either upgrade Salt on AWS, or switch back to sysv init for Ubuntu on AWS (which does appear to work)

I lean towards the second option.

@mikedanese @zmerlynn @justinsb
@mikedanese
Copy link
Member

It seems like vagrant salt and kube-up is using systemd successfully. What leads you to believe this?

@justinsb
Copy link
Member

justinsb commented Dec 4, 2015

Indeed ... I'm a little confused here. Salt's support for systemd is indeed mostly broken, but we work around it by using our own script to manage systemd services...

@zmerlynn zmerlynn added the sig/node Categorizes an issue or PR as relevant to SIG Node. label Dec 5, 2015
@roberthbailey roberthbailey mentioned this issue Dec 8, 2015
Closed
@justinsb
Copy link
Member

OK to close @brendandburns ? We've worked around the problems in salt, kube-up is in maintenance mode, nobody in their right mind would choose salt again :-)

@justinsb justinsb self-assigned this Nov 17, 2016
@fejta-bot
Copy link

Issues go stale after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 18, 2017
@zmerlynn
Copy link
Member

/close

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

@justinsb justinsb

@zmerlynn zmerlynn

Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. sig/node Categorizes an issue or PR as relevant to SIG Node.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@justinsb @mikedanese @zmerlynn @brendandburns @k8s-ci-robot @fejta-bot