SM UI: Bond member Interfaces mandates IP address in UI - does not allow provision to get completed in 3.0 2723
Bug #1555319 reported by
sundarkh
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R2.22.x |
Won't Fix
|
Critical
|
Chinmay Zanpure | |||
R3.0 |
Fix Committed
|
High
|
Chinmay Zanpure | |||
R3.1 |
Fix Committed
|
High
|
Chinmay Zanpure | |||
Trunk |
Fix Committed
|
High
|
Chinmay Zanpure |
Bug Description
SM UI: Bond member Interfaces mandates IP address in UI - does not allow provision to get completed in 3.0 2723
Adding interfaces under Physical Interfcaes (mandates IP) though they are going to get accommodated under bond interfaces (Please find first two attachemnts) .
Because of which the Node gets configured with same IP across multiple interfaces (third attachment) provision gets stuck at compute_started
Issue seen only when trying to provision a target which has bond interface from SM UI
SM : nodej5.
Target : nodea4.
SM WebUI: https:/
To post a comment you must log in.
Review in progress for https:/ /review. opencontrail. org/18324
Submitter: Chinmay (<email address hidden>)