Bug 1808281

Summary: First port is shown as target-port in the routing section of deploy image edit form always
Product: OpenShift Container Platform Reporter: divgupta
Component: Dev ConsoleAssignee: divgupta
Status: CLOSED ERRATA QA Contact: Jaivardhan Kumar <jakumar>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.4CC: aos-bugs, cvogt, jakumar, nmukherj, rgarg
Target Milestone: ---   
Target Release: 4.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: 1798404 Environment:
Last Closed: 2020-05-04 11:43:15 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1798404    
Bug Blocks:    

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