Skip to content
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

Role fails on Debian 11 due to missing python-ipaddr package. #72

Closed
peterkuiper opened this issue Mar 15, 2022 · 11 comments · Fixed by #79
Closed

Role fails on Debian 11 due to missing python-ipaddr package. #72

peterkuiper opened this issue Mar 15, 2022 · 11 comments · Fixed by #79

Comments

@peterkuiper
Copy link

Describe the bug
Role fails on Debian 11 due to missing python-ipaddr package.

To Reproduce
Steps to reproduce the behavior:

  1. Create a Debian 11 VM
  2. Create a playbook that includes the mrlesmithjr.frr role
  3. The task fails with the following error: fatal: [127.0.0.1]: FAILED! => {"changed": false, "msg": "No package matching 'python-ipaddr' is available"}

Expected behavior
The role should install FRR without errors.

Screenshots

TASK [mrlesmithjr.frr : Install FRR] ****************************************************************************************************************************
fatal: [127.0.0.1]: FAILED! => {"changed": false, "msg": "No package matching 'python-ipaddr' is available"}

Desktop (please complete the following information):

  • OS: MacOS
  • Browser: N/A
  • Version: latest

Additional context

Changing python-ipaddr in

- python-ipaddr
to python3-ipaddr fixes the error.

@stale
Copy link

stale bot commented May 14, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix This will not be worked on label May 14, 2022
@stale stale bot closed this as completed May 21, 2022
@arhue
Copy link

arhue commented Jul 25, 2022

I have the same issue.

@sirhopcount
Copy link
Contributor

Can we reopen this please? This is still an issue.

@elcomtik
Copy link
Collaborator

Yes, we can reopen. However it will be auto closed if no one step in as contributor for this feature.

@elcomtik elcomtik reopened this Nov 21, 2022
@stale stale bot removed the wontfix This will not be worked on label Nov 21, 2022
@peterkuiper
Copy link
Author

peterkuiper commented Nov 21, 2022

@elcomtik I'm happy to make a PR with the above fix but I'm not sure if it would break older Debian versions.

I could do an conditonal like so:

when: ansible_distribution == 'Debian' and ansible_distribution_version == '11'

@elcomtik
Copy link
Collaborator

elcomtik commented Nov 21, 2022

Package list should be defined in variables and included at beginning for each supported distribution. You may look at implementation of proposed functionality at mrlesmithjr/ansible-matiadb-galera-cluster.

@sirhopcount
Copy link
Contributor

I have a pull request ready but the workflow seem to fail for an unrelated reason:

  Building wheel for ruamel-yaml-clib (setup.py): started
  Building wheel for ruamel-yaml-clib (setup.py): finished with status 'error'
  error: subprocess-exited-with-error
  
  × python setup.py bdist_wheel did not run successfully.
  │ exit code: 1
  ╰─> [25 lines of output]
      sys.argv ['/tmp/pip-install-_ip6syqe/ruamel-yaml-clib_03f3eedea5c64338b247d834a1ef3aba/setup.py', 'bdist_wheel', '-d', '/tmp/pip-wheel-e0k5vido']
      test compiling /tmp/tmp_ruamel_ogwdrwmp/test_ruamel_yaml.c -> test_ruamel_yaml OK
      /opt/hostedtoolcache/Python/3.11.0/x64/lib/python3.11/site-packages/setuptools/dist.py:286: SetuptoolsDeprecationWarning: The namespace_packages parameter is deprecated, consider using implicit namespaces instead (PEP 420).

https://github.com/sirhopcount/ansible-frr/actions/runs/3522233314/jobs/5904965166#step:4:295

So I think we might need to fix that first (I assume via a different issue/pull request).

@sirhopcount
Copy link
Contributor

Python is not really my area of expertise but it seems to be an issue with ruamel.yaml and ruamel.yaml.clib. From what I can tell adding python3-dev to the docker containers would solve the issue but there may be an other way to solve this by using a different version of as talked about here:

https://stackoverflow.com/a/68627053

Can someone with some more expertise confirm that. If simply adding python3-dev is enough I'll make a pull request for that change on mrlesmithjr/dockerfiles.

@stale
Copy link

stale bot commented Jan 22, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix This will not be worked on label Jan 22, 2023
@stale stale bot closed this as completed Feb 1, 2023
@elcomtik elcomtik reopened this Feb 1, 2023
@elcomtik
Copy link
Collaborator

elcomtik commented Feb 2, 2023

@sirhopcount I'll update python requirements as I have experienced a similar issue due to outdated python packages. Please rebase your code ad test if issue persist

@stale stale bot removed the wontfix This will not be worked on label Feb 2, 2023
@elcomtik
Copy link
Collaborator

The tests were fixed today. Please do rebase.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants