-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Transformer: Creating the leaf version in igmp-snooping throws error "Entry Vlan10 already exists" #223
Comments
@mbalachandar - Should this be closed as the YANG used will be different now ? |
This issue is irrespective of this model, this error should not be thrown since VLAN is not a target node of the URI |
@mbalachandar Once an initial creation is made, you should use ether PATCH or PUT. |
igmp-snooping is not exist at this time of issuing the request |
@mbalachandar |
yes Kwan, keep the parent table VLAN with the entry Vlan10 in the db, and try create the target node igmp-snooping |
@mbalachandar I1030 17:40:29.775709 71235 common_app.go:323] CREATE case |
@kwangsuk - IGMP snooping will be augmented using network-instance YANG. @mbalachandar - Please create a new issue if you are still running into issues with that YANG. |
I understand Bala will have a different yang path. But this is a generic transformer issue and this was discussed in length when we visited DELL. Following is the understanding on this. Kwan,Mari, I discussed with Bala on the default value handling. He clarified that the create at leaf level (URI containing the leaf) is not allowed by the REST server itself. So I am updating the behavior. Create Operation:
|
Please clarify why this is an issue. |
Hi Mari / Kwan
As discussed, facing this issue, creating it in the git-hub for the tracking purpose. Please let me know if you need more details.
While trying to create the leaf "version" using POST (create) method, we get error saying "Entry Vlan10 already exists". Please see the logs below:
rest-server trace
=======
The text was updated successfully, but these errors were encountered: