| Summary: | Cannot get new istag after oc tag adds new tag to the same imagestream (compatibility oc v3.3/v3.4 VS openshift v3.1) | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Xingxing Xia <xxia> |
| Component: | oc | Assignee: | Fabiano Franz <ffranz> |
| Status: | CLOSED WONTFIX | QA Contact: | Xingxing Xia <xxia> |
| Severity: | low | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.3.0 | CC: | aos-bugs, ffranz, jokerman, jvallejo, mmccomas |
| Target Milestone: | --- | ||
| Target Release: | 3.7.0 | ||
| 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: | 2017-11-06 06:19:16 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: | |
Also reproduced when testing oc 3.4.0.33 against openshift 3.1.1.10 I am unable to reproduce with a recent client: ``` $ oc tag --source=docker docker.io/library/busybox:latest mystream:latest Tag mystream:latest set to docker.io/library/busybox:latest. $ oc tag --source=docker docker.io/library/busybox:latest mystream:tagTag mystream:tag set to docker.io/library/busybox:latest. ``` ``` $ oc get istag mystream:tag NAME DOCKER REF UPDATED IMAGENAME mystream:tag docker.io/library/busybox@sha256:030fcb92e1487b18c974784dcc110a93147c9fc402188370fbfd17efabffc6af 33 seconds ago sha256:030fcb92e1487b18c974784dcc110a93147c9fc402188370fbfd17efabffc6af $ oc get istag mystream:latest NAME DOCKER REF UPDATED IMAGENAME mystream:latest docker.io/library/busybox@sha256:030fcb92e1487b18c974784dcc110a93147c9fc402188370fbfd17efabffc6af About a minute ago sha256:030fcb92e1487b18c974784dcc110a93147c9fc402188370fbfd17efabffc6af ``` Since this bug was not marked as a blocker, I do not believe there are plans for backporting a fix. Tagging Fabiano for confirmation of this. ``` $ oc version oc v3.7.0-rc.0+6b1a836-59-dirty kubernetes v1.7.6+a08f5eeb62 features: Basic-Auth ``` No backport planned. (In reply to Juan Vallejo from comment #3) > I am unable to reproduce with a recent client: > $ oc version > oc v3.7.0-rc.0+6b1a836-59-dirty > kubernetes v1.7.6+a08f5eeb62 > features: Basic-Auth It is only reproduced as compatibility issue as title says "oc v3.3/v3.4 VS openshift v3.1" and not reproduced as below info shows (In reply to Xingxing Xia from comment #0) > Not reproduced when using: > oc v3.3 VS openshift v3.2 > oc v3.3. VS openshift v3.3 > oc v3.1.1.6 VS openshift v3.1.1.6 (In reply to Fabiano Franz from comment #4) > No backport planned. OK. Due to no backport plan and no PR given, and it is unworthy to launch an openshift v3.1 env to check it once again, closing this bug. Thanks! |
Description of problem: Cannot get new istag after oc tag adds new tag to the same imagestream when test compatibility using oc v3.3 VS openshift v3.1.1.6. Not reproduced when using: oc v3.3 VS openshift v3.2 oc v3.3. VS openshift v3.3 oc v3.1.1.6 VS openshift v3.1.1.6 They all get expected results like below. Version-Release number of selected component (if applicable): CLI: oc v3.3.0.25+d2ac65e-dirty kubernetes v1.3.0+507d3a7 features: Basic-Auth GSSAPI Kerberos SPNEGO Server: openshift v3.1.1.6-64-g80b61da kubernetes v1.1.0-origin-1107-g4c8e6f4 etcd 2.1.2 How reproducible: Always Steps to Reproduce: 1. Login, create project 2. First oc tag $ oc tag --source=docker docker.io/library/busybox:latest mystream:latest 3. Second oc tag with new tag $ oc tag --source=docker docker.io/library/busybox:latest mystream:tag # More log when --loglevel=8 is specified, see Additional Info below 4. Check is and istag 1> $ oc get is mystream # See -o yaml in Additional Info below 2> $ oc get istag mystream:tag 5. Try the same command in step 3 again and then check the imagestream Actual results: 4. 1> NAME DOCKER REPO TAGS UPDATED mystream 172.30.237.56:5000/xxia-proj/mystream latest 20 minutes ago 2> Error from server: imageStreamTag "mystream:tag" not found 5. Now it has the tag "tag" Expected results: 4. 1> Should include the new tag "tag" like: NAME DOCKER REPO TAGS UPDATED mystream 172.30.109.132:5000/xxia-proj/mystream tag,latest 4 seconds ago 2> Should succeed and show: NAME DOCKER REF UPDATED IMAGENAME mystream:tag docker.io/library/busybox@sha256:65ce39ce3eb0997074a460adfb568d0b9f0f6a4392d97b6035630c9d7bf92402 7 minutes ago sha256:65ce39ce3eb0997074a460adfb568d0b9f0f6a4392d97b6035630c9d7bf92402 Additional info: '-o yaml' for step 4.1: $ oc get is mystream -o yaml # In status, it only shows one tag "latest" apiVersion: v1 kind: ImageStream metadata: annotations: openshift.io/image.dockerRepositoryCheck: 2016-08-25T08:55:52Z creationTimestamp: 2016-08-25T08:55:51Z name: mystream namespace: xxia-proj resourceVersion: "44296" selfLink: /oapi/v1/namespaces/xxia-proj/imagestreams/mystream uid: b93f583a-6aa1-11e6-93cb-fa163eb1d16c spec: tags: - annotations: null from: kind: DockerImage name: docker.io/library/busybox:latest generation: null importPolicy: {} name: latest - annotations: null from: kind: DockerImage name: docker.io/library/busybox:latest generation: null importPolicy: {} name: tag status: dockerImageRepository: 172.30.237.56:5000/xxia-proj/mystream tags: - items: - created: 2016-08-25T08:55:52Z dockerImageReference: docker.io/library/busybox@sha256:65ce39ce3eb0997074a460adfb568d0b9f0f6a4392d97b6035630c9d7bf92402 generation: 0 image: sha256:65ce39ce3eb0997074a460adfb568d0b9f0f6a4392d97b6035630c9d7bf92402 tag: latest '--loglevel=8' log for step 3: See next comment