I opened a ticket: https://bugzilla.redhat.com/show_bug.cgi?id=1303273
On Fri, Jan 29, 2016 at 9:07 PM, Dean Peterson <[email protected]> wrote: > I also noticed, the deployments keep saying say are trying to use the > oldest image id even though there have been many subsequent successful > builds. I have attached the output. I will open a ticket too. > > On Fri, Jan 29, 2016 at 10:00 PM, Clayton Coleman <[email protected]> > wrote: > >> That error specifically is from Docker - it's probably causing the issue >> (please file the issue with requested info attached so we can correct the >> system) in the UI, but the fix will likely be on your system, and may be >> related to any changes you made in Docker storage recently. >> >> On Jan 29, 2016, at 9:22 PM, Dean Peterson <[email protected]> >> wrote: >> >> <image.png> >> I don't know if the image above can be viewed in the user's list archives >> but in it you can see three separate deployments for one service; all of >> them hung in various states. This is after I have been able to deploy >> before without any changes. The new openshift v1.1.1 just randomly starts >> giving me errors. The latest is this: Failed to pull image " >> 172.30.250.187:5000/abecorn/tradeclient@sha256:cbca9d885bf1c23bb518662cc51d61b5365ab321147a59d2be5b86869f50c08e": >> Driver devicemapper failed to create image rootfs >> 0dd71c06ef1387030a9c4c05e3cea6727405fce6eda53b5d01cb5ff442440d02: >> Unknown device e551632771dbc2fa0728e96af65300 >> 567243f2413311b76334e3abebbe836e19 >> >> _______________________________________________ >> users mailing list >> [email protected] >> http://lists.openshift.redhat.com/openshiftmm/listinfo/users >> >> >
_______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
