yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #28857
[Bug 1426252] [NEW] Create Port gives error "Network Name is required" which is a read-only field.
Public bug reported:
While creating a port "Network Name" and "Network Id" are mandatory fields in read-only mode. Now if a network is there with no name(as per Api reference network name is optional) and we try to create a port on it then it will give an error that network name is a mandatory field.
Thus, this leads to inconsistency between port creation and network creation.
Steps to reproduce:
Create a network without giving name to it.
>From Admin->Networks, select that network and try to create a port on it.
Expected Solution:
Network name in port creation should be an optional field.
** Affects: horizon
Importance: Undecided
Assignee: Kanchan Gupta (kanchan-gupta1)
Status: In Progress
** Changed in: horizon
Assignee: (unassigned) => Kanchan Gupta (kanchan-gupta1)
** Changed in: horizon
Status: New => In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1426252
Title:
Create Port gives error "Network Name is required" which is a read-
only field.
Status in OpenStack Dashboard (Horizon):
In Progress
Bug description:
While creating a port "Network Name" and "Network Id" are mandatory fields in read-only mode. Now if a network is there with no name(as per Api reference network name is optional) and we try to create a port on it then it will give an error that network name is a mandatory field.
Thus, this leads to inconsistency between port creation and network creation.
Steps to reproduce:
Create a network without giving name to it.
From Admin->Networks, select that network and try to create a port on it.
Expected Solution:
Network name in port creation should be an optional field.
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1426252/+subscriptions
Follow ups
References