Closed duddis1 closed 1 year ago
Hi, thank you for reporting these issues.
jsonschema>=4.5.1,<4.18
still fulfills the jsonschema>=3.2.0
requirement.arista.eos
collection is maintained by RedHat, so any discrepancies will have to be solved on their repo. I checked what you mentioned, and it seems like they overwrote their automatic version numbering in this commit. If you just install from galaxy or automation hub, you should not see any issues.I would like to understand why these things are blocking you. Feel free to contact me directly if we should set up a call: holbech@arista.com.
We are getting below error message highlighted while running AVD for the second issue which was reported, due to this we can proceed further.
Do you want us to raise separate ticket in eos space to correct this error in their codebase? https://github.com/ansible-collections/arista.eos
ERROR LOG:- TASK [arista.avd.eos_designs : Verify Requirements] **** task path: /home/avd/.ansible/collections/ansible_collections/arista/avd/roles/eos_designs/tasks/main.yml:2 Not a git repository AVD version 4.2.0-dev2
To unblock your workflow, add this to your group_vars:
avd_ignore_requirements: true
So our arista.eos
collection requirement is >=6.0.1
but you only have 6.0.0
installed as reported by both ansible-galaxy collection list
as well as our requirements validation tool.
So I think you should try to upgrade arista.eos
with ansible-galaxy collection install "arista.eos:==6.0.1"
.
I just checked the tar ball from Ansible Galaxy and it correctly reports version 6.0.1.
If you clone from Github based on the tag, this might indeed fail like you see, because of the issue you mentioned. Generally we always recommend to install from Galaxy.
Re the arista.eos
version issue, it would be good to submit an issue on that repo.
we are installing eos 6.0.1 using ansible-galaxy But when it gets installed the MANIFEST.json gets created & it gets the version 6.0.0 from galaxy.yml Your python script verify_requirements.py reads MANIFEST.json to find out the installed version
Raised below issue in arista.eos repo https://github.com/ansible-collections/arista.eos/issues/427
I think there is still some misunderstanding here:
galaxy.ansible.com
you pull down the tar file (https://galaxy.ansible.com/download/arista-eos-6.0.1.tar.gz) and when checking that file, you can see the MANIFEST.json having 6.0.1 in there:
{
"collection_info": {
"namespace": "arista",
"name": "eos",
"version": "6.0.1",
"authors": [
"Ansible Network Community (ansible-network)"
],
...
So I am not sure how you are installing it, but I am guessing you are installing it with some git tag instead of using galaxy.ansible.com
.
Moving to a discussion since this is not a bug in arista.avd.
Issue Summary
We are unable to generate the intended config with Arista AVD Version "4.2.0-dev2". We have identified the root cause of the issues and some we have resolved with work around, but others we are unable to resolve, and this will require a change in your code base.
Which component(s) of AVD impacted
new components
How do you run AVD ?
Ansible CLI with AVD Runner
Steps to reproduce
Relevant log output
No response
Contributing Guide