[ovs-discuss] OVSDB Error:Type mismatch for member 'uuid-name
Ben Pfaff
blp at ovn.org
Fri Jun 26 23:52:22 UTC 2020
On Fri, Jun 26, 2020 at 06:10:09PM -0400, Vasu Dasari wrote:
> Hi,
>
> I am seeing a strange error. Can someone see if this ia bug or I am using
> this wrong?
>
> The following transaction is successful
>
> root at ovs1:~# ovsdb-client transact '
> [
> "Open_vSwitch",
> {
> "op": "insert",
> "row": {
> "name": "br1-eth1"
> },
> "table": "Interface",
> "uuid-name": "a33f0e9e60105b9d8f8c15797107f29c"
> }
> ]
> '
> [{"uuid":["uuid","69ee67e3-4a32-4c88-998f-fd354b7b0509"]}]
>
> whereas the following transaction fails:
> root at ovs1:~# ovsdb-client transact '
> [
> "Open_vSwitch",
> {
> "op": "insert",
> "row": {
> "name": "br1-eth1"
> },
> "table": "Interface",
> "uuid-name": "133f0e9e60105b9d8f8c15797107f29c"
> }
> ]
> '
> [{"details":"Parsing ovsdb operation 1 of 1 failed: Type mismatch for
> member 'uuid-name'.","error":"syntax
> error","syntax":"{\"op\":\"insert\",\"row\":{\"name\":\"br1-eth1\"},\"table\":\"Interface\",\"uuid-name\":\"133f0e9e60105b9d8f8c15797107f29c\"}"}]
> root at ovs1:~#
>
> The only difference in above commands is the uuid-name string.
> a33f0e9e60105b9d8f8c15797107f29c. << Successful one
> 133f0e9e60105b9d8f8c15797107f29c. << Failed one
>
> Also you can notice that the first letter in the above strings is the only
> thing that is different. Actually, this command fails if the first letter
> is any digit(0-9).
>
> Can someone please share what's going on here, why this is failing?
As documented in the RFC, uuid-name must be an <id>, which must start
with _ or a letter.
More information about the discuss
mailing list