Bug 1490500
| Summary: | [free-int] Spurious registry push failure | ||
|---|---|---|---|
| Product: | OpenShift Online | Reporter: | Justin Pierce <jupierce> |
| Component: | Image Registry | Assignee: | Ben Parees <bparees> |
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Dongbo Yan <dyan> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.x | CC: | agladkov, aos-bugs, bparees, jupierce, mfojtik, xtian |
| Target Milestone: | --- | Keywords: | OnlineStarter |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-01-19 17:00:12 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Justin Pierce
2017-09-11 19:06:49 UTC
Registry logs: http://file.rdu.redhat.com/~jupierce/share/free-int-failed-docker-push.tgz [root@free-int-master-3c664 ~]# oc project default Now using project "default" on server "https://internal.api.free-int.openshift.com:443". [root@free-int-master-3c664 ~]# oc get pods NAME READY STATUS RESTARTS AGE docker-registry-21-cb9hd 1/1 Running 0 4d docker-registry-21-frppl 1/1 Running 0 4d Alexey have you had a chance to take look at the logs Justin provided? Oops. Yes, I miss them. I do not see any errors on the registry side. Does this error continue to be reproduced? I have not seen it recently, no. However, if there is not enough logging to determine the problem, can we use this BZ to add what is necessary to diagnose it next time? doesn't seem to be recurring, so low severity. I need to check what we're logging in the build logs on failed push, might be the case that we weren't even able to reach the registry (hence nothing in the registry logs) and we didn't log a useful error in the build to indicate why the push failed. We now log the error that lead to the retries/failure so if we hit this again we'll have more information:
return fmt.Errorf("After retrying %d times, %s image still failed due to error: %v", DefaultPushOrPullRetryCount, actionName, err)
Nothing else we can do with it for now, i'm going to close it and it can be reopened if further push issues are seen.
|