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

Flaky test: DockerSwarmSuite.TestSwarmRotateUnlockKey #28240

Closed
thaJeztah opened this issue Nov 10, 2016 · 1 comment · Fixed by #28251
Closed

Flaky test: DockerSwarmSuite.TestSwarmRotateUnlockKey #28240

thaJeztah opened this issue Nov 10, 2016 · 1 comment · Fixed by #28251
Assignees
Milestone

Comments

@thaJeztah
Copy link
Member

Seen failing on #28221, and #28173 (comment)

@aaronlehmann is working on this, but opening an issue to track #27967 (comment)

04:07:17 ----------------------------------------------------------------------
04:07:17 FAIL: docker_cli_swarm_test.go:952: DockerSwarmSuite.TestSwarmRotateUnlockKey
04:07:17 
04:07:17 [d7e4655c1124a] waiting for daemon to start
04:07:17 [d7e4655c1124a] daemon started
04:07:17 [d7e4655c1124a] exiting daemon
04:07:17 [d7e4655c1124a] waiting for daemon to start
04:07:17 [d7e4655c1124a] daemon started
04:07:17 [d7e4655c1124a] exiting daemon
04:07:17 [d7e4655c1124a] waiting for daemon to start
04:07:17 [d7e4655c1124a] daemon started
04:07:17 docker_cli_swarm_test.go:1020:
04:07:17     c.Assert(err, checker.IsNil, check.Commentf("out: %v", string(out)))
04:07:17 ... value *exec.ExitError = &exec.ExitError{ProcessState:(*os.ProcessState)(0xc4203db880), Stderr:[]uint8(nil)} ("exit status 1")
04:07:17 ... out: Error response from daemon: swarm could not be unlocked: invalid key provided
04:07:17 
04:07:17 
04:07:17 [d7e4655c1124a] exiting daemon
04:07:18 
@aaronlehmann
Copy link
Contributor

I think we've tracked this down to a problem in the test. It was intended to set unlockKey = newUnlockKey at the end of the loop. This is missing, and it prevents a special case from triggering after two iterations through the loop. @cyli is going to include the fix in her vendor PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants