Bug 1141285

Summary:	Edit Network dialog does not allow you to edit ID but does make the field look editable
Product:	Red Hat OpenStack	Reporter:	Jeff Needle <jneedle>
Component:	python-django-horizon	Assignee:	Matthias Runge <mrunge>
Status:	CLOSED ERRATA	QA Contact:	Ido Ovadia <iovadia>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	5.0 (RHEL 6)	CC:	aortega, athomas, jschluet, mreid, mrunge, nyechiel, sclark, yeylon
Target Milestone:	ga	Keywords:	Triaged, ZStream
Target Release:	7.0 (Kilo)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	python-django-horizon-2015.1.0-8.el7ost	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-08-05 13:13:50 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:

Description Jeff Needle 2014-09-12 15:33:05 UTC

Edit Network dialog has ID as a required field and looks editable, but is read only. The mouse changes to a cancel sign when you mouse over it, and you can't type within it, although you can click and hightlight text. If they can't change the ID, we should just show it as a read-only text, and not bother putting it in a field.

Comment 2 Matthias Runge 2014-09-22 08:47:31 UTC

Network ID is a required parameter, when changing anything on a network. Editing is disabled.
It's most useful to know this info, when using command line. But I agree, it's mostly useless here.

https://bugs.launchpad.net/horizon/+bug/1372348

Comment 5 Matthias Runge 2015-02-11 08:28:29 UTC

This was merged for kilo. It looks like it should be backportable.

Comment 6 Julie Pichon 2015-02-11 10:40:39 UTC

Fixed in kilo.

Comment 8 Ido Ovadia 2015-06-11 13:12:20 UTC

Verified
========
python-django-horizon-2015.1.0-8.el7ost.noarch

Comment 11 errata-xmlrpc 2015-08-05 13:13:50 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/RHEA-2015:1548