Bug 1808281 - First port is shown as target-port in the routing section of deploy image edit form always
Summary: First port is shown as target-port in the routing section of deploy image edi...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Dev Console
Version: 4.4
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.4.0
Assignee: divgupta
QA Contact: Jaivardhan Kumar
URL:
Whiteboard:
Depends On: 1798404
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-02-28 07:06 UTC by divgupta
Modified: 2020-05-04 11:43 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of: 1798404
Environment:
Last Closed: 2020-05-04 11:43:15 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 4561 0 None closed [release-4.4] Bug 1808281: Set target-port as the first port when route target-port is empty in edit forms 2020-05-04 04:43:41 UTC
Red Hat Product Errata RHBA-2020:0581 0 None None None 2020-05-04 11:43:33 UTC

Description divgupta 2020-02-28 07:06:28 UTC 
+++ This bug was initially created as a clone of Bug #1798404 +++

Description of problem:

The first port from the list of available ports is shown as the target-port in the routing section of deploy-image edit form instead of the previously selected port while the app was being created.

Actual results:
Even if a different target-port was selected during app creation, the first port is shown as the target-port.


Expected results:
If a different target-port was selected during app creation, that port should be shown as the target-port.
Comment 3 Jaivardhan Kumar 2020-03-03 15:10:06 UTC 
Verified on

OpenShift Version
4.4.0-0.ci-2020-03-03-033811
Kubernetes Version
v1.17.1
Channel
stable-4.4
Cluster ID
37161db2-0014-4306-b745-440768152cb5
API Server
https://api.sp79.devcluster.openshift.com:6443
Comment 5 errata-xmlrpc 2020-05-04 11:43:15 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-2020:0581
Note You need to log in before you can comment on or make changes to this bug.