Improve `openshift_transport.go` error messages about image HOT 7 CLOSED

This can be closed: #186

from image.

I don’t think so; we use errors.Errorf, which gives us a stack trace, but the original error values are not attached (these lines have been updated to use errors.Errorf, but not errors.Wrap)

from image.

… oops, there is no “original error” in these cases. So, yes, the stack trace is in principle sufficient to tell what is going on—for the developers. A readable error message would still be an improvement.

from image.

I'm ok adding more context to the error (it was my fault at writing those subtle errors). I'll fix this tomorrow.

from image.

@runcom I can handle it, fixing it up now

from image.

Cool, thanks Grant!

from image.

This was fixed back in January by #209.

from image.