A set request results in error : no changes between
<!--- Provide a general summary of the issue in the Title above -->
In some cases the provided information within a SET request are not considered as a difference, even though the information provided is indeed a change or new.
## Description
<!--- Provide a more detailed introduction to the issue itself, and why you consider it to be a bug -->
When requesting to set the given IETF JSON provided below for the path interfaces/interface[name=Ethernet1] on an Arista cEOS results in an error: `There are no changes between [...] and [...].`
Comparing the two values from the change, in fact result in no difference to be detected. Even though the JSON is valid and should add a new IP address.
--------
```json
{
"openconfig-interfaces:config": {
"mtu": 0,
"name": "Ethernet1",
"type": "iana-if-type:ethernetCsmacd"
},
"openconfig-interfaces:name": "Ethernet1",
"openconfig-interfaces:subinterfaces": {
"subinterface": [
{
"index": 0,
"openconfig-if-ip:ipv4": {
"addresses": {
"address": [
{
"config": {
"ip": "10.10.10.0",
"prefix-length": 31
},
"ip": "10.10.10.0"
}
]
},
"config": {
"enabled": true
}
}
}
]
}
}
```
## Expected Behavior
<!--- Tell us what should happen -->
The information from the JSON should add a new IP address for the interface `Ethernet1` and should therefore be traceable within a change. And it should then be possible to push them to the given network element.
## Actual Behavior
<!--- Tell us what happens instead -->
No changes are detected and nothing is pushed to the device.
## Possible Fix
<!--- Not obligatory, but suggest a fix or reason for the bug -->
## Steps to Reproduce
<!--- Provide a link to a live example, or an unambiguous set of steps to -->
<!--- reproduce this bug. Include code to reproduce, if relevant -->
1.
2.
3.
4.
## Context
<!--- How has this bug affected you? What were you trying to accomplish? -->
## Your Environment
<!--- Include as many relevant details about the environment you experienced the bug in -->
* Version used:
* Environment name and version (e.g. go v1.16.3 on FreeBSD 13.0-current):
* Server type and version:
* Operating System and version:
issue