-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Unable to restart service docker: Job for docker.service failed because the control process exited with error code. #14161
Comments
|
The last job that was successful was docker-1.12.6-16, the first job that failed was 1.12.6-19. So I suspect this is https://bugzilla.redhat.com/show_bug.cgi?id=1447536 and the fix is to ensure we use docker-1.12.6-25 or newer. |
|
I see -- let me see what we can do immediately. |
I've removed the readiness specification from the newest AMI, so we should be back to |
It's been green since @stevekuznetsov reverted to older docker in the image. Closing. |
I've re-enabled new AMI jobs for the base stage -- we have |
why not docker-1.12.6-28.git1398f24.el7
<https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=558060> as
that's what's shipping to rhel7 any moment now?
…On Wed, May 24, 2017 at 6:17 PM, Steve Kuznetsov ***@***.***> wrote:
I've re-enabled new AMI jobs for the base stage -- we have
docker-1.12.6-25.git62520c0.el7 now available in our tested repo.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#14161 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAC8IXoI4tr5Tvm4V_CzvfexL9Vt3qqxks5r9KxhgaJpZM4NZQ1j>
.
|
@sdodson I am just using the same pipeline as before -- looking at the RHEL7 Next mirrors we have and triggering off of new Brew builds -- I run tests on whatever latest package I see available. |
Seen in https://ci.openshift.redhat.com/jenkins/job/test_pull_request_origin/1387/
Reaching out to docker service logs gave me this:
The text was updated successfully, but these errors were encountered: