Bug 1338754 - Containers -- Providers -- Tile View - Port number is shown incorrectly
Summary: Containers -- Providers -- Tile View - Port number is shown incorrectly
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.6.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: 5.6.1
Assignee: zakiva
QA Contact: Einat Pacifici
URL:
Whiteboard: container
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-23 11:49 UTC by Einat Pacifici
Modified: 2022-07-09 07:43 UTC (History)
6 users (show)

Fixed In Version: 5.6.1.2
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-08-18 17:45:08 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Screenshot shown port number (22.16 KB, image/png)
2016-05-23 11:49 UTC, Einat Pacifici
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:1634 0 normal SHIPPED_LIVE Important: CFME 5.6.1 security, bug fix, and enhancement update 2016-08-18 21:43:52 UTC

Description Einat Pacifici 2016-05-23 11:49:39 UTC
Created attachment 1160548 [details]
Screenshot shown port number

Description of problem:
View Containers -- Providers -- Tile View - Port Number is shown as 8,443 it should be seen as 8443

Version-Release number of selected component (if applicable):
5.6.0.7

How reproducible:
Always

Steps to Reproduce:
1.View Containers -- Providers -- Tile View - Port Number

Actual results:
Port number is shown as; 8,443

Expected results:
Port number should be shown as: 8443


Additional info:
Screenshot attached.

Comment 2 Federico Simoncelli 2016-07-12 16:57:20 UTC
Zahi can you take a look at this? Thanks!

Comment 3 zakiva 2016-07-13 13:21:40 UTC
Bug fix: https://github.com/ManageIQ/manageiq/pull/9776

Comment 5 Einat Pacifici 2016-07-31 08:39:08 UTC
Port number is now seen correctly

Comment 7 errata-xmlrpc 2016-08-18 17:45:08 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://rhn.redhat.com/errata/RHSA-2016-1634.html


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