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.

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

AWS: error from salt minion logs #19386

Closed
justinsb opened this issue Jan 8, 2016 · 0 comments
Closed

AWS: error from salt minion logs #19386

justinsb opened this issue Jan 8, 2016 · 0 comments
Labels
sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle.

Comments

@justinsb
Copy link
Member

justinsb commented Jan 8, 2016

Not sure if this is causing a problem, but it looks like the version test for salt can't find salt:

> less /var/log/salt/minion

2016-01-08 00:10:59,028 [salt.loaded.int.module.cmdmod][ERROR   ] Command 'salt --version | grep -c Helium' failed with return code: 1
2016-01-08 00:10:59,028 [salt.loaded.int.module.cmdmod][ERROR   ] output: /bin/sh: 1: salt: not found
0
...

cc @brendandburns in case you're still having trouble with AWS e2e

@bgrant0607-nocc bgrant0607-nocc added sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. team/control-plane labels Jan 11, 2016
justinsb added a commit to justinsb/kubernetes that referenced this issue Jan 17, 2016
We've had a lot of salt problems with systemd on AWS; we have a
workaround in place that we use everywhere else, we should use that for
kube-node-unpacker too.

Fixes kubernetes#19386
Issue kubernetes#19388
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle.
Projects
None yet
Development

No branches or pull requests

2 participants