Bug 1247523 - [RFE]-UI only includes first port in generated service
Summary: [RFE]-UI only includes first port in generated service
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 3.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: ---
Assignee: Samuel Padgett
QA Contact: Yanping Zhang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-07-28 08:45 UTC by Miheer Salunke
Modified: 2022-07-09 07:37 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-01-26 19:16:09 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:0070 0 normal SHIPPED_LIVE Important: Red Hat OpenShift Enterprise 3.1.1 bug fix and enhancement update 2016-01-27 00:12:41 UTC

Comment 2 Jordan Liggitt 2015-08-06 14:22:25 UTC
Creating services with all ports is blocked by routes not supporting multi-port services

Comment 5 Jessica Forrester 2016-01-08 15:15:54 UTC
This was fixed in https://github.com/openshift/origin/issues/4956

Comment 6 Yanping Zhang 2016-01-12 08:10:05 UTC
Tested on puddle AtomicOpenShift/3.1/2016-01-11.1

# openshift version
openshift v3.1.1.1
kubernetes v1.1.0-origin-1107-g4c8e6f4
etcd 2.1.2

Steps to test:
1.Create an image exposing multiple ports, such 5858, 8080.
2.Create app from console using the image created in step 1.
On the creation page, under the Routing configuration, user could choose to use any port in Target Port list.
3.After choose the proper port eg,8080, click "Create", the app is created successfully.
4.Check that the route target port is exactly the chosen port, and access the route url for service, app can be accessed successfully.

The bug has been fixed, so move it to Verified.

Comment 8 errata-xmlrpc 2016-01-26 19:16:09 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/RHSA-2016:0070


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