functional: sudo command returns error on CoreOS 1053.2.0

coreos / fleet

fleet ties together systemd and etcd into a distributed init system

Apache License 2.0

2.42k stars 302 forks source link

functional: sudo command returns error on CoreOS 1053.2.0 #1591

Closed dongsupark closed 8 years ago

dongsupark commented 8 years ago

"sudo systemctl stop fleet" seems to fail on CoreOS 1053.2.0, the most recent developer version. Multiple tests like TestDynamicClusterNewMemberUnitMigration or TestShutdown fail like below:

--- FAIL: TestShutdown (1.99s)
    shutdown_test.go:43: exit status 1

But those tests never failed on CoreOS 1032.1.0. It's also interesting, that both CoreOS versions, 1032 and 1053, have systemd v229. Will investigate.

dongsupark commented 8 years ago

It turns out, every sudo command fails like above. Hence this has nothing to do with systemd, but it rather looks like a PAM issue. Digging into this a little more, I got such a message from stderr:

--- FAIL: TestShutdown (1.75s)
    shutdown_test.go:49: 
        stderr: Warning: Permanently added '172.18.1.1' (RSA) to the list of known hosts.^M
        sudo: unable to initialize PAM: No such file or directory