-
Notifications
You must be signed in to change notification settings - Fork 219
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
Data model issues after upgrading to 5.0 #4686
Comments
also, please advise how can we resolve the below two errors, if you have any idea? ERROR! [MBH-CAMP0S]: 'Validation Error: node_type_keys': Primary key 'key' is not set on all items as required. |
The primary key is always the first key shown in the documentation for a given list of dicts. ip_helpers:
- ip_helper: 1.1.1.1
Without seeing your inputs for
The Until then you can move the |
Thanks for providing the details! if I move dot1x key under structured_config it is rendering correctly, but it is applied to all the switches. I have to see whether I can restrict this in populating for only campus switches. also , I have amended the type for node_type_keys from spine to l2spine as mentioned in below link
|
You need to add |
I meant add it under the |
The above-mentioned errors have been resolved. Currently, the following error is pending: TASK [arista.avd.eos_designs : Set eos_designs facts] *************************************************************************************************************************************************************** |
So AVD wants to configure BGP for the switch |
Enhancement summary
We are trying to adopt arista AVD version v5.0.0, and finding below validation errors.
We can find from the release notes Data model changes from “dict-of-dicts” to “list-of-dicts” for only Ethernet interfaces, and you are using the key as "name" for the Ethernet interface name.
but we can't find the key name for ip_address and ip_helper attributes, please let us know which key we have to use for ip_address and ip_helper values while converting them to list of lists.
Which component of AVD is impacted
eos_cli_config_gen
Use case example
We tried populating the config using below list of lists format for ip_helpers and ip_address for bgp_peers, but getting error saying ip_helper is not a valid key.
Describe the solution you would like
The config should access the key names ip_helper and ip_address as detailed below.
Describe alternatives you have considered
No response
Additional context
No response
Contributing Guide
The text was updated successfully, but these errors were encountered: