| Thread Previous • Date Previous • Date Next • Thread Next |
** Tags removed: folsom-backport-potential
** Also affects: quantum/folsom
Importance: Undecided
Status: New
** Changed in: quantum/folsom
Status: New => In Progress
** Changed in: quantum
Status: In Progress => Fix Released
** Changed in: quantum
Assignee: (unassigned) => Akihiro Motoki (amotoki)
** Changed in: quantum/folsom
Importance: Undecided => Medium
** Changed in: quantum
Importance: Undecided => Medium
** Changed in: quantum/folsom
Assignee: (unassigned) => Akihiro Motoki (amotoki)
** Changed in: quantum/folsom
Milestone: None => 2012.2.4
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to quantum.
https://bugs.launchpad.net/bugs/1166077
Title:
Folsom NEC plugin fails to create a network/port on some version of
PFC due to too long string
Status in OpenStack Quantum (virtual network service):
Fix Released
Status in quantum folsom series:
In Progress
Bug description:
Folsom NEC plugin can fails to create a network/port on some version of
the OpenFlow controller supported.
Some version of NEC ProgrammableFlow OpenFlow controller, one of the OpenFlow
controllers (OFCs), accepts the string up to 31 chars as a network ID.
The folsom version of NEC plugin now uses Quantum UUID as ID on OFC,
so this leads to failure on network creation. This commit changes
the plugin to generate a 31-char ID on OFC to keep its uniqueness.
The same thing can be said to port ID.
Similarly, the description field must be a string up to 127 chars
and consist of [A-Za-z0-9_] characters. This change also fixes it.
To manage notifications about this bug go to:
https://bugs.launchpad.net/quantum/+bug/1166077/+subscriptions
| Thread Previous • Date Previous • Date Next • Thread Next |
