Bug 1375480 - If the default app name is changed, pod is not created when deployed from ImageStreamTag on web console
Summary: If the default app name is changed, pod is not created when deployed from Ima...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
: 3.3.1
Assignee: Samuel Padgett
QA Contact: Yadan Pei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-13 09:01 UTC by Xingxing Xia
Modified: 2016-10-27 15:41 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: In the web console, if you deployed an image from an image stream tag and changed the default name, an incorrect image change trigger would be set in the deployment config. Consequence: A deployment would fail to run because the image stream tag trigger is wrong. Fix: The web console was fixed to use the correct image stream for the deployment config trigger. Result: You can change the default name for Add to Project -> Deploy Image.
Clone Of:
Environment:
Last Closed: 2016-10-27 15:41:52 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2084 0 normal SHIPPED_LIVE Red Hat OpenShift Container Platform 3.3.1.3 bug fix update 2016-10-27 19:41:25 UTC

Description Xingxing Xia 2016-09-13 09:01:41 UTC
Description of problem:
If the default app name is changed, pod is not created when deployed from ImageStreamTag on web console

Version-Release number of selected component (if applicable):
v3.3.0.30

How reproducible:
Always

Steps to Reproduce:
1. Login to Openshift web console and create a new project
2. Add to project -> Deploy Image -> Image Stream Tag
3. Choose one istag, e.g. openshift/mongodb:latest, then change the default app name "mongodb", e.g. to "mongodbxxia", then click "Create"
4. Check pod 

Actual results:
3. Return creation success
4. No pod. If check `oc deploy mongodbxxia`, it shows "mongodbxxia deployment #1 waiting on image or update", even after waiting some time.

Check the dc, found:
$ oc get dc mongodbxxia -o yaml
  triggers:
  - type: ConfigChange
  - imageChangeParams:
      automatic: true
      containerNames:
      - mongodbxxia
      from:
        kind: ImageStreamTag
        name: mongodbxxia:latest   <-- the cause
        namespace: openshift
    type: ImageChange

However:
A. If don't change the default app name, then pod will be created
B. Even if default app name is changed, corresponding CLI approach can quickly see created pod:
$ oc new-app mongodb:latest --name mongodb2nd
$ oc deploy mongodb2nd
mongodb2nd deployment #1 deployed about a minute ago - 1 pod

C. Even if default app name is changed, another choice "Deploy Image -> Image Name" can quickly see created pod as well.

Expected results:
4. Should see created pod.

Additional info:

Comment 2 Samuel Padgett 2016-09-13 13:57:51 UTC
enterprise-3.3 fix: https://github.com/openshift/origin-web-console/pull/535

Comment 4 Xingxing Xia 2016-10-13 03:17:44 UTC
Verified with OpenShift master v3.3.1.1, the issue in comment 0 is fixed. Now dc references "name: mongodb:latest" instead of "name: mongodbxxia:latest" and pod is therefore deployed successfully.

Comment 6 errata-xmlrpc 2016-10-27 15:41:52 UTC
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/RHBA-2016:2084


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