Bug 1914196 - target port in `from dockerfile` flow does nothing
Summary: target port in `from dockerfile` flow does nothing
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Dev Console
Version: 4.7
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.7.0
Assignee: Mohammed Saud
QA Contact: Gajanan More
Depends On:
TreeView+ depends on / blocked
Reported: 2021-01-08 10:41 UTC by Mohammed Saud
Modified: 2021-02-24 15:51 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Last Closed: 2021-02-24 15:51:24 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift console pull 7767 0 None closed Bug 1914196: Use route port field for docker container port in Dockerfile import 2021-01-19 08:41:40 UTC
Red Hat Product Errata RHSA-2020:5633 0 None None None 2021-02-24 15:51:39 UTC

Description Mohammed Saud 2021-01-08 10:41:15 UTC
Description of problem:
When using the `from dockerfile` add flow, there are 2 similar fields that are used to specify which port the application is listening on:

dockerfile -> container port

route -> target port

No matter what value is entered for the `target port`, it is never persisted anywhere.

It seems like

Steps to Reproduce

    go to +Add => `from dockerfile`
    Enter git URL https://github.com/rohitkrai03/flask-dockerfile-example
    Enter docker container port 5000
    open routing advanced options
    Enter target port 1234
    Complete form

Actual results:
Service is created with port equal to container port.

No where in the deployment or service is the target port 1234 used.

Expected results:
Container port and target port are the same thing in the form and therefore should be treated as such. They should probably share the same value in the form data.

Reproducibility (Always/Intermittent/Only Once):

Build Details:

Comment 2 divgupta 2021-01-13 12:16:41 UTC
Verified this on -

Build: 4.7.0-0.nightly-2021-01-13-054018

Browser: Chrome

Marking this as done.

Comment 5 errata-xmlrpc 2021-02-24 15:51:24 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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


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