config network topology.zip
[OVSDB-280] In OVSDB 3 node cluster northbound remote ip address validation missing in configuration data store Created: 01/Feb/16 Updated: 19/Oct/17 Resolved: 01/Feb/16 |
|
| Status: | Resolved |
| Project: | ovsdb |
| Component/s: | Northbound |
| Affects Version/s: | unspecified |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | ranjithkumar_t | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Attachments: |
config network topology.zip
|
| External issue ID: | 5161 |
| Description |
|
Observation : 1 (Passing valid remote ip) I used valid remote ip as "10.106.138.128" "option": "remote_ip", Bridge creation successful and the data reflected in both configuration and operational data store. Observation : 2 (Passing invalid remote ip) I changed the remote ip value as "1234.5678.1155.5555". The data will be reflected in configuration data store. "option": "remote_ip", Bridge creation successful in configuration data store and updated with invalid remote ip as below. <options xmlns="urn:opendaylight:params:xml:ns:yang:ovsdb"> In operational data store there is no update. Observation : 3 (Passing special characters) I changed the remote ip value as "!@#$%^&*()". The data reflected in config data store as below. <options xmlns="urn:opendaylight:params:xml:ns:yang:ovsdb"> In operational data store there is no update. Many times I have tried, but I got the above behavior. For your information I have attached restconf url, config and operational data store output. |
| Comments |
| Comment by ranjithkumar_t [ 01/Feb/16 ] |
|
Attachment config network topology.zip has been added with description: I have attached restconf url, config and operational data store output |
| Comment by Anil Vishnoi [ 01/Feb/16 ] |
|
Hi Ranjit, In OVSDB schema, option & value are just string type, so you can push any value through it and southbound plugin will push that data down to ovsdb. OVSDB might reject that data if it's not valid and your operation will fail and you won't see any update in the operational data store. This is the expected behavior, application/user need to make sure that they pass correct argument while creating any ovsdb resource. |
| Comment by Sam Hague [ 01/Feb/16 ] |
|
As Anil mentioned, other_config are key value pairs composed of strings so the ovsdb southbound is working as designed. |