-
Notifications
You must be signed in to change notification settings - Fork 23
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
Problem with firmware upload after changing from aoscx role to collection #82
Comments
Hi @jon-larsen ! Can you confirm if the IP address you're using is on the mgmt vrf or another? I feel this may be similar to this issue which we are investigating internally: #78 |
The IP belongs to a VLAN interface which has no vrf configured. |
Tested my playbook on an 8325 switch which is using the mgmt vrf, and it works on that one. |
@jon-larsen thank you for that verification! I believe this is similar to #78 and we're currently investigating a fix which is anticipated in an upcoming minor release - I'll update this issue once we've implemented a fix. Thank you for your patience! |
Hello @jon-larsen ! We've just published a fix for this issue, please install the latest version of the collection and verify if you no longer see this issue:
|
I got a new error message now: |
@jon-larsen which pyaoscx version is installed? |
I had 2.5.0 at first, but I got the same error with 2.5.1 |
@jon-larsen after looking at your original issue the remote file path is this value: is that correct? to have that github link within the path? |
That indeed looks weird. Not sure what happened there, but I did a lot of trial and error when I first had this problem. Maybe there is something I have changed and not reverted... Here's the current output. The firmware path is correct here:
|
since this is a login error can you verify if other modules in your environment present the same error or is it just the aoscx_upload_firmware - can you try aoscx_facts or aoscx_interface in a playbook and see if that is successful? |
can you verify which version of the CX collection you have with the |
Yes. It gets the current firmware first, to check if firmware upload is necessary:
Full list of collections:
And Python packages:
|
@jon-larsen can you confirm if you're still experiencing this issue with the latest collection and pyaoscx version? |
I still get the problem with the following versions:
We have however changed from ansible-core to ansible a while back, and now I see the following warning in the play:
Running the default Ansible version in Ubuntu 22.04. |
@jon-larsen thanks for the clarification - I'm thinking this is due to Ansible using an out of date version of the I noticed in the previous error message the error was being thrown at line Can you execute the following commands and supply the output? Also please supply the output of the error if it's different/changed from when previously posted |
Thanks Tiffany, that is strange indeed. I wonder if I should redeploy the VM that we use for Ansible, as we've been doing lots of manual configuration on it during troubleshooting of all different kinds of issues with Ansible. We have the following configuration in
Here's the output of which:
With the latest run, it looks like it is using python 3.10 and the correct path for pyaoscx. The date on the file looks correct at least:
Here is the latest output of the playbook-run
|
I redeployed the VM (now with Ubuntu 24.04), but still the same problem. Here is the output of the run from the new Ansible VM
|
I am also having similar issues (LOGIN ERROR, Cookies where not set correctly. Login failed). I managed to solve the Login failed error by replacing the following lines in the aoscx_upload_firmware.py:
Unfortunately, this only lead to new errors:
I'm running out of time to look into this issue, so I just wanted to share my findings in case they might be usefull for anyone. For the record, I'm running this in an Alpine 3.20 docker image. Details
|
A couple of months ago I changed all ansible-playbooks from using the aoscx role to using the aoscx collection. All of them have been working fine, except for the playbook for uploading firmware. I didn't find this out until now, so I am not completely sure if there could be any other reason than changing to collection.
Switch: 6200F
Firmware: ML.10.10.1070
This is the error I receive:
GENERIC OPERATION ERROR: Command not allowed.\\n: Code: 403
It takes about a minute before the error appears, so it seems Ansible is working with something before it fails.
https-server rest access-mode read-write
is configured on the switch (not visible in the config since it is default).I have a group_vars for the switches which contains this:
The user running Ansible have access to the firmware file. I have tested copying the path from the ansible output and using
ls
andcat
on the filepath with the user.playbook
playbook output
collection versions
ansible version
pip versions
switch logs
The text was updated successfully, but these errors were encountered: