Description of problem:
For a deployment triggered by config change or image change, there are always a yellow triangle near each dc on dc page. Hover mouse on the angle, it shows "caused by a config change", "caused by an image change". This display is ugly. Because, after all, the causes are normal. Triangle should display only when message is abnormal
Version-Release number of selected component (if applicable):
features: Basic-Auth GSSAPI Kerberos SPNEGO
Steps to Reproduce:
1. Create a dc of config change:
oc run hello --image openshift/hello-openshift
2. Create a dc of image change:
oc new-app centos/ruby-22-centos7~https://github.com/openshift/ruby-ex.git
3. Wait for the dc/hello, dc/ruby-ex deployed.
$ oc deploy hello
hello deployment #1 deployed 43 minutes ago - 1 pod
$ oc deploy ruby-ex
ruby-ex deployment #1 deployed 23 hours ago - 1 pod
4. Login to web console, go to dc page:
1> Click "Browse" --> "Deployments"
2> Click one dc, e.g. "hello", check the dc/hello page
1> On dc page, near each dc, there is yellow triangle. Hover mouse on the triangle, it shows "caused by a config change", "caused by an image change". But there are already a "Trigger" column showing "Config change", "Image change"
2> On dc/hello page, there is also a yellow triangle near the dc name
4. Should remove the yellow triangle of such warning
In fact, this warning is from CLI:
oc get dc hello -o yaml:
- type: ConfigChange
message: caused by a config change
But it is ugly and not useful to show this specific kind of message on web
Commit pushed to master at https://github.com/openshift/origin-web-console
Bug 1356018: dc's warning triangle 'caused by config/image change' is not useful on web
Checked latest puddle, it does not yet include the fix. Will check next puddle when available.
First tested with latest Origin, the issue is fixed. The warning triangle now is not shown in dc list page and specific dc page.
$ openshift version
Like comment 3, fixed.
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.