Bug 1392416
| Summary: | openshift-jvm Camel route delete: route persists in html page after delete | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Libor Fuka <lfuka> | ||||||
| Component: | Management Console | Assignee: | Alexandre Kieling <abrianik> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Peng Li <penli> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | high | ||||||||
| Version: | 3.3.1 | CC: | abrianik, aos-bugs, jforrest, jokerman, maschmid, mmccomas, penli, tdawson | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: |
Cause: JavaScript bug
Consequence: HTML page is not refreshed after Camel route delete
Fix: Fix JavaScript bug
Result: HTML page is refreshed after Camel route delete
|
Story Points: | --- | ||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2017-01-18 12:50:33 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: | |||||||||
| Attachments: |
|
||||||||
|
Description
Libor Fuka
2016-11-07 13:02:01 UTC
Fix ready for testing. Please use openshift-jvm v1.0.51 in web console in https://github.com/openshift/origin-web-console/pull/858 This has been merged into ocp and is in OCP v3.4.0.25 or newer. verified [root@ip-172-18-11-178 ~]# openshift version openshift v3.4.0.25+1f36858 check and compare the tree in screenshots. Created attachment 1220773 [details]
before
Created attachment 1220774 [details]
after
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-2017:0066 |