Bug 1109422

Summary:	Launch Instance dialog - "nic" should probably be capitalized on the Networking tab
Product:	Red Hat OpenStack	Reporter:	Matt Reid <mreid>
Component:	python-django-horizon	Assignee:	Julie Pichon <jpichon>
Status:	CLOSED ERRATA	QA Contact:	Ido Ovadia <iovadia>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.0	CC:	aortega, athomas, iovadia, jpichon, mrunge, nyechiel, yeylon
Target Milestone:	Upstream M1	Keywords:	Triaged
Target Release:	6.0 (Juno)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	python-django-horizon-2014.2-4.el7ost	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-02-09 14:55:59 UTC	Type:	Bug
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:
Bug Blocks:	1099570

Description Matt Reid 2014-06-13 20:14:45 UTC

Description of problem:
On the Networking tab of the Launch Instance dialog, "nic" is all lowercase. Generally acronyms are capitalized. "nic" is used both for each interface, and in the description on the right pane.

Somewhat related to that, on the same dialog and tab, we say "Selected Networks" and underneath that, "Available networks", which don't follow the same capitalization conventions. "Available Networks" would match what seems to be used elsewhere in the UI.

Note: This has been fixed upstream since I filed it earlier this month.

Comment 1 Julie Pichon 2014-06-24 09:34:14 UTC

Fixed in Juno upstream.

Comment 2 Julie Pichon 2014-11-20 11:53:25 UTC

How to test:
------------

1. Go to the Launch Instance form and click on the Networking tab
2. Check NIC is properly capitalised for the networks
3. Same for "Available networks" and "Selected networks"...

Comment 4 Ido Ovadia 2014-12-08 14:28:50 UTC

Verified
========
python-django-horizon-2014.2-5.el7ost.noarch

Comment 6 errata-xmlrpc 2015-02-09 14:55:59 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/RHEA-2015-0154.html