Bug 1491589
Summary: | Image Size Limit does not work | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | zhou ying <yinzhou> |
Component: | ImageStreams | Assignee: | Oleg Bulatov <obulatov> |
Status: | CLOSED ERRATA | QA Contact: | Dongbo Yan <dyan> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.7.0 | CC: | aos-bugs, bparees, decarr, jokerman, mmccomas, xtian |
Target Milestone: | --- | Keywords: | Regression |
Target Release: | 3.7.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Cause: the size of an image is not available on the api side
Consequence: the size is zero for schema 1 manifests
Fix: send the image size from the registry side
Result: bug fixed
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2017-11-28 22:10:58 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
zhou ying
2017-09-14 08:43:38 UTC
PR with a fix: https://github.com/openshift/origin/pull/16325 PR has merged. Moving to modified. The previous PR is insufficient: here's a follow-up on review: https://github.com/openshift/origin/pull/16776 Oleg, Looks like you are working on this here now: https://github.com/openshift/origin/pull/16885 let me know if that's incorrect. Confirmed with the latest OCP, the issue has fixed: openshift version openshift v3.7.0-0.179.0 kubernetes v1.7.6+a08f5eeb62 etcd 3.2.8 When try to push image larger than the limits, will met error: level=error msg="denied creating ImageStreamMapping: imagestreammappings.image.openshift.io \"singlelayer\" is forbidden: requested usage of storage exceeds the maximum limit per openshift.io/Image (159303155 > 65Mi)" Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2017:3188 |