ansible-navigator cannot find the oslo module
Good morning/evening/day, ansible-navigator builds and is installable, but does not find the "oslo" module:
ansible-navigator --version Traceback (most recent call last): File "/usr/bin/ansible-navigator", line 8, in <module> sys.exit(main()) File "/usr/lib/python3.10/site-packages/ansible_navigator/cli.py", line 143, in main messages: list[LogMessage] = log_dependencies() File "/usr/lib/python3.10/site-packages/ansible_navigator/cli.py", line 83, in log_dependencies spec = find_spec(pkg_name) File "/usr/lib64/python3.10/importlib/util.py", line 94, in find_spec parent = __import__(parent_name, fromlist=['__path__']) ModuleNotFoundError: No module named 'oslo'
My problem is that installing all of the python3-oslo.* packages does not solve that error. And I cannot find a reference to oslo in the projects source code or issues. I found a package called oslo-core on pypi, which seems to be missing on Tumbleweed (while lots of other oslo.* modules seem to be present). Is there a reason for oslo-core missing? I tried to package it, but it is missing lots of dependencies: unresolvable: nothing provides python39-dacite nothing provides python311-dacite nothing provides python310-dacite nothing provides python39-ninja nothing provides python311-ninja nothing provides python310-ninja nothing provides python39-torch nothing provides python311-torch nothing provides python310-torch nothing provides python39-transformers nothing provides python311-transformers nothing provides python310-transformers So before going down that rabbit hole I wanted to ask for ideas (especially where this requirement comes from). Thanks in advance. Kind Regards, Johannes -- Johannes Kastl Linux Consultant & Trainer Tel.: +49 (0) 151 2372 5802 Mail: kastl@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg http://www.b1-systems.de GF: Ralph Dehner Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
Am Mittwoch, 3. Mai 2023, 07:20:14 CEST schrieb Johannes Kastl: Hi Johannes,
File "/usr/lib/python3.10/site-packages/ansible_navigator/cli.py", line 143, in main
Are you using this on tumbleweed? On sle15 there is no matching oslo package for python 3.10.
I found a package called oslo-core on pypi, which seems to be missing on Tumbleweed (while lots of other oslo.* modules seem to be present). Is there a reason for oslo-core missing? I tried to package it, but it is missing lots of dependencies:
Thats old, please don't go there. Oslo"dot" xx would be the right project. Where is that ansible-navigator package that you have issues with which distribution? Greetings, Dirk
Hi Dirk, On 03.05.23 at 11:41 Dirk Müller wrote:
Am Mittwoch, 3. Mai 2023, 07:20:14 CEST schrieb Johannes Kastl:
File "/usr/lib/python3.10/site-packages/ansible_navigator/cli.py", line 143, in main
Are you using this on tumbleweed?
Yes.
On sle15 there is no matching oslo package for python 3.10.
There are almost no packages for SLES15 and python3.10 that are required, hence I started to build all of them to see if this works out. :-) I planned to move all of this to systemsmanagement:ansible:SLES15 and child projects, but had no time yet.
I found a package called oslo-core on pypi, which seems to be missing on Tumbleweed (while lots of other oslo.* modules seem to be present). Is there a reason for oslo-core missing? I tried to package it, but it is missing lots of dependencies:
Thats old, please don't go there. Oslo"dot" xx would be the right project.
OK, that would explain why it is missing.
Where is that ansible-navigator package that you have issues with which distribution?
Here:
https://build.opensuse.org/package/show/home:ojkastl_buildservice:Branch_sys...
I installed this on my workstation that is running Tumbleweed with the latest updates from yesterday. Kind Regards, Johannes -- Johannes Kastl Linux Consultant & Trainer Tel.: +49 (0) 151 2372 5802 Mail: kastl@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg http://www.b1-systems.de GF: Ralph Dehner Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
Am Mittwoch, 3. Mai 2023, 12:13:13 CEST schrieb Johannes Kastl: Hi Johannes,
File "/usr/lib/python3.10/site-packages/ansible_navigator/cli.py", Are you using this on tumbleweed? Yes.
Weird, I cannot reproduce this : 7d27fdd42cc7:/ # ansible-runner --version 1.4.7 7d27fdd42cc7:/ # cat /etc/os-release NAME="openSUSE Tumbleweed" # VERSION="20230402" The problem I had was that python310-setuptools is not in the requires of ansible-runner. After installing that things work.
There are almost no packages for SLES15 and python3.10 that are required, hence I started to build all of them to see if this works out. :-)
Please don't. I'm not sure if you realized but devel:languages:python:backports provides a python311 stack for SLE15 SP4 and SP5 and we (SUSE) intend to provide that supported on SLE15 going forward. Please leverage that over building your own stack.
I planned to move all of this to systemsmanagement:ansible:SLES15 and child projects, but had no time yet.
No, please don't. Lets work together on this instead.
https://build.opensuse.org/package/show/home:ojkastl_buildservice:Branch_s ystemsmanagement_ansible/ansible-navigator
I installed this on my workstation that is running Tumbleweed with the latest updates from yesterday.
That works as well for me (running in an opensuse container to avoid any local modifications that might make this work for me) Problem: problem with the installed ansible-runner-1.4.7-2.4.noarch Solution 1: install ansible-runner-2.3.2-10.1.noarch from vendor obs:// build.opensuse.org/home:ojkastl_buildservice replacing ansible-runner-1.4.7-2.4.noarch from vendor openSUSE Solution 2: keep obsolete ansible-runner-1.4.7-2.4.noarch Choose from above solutions by number or cancel [1/2/c/d/?] (c): 1 Resolving dependencies... Computing distribution upgrade... The following package is going to be upgraded: ansible-runner The following package is going to change vendor: ansible-runner openSUSE -> obs://build.opensuse.org/ home:ojkastl_buildservice 1 package to upgrade, 1 to change vendor. Overall download size: 131.4 KiB. Already cached: 0 B. After the operation, additional 403.6 KiB will be used. Continue? [y/n/v/...? shows all options] (y): Retrieving: ansible-runner-2.3.2-10.1.noarch (tumbleweed) (1/1), 131.4 KiB Retrieving: ansible-runner-2.3.2-10.1.noarch.rpm ................................................................................................................................................. [done] Checking for file conflicts: ..................................................................................................................................................................... [done] (1/1) Installing: ansible-runner-2.3.2-10.1.noarch ............................................................................................................................................... [done] 7d27fdd42cc7:/ # ansible-runner --version 2.3.2 Greetings, Dirk
Hi Dirk, thanks for taking the time to investigate. On 04.05.23 at 17:32 Dirk Müller wrote:
Am Mittwoch, 3. Mai 2023, 12:13:13 CEST schrieb Johannes Kastl:
File "/usr/lib/python3.10/site-packages/ansible_navigator/cli.py",
Are you using this on tumbleweed? Yes.
Weird, I cannot reproduce this :
7d27fdd42cc7:/ # ansible-runner --version
ansible-runner works. ansible-navigator misses the oslo module.
The problem I had was that python310-setuptools is not in the requires of ansible-runner. After installing that things work.
OK, noted, I'll add that.
Please don't. I'm not sure if you realized but devel:languages:python:backports provides a python311 stack for SLE15 SP4 and SP5 and we (SUSE) intend to provide that supported on SLE15 going forward. Please leverage that over building your own stack.
When I started last year there was no usable stack (or I missed it, backports looked mostly "unresolvable"). Now with the new SLES15-macro being used I already planned to switch to that and use what is already there. What would I need in my project meta to build against that? Because 15.4 looks like Leap in this case, and there is no SLES15SP4 target.
I planned to move all of this to systemsmanagement:ansible:SLES15 and child projects, but had no time yet.
No, please don't. Lets work together on this instead.
Sorry, my statement was unclear. I wanted to make this official by building in systemsmanagement:ansible:SLES15 using the new macros and the existing 3.11 stack.
That works as well for me (running in an opensuse container to avoid any local modifications that might make this work for me)
-- Johannes Kastl Linux Consultant & Trainer Tel.: +49 (0) 151 2372 5802 Mail: kastl@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg http://www.b1-systems.de GF: Ralph Dehner Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
Am Freitag, 5. Mai 2023, 07:00:46 CEST schrieb Johannes Kastl: Hi Johannes,
7d27fdd42cc7:/ # ansible-runner --version ansible-runner works. ansible-navigator misses the oslo module.
It does seem to work here in tumbleweed as well, because primary python is 3.10. The difference with python.oslo* is that it is only buitl for the main python interpreter not for all.
When I started last year there was no usable stack (or I missed it, backports looked mostly "unresolvable"). Now with the new SLES15-macro being used I already planned to switch to that and use what is already there.
Thanks. Feel free to submit the macro into the packages into factory as well, then devel:languages:python:backports will get it automatically. Also I can link ansible into :backports if thats what you're looking for.
What would I need in my project meta to build against that? Because 15.4 looks like Leap in this case, and there is no SLES15SP4 target.
Thats the same, you also have the macro there.
Sorry, my statement was unclear. I wanted to make this official by building in systemsmanagement:ansible:SLES15 using the new macros and the existing 3.11 stack.
If it is submitted to factory, the python modules should get linked to :backports and be building there. Greetings, Dirk
Hi Dirk, On 05.05.23 at 12:54 Dirk Müller wrote:
Am Freitag, 5. Mai 2023, 07:00:46 CEST schrieb Johannes Kastl:
7d27fdd42cc7:/ # ansible-runner --version ansible-runner works. ansible-navigator misses the oslo module.
It does seem to work here in tumbleweed as well, because primary python is 3.10. The difference with python.oslo* is that it is only buitl for the main python interpreter not for all.
Thanks for testing, I'll investigate this further. Did you install any python.oslo packages?
Thanks. Feel free to submit the macro into the packages into factory as well, then devel:languages:python:backports will get it automatically.
Also I can link ansible into :backports if thats what you're looking for.
I have no idea what you mean, but to rephrase: Nothing to do for you, I'll setup builds for SLES15 in systemsmanagement:ansible myself.
What would I need in my project meta to build against that? Because 15.4 looks like Leap in this case, and there is no SLES15SP4 target.
Thats the same, you also have the macro there.
In regards to the macro: Yes. But I had the impression that Leap was a superset of packages of SLE, so building against Leap might mean some packages are missing when using the package on SLES... Hence my question. Have a nice weekend and thanks for the help! Kind Regards, Johannes -- Johannes Kastl Linux Consultant & Trainer Tel.: +49 (0) 151 2372 5802 Mail: kastl@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg http://www.b1-systems.de GF: Ralph Dehner Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
participants (2)
-
Dirk Müller -
Johannes Kastl