Bug 1476217 - missing tag does not allow importing or patching objects
Summary: missing tag does not allow importing or patching objects
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OKD
Classification: Red Hat
Component: Image Registry
Version: 3.x
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
: ---
Assignee: Michal Minar
QA Contact: ge liu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-28 10:18 UTC by ge liu
Modified: 2017-11-06 23:08 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-11-06 23:08:05 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description ge liu 2017-07-28 10:18:56 UTC
Description of problem:
The background is: https://github.com/openshift/origin/issues/15492, file this bug to trace this issue.

How reproducible:
Always

openshift v3.6.172.0.0
kubernetes v1.6.1+5115d708d7
etcd 3.2.1

Steps to Reproduce:
1. # docker push docker-registry.default.svc:5000/yin/hello-openshift
The push refers to a repository [docker-registry.default.svc:5000/yin/hello-openshift]
b00b8efd7213: Pushed 
6e7aea341eb2: Pushed 
5f70bf18a086: Pushed 
c6f988f4874b: Pushed 
latest: digest: sha256:e32d83c8d8edd39b859879dae947d8e6a6a82b47b084561318437d2863e96e10 size: 1154
2. # oc get istag -o yaml > /tmp/x
# vim /tmp/x 
3.# oc apply -f /tmp/x 
Warning: kubectl apply should be used on resource created by either kubectl create --save-config or kubectl apply
Warning: kubectl apply should be used on resource created by either kubectl create --save-config or kubectl apply
imagestreamtag "ruby-22-centos7:latest" configured
The ImageStream "hello-openshift" is invalid: spec.tags[latest].referencePolicy.type: Invalid value: "": valid values are "Source", "Local"

Comment 1 Ben Parees 2017-11-06 23:08:05 UTC
upstream issue was closed as working as designed as discussed here:
https://github.com/openshift/origin/issues/15492#issuecomment-319630623

so closing this as well.


Note You need to log in before you can comment on or make changes to this bug.